10.5 Supervision, Quality Control, and Records
Key Takeaways
- Supervision ensures that staff assignments match competence, project risk, and review requirements.
- Quality control should check field data, computations, mapping, deliverables, and consistency with scope before release.
- Records should be complete enough to reconstruct what was done, by whom, when, with what information, and why decisions were made.
- Good documentation supports continuity, client service, ethical practice, and defense of professional judgment.
Supervision and Records That Make Work Defensible
Surveying firms rely on teams. Field crews, technicians, drafters, analysts, project managers, and licensed professionals may all contribute to one deliverable. Supervision is the process that keeps those contributions aligned with scope, competence, standards, and client needs. The FS exam may ask what a supervisor should do when staff are inexperienced, field notes are incomplete, calculations do not check, or a deliverable is ready for release without review.
A supervisor should assign work based on competence and risk. Routine data collection may be appropriate for trained staff under established procedures. Boundary analysis, professional certifications, unusual construction tolerances, or high-liability deliverables may require closer review. Delegation does not eliminate responsibility for proper direction, review, and documentation.
Quality and Record Controls
| Control | What it checks | Example |
|---|---|---|
| Field note review | Completeness and clarity of observations | Point IDs, setups, sketches, conditions |
| Computation check | Math, closure, units, transformations | Traverse closure, level loop, coordinate inverse |
| Deliverable review | Scope, standards, title, datum, certification | Plat, map, report, digital file |
| Version control | Current plans, revisions, and file history | Construction plan revision used for staking |
| Independent check | Separate verification of critical items | Check stakeout coordinates before field release |
| Record retention | Ability to reconstruct work later | Notes, correspondence, calculations, approvals |
Records include field books or electronic files, raw observations, metadata, instrument information, sketches, photographs, control reports, computations, correspondence, contracts, change authorizations, review comments, deliverables, and transmittals. Good records do not need to be verbose, but they must be understandable. A future reviewer should be able to determine what was measured, what assumptions were used, what decisions were made, and what was delivered.
Electronic records create both opportunities and risks. Data collectors, cloud folders, CAD files, Geographic Information System data, point clouds, and emails can improve traceability when organized. They can also create confusion if filenames, revisions, coordinate systems, and permissions are uncontrolled. A wrong plan revision used for layout can create a serious construction problem even if the staking math was correct for that wrong file.
Quality control should happen before delivery. A final plat should be checked against the scope, record documents, field evidence, dimensions, labels, closure, title block, certification, and client requirements. A construction staking package should be checked against current plans, control, units, coordinate basis, and requested tolerances. The best review is not merely proofreading; it asks whether the deliverable is fit for its intended purpose.
On the FS exam, choose answers that preserve professional accountability. If a junior staff member finds a discrepancy, the supervisor should investigate rather than dismiss it. If field notes are unclear, the team should clarify while the work is fresh. If an error is discovered after delivery, the firm should communicate appropriately and correct the issue according to professional and contractual responsibilities.
What is the main purpose of quality control before releasing a survey deliverable?
Which record practice is most defensible?
A crew used an outdated construction plan revision for stakeout calculations. What type of control might have prevented this?