10.1 Project Planning, Scope, and Work Breakdown
Key Takeaways
- FS Business Concepts questions often test whether the planned work matches the scope, deliverables, schedule, budget, and standard of care.
- A clear scope defines what is included, what is excluded, what assumptions are made, and what deliverables will be provided.
- Work breakdown thinking helps connect field tasks, office computations, review, submittals, and client communication.
- Uncontrolled scope changes can create safety, liability, schedule, and fee problems.
Planning Survey Work Before Measuring Anything
The official FS Business Concepts area includes project planning, resource management, scheduling, cost estimating, safety, liability, contracts, supervision, records, ethics, and communication. Planning is the thread that connects those topics. A surveying project can fail even when the field measurements are technically strong 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, standards or specifications to be followed, deliverables, schedule assumptions, and exclusions. In exam scenarios, watch for language that 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.
Planning Elements
| Element | Purpose | Risk if missing |
|---|---|---|
| Objective | Explains why the survey is needed | Team solves the wrong problem |
| Limits | Defines area, parcels, stations, or features | Field crew collects too much or too little |
| Deliverables | States maps, plats, files, reports, or stakes required | Client expects a different product |
| Assumptions | Identifies access, records, control, weather, or approvals | Schedule and budget become unrealistic |
| Exclusions | Clarifies what is not included | Scope creep and fee disputes increase |
| Change process | Controls added work | Unauthorized effort creates liability and cost issues |
A work breakdown structure turns the scope into manageable tasks. For a boundary survey, tasks may include record research, field reconnaissance, control, evidence recovery, measurements, analysis, drafting, review, and delivery. For construction staking, tasks may include plan intake, control verification, calculations, field layout, cut sheets, as-built checks, and documentation. Each task needs responsible staff, equipment, schedule time, and quality review.
Planning should reflect the nature of the project. A topographic survey needs feature codes, mapping limits, vertical datum, contour interval, utility coordination, and surface deliverables. 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, tolerances, site safety, and communication with contractors.
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 work may seem cooperative, but it can create fee, schedule, and liability problems.
Good planning also includes quality control. Review points should be scheduled before final delivery, not after the client discovers a problem. Field records, computations, map checks, and deliverables should be traceable. Planning is not paperwork for its own sake; it is the structure that makes technical surveying defensible, repeatable, and aligned with client needs.
A client asks for an additional staking task outside the written scope. What is the best first response?
Which item best belongs in a scope of work?
Why is a work breakdown structure useful?