A phased survey delivery schedule should identify each deliverable, the decision it can support, the inputs needed to complete it, and the person who accepts it. For a Washington design team, “survey due” is too vague if the architect expects a review base while the civil engineer expects a complete, checked file. Agree on those separate milestones with the surveyor before adding them to the project schedule.
Separate a field visit from a usable deliverable
Ask the surveyor what will be available at each proposed handoff. A fieldwork date describes an activity. A delivery date should identify a file or drawing, its covered area, its review status and its intended use. If the project needs information in stages, ask whether the assignment can support that sequence and what additional coordination it requires.
The team should not assume that a partial or preliminary release is suitable for a permit submission, construction layout, a transaction or any other use. Have the surveyor identify the release’s limitations and have the receiving professional confirm whether it answers the immediate design question. A planned milestone is useful only when both sides understand the output.
Use a delivery register with named dependencies
The following is a planning template, not a standard Terrane package or a promised delivery sequence. Include only the releases the surveyor agrees are appropriate for the assignment.
| Proposed milestone | Define in the schedule | Confirm before relying on it |
|---|---|---|
| Agreed fieldwork window | Areas to be reached, access contact and any restricted work windows. | Which observations remain outstanding if access or site conditions change. |
| Design-review release, if agreed | Covered area, included features, file format, revision date and intended review task. | Open questions, excluded information and uses the release does not support. |
| Completed survey deliverable | The specified drawing or files and the agreed review or certification requirements. | Which earlier files it supersedes and whether the recipients have the current version. |
Give each missing input an owner
List the records, access permissions, design limits and file requirements on which each release depends. Assign a contact and a needed-by date to each open item. Then ask the surveyor which milestone would be affected if that item arrives late. This makes the consequence visible without assuming that every missing record stops every part of the assignment.
For example, if the civil designer needs an off-site connection that the original scope did not include, identify the additional survey coverage, permission and review needed before assigning it a delivery date. Let the surveyor confirm the revised work and schedule. Do not quietly carry the original date into a larger assignment.
Control the handoff when a file changes
For each release, record the file name, issue date, covered area, intended use, unresolved limitations and recipients. When a revised file arrives, ask the design lead to identify what changed and confirm which earlier files should be retired from active use. Keep the revision record with the project’s drawing and model files.
Finish the kickoff with one agreed delivery register: what is due, who needs it, what it supports and what remains necessary to produce it. Terrane’s survey proposal intake guide helps assemble the starting information. The surveying overview provides the relevant service paths for discussing the proposed releases.
