10.1 Project Planning, Scope, and Work Breakdown

Planning Survey Work Before Measuring Anything

The official NCEES Fundamentals of Surveying (FS) Business Concepts area covers project planning, resource management, scheduling, cost estimating, engineering economics, safety, liability, contracts, supervision, records, ethics, and communication. Planning is the thread that connects all of them. A survey can fail even when the field measurements are technically excellent if the scope is vague, the deliverables are misunderstood, or the schedule ignores approvals and review.

A scope of work should describe the client objective, project limits, tasks to be performed, the standards or specifications to be followed, the deliverables, schedule assumptions, and exclusions. In exam scenarios, watch for language that quietly adds a task without a corresponding authorization. A request to stake additional improvements, prepare a new exhibit, or certify a matter outside the original agreement may require a scope change before work proceeds.

Planning Elements

Work Breakdown Structures Turn Scope Into Tasks

A work breakdown structure (WBS) decomposes the scope into manageable, deliverable-oriented tasks. For a boundary survey, the WBS may include record research, field reconnaissance, control, evidence recovery, measurements, analysis, drafting, professional review, and delivery. For construction staking, it may include plan intake, control verification, calculations, field layout, cut sheets, as-built checks, and documentation. Each task needs a responsible person, equipment, an allotted schedule, and a quality-review point.

The WBS is also the skeleton for estimating: you cannot estimate hours or cost reliably for work you have not broken down.

Planning should reflect the nature of the project. A topographic survey needs feature codes, mapping limits, a vertical datum, a contour interval, utility coordination, and a defined surface deliverable. A right-of-way survey needs record documents, evidence analysis, legal-description requirements, and agency review. A construction layout project needs current plans, revision control, stated tolerances, site safety, and direct communication with the contractor. The WBS exposes dependencies these scopes hide.

Decomposition Checklist

• Each WBS task produces a verifiable output (a note set, a computation, a sheet, a staked line).
• Every task names a responsible role and the competence it requires.
• Review and quality-control tasks appear in the WBS, not as afterthoughts.
• Hand-offs between field and office are explicit so nothing falls between crews.

Change Control and Quality Built Into the Plan

The FS exam may ask what a supervisor should do when a project condition changes. The best answer usually protects clarity and professional responsibility: document the condition, communicate with the appropriate party, evaluate scope and safety impacts, and obtain authorization before performing materially different work. Quietly absorbing extra effort may feel cooperative, but it creates fee, schedule, and liability exposure and weakens any later business or professional defense.

Good planning also schedules quality control (QC) before delivery, not after the client finds a problem. Field notes, computations, map checks, and deliverables should be traceable so a future reviewer can reconstruct what was done and why. Planning is not paperwork for its own sake; it is the structure that makes technical surveying defensible, repeatable, and aligned with the client's actual need. A typical engineering-economic frame even enters here: the cost of an extra review hour is almost always smaller than the cost of a re-survey, a delayed closing, or a claim. Planning is the cheapest insurance a surveying firm buys.

Why Scope Creep Is Dangerous

Scope creep, the gradual unauthorized expansion of work, is dangerous for four linked reasons: fee erosion (uncompensated tasks consume profit), schedule slip (added work pushes the critical path into missed deadlines), liability (certifying work outside the authorized scope invites claims), and standard-of-care drift (rushed additions skip the review that makes work defensible). The remedy is one loop, recognize the change, document it, communicate, and obtain written authorization before doing materially different work.

Connecting Planning to the Other Business Topics

Project planning is the hub that the rest of the Business Concepts area spins around, and the FS exam tends to test it that way rather than in isolation. Scope and the work breakdown structure come first, because you cannot estimate hours, assign crews, or build a Critical Path Method network for tasks you have not yet identified.

Planning then drives cost estimating and fees: the business entity must authorize and price the work against that defined scope. Planning also drives safety: a roadway topographic survey plan should budget traffic control, and a deep-monument plan should budget utility locates through 811. Planning feeds quality control and names who reviews each deliverable. Finally, planning underlies the contract and communications — the assumptions, exclusions, and change process that keep the client, crew, and reviewer aligned.

A practical planning habit is to write the plan from the deliverable backward. Ask what the client will actually rely on, then list every task, record, control point, and review needed to produce it to the stated standard. Working backward exposes hidden dependencies (a plat needs prior record research; a stakeout needs verified control) and prevents the common failure of planning only the visible field day while ignoring the office work that consumes most of the budget.