What you will learn
- What staking covers on a construction site, and what it does not
- How layout points move from design files to the field
- How revision control stops crews staking from an outdated drawing
- How field checks and as-built records close the loop
- The errors that cause rework, and how the software prevents them
What the project is
Staking, also called setting out, transfers design coordinates to physical marks on site. The surveyor stakes building corners, grid lines, road centrelines, kerb lines, and utility alignments, and the builder works from those marks. When a mark is wrong or outdated, concrete and steel follow the error, so accuracy and revision control are the whole job.
The software manages the point list, the design revisions behind it, the field checks, and the as-built record. It does not replace the instrument or the surveyor's verification; it makes sure the right points, from the right revision, are staked and recorded.
Core features
Point list management is the core: import design points, organise them by structure and stage, and track each point as pending, staked, checked, or revised. Revision control is what makes the system trustworthy: when a design revision arrives, affected points are flagged and the crew sees the change before staking, not after. As-built capture records what was actually built, with measured coordinates and notes, for comparison against design.
- Design point import organised by structure, stage, and revision
- Revision flags that mark affected points when a design changes
- Field staking lists with point status: pending, staked, checked, revised
- As-built capture with measured coordinates and variance notes
- Daily staking reports for the builder and the project record
- Photo attachment for marks, control, and site conditions
How it is built
Start with the point list and revision control, because those two carry the risk. Field capture and as-built reporting follow, then builder-facing reports. Testing should happen on a live site with a real revision change, because that is the moment the system either earns trust or loses it.
- Define the point model: design coordinates, revision, structure, and stage.
- Build import from design files with revision tracking.
- Build field staking lists with status tracking and offline support.
- Add as-built capture and variance reporting against design.
- Add builder reports and the daily record, tested on a live site.
Technology considerations
Coordinate handling is critical: design files arrive in project coordinates, field instruments work in site control, and any transformation between them must be explicit, recorded, and reversible. A silent coordinate shift is the most expensive bug this software can have.
Offline support matters on large sites and in basements where signal fails. The staking list must work offline, and the sync must preserve the record of what was staked from which revision, even when the device reconnects hours later.
Challenges to plan for
Design revisions are the chronic challenge. A revision issued on Friday and staked from the old drawing on Monday is a familiar and costly failure, and the software must make the current revision unmistakable in the field. A second challenge is control: if site control moves or is disturbed, every point staked from it is suspect until control is rechecked.
- Crews staking from superseded drawings or point lists
- Disturbed site control that invalidates recent staking
- As-built variances found late, after the next trade has built over them
- Point lists that grow unmanageable on large multi-stage sites
Who it is for, and its limits
This software fits survey firms doing construction layout, engineering firms with survey teams, and large contractors that run in-house setting-out crews. It is most valuable on multi-stage sites where revisions are frequent.
It does not design the building and it does not certify construction. The surveyor's checks and the builder's own quality control remain separate responsibilities, and the as-built record supports, but does not replace, those checks. Costs and timelines vary with design-format support and site scale, so confirm with a quote before budgeting.
Frequently asked questions
What is construction staking?
It is marking design positions on the ground, such as building corners, grid lines, and road alignments, so builders can work from physical marks rather than from drawings alone.
Why does revision control matter so much?
Because designs change during construction. If a crew stakes from a superseded revision, the builder follows the wrong marks, and the rework can be extensive. The software must flag affected points when a revision arrives.
What is an as-built record?
A record of what was actually built, measured after construction, compared against design. Variances are noted, so the project team knows where the built work differs from the design.
Does the software replace field instruments?
No. Instruments measure and set out points; the software manages the point list, revisions, checks, and records around that work.
What happens if site control is disturbed?
Staking from that control becomes suspect until control is rechecked. The software should let the surveyor flag affected points and record the recheck.