Construction - managing a provisional sum instruction
8 steps. Instruction received to final account protected.
Step by step
- Receive Written InstructionJobs
Log the written instruction against the job record with date received, instructed scope, and contract administrator's name.
- Compare Allowance to ScopeJobs
Review the contract bills allowance against the confirmed scope. Flag material differences to the contract administrator before committing costs.
- Issue RFQsRFQs
Issue RFQs for specialist supply or subcontract input, including confirmed scope, programme constraints, and site requirements.
- Raise Purchase OrdersPurchase Orders
Select suppliers and raise purchase orders against the job record to create final account evidence.
- Update Cost PlanJobs
Revise the job cost plan to reflect actual instructed cost vs provisional sum allowance. Document any programme impact.
- Issue Cost NotificationInvoices
Notify the contract administrator in writing of any cost adjustment, with supporting documentation.
- Execute Work and Record CostsDelivery Notes
Record labour, materials, and subcontractor costs against the job. Confirm goods receipt against purchase orders.
- Include in Interim ValuationInvoices
Include the provisional sum adjustment in the next payment application with full supporting documentation.
What this workflow solves
- Provisional sum work is started before a written instruction is issued, making the costs difficult to validate in the final account.
- The actual cost of instructed work exceeds the provisional sum allowance but no cost notification is issued, leading to disputes over the contract sum adjustment.
- Purchase orders raised against provisional sum instructions are not linked to the specific instruction, creating incomplete evidence at final account stage.
Frequently asked questions
See it live
Want to see this workflow in Zigaflow?
Book a demo and we'll run through your exact process live.
Book a free demoBuild your own workflow