Scope changes
and procurement
Changed requirements and approvals can affect tendering, commercial terms, supply and resource mobilisation.
Infrastructure & EPC
Scope, procurement, budgets and site commitments are connected—from project definition through commissioning and operating handover.
Capital and transport infrastructure projects.
Discuss your projectA scope change reaches
beyond the drawing.
Requirements and approvals shape tendering, sourcing, commercial commitments, mobilisation, construction and installation. A change in scope can affect budgets, resources and the programme. Decisions are distributed across offices, vendors and sites.
Discuss your project
Decisions influence cost
and resourcing
Approvals enable procurement
and site activity
Scope changes
Budgets and approvals
Budget and resource commitments need to be read alongside the decisions and approvals they depend on.
Site activity and readiness
Coordination on site depends on procurement, packages, resources and site readiness.
A broader perspectivePhysical progress is only
Physical progress is only
part of the picture.
Understanding what’s built on site is essential, but it gives an incomplete view. The next section looks at the evidence and responsibilities needed for operating readiness.
Explore what’s next
Physical progress does not by itself establish readiness for operation.
As projects near completion, three questions need to be considered together—acceptance, operability and handover. They are concurrent considerations, not mandatory stages.
01
Can the work be accepted?
Review acceptance criteria, test status and unresolved actions alongside completed work.
- Acceptance criteria
- Test status
- Unresolved actions
02
Can it be operated?
Operating documents, instructions and training carry knowledge into use, with open actions visible.
- Operating documents
- Instructions
- Training
- Open actions
03
Who receives the work and carries responsibilities forward?
Connect accepted systems, receiving-team sign-off, transfer of records and responsibilities, with clear receiving owners and remaining actions.
- Accepted systems
- Receiving-team sign-off
- Transfer of records and responsibilities
- Receiving owners and remaining actions
Three questions. One complete picture.
Bring acceptance, operability and handover into view together.
The information
that connects delivery.
Useful records connect project activity to decisions. Five connected work areas retain their focus and dependencies, so the right information reaches the right people at the right time.
Focused work. Connected decisions.
Each work area has a clear purpose, supported by the right information and dependent on decisions from the others.
Each work area has a different focus and depends on decisions from the others.
01
Scope & design
Define requirements and align the programme.
Scope, approvals and acceptance criteria. Depends on business case and stakeholder decisions.
02
Procurement
Tender, evaluate and agree commercial commitments.
Supply strategy, terms and vendor readiness. Depends on approved requirements and funding.
03
Site activity
Coordinate packages, resources and delivery actions.
Programme delivery, risk and change. Depends on procurement and site readiness.
04
Commissioning
Test, resolve actions and demonstrate acceptance.
Systems integration and operating documents. Depends on completed work and acceptance evidence.
05
Handover
Transfer records and responsibilities into operation.
Instructions, training and open actions. Depends on accepted systems and receiving-team sign-off.
Supporting informationRecords that connect
Records that connect
the detail to the decision.
Project information takes many forms. When it’s structured and connected, it enables clear oversight and accountability across the five work areas. Contractor compliance, site records, audits and corrective actions connect with workforce and risk responsibilities.
Useful project records connect delivery actions with decisions. Contractor compliance, site records, audits and corrective actions connect with workforce and risk responsibilities.
- Project formats and gates
- Tender and negotiation records
- Vendor follow-up and readiness
- Forecasts and budgetary control
- Contractor compliance, site records, audits and corrective actions
- Reporting and approval paths
From project decisions
to practical progress.
Project and implementation support can connect decisions, evidence and actions within an agreed scope.
SPPArC’s proposed role is project and implementation support within agreed scope. Engineering and construction responsibilities remain with the appointed parties.
SPPArC’s proposed role is project and implementation support within agreed scope. Engineering and construction responsibilities remain with the appointed parties.
Illustrative outputs
Possible outputs, shaped to the agreed scope. These examples are illustrative, not promised deliverables.
Programme-control framework
Connects scope, actions, gates and owners.
Procurement decision record
Retains commercial and vendor evidence.
Budget and resource view
Connects utilisation and exceptions to decisions.
Commissioning and handover plan
Defines readiness, acceptance and transfer.
What’s your next
question?
Every project brings a different question into focus. Choose the area that best matches what you want to explore next, or browse related industries.
Discuss the project decision that needs attention.
Share the project stage, the evidence available and the approval, package or handover question you need to resolve.
- Packages
- Sites
- Schedules
- Budgets
- Approval constraints
- Target handover
Helpful context, not prerequisites. Begin with the question you have.