For public works surveying teams

Survey request tracking for public works — every staking request on the map.

Survey requests on public works projects are field-generated. A foreman identifies where stakes or grade verification are needed and submits the request so the survey crew can schedule the work. Tracking those requests by location shows what is waiting, what has been staked, and where the survey crew is working next.

What you track on the survey map

• Staking requests — Pin each staking request to the station or structure where the survey crew needs to work. Track request date, type of staking, priority, and completion status. Open requests stay visible until the crew closes them.
• Grade verification — Log grade check requests at the specific location where tolerance needs to be confirmed — a subgrade section, a finished surface, a concrete pour. Attach the measured readings and close the pin when the grade is confirmed.
• Utility locates — Track utility locate requests at the conflict point on the map. Attach the locate marks, potholing results, and any changes to the design alignment. The PM and the excavation crew see the same information.
• As-built documentation — Close staking pins with as-built shots attached — photos of the hub, grade rod readings, GPS coordinates. The as-built record is location-indexed and available for the project file without any separate filing step.
• Survey crew scheduling — The survey crew views all open requests on the map, groups work by location, and plans routes to avoid unnecessary travel across the project. Priority and due date flags highlight urgent items.

Why a map makes survey coordination faster

Survey requests that live in a spreadsheet or email thread have no location context. The survey crew cannot see that two requests at opposite ends of the project are scheduled back-to-back, or that three requests near Station 48 could all be done in one trip. A map makes the geography obvious and the scheduling decisions faster.