Joint scope meetings

Where the meeting belongs

Use the job order lifecycle to place the meeting after the facility need has been identified and before the written scope and contractor proposal are finalized. The practical sequence is need, joint scope meeting, scope of work, proposal, owner review, issued order, work and closeout. The meeting develops information for those later steps; it is not itself an authorization to start work.

State the need before inviting participants. Name the affected area, the problem to address and the result the owner wants. If the need is only “repair the building,” identify the locations and tasks that require discussion before treating it as a complete work package.

Assign someone to record observations and decisions. Identify who can settle the scope and who can answer access or facility-use questions. Bring relevant trades when their field input is needed to describe a task, rather than leaving their questions until proposal review.

See the full job order lifecycle

What the owner should bring

Bring the work description, available drawings, relevant requirements and existing site records. Identify which documents are current and which details need checking in the field. An old drawing can prompt a useful question without being treated as a confirmed description of present conditions.

Arrange access to the affected locations and identify the facility representative who can explain how the spaces are used. Prepare questions about staging, entry routes, areas to remain available and the proposed work window. Give participants enough site information to distinguish a task question from an access problem.

Decide who will confirm the intended result, inclusions and exclusions. If a decision-maker cannot attend, identify how the unresolved question will reach that person. Do not allow an unanswered finish, boundary or scheduling question to become an unstated estimating assumption.

• Need and result: identify what is to change and why it is in the proposed scope.
• Site records: bring relevant drawings, photographs and requirements.
• Access: arrange entry and a contact who can answer facility questions.
• Constraints: identify occupied areas, work windows and coordination questions.
• Decisions: name the person responsible for each unresolved scope issue.

What the contractor should bring

Bring field questions based on the proposed work description. Identify dimensions, material details or task boundaries needed for estimating. Prepare to record measurements with units and location labels rather than relying on a recollection of the walk.

Use constructability notes to identify questions that affect how the intended work is described. Ask about access to the task, adjacent work to retain and coordination between trades. Separate a confirmed observation from a proposed solution that still needs the owner’s decision.

Photograph location views and useful details under the facility’s photography rules. Label each image with the location and task it supports. Attach measurement notes to the quantity takeoff so a proposal reviewer can follow the calculation without repeating the meeting.

Topics to settle during the walk

Walk the affected locations together and establish the physical limits of the work. Discuss existing conditions, the intended tasks and adjacent areas that are excluded. If the work is to be phased, identify which areas or tasks belong to each proposed phase and which decisions remain open.^[2][3]

Record proposed working hours explicitly. Solicitations may distinguish normal from other than normal working hours, and work outside normal hours is generally expected to carry a higher coefficient. Compare the proposed hours with the actual category definitions rather than assigning a factor from a phrase such as “holiday work.”

Flag tasks that may not be represented in the price book. Non-prepriced items are work outside the book and generally carry a coefficient above 1.00. A field concern is a question to investigate, not proof that a suitable entry is absent; check the book and its descriptions before deciding on the treatment.

Turn the meeting into a written scope

A price-book proposal calculates each selected line amount from unit price, quantity and contractor coefficient. The meeting notes should supply the task definition and measurement support needed for that selection. Keep access and scheduling decisions beside the physical work description.^[1][4]

Write the scope with consistent location names, explicit boundaries and the decisions made on site. Avoid “as discussed” where the reader needs an actual task or limit. Attach labeled photographs and takeoff notes, then identify pending questions and the person responsible for each answer.

Before proposal review, confirm that the scope and proposal refer to the same work. Because negotiation is mostly about entries and quantities, a changed boundary must be visible in both the description and pricing. Record revisions together so a meeting decision cannot disappear into a changed total.

Turn site observations into a clear scope of work