Define the Scope of a Residential Construction Project

A. Finished-Project Specification

Deliverable: one approved residential project scope statement, containing measurable objectives, the completed physical outcome, mandatory authority conditions, a complete deliverable list, defined inclusions and exclusions, a stakeholder list, a responsibility matrix, documented assumptions and constraints, and a defined change-approval process, reconciled against the estimate and permit plan and approved by the authorized party.

B. Scope Statement Document Schedule

Section	Content	Source	Purpose
Project identification	Address, property boundaries, project type, delivery method, intended use	Owner request, agreement, permit application	Establishes the project the scope statement governs
Objectives	Business and owner objectives stated in measurable terms	Owner request, agreement	Defines what success means for the project
Completed physical outcome	Outcome by area, system, room, structure, and trade	Drawings, specifications	Defines the physical result the owner will accept
Authority conditions	Mandatory permit, code, design, lender, insurer, utility, HOA conditions	Permits, agreement, authority requirements	Identifies conditions that must be satisfied regardless of contractor preference
Deliverables	Every item required for owner acceptance, including temporary work and closeout items	Agreement, drawings, specifications	Defines the complete list the owner will check against at handoff
Inclusions / exclusions	Included design, procurement, installation responsibilities; explicit exclusions; deferred work; allowances; alternates	Agreement, estimate, owner selections	Bounds the contractor's responsibility in plain language
Stakeholders	Name or role, organization, interest, authority, contact method	Agreement, project directory	Identifies who must be consulted, informed, or asked to approve
Responsibility matrix	Owner, contractor, subcontractors, suppliers, designer, inspectors, utilities, other parties	Agreement, permit plan	Prevents two parties from each assuming the other owns a task
Assumptions / constraints	Dimensions, access, hours, utilities, occupancy, weather, soil, structure, budget, schedule, neighborhood	Field observation, agreement, owner input	Records conditions the scope statement depends on rather than burying them in notes
Quality and acceptance	Quality and performance requirements; milestone and completion conditions without unsupported dates	Drawings, specifications, samples, manufacturer instructions	Defines how the owner and contractor will recognize the work as complete
Change process	Process for RFIs, substitutions, hidden conditions, owner requests, delays, change orders	Agreement, company policy	Defines how the baseline may be modified after approval

C. Information and Document Takeoff

• Source records: owner request, executed agreement or proposal, approved estimate, drawings, specifications, addenda, permits, and prior correspondence, sufficient to draft every section of the document schedule above without inventing missing information.
• Comparison records: the Book 24 estimate and the Book 25 permit-and-inspection plan, used in Steps 26–27 to identify priced items, unpriced items, gaps, duplications, regulated work, and permit-holder responsibilities.
• Approval record: written confirmation of the person or role authorized to approve scope, cost, schedule, design, and final acceptance, obtained before drafting begins.
• Revision control: a baseline numbering and archive convention sufficient to distinguish the current approved scope statement from every superseded draft.

D. Acceptance Standards

Check	Standard
Objectives	Stated in measurable terms; not merely a general aspiration
Deliverables	Every item required for owner acceptance is listed individually, not implied
Exclusions	Stated in language understandable without trade assumptions; distinguished from deferred work, allowances, and alternates
Stakeholders and authority	Every stakeholder identified with role, organization, and contact method; decision authority explicitly named for scope, cost, schedule, design, and acceptance
Assumptions and constraints	Recorded as a managed log, not embedded only in narrative text
Reconciliation	Scope compared against the estimate and permit plan; gaps and duplications identified and resolved before approval
Approval	Written approval obtained from the authorized party; baseline number and date assigned before distribution

E. Preparation — Collect Documents and Identify Project Basics

1. Collect the owner request, executed agreement or proposal, approved estimate, drawings, specifications, addenda, permits, clarifications, selections, and prior correspondence. Assemble every available document before drafting begins.
2. Identify the project address, property boundaries, occupied conditions, project type, delivery method, and intended use. Record these facts from the agreement and permit application.
3. Define the business and owner objectives in measurable terms. State the objective in terms that can later be checked as met or not met.
4. Define the completed physical outcome by area, system, room, structure, and trade. Draw the outcome directly from the approved drawings and specifications.
5. Identify mandatory permit, code, design, lender, insurer, utility, HOA, and authority conditions. Record each condition and the document or authority that establishes it.
6. List every primary deliverable required for the owner to accept the work. Include each deliverable individually rather than as a general category.

F. Objectives, Deliverables, and Authority Conditions

7. List temporary work, protection, access, utilities, storage, sanitation, security, and cleanup needed to deliver the project. Record these as deliverables even though they are not part of the permanent finished work.
8. Identify demolition, salvage, disposal, testing, inspection, commissioning, training, warranty, and closeout deliverables. Record each as an individual item on the deliverable list.
9. Define included design, engineering, surveying, selections, submittals, mockups, samples, and shop-drawing responsibilities. State which party is responsible for each.
10. Define included procurement, delivery, unloading, staging, installation, startup, and warranty responsibilities. State which party is responsible for each.
11. Identify owner-furnished, contractor-installed and owner-furnished, owner-installed items. List each item and its furnishing and installation responsibility separately.
12. Identify work by utility, municipality, separate contractor, landlord, tenant, HOA, designer, or other third party. Record the party and the work they are responsible for.
13. Define explicit exclusions in language that can be understood without trade assumptions. State each exclusion as a specific item, not a general category.
14. Distinguish excluded work from deferred work, alternates, allowances, and future phases. Label each item with its correct category rather than leaving it ambiguous.
15. Identify stakeholders by name or role, organization, interest, authority, contact method, and required communication. Build the stakeholder list from the agreement and project directory.
16. Identify the person authorized to approve scope, cost, schedule, design, and final acceptance. Confirm this authority in writing before proceeding.
17. Create a responsibility matrix for owner, contractor, subcontractors, suppliers, designer, inspectors, utilities, and other parties. Assign one primary responsible party to each category of work.

G. Exclusions, Assumptions, and Constraints

18. Document existing-condition information and conditions that remain concealed or unverified. State clearly which existing conditions have not been confirmed by direct observation.
19. Document assumptions concerning dimensions, access, working hours, utilities, occupancy, weather, soil, structure, and existing systems. Record each assumption individually in the assumptions log.
20. Document constraints concerning permits, budget, financing, schedule, neighborhood, storage, noise, dust, parking, and seasonal work. Record each constraint individually in the constraints log.
21. Define quality and performance requirements using approved documents, samples, manufacturer instructions, and acceptance criteria. Cite the controlling document for each requirement rather than describing it generally.
22. Define milestone and completion conditions without assigning unsupported dates. State the condition that defines each milestone; leave date assignment to the Project 04 schedule.
23. Define how owner selections and allowance decisions will be made and by what deadlines. Record the decision process and the consequence of a missed deadline.
24. Define the process for RFIs, substitutions, hidden conditions, owner requests, delays, and change orders. Reference the change-control process established for the project.
25. Define which work may not begin until approval, permit, inspection, selection, or payment condition is satisfied. List each hold condition and the work it affects.

H. Draft, Reconcile, and Approve the Scope Statement

26. Compare the scope against the Book 24 estimate and identify priced items, unpriced items, gaps, and duplicated items. Record every discrepancy found.
27. Compare the scope against the Book 25 permit plan and identify regulated work and permit-holder responsibilities. Confirm each regulated item is assigned to the correct responsible party.
28. Create a scope-gap and ambiguity list. Record every unresolved item discovered during Steps 26–27 in the scope-gap log.
29. Resolve gaps through written clarification, approved assumption, allowance, alternate, exclusion, or contract revision. Do not leave a gap-log item unresolved when the draft is submitted for review.
30. Prepare the draft scope statement in logical project sequence. Follow the document schedule in Section B.
31. Review the draft with the owner, project manager, estimator, field lead, designer, and key trades as applicable. Distribute the draft far enough in advance for informed review.
32. Record comments and revise the statement without deleting unresolved risk. Preserve a record of every comment received and how it was addressed.
33. Obtain approval from the authorized parties. Confirm the approval is from the person or role identified in Step 16.
34. Assign the scope baseline number and date. Record both directly on the scope-approval record.
35. Distribute the approved scope and archive the superseded drafts. Move superseded drafts to the archive location so they cannot be mistaken for the current baseline.
36. Create a change-control rule preventing informal expansion of the approved baseline. State the rule in the scope statement itself and confirm it matches the process defined in Step 24.