10.5 Supervision, Quality Control, and Records

Responsible Charge and Supervision

Surveying firms rely on teams, field crews, technicians, drafters, analysts, project managers, and licensed professionals all contribute to one deliverable. Supervision keeps those contributions aligned with scope, competence, standards, and client needs. A key licensure concept is responsible charge (also called direct supervision): the Professional Land Surveyor (PLS) who signs and seals a document must have exercised direct control and personal professional supervision over the work. The NCEES Model Rules require that a licensee seal only work performed by the licensee or under the licensee's responsible charge.

A supervisor assigns work by competence and risk. Routine data collection may suit trained staff under established procedures. Boundary analysis, professional certifications, unusual construction tolerances, or high-liability deliverables demand closer review. Delegation does not eliminate responsibility, the licensee remains accountable for proper direction, review, and documentation of subordinate work.

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; the responsible answer preserves accountability and verification.

Quality Control Before Release

Quality control (QC) happens before delivery, not after the client finds a problem. A final plat is checked against the scope, record documents, field evidence, dimensions, labels, mathematical closure, title block, certification, and client requirements. A construction-staking package is checked against the current plans, control, units, coordinate basis, and requested tolerances. The best review is not proofreading; it asks whether the deliverable is fit for its intended purpose.

Quality and Record Controls

An independent check of critical quantities, a second person re-computing stakeout coordinates from the plans, catches errors that a self-check often misses, and it costs far less than a wrong layout poured into concrete.

Records and Version Control

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 need not 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 opportunity and risk. Data collectors, cloud folders, CAD files, GIS data, point clouds, and emails improve traceability when organized, but cause confusion if filenames, revisions, coordinate systems, and permissions are uncontrolled. A wrong plan revision used for layout can cause a serious construction error even when the staking math was correct for that wrong file, which is exactly why version control is a named QC control.

On the FS exam, choose answers that preserve professional accountability: investigate a discrepancy a junior staff member raises rather than dismiss it, clarify unclear notes while the work is fresh, and, if an error is found after delivery, communicate appropriately and correct it per professional and contractual duties.

Sealing, Retention, and the Public Record

When the licensed surveyor signs and seals a plat, map, or report, the seal certifies that the work was performed by the surveyor or under the surveyor's responsible charge and meets the applicable standard of care. The NCEES Model Rules prohibit sealing work the licensee did not control, and prohibit sealing in a field outside the licensee's competence. The seal is therefore both a professional representation and a legal one; recorded surveys become part of the public record that future surveyors, owners, and courts rely on, which is why the integrity and traceability of the underlying records matter so much.

Record retention supports that reliance over time. Boundary monuments, recorded plats, and the field evidence behind them may be revisited decades later. Many state board rules set minimum retention periods for project records, and good practice is to retain field notes, observations, computations, and correspondence long enough to defend the work and to support resurveys. Organized retention also enables continuity: if a project manager leaves or a client returns years later, the firm can reconstruct what was measured, what assumptions governed, and what was delivered.

A Practical Pre-Release Review Sequence

1. Scope check, does the deliverable match what the contract authorized and the client requested?
2. Technical check, do closures, units, datum, and coordinate basis verify, ideally by an independent reviewer?
3. Standards check, does it meet the cited accuracy class or specification?
4. Certification check, are the title block, date, surveyor's name, and seal correct and supportable?
5. Record check, are the supporting notes, computations, and approvals filed and traceable?

Following a fixed sequence keeps QC from depending on memory and makes it repeatable across staff and projects, the same reliability principle that underlies version control and supervision.