The JOC task order lifecycle from request to closeout
Each task order needs a clear path from an identified facility need to an accepted, documented result. Use this owner-side sequence as a framework, then follow the details of your contract.
Updated October 2026
General information only. Not legal or procurement advice. Check your own procurement rules, statutes, and contract documents.
Begin with a work request and need statement
Describe the problem the owner needs to solve, the affected facility, and the desired outcome. Separate what is known from what still needs investigation. A request such as 'repair the damaged area' needs location, observed conditions, operational concerns, and enough context for a meaningful discussion. The initial request is not yet the full construction scope.
Confirm that the proposed work appears eligible under the JOC contract and identify the staff responsible for scoping and approvals. Note funding considerations and important occupancy constraints early. Use the task order checklist to surface questions before the contractor prepares a price, not only when the proposal is ready to sign.
Task order checklistWalk the site together
A joint scope meeting or site walk lets the owner and contractor discuss field conditions and the intended result. Include the people who can explain access, existing systems, building use, and maintenance concerns. Record measurements and observations that will affect the work. Identify conditions that require further investigation instead of treating assumptions as facts.
Discuss work hours, security, occupied areas, shutdowns, staging, waste removal, and any restrictions on noise or access. If end users or maintenance staff must confirm a condition, assign that follow-up. A useful site walk produces a common understanding and a list of unresolved questions, not simply an agreement to 'send a proposal.'
Turn the discussion into a written scope
Document the work to be performed, including locations, quantities or measurement bases, required results, and relevant standards identified in the contract or project documents. State inclusions and exclusions plainly. Identify site constraints, owner responsibilities, and any design information or approvals needed before work can proceed.
Resolve scope questions before comparing prices. If a condition remains unknown, document the agreed approach under the contract rather than leaving an unspoken allowance. Keep the written scope connected to the site-walk record so the proposal can be reviewed against what both sides actually discussed. The task order checklist helps organize these decisions.
Task order checklistReceive a detailed contractor proposal
The contractor translates the scope into unit price book tasks, quantities, and the applicable coefficient. The proposal should provide enough detail for an owner reviewer to understand the selection and calculation of each line. Use the contract's required format and supporting documents. A lump total without the required breakdown is not a substitute for a reviewable proposal.
Non-prepriced items should be identified separately with the pricing method and documentation the contract requires. Check how adjustments or other permitted components are shown. The coefficient explainer can help staff understand a simple book-price calculation, but the actual proposal must follow the executed agreement, including its treatment of non-prepriced work.
Coefficient explainerReview scope, quantities, price-book mapping, and schedule
Compare the proposal with the written scope and field conditions. Check that task descriptions cover the proposed work, quantities use the correct units, and line items do not duplicate work already included elsewhere. Verify the book edition and applicable coefficient. Ask for clarification when a reviewer cannot trace a line back to the required work.
Review the schedule with building occupants and the people responsible for access and shutdowns. Confirm permits, material lead times, inspection points, and owner-furnished items. Record revisions and keep the final agreed scope and proposal together. Before approval, work through the task order checklist so pricing decisions are not separated from funding, authority, and delivery constraints.
Task order checklistFollow construction and document changes
During construction, designated owner staff coordinate access, monitor progress, and arrange the required inspections. Keep a record of significant decisions and observed conditions. Compare delivery with the authorized scope and schedule. Raise issues promptly through the agreed contacts rather than waiting until acceptance to resolve them.
When a change is needed, document the reason, revised scope, pricing, schedule effect, and required approval under the contract. Field conversations do not replace the change process. Keep change records connected to the original order so the final cost and scope can be understood without reconstructing scattered messages later.
Accept the work and close the record
Walk the completed work, record punch list items, and confirm they are resolved through the required process. Acceptance should reflect the actual contract requirements, not only that the space is usable. Collect the specified closeout documents, which may include warranties, operating information, inspection records, permit closeout, and record drawings where required.
Complete payment and acceptance steps under the agency's procedures. Retain the request, scope, proposals, price-book references, review notes, approvals, changes, and closeout documents in one place per order. Use your agency's retention rules. The task order checklist can support the closeout discussion, but the contract determines the deliverables and the official record.
Task order checklistCommon questions
What is the difference between a work request and a written scope?
The request explains the need. The written scope defines the work, inclusions, exclusions, site constraints, and responsibilities used to prepare and review the proposal.
Should the owner review quantities even when a price book is used?
Yes. A price book establishes unit prices, but the owner still needs to check task selection, quantities, units of measure, and consistency with field conditions.
When can the contractor start work?
Work should begin only after the authorization and start conditions required by the contract and the agency's process are satisfied. A draft proposal or site walk is not that authorization.
How are changes handled after an order is issued?
Follow the contract's change procedure. Document the reason, revised scope, price, schedule effects, and required approvals, and retain the record with the order.
Which closeout documents should be retained?
Retain the deliverables required by the contract and your agency's policies, together with scope, pricing, approvals, changes, inspections, and acceptance records. Requirements vary by project and program.