
Method · The asset lifecycle
Asset lifecycle method
How an organisation governs a physical asset from the need for it through operation, renewal or disposal: what happens, in what order, who acts in what capacity, what goes in and comes out, what is accepted, and what returns to the next investment decision.
The sequence
It documents the decisions, requirements, evidence, interfaces and acceptance conditions through which procurement and design preserve, or lose, the sanctioned outcome and the asset’s future operating needs. It does not prescribe procurement practice or engineering design.
Neither method is a standard, a law, a certification scheme or a procedure every organisation must follow, and neither is legal advice, procurement guidance or design instruction. Where an external instrument requires something, the method names the instrument, the clause and whom it binds; everything else is this publication’s analysis or the organisation’s own decision, and is marked as such.
Four stages, the three seams between them, and the return loop from operation to the next investment decision. Steps are listed in dependency order: each comes after the steps it depends on. Some steps may occur in either order, overlap or coincide; those steps state the permitted timing.
How to read it
Every statement
carries one basis
Every statement carries one basis, and the page marks which.
The method itself belongs to no jurisdiction. A statement about a national instrument names the instrument and the government or function it binds, and binds nobody else. The Saudi statements identify the text read and the government or function it binds.
Required
An external instrument requires it. The citation gives the document and the clause, and a label says whom the instrument binds.
Projects Advisors analysis
This publication’s own reasoning. Marked where a step first relies on it; a statement in that step with no citation is analysis too.
Your organisation decides
The organisation’s own choice: a delegation, a threshold, a classification. The method names the decision and does not make it.
Outside this method
Deliberately not covered, with the reason, where a reader would otherwise expect it.

Stage 01 · 5 steps
Inception & Development
The decisions taken before anything is built. And the operating consequences they quietly fix in place.
The steps, in dependency order
Step 1 of 5: Need and outcomeState the outcome the asset is meant to produce, separately from any description of the asset, so that every later decision can be tested against it.
Stage 01 · step 01 of 05
- Located in
- Stage 01 · Inception & Development
- Follows
- The first step
- Releases to
- Options and business case
What governs it
ISO/TC 251 describes ISO 55001:2024 as requiring a strategic asset management plan, in new subclause 6.2.1, which it presents as the means of aligning asset management with the organisation’s objectives, and as making clearer in 6.2.2 and 6.2.3 that asset management objectives have to be resourced and planned for, not only listed. required
Binding only where it is adopted or contracted
ISO/TC 251, Updated Guidance on Asset Management System Requirements, ISO 55001:2024, p. 2, 6.2.1; ISO/TC 251 Asset management, ISO 55001 project page, 6.2.1, 6.2.2 and 6.2.3; ISO/TC 251, ISO 55001:2024 update overview (presentation hosted by the Institute of Asset Management), slide 22, 6.2
The outcome statement is where an investment takes up that line of sight: objectives carried from the organisation’s objectives through the strategic asset management plan into a basis against which each planning and investment decision can be tested. analysis
Reasoned from ISO/TC 251, ISO 55001:2024 update overview (presentation hosted by the Institute of Asset Management), slide 19, 4.5
- Entry condition
A need has been raised through whatever channel the organisation uses to start investment. your organisation decides
- Inputs
Organisational objectives, the problem the need responds to, and evidence returned from earlier investments of the same kind.
- Activities
Write the outcome in terms that can be measured after handover, and name the role that will own it once the delivery organisation disbands.
- Outputs
An outcome statement with a named owner, a measure, and the objective it traces to.
- Evidence
The dated outcome statement, kept so that later drift from it can be seen and explained.
- Decisions
Proceed to options, reframe the need, or stop.
- Exceptions
Where no measurable outcome can be stated, the gap is recorded and the case proceeds only with that gap visible to whoever sanctions it.
- Receiver
The team preparing options and the business case.
- What returns
The outcome statement is the measure against which benefits are later evaluated, and the record that makes that evaluation possible.
Who acts
Sponsor or investment ownerbecomes accountable; progression authority
Which post holds this authority, and its limits, are set by the organisation’s own delegation of investment authority. your organisation decides
Project developmentprepares; technical owner
Who drafts the outcome statement is the organisation’s choice. your organisation decides
Operatorreviews; participant
The future operator reviews whether the outcome can be run and measured. The method asks for this review at this stage; the external requirements it relies on do not.
Records it uses
Link to this stepWhere this publication examines it
- Glossary
Step 2 of 5: Options and business caseChoose between options against criteria recorded before the choice, and cost the chosen option over its whole life.
Stage 01 · step 02 of 05
- Located in
- Stage 01 · Inception & Development
- Follows
- Need and outcome
- Releases to
- Sanction and the authority to stop
What governs it
In UK central government appraisal, social costs and benefits are calculated over the lifetime of the proposal, through to termination or decommissioning. required
Applies to United Kingdom, central government
HM Treasury, The Green Book, 2026 edition, paragraph 2.21
The Green Book asks appraisals to draw on evidence from previous evaluations and to consider from the outset how the proposal will be evaluated. required
Applies to United Kingdom, central government
HM Treasury, The Green Book, 2026 edition, paragraph 1.10
Timing
May overlap Delivery and contracting strategy
In HM Treasury’s business case method the procurement strategy is determined while the outline business case is prepared, not after it. analysis
Reasoned from HM Treasury, International Guide to Developing the Project Business Case, Chapter 6, Step 5, Action 14
- Entry condition
An outcome statement exists and has an owner.
- Inputs
The outcome statement, options including doing the minimum, cost estimates with their class and range, and evidence from earlier evaluations.
- Activities
Record the decision criteria and who is entitled to apply them; estimate whole-life cost including operation, maintenance and decommissioning; plan how the outcome will be evaluated.
- Outputs
A business case naming the preferred option, its whole-life cost, its estimate range and its evaluation plan.
- Evidence
The criteria as written before options were scored, the estimate basis, and the operating-cost estimate with who prepared it.
- Decisions
Recommend an option for sanction, return to options, or stop.
- Exceptions
An estimate whose class does not match the definition achieved goes forward with its range shown, not as a single figure.
- Receiver
Whoever holds the authority to sanction.
- What returns
The operating-cost estimate made here is the figure later compared with actual operating cost.
Who acts
Project developmentprepares; technical owner
Which function prepares the case is the organisation’s choice. your organisation decides
Financereviews; participant
Finance reviews affordability under the organisation’s own budgeting rules. your organisation decides
Operatorchallenges; participant
The unit that will pay the operating cost challenges its estimate before sanction; the external requirements the method relies on do not require that unit’s sign-off.
Sponsor or investment ownerrecommends; progression authority
Which post holds this authority, and its limits, are set by the organisation’s own delegation of investment authority. your organisation decides
Records it uses
Link to this stepWhere this publication examines it
Step 3 of 5: Delivery and contracting strategyDecide how the asset will be delivered and contracted, and record which party will carry each lifecycle obligation, including operation, information and maintenance.
Stage 01 · step 03 of 05
- Located in
- Stage 01 · Inception & Development; Runs into From sanction to committed delivery
- Follows
- Need and outcome
What governs it
HM Treasury’s method requires the commercial case to show that the preferred option will result in a viable procurement and a well structured deal. required
Binding only where it is adopted or contracted
HM Treasury, International Guide to Developing the Project Business Case, Chapter 2, The Commercial Case
In UK central government a Gate 2 review validates the proposed delivery strategy before any commitments are made to prospective suppliers. required
Applies to United Kingdom, central government
Gate 2 Review: Delivery Strategy (workbook), Delivery Strategy, purpose
One objective of Saudi Arabia’s 2026 procurement law, gazetted on 4 September 2026 to take effect 120 days after publication in place of the 2019 law, is best value for public money in contracting for and executing works and purchases, at fair competitive prices and with regard to life-cycle cost, quality of execution, operating efficiency and risk management. required
Applies to Saudi Arabia, government entities Text read: as gazetted 4 September 2026, not yet in force.
Government Tenders and Procurement Law, new law published in Umm Al-Qura 22/3/1448 (4 September 2026), Arabic, Article 2(2); Articles 100 and 101
- Entry condition
A preferred option, or a short list of options, exists. analysis
- Inputs
The business case, the outcome statement, and what the organisation can and cannot do for itself after handover.
- Activities
Record why the chosen delivery and contracting model fits the sanctioned case, and allocate design, testing, commissioning, training, spares, warranties and information to named parties.
- Outputs
A delivery and contracting strategy with an allocation of lifecycle obligations.
- Evidence
The strategy as approved, and the reasons recorded for the model chosen.
- Decisions
Approve the strategy, revise it, or return to the case.
- Exceptions
An obligation that no party has been allocated is recorded as unallocated and goes to the decision-maker, not left to be found at handover.
- Receiver
Those preparing requirements and tender documents.
- What returns
Whether the allocation held is evidence for the next strategy decision of the same kind.
Who acts
Commercial and procurementprepares; technical owner
Which function prepares the strategy is the organisation’s choice. your organisation decides
Operatorreviews; participant
The future operator reviews the allocation of operating obligations; none of the external requirements the method relies on makes it an approver.
Assurancereviews; participant
In UK central government the Gate 2 review team validates the strategy and reports; the review itself is not the decision. required
Applies to United Kingdom, central government
Gate 2 Review: Delivery Strategy (workbook), Delivery Strategy, purpose; Gate 4 Review: Readiness for Service (workbook), The Gate Review Process
Gate or approving authorityapproves; progression authority
Which post holds this authority, and its limits, are set by the organisation’s own delegation of procurement and investment authority. your organisation decides
Link to this stepWhere this publication examines it
Step 4 of 5: Sanction and the authority to stopAuthorise the investment to proceed, with conditions, or stop it.
Stage 01 · step 04 of 05
- Located in
- Stage 01 · Inception & Development
- Follows
- Options and business case
What governs it
Which post holds this authority, and its limits, are set by the organisation’s own delegation of investment authority. your organisation decides
An investment gate is effective only when it has both adequate information and the authority to stop or defer the proposal; that is this publication’s argument, not an external requirement. analysis
Timing
May come before Commitment: award and release of the baseline
HM Treasury’s method separates the outline business case from the full business case, at which the negotiated deal is set out, so an in-principle sanction can precede commitment.
Reasoned from HM Treasury, International Guide to Developing the Project Business Case, Chapter 6 and Chapter 7, Step 9, Action 28
- Entry condition
A business case with its whole-life cost, estimate range and evaluation plan.
- Inputs
The business case and any review of it.
- Activities
Decide against the recorded criteria, and record the decision, its conditions and any dissent.
- Outputs
A decision record: sanctioned, sanctioned with conditions, deferred or stopped.
- Evidence
The decision record with the authority exercised and the information the decision-maker had.
- Decisions
Sanction, sanction with conditions, defer, or stop.
- Exceptions
Conditions attached to sanction go into the conditions record with an owner and a date.
- Receiver
Those authorised to enter into contracts with suppliers on the organisation’s behalf.
- What returns
The decision record is the baseline against which later change is measured.
Who acts
Gate or approving authorityapproves; progression authority
Which post holds this authority, and its limits, are set by the organisation’s own delegation of investment authority. your organisation decides
Sponsor or investment ownerbecomes accountable; progression authority
The organisation names who answers for the sanctioned outcome. your organisation decides
Assurancereviews; participant
Whether an independent review informs sanction is the organisation’s choice where no regime requires one. your organisation decides
Financeis notified; participant
Finance is notified so that the budget provides for the investment as sanctioned. your organisation decides
Records it uses
Link to this stepWhere this publication examines it
- Framework domains
- Glossary
Step 5 of 5: Operating and information requirements into tenderPut what the operator will need, in information, testing, training, spares and acceptance criteria, into the documents suppliers price, before they price them.
Stage 01 · step 05 of 05
- Located in
- Stage 01 · Inception & Development; Runs into From sanction to committed delivery
What governs it
Where EXPRO’s turnover procedure for Saudi government entities applies, the entity’s project management organisation sets the turnover strategy at initial planning together with the operations department and its custodian, including the records each completion package carries and the deficiencies the operations department will accept as open at turnover; the strategy goes into the design tender, and the turnover packages the designer defines go into the construction bidding documents and so into the contractor’s scope. required
Applies to Saudi Arabia, government entities applying the EXPRO national manuals
EXPRO, National Manual for Projects Management, EPM-KTC-PR-000001, Project Turnover of Facility/Infrastructure Procedure, sections 7.1 to 7.4, pp. 10–11
Before the tender is released, the function expected to operate and maintain the asset reviews the operating, maintenance, information and acceptance requirements while the brief and design are developed, and reviews the final requirement set again before release. analysis
Where no such function exists yet, the owner nominates a competent function to represent future operations.
The review record identifies who represented operations, the requirements reviewed, the objections and qualifications raised, how each was resolved, who approved the final requirement set under the organisation’s delegated authority, and the residual operational risks accepted at tender release.
Formal approval of those requirements rests with the authority that the organisation’s own governance arrangements assign. your organisation decides
In UK central government, Gate 2 expects the specification to include success factors showing how achievement of outputs or outcomes will be assessed, and expects live-service operation to have been considered. required
Applies to United Kingdom, central government
Gate 2 Review: Delivery Strategy (workbook), questions 3.3 and 5.9
Where ISO 19650 is adopted, each exchange information requirement is derived from the project and asset information requirements and issued at the invitation-to-tender stage. required
Binding only where it is adopted or contracted
UK BIM Framework, Information management according to BS EN ISO 19650, Guidance Part 2, Parties, teams and processes for the delivery phase of the assets, clause 5.2.1 guidance (PDF page 39); Table 2, stage 5.2
The UK BIM Framework guidance describes ISO 19650 as voluntary unless a contract or policy adopts it.
Reasoned from UK BIM Framework, Information management according to BS EN ISO 19650, Guidance Part 3, Operational phase of the asset life-cycle, edition 1, Guidance Part 3, section 2.0
Once Saudi Arabia’s 2026 procurement law takes effect, 120 days after its gazettal on 4 September 2026, a government entity must submit the feasibility study, cost estimate and tender documents to the unified procurement body for review before tendering, subject to the exceptions in Article 15(4); until then the 2019 law it replaces applies. required
Applies to Saudi Arabia, government entities Text read: as gazetted 4 September 2026, not yet in force.
Government Tenders and Procurement Law, new law published in Umm Al-Qura 22/3/1448 (4 September 2026), Arabic, Article 15(3) and (4); Articles 100 and 101
- Entry condition
A delivery and contracting strategy allocating those obligations.
- Inputs
The outcome statement, the operating concept, the organisation’s information requirements and the allocation of obligations.
- Activities
Write operating, maintenance, information, testing and commissioning requirements and the criteria for accepting each deliverable, and name the receiving party and receiving system for each.
State the following separately in the tender documents, as the governing contract provides: the event of taking over or preliminary receipt; the date on which any defects notification or defects liability period begins; the event at which care of the works passes; the party bearing the risk of loss or damage; the party responsible for insurance and how continuous cover will be maintained; and the start and expiry of each applicable warranty. The dates and allocations need not coincide, and no one item is to be inferred from another.
- Outputs
Tender documents carrying those requirements, acceptance criteria and receivers.
- Evidence
The deliverable and evidence register as issued with the tender.
The review record, with the disposition of each objection and qualification and the approval of the final requirement set.
- Decisions
Release the tender package, or hold it until the requirements are complete.
- Exceptions
A requirement left for later is recorded as a condition with an owner and a date; one never written cannot be enforced against a supplier.
- Receiver
Tenderers, and then the appointed supplier.
- What returns
Information the operator later finds missing is returned to the requirements template for the next tender.
Who acts
Information or data ownerprepares; technical owner
The information-owner function does the work ISO 19650 gives the appointing party: establishing the information requirements, including the exchange information requirements issued with the tender.
Reasoned from UK BIM Framework, Information management according to BS EN ISO 19650, Guidance Part 2, Parties, teams and processes for the delivery phase of the assets, clause 5.2.1 guidance; Table 4
Operatorreviews; participant
The function expected to operate and maintain the asset reviews the requirements while the brief and design are developed and reviews the final set before release; where it does not yet exist, the owner’s nominee does.
Commercial and procurementprepares; technical owner
Who assembles the tender documents is the organisation’s choice. your organisation decides
Gate or approving authorityapproves; progression authority
Which post holds this authority, and its limits, are set by the organisation’s own delegation of procurement authority. your organisation decides
Records it uses
Deliverable and evidence register; Operating-obligation register; Outcome-feedback record
Link to this stepWhere this publication examines it

Seam · between stage 01 and stage 02
From sanction to committed delivery
- Before the releasing side lets go
In UK central government the delivery strategy is validated at Gate 2 before commitments are made to prospective suppliers. required
Applies to United Kingdom, central government
Gate 2 Review: Delivery Strategy (workbook), Delivery Strategy, purpose
Operating, information, testing and commissioning requirements, with the criteria for accepting each deliverable, are in the tender documents before suppliers price them. analysis
Reasoned from Gate 2 Review: Delivery Strategy (workbook), question 3.3; UK BIM Framework, Information management according to BS EN ISO 19650, Guidance Part 2, Parties, teams and processes for the delivery phase of the assets, clause 5.2.1 guidance (PDF page 39)
Every lifecycle obligation has been allocated to a named party, or recorded as unallocated for the decision-maker.
- Before the receiving side takes over
In UK central government, Gate 3 confirms the investment decision before the contract is placed, and expects acceptance criteria for key milestones to be agreed and an operator to exist who will lead testing and commissioning. required
Applies to United Kingdom, central government
Gate 3 Review: Investment Decision (workbook), Decision, purpose; questions 4.4 and 6.3
Delivery accepts a baseline only as approved and recorded; anything dropped in negotiation is a recorded deviation from the sanctioned case.
- Who receives
Project management and project controls, who hold the baseline; the information owner, who holds the information requirements.
Steps at this seam Delivery and contracting strategy; Operating and information requirements into tender; Commitment: award and release of the baseline; Design basis control and design acceptance
Step 1 of 1: Commitment: award and release of the baselineCommit the organisation to a supplier and fix the baseline that delivery will be measured against.
Seam · step 01 of 01
What governs it
In UK central government a Gate 3 review confirms that the recommended investment decision is appropriate before the contract is placed. required
Applies to United Kingdom, central government
Gate 3 Review: Investment Decision (workbook), Decision, purpose
In UK central government, Gate 3 also expects acceptance criteria for key milestones to have been agreed. required
Applies to United Kingdom, central government
Gate 3 Review: Investment Decision (workbook), question 4.4
In UK central government, Gate 3 expects an operator to exist who will lead through testing, commissioning and entry into service. required
Applies to United Kingdom, central government
Gate 3 Review: Investment Decision (workbook), question 6.3
Which post holds this authority, and its limits, are set by the organisation’s own delegation of contract award authority. your organisation decides
Timing
May coincide with Sanction and the authority to stop
Where the final investment decision is taken on the full business case, sanction and commitment fall together; otherwise commitment follows an in-principle sanction. analysis
Reasoned from HM Treasury, International Guide to Developing the Project Business Case, Chapter 7, Step 9, Action 28
- Entry condition
Sanction, an approved strategy, and tender documents carrying the operating and information requirements.
- Inputs
The evaluated tenders, the updated business case and the acceptance criteria for milestones and deliverables.
- Activities
Confirm the award against the stated criteria, agree acceptance criteria, and approve and record the baseline.
- Outputs
A signed contract, an approved baseline and a decision record.
- Evidence
The award decision, the contract as signed and the baseline as approved, each dated.
- Decisions
Award, award with conditions, retender, or stop.
- Exceptions
A requirement dropped during negotiation is recorded as a deviation from the sanctioned case.
- Receiver
Project management and project controls, who hold the baseline from here.
- What returns
The baseline is what later performance and change are measured against.
Who acts
Gate or approving authorityapproves; progression authority
Which post holds this authority, and its limits, are set by the organisation’s own delegation of contract award authority. your organisation decides
Commercial and procurementprepares; technical owner
Who conducts the award is set by the organisation within any procurement law that applies. your organisation decides
Operatoris notified; participant
The operator is notified of the award and the baseline it will take over.
Project managementbecomes accountable; technical owner
The organisation names who answers for delivery against the baseline. your organisation decides
Records it uses
Link to this stepWhere this publication examines it
- Framework domains
- Glossary

Stage 02 · 4 steps
Delivery & Controls
The difference between progress and health. Governance, cost, schedule and risk during construction.
The steps, in dependency order
Step 1 of 4: Design basis control and design acceptanceFix a controlled design basis that traces to the sanctioned outcome and the operating requirements, and record what was examined before it was accepted.
Stage 02 · step 01 of 04
- Located in
- Stage 02 · Delivery & Controls; Runs into Inception & Development
What governs it
Under FIDIC 2017, as Howard Kennedy’s commentary summarises Sub-Clause 5.2, approval or review of the Contractor’s Documents does not relieve the Contractor of any obligation or responsibility. required
Binding only where it is adopted or contracted
Howard Kennedy, FIDIC 2017: Clause 5, Design, Sub-Clause 5.2
Particular Conditions may change this allocation, and the method records the clause in force. analysis
How the design is produced, calculated, coordinated or checked against codes. outside this method
Why Engineering design is a professional discipline this publication does not teach. The method records only what the design must trace to, who examined it, and what was decided.
Timing
May come before Commitment: award and release of the baseline
Where the employer designs before tender, design acceptance precedes award.
May come after Commitment: award and release of the baseline
Where the contractor designs, design acceptance follows award and is governed by the contract.
- Entry condition
Operating and information requirements exist to trace the design to.
- Inputs
The requirements, the operating concept, the named future operator, and the maturity the next decision needs.
- Activities
Trace requirements into the design basis; record whether constructability, maintainability, operability and testability were examined, against what criteria, by which functions, and what followed; set test and commissioning requirements before construction.
- Outputs
An accepted design basis, a record of the examinations and their outcomes, and the test requirements.
- Evidence
The design basis under configuration control and the dated record of each examination and decision.
- Decisions
Accept the design basis, accept it with recorded deviations, or return it.
- Exceptions
Departures from the basis are recorded as deviations or concessions, each with an approver and conditions.
- Receiver
Construction, project controls and the operator.
- What returns
Design decisions that fix whole-life cost are recorded so that operating evidence can later be traced back to them.
Who acts
Engineeringprepares; technical owner
Which party prepares the design follows from the delivery model and the contract. your organisation decides
Operatorreviews; participant
The operator reviews operability and maintainability; none of the external requirements the method relies on makes it an approver of the design.
Information or data ownerreviews; participant
The information owner reviews identifiers and information against the requirements.
Financereviews; participant
Finance reviews decisions that change whole-life cost against the sanctioned case.
Project managementapproves; progression authority
Who accepts the design basis on the organisation’s behalf is set by its delegation and the contract. your organisation decides
Link to this stepWhere this publication examines it
Step 2 of 4: Controlled baseline, change, deviation and configurationDeliver to the approved baseline and keep every change to it examined, approved and reflected in the record of what is being built.
Stage 02 · step 02 of 04
- Located in
- Stage 02 · Delivery & Controls
What governs it
Change, deviation and configuration control keep the approved design, the built condition and the operating record describing the same asset. analysis
How schedules, estimates and earned value are produced. outside this method
Why Project controls technique belongs to its own discipline; the method links to the domains and tools that test it.
- Entry condition
An approved baseline and a signed contract.
- Inputs
The baseline, the design basis, change requests and progress records.
- Activities
Assess changes before they are made, record their effect on operation as well as cost and time, and keep the design record in step with what is built.
- Outputs
An updated baseline with every step from the sanctioned one documented, and a current configuration record.
- Evidence
Change and deviation records made at the time, not reconstructed later.
- Decisions
Approve a change, reject it, or approve it with conditions; re-baseline only by recorded decision.
- Exceptions
A change made without assessment is recorded as such and assessed after the event.
- Receiver
Testing and commissioning, and finance for the cost record.
- What returns
Changes that altered operation are carried into the operating record and the requirements template.
Who acts
Project controlsprepares; technical owner
Who maintains the baseline is the organisation’s choice. your organisation decides
Engineeringverifies; participant
Engineering verifies the technical effect of each change on the design basis.
Operatoris notified; participant
The operator is notified of changes that alter how the asset will be run.
Project managementapproves; progression authority
Which post holds this authority, and its limits, are set by the organisation’s own delegation of change authority. your organisation decides
Link to this stepWhere this publication examines it
Step 3 of 4: Testing and commissioningShow, against criteria set before construction, that the asset performs as required and can be operated.
Stage 02 · step 03 of 04
- Located in
- Stage 02 · Delivery & Controls; Runs into Completion
What governs it
In UK central government, Gate 4 checks that testing, including commissioning of buildings and user acceptance testing, has been done to the client’s satisfaction. required
Applies to United Kingdom, central government
Gate 4 Review: Readiness for Service (workbook), Purpose of the Gate 4 Review
Which tests are contractual, and the criteria they are judged against, come from the requirements fixed before award. analysis
Timing
May overlap Certification and issue of the taking-over certificate
Under FIDIC 2017, as Tyson summarises Clause 10, a taking-over certificate for a part identifies outstanding work, including Tests on Completion, so some testing may continue after taking over.
Reasoned from Tyson, FIDIC 2017: Clause 10, Employer’s Taking Over, Howard Kennedy, Sub-Clause 10.2
- Entry condition
Test requirements and acceptance criteria exist from the design stage.
- Inputs
The test requirements, the design basis and the as-built configuration.
- Activities
Carry out the tests with the future operator present, and record results against the criteria, including tests that could not be run.
- Outputs
Test and commissioning records, and a list of tests outstanding.
- Evidence
Dated test records signed by whoever witnessed them, and the reasons for any test deferred.
- Decisions
Tests passed, passed with recorded deviations, failed and repeated, or deferred with a reason.
- Exceptions
A deferred test is listed as outstanding work with a date and an owner.
- Receiver
The party applying for taking over, the operator, and finance for the capability test.
- What returns
Failures found late are traced back to the design decision or requirement that caused them.
Who acts
Engineeringprepares; technical owner
Who runs the tests follows from the contract. your organisation decides
Operatorreviews; participant
The operator takes part in testing and commissioning; UK central government expects more, an operator who leads through them.
Reasoned from Gate 3 Review: Investment Decision (workbook), question 6.3
Engineeringverifies; participant
Who verifies results against criteria is set by the contract and the organisation. your organisation decides
Records it uses
Deliverable and evidence register; Operating-obligation register
Link to this stepWhere this publication examines it
- Glossary
Step 4 of 4: Financial recognition and measurementRecord the asset’s cost in the entity’s accounts as the criteria are met, on the elements of cost the standard allows.
Stage 02 · step 04 of 04
- Located in
- Stage 02 · Delivery & Controls; Runs into Handover & Transition
What governs it
Under IPSAS 45 an item of property, plant and equipment is recognised if, and only if, future economic benefits or service potential are probable and the item can be measured reliably. required
Binding only where it is adopted or contracted
IPSAS 45, property, plant and equipment, paragraph 6
IPSAS 45 includes in cost the initial estimate of the costs of dismantling and removing the item and restoring its site, where the entity has that obligation. required
Binding only where it is adopted or contracted
IPSAS 45, property, plant and equipment, paragraph 14(c)
Under IPSAS 19, for an asset carried at cost, a change in a decommissioning or restoration liability is added to or deducted from the asset’s cost in the current period; the deduction cannot exceed the carrying amount, any excess goes to surplus or deficit, and an addition prompts consideration of whether the asset is still recoverable. For an entity reporting under IFRS, IAS 16 includes the initial estimate in cost, IAS 37 requires the provision to be reviewed and adjusted at the end of each reporting period, and IFRIC 1 treats a change in it under the cost model the same way, with any excess in profit or loss. required
Binding only where it is adopted or contracted
IPSASB, 2025 Handbook of International Public Sector Accounting Pronouncements, IPSAS 19, Appendix B, paragraph B5(a) to (c); Commission Regulation (EU) 2023/1803 adopting certain international accounting standards, IAS 16, paragraph 16(c); IAS 37, paragraph 59; IFRIC 1, paragraph 5
IPSAS 45 measures the cost of a self-constructed asset on the same principles as an acquired one. required
Binding only where it is adopted or contracted
IPSAS 45, property, plant and equipment, paragraph AG18
Timing
May come before Certification and issue of the taking-over certificate
Recognition turns on the IPSAS 45 criteria, not on a contractual event, so the costs of an asset under construction can be recognised before taking over; recognition does not wait for a taking-over certificate. analysis
Reasoned from IPSAS 45, property, plant and equipment, paragraph 6; paragraph AG18
- Entry condition
Costs are being incurred under a sanctioned and committed project.
- Inputs
Certified and paid amounts, directly attributable costs, and the dismantling and restoration obligation where one exists.
- Activities
Classify costs as eligible or not, and hold eligible costs as work in progress against identifiable items.
- Outputs
Work in progress balances traceable to items and to the project record.
- Evidence
The cost records and the basis for each eligibility judgement.
- Decisions
Recognise a cost, expense it, or hold it pending information.
- Exceptions
Costs that cannot be traced to an item are recorded as such, not spread silently.
- Receiver
Finance, for the capitalisation decision.
- What returns
Actual cost by element is the evidence later compared with the estimate in the business case.
Who acts
Financeprepares; technical owner
Who prepares the accounting record is the organisation’s choice within its reporting framework. your organisation decides
Project controlsverifies; participant
Project controls verifies that recorded costs match the project record.
Records it uses
Link to this stepWhere this publication examines it

Seam · between stage 02 and stage 03
Completion
- Before the releasing side lets go
Tests have been run against the criteria set before construction, and those not run are listed as outstanding. analysis
Under FIDIC 2017, as Tyson summarises Sub-Clause 10.1, as-built records, operation and maintenance manuals and training are a requirement of taking over. required
Binding only where it is adopted or contracted
Tyson, FIDIC 2017: Clause 10, Employer’s Taking Over, Howard Kennedy, Sub-Clause 10.1
- Before the receiving side takes over
The employer takes over under the contract on the certificate the contract provides; that is a contractual act and accepts nothing beyond what the contract says it does.
Under FIDIC 2017 Sub-Clause 11.9, as quoted in a FIDIC-published presentation, only the Performance Certificate is deemed to constitute acceptance of the Works. required
Binding only where it is adopted or contracted
Cotovelea, Tsaturova and Glover, Differences between the Civil and Common Law, Part 2: Delay Damages and Taking-Over, slide quoting Sub-Clause 11.9
- Who receives
The employer, with the contractor still holding outstanding work and defects.
Steps at this seam Testing and commissioning; Application for taking over; Certification and issue of the taking-over certificate; Transfer of care of the works
Step 1 of 3: Application for taking overPut the contractor’s claim that the works are complete on the record, with what it is supplying in support.
Seam · step 01 of 03
- Located in
- Seam · Completion
- Follows
- Testing and commissioning
What governs it
The contract in force says who may apply for taking over, when, and with what. The method records the clause relied on. analysis
Under FIDIC 2017, as Tyson summarises Sub-Clause 10.1, as-built records, operation and maintenance manuals and training are an express requirement of taking over. required
Binding only where it is adopted or contracted
Tyson, FIDIC 2017: Clause 10, Employer’s Taking Over, Howard Kennedy, Sub-Clause 10.1
- Entry condition
The contractor considers the works, or a section, complete under the contract.
- Inputs
Test records, as-built records, operation and maintenance manuals and training records, as the contract requires them.
- Activities
Record the application, its date and the deliverables offered with it against the deliverable register.
- Outputs
A dated application and the list of deliverables submitted with it.
- Evidence
The application and the register entries showing what was submitted and what was not.
- Decisions
None by the employer at this point; the application starts the contractual clock for certification.
- Exceptions
Deliverables required for taking over but not submitted are recorded against the application.
- Receiver
The party the contract names to certify, and the employer.
- What returns
Deliverables repeatedly missing at application are returned to the requirements template.
Who acts
Commercial and procurementis notified; participant
Who receives the application on the employer’s side is set by the contract. your organisation decides
Information or data owneris notified; participant
The information owner is notified so that information acceptance can start.
Records it uses
Link to this stepWhere this publication examines it
Step 2 of 3: Certification and issue of the taking-over certificateRecord that the works, or a section, have been taken over under the contract, and on what terms.
Seam · step 02 of 03
- Located in
- Seam · Completion
- Follows
- Application for taking over
What governs it
Which party certifies, and what certification means, is set by the contract form and its Particular Conditions. analysis
Under Article 127(2) of the 2019 Executive Regulations of Saudi Arabia’s Government Tenders and Procurement Law, works under a public construction contract are received initially after the contractor gives notice that they are complete, and the government entity forms a committee to begin inspection and receipt within fifteen days of that notice. required
Applies to Saudi Arabia, government entities Text read: consolidated Arabic, third edition.
Saudi Government Tenders and Procurement Law and its Executive Regulations, consolidated Arabic text, third edition, Executive Regulations Article 127(2), p. 94
Under the same paragraph, where the entity cannot receive the project for reasons not attributable to the contractor, such as something that prevents operation or trial running, «كوجود ما يمنع من التشغيل أو التجربة», it prepares an inspection report with the contractor or its representative listing all completed work; the completed report counts as initial receipt and supports payment for that work and the final statement, and the contractor remains responsible for the tests and trial running needed for final receipt if those reasons cease within the warranty period. required
Applies to Saudi Arabia, government entities Text read: consolidated Arabic, third edition.
Saudi Government Tenders and Procurement Law and its Executive Regulations, consolidated Arabic text, third edition, Executive Regulations Article 127(2), p. 94
Article 127 sets up a mechanism for inspecting and receiving construction works. Where the contract does not define operating, commissioning, information and acceptance criteria, the committee may have no objective contractual basis on which to judge whether the asset is ready to operate.
Where EXPRO’s preliminary and final handover procedure for Saudi government entities applies, it includes among the conditions for applying for preliminary handover: the works complete, with testing and commissioning done, and ready for operation for their intended purpose; and the entity’s acceptance of the record documents including as-built drawings, of the operation and maintenance requirements and manuals, and of spare parts, special tools and consumables, together with completion of the training the agreement requires. required
Applies to Saudi Arabia, government entities applying the EXPRO national manuals
EXPRO, National Manual for Projects Management, EPM-KD0-PR-000019, Preliminary and Final Handover Procedure, section 6.1, pp. 6–7
Under FIDIC 2017 Sub-Clause 11.9, as quoted in a FIDIC-published presentation, only the Performance Certificate is deemed to constitute acceptance of the Works; the taking-over certificate does not. required
Binding only where it is adopted or contracted
Cotovelea, Tsaturova and Glover, Differences between the Civil and Common Law, Part 2: Delay Damages and Taking-Over, slide quoting Sub-Clause 11.9
Under Saudi Arabia’s 2019 regulations the warranty period of not less than one year runs from initial receipt, «الاستلام الابتدائي». required
Applies to Saudi Arabia, government entities Text read: consolidated Arabic, third edition.
Saudi Government Tenders and Procurement Law and its Executive Regulations, consolidated Arabic text, third edition, Executive Regulations Article 128(1), pp. 76–77
Timing
May come after Asset-information acceptance
A contractual no-objection to as-built records is required before taking over; the organisation’s own information acceptance is a separate event with its own timing.
Reasoned from Tyson, FIDIC 2017: Clause 10, Employer’s Taking Over, Howard Kennedy, Sub-Clause 10.1
- Entry condition
An application, and whatever the contract requires before certification.
- Inputs
The application, the deliverables submitted, test records and the list of work and defects outstanding.
- Activities
Certify, or refuse with reasons, under the contract; list what is outstanding on the certificate.
- Outputs
A taking-over certificate, or its national equivalent, with its date and the outstanding work and defects listed.
- Evidence
The certificate, the minutes where a receipt committee is used, and any waivers given to reach the date.
- Decisions
Issue the certificate, issue it with outstanding items listed, or refuse it with reasons.
- Exceptions
A requirement waived to reach taking over is recorded in the conditions record with who agreed it.
- Receiver
The employer, and the contractor, who keeps obligations for outstanding work and defects.
- What returns
Waivers given at taking over are evidence for how the next contract states its completion requirements.
Who acts
Project managementis notified; participant
Which party certifies is set by the contract and its Particular Conditions; the certifier may sit outside the organisation, and project management receives and administers the certificate on its side. your organisation decides
Operatoris notified; participant
The operator is notified of the date, because care and risk may change on it.
Financeis notified; participant
Finance is notified; the certificate is an input to its own capability test, not the test itself.
Records it uses
Lifecycle decision and conditions record; Authority view; Deliverable and evidence register; Operating-obligation register
Link to this stepWhere this publication examines it
- Framework domains
- Glossary
Step 3 of 3: Transfer of care of the worksRecord the date the employer becomes responsible for the physical care of the works, and who on its side holds it.
Seam · step 03 of 03
- Located in
- Seam · Completion; Runs into Handover & Transition
- Follows
- Application for taking over
What governs it
The governing contract and its amendments determine when responsibility for care of the works passes. The step identifies the event on which it passes, the custodian on the employer’s side, and the arrangements that follow from that event for access, insurance, security and outstanding work. analysis
Where EXPRO’s turnover procedure for Saudi government entities applies, the entity’s operations department designates a custodian to receive the completed works on the entity’s behalf, and the custodian ensures that arrangements, including insurance, are in place for their operation, maintenance, repair, safety and security. required
Applies to Saudi Arabia, government entities applying the EXPRO national manuals
EXPRO, National Manual for Projects Management, EPM-KTC-PR-000001, Project Turnover of Facility/Infrastructure Procedure, sections 5.8 and 5.10, p. 7
- Entry condition
The event on which the governing contract passes care has occurred for the works or the section concerned.
- Inputs
The governing contract and its amendments, the record of the event on which care passes, and the clauses on care, risk and insurance.
- Activities
Name the custodian, confirm insurance and security cover from the date, and record access the contractor keeps for outstanding work.
- Outputs
A custody record naming the custodian and the date.
- Evidence
The custody record and the insurance confirmation, dated.
- Decisions
Accept custody, or record why custody cannot yet be taken.
- Exceptions
Where nobody on the employer’s side is ready to hold care, the gap is escalated before the date, not after it.
- Receiver
The custodian on the employer’s side.
- What returns
Gaps in custody at handover are evidence for the readiness plan of the next project.
Who acts
Records it uses
Link to this stepWhere this publication examines it
- Framework domains
- Glossary

Stage 03 · 7 steps
Handover & Transition
Where information, accountability and intent change hands. A delivered file is not an accepted record.
The steps, in dependency order
Step 1 of 7: Outstanding work and defects after taking overKeep the work and defects left after taking over on one list, with owners and dates, until each is closed.
Stage 03 · step 01 of 07
- Located in
- Stage 03 · Handover & Transition; Runs into Operations & Asset Management
What governs it
Under FIDIC 2017, as Tyson summarises Clause 10, a taking-over certificate for a part identifies the outstanding work to be completed and the defects. required
Binding only where it is adopted or contracted
Tyson, FIDIC 2017: Clause 10, Employer’s Taking Over, Howard Kennedy, Sub-Clause 10.2
Outstanding work and defects stay the contractor’s obligation while the employer operates the asset; the method keeps one list that both sides work from. analysis
Timing
May overlap Operation and maintenance under established requirements
Under FIDIC 2017, as Tyson summarises Clause 11, the defects notification period runs after taking over and may be extended, but not by more than two years beyond its expiry; the asset is commonly in use during it.
Reasoned from Tyson, FIDIC 2017: Clause 11, Defects After Taking Over, Howard Kennedy, Sub-Clause 11.3, p. 3
- Entry condition
A taking-over certificate listing what is outstanding.
- Inputs
The list on the certificate and defects notified during operation.
- Activities
Track each item to closure, and record the operator’s confirmation that it was closed in service.
- Outputs
A list of outstanding work and defects with closure evidence.
- Evidence
Dated notices of defects and dated closure records.
- Decisions
Close an item, extend its date, or treat it under the contract’s remedies for defects not remedied.
- Exceptions
An item the contractor does not remedy goes to the contract’s remedy, recorded with the decision.
- Receiver
The party that will issue final certification.
- What returns
Recurring defects are returned to design and requirements for the next project.
Who acts
Operatorverifies; participant
The operator confirms that an item is closed in service.
Project managementapproves; progression authority
Who closes items on the employer’s behalf is set by the contract and the organisation. your organisation decides
Records it uses
Link to this stepWhere this publication examines it
- Framework domains
Step 2 of 7: Asset-information acceptanceTest the delivered information against the requirements set before tender, by the people who will use it, and accept it into the receiving systems.
Stage 03 · step 02 of 07
- Located in
- Stage 03 · Handover & Transition
What governs it
Where ISO 19650 is adopted, the appointing party reviews and accepts the information model; acceptance is a step of its own. required
Binding only where it is adopted or contracted
UK BIM Framework, Information management according to BS EN ISO 19650, Guidance Part 2, Parties, teams and processes for the delivery phase of the assets, activity 5.7.4 (PDF pages 18 and 23)
A contractual no-objection shows the information was received and not objected to; it does not show the information was accepted into the systems that will use it. analysis
Timing
May come before Certification and issue of the taking-over certificate
A contractual no-objection to as-built records can be required before taking over; the organisation’s acceptance of the information into its own systems is a separate act that may come before or after.
Reasoned from Tyson, FIDIC 2017: Clause 10, Employer’s Taking Over, Howard Kennedy, Sub-Clause 10.1
May come after Certification and issue of the taking-over certificate
Under the 2017 FIDIC Red Book, as Tyson summarises Sub-Clause 10.1, the Engineer’s Notice of No-objection to the as-built records is a condition of taking over. It shows that the records arrived and drew no objection, not that the organisation has taken them into its own systems, which can happen after taking over. required
Binding only where it is adopted or contracted
Tyson, FIDIC 2017: Clause 10, Employer’s Taking Over, Howard Kennedy, Sub-Clause 10.1
- Entry condition
Information requirements with acceptance criteria exist from the tender documents.
- Inputs
As-built records, manuals, asset data and the deliverable register.
- Activities
Check each deliverable against its criteria; trace records to the assets row by row; load accepted information into the receiving systems.
- Outputs
Information accepted into named receiving systems, and a list of what was rejected and why.
- Evidence
The deliverable register showing who accepted each item, when, and into which system.
- Decisions
Accept, accept with recorded deficiencies, or reject and return.
- Exceptions
Information accepted with deficiencies goes into the conditions record with a date for correction.
- Receiver
The asset register, the maintenance system and the operator.
- What returns
Deficiencies found here are returned to the information requirements template.
Who acts
Information or data owneraccepts; progression authority
Who accepts information into each system is the organisation’s choice. your organisation decides
Operatorverifies; participant
The people who will use the information verify it is usable.
Project managementis notified; participant
Project management is notified of rejections, which may affect the contract.
Records it uses
Link to this stepWhere this publication examines it
- Framework domains
- Glossary
Step 3 of 7: Knowledge captureCapture the reasons behind design and construction decisions, and the compromises accepted, while the people who know them are still there.
Stage 03 · step 03 of 07
- Located in
- Stage 03 · Handover & Transition; Runs into Delivery & Controls
What governs it
Why the asset is the way it is, and what was accepted rather than resolved, is held by people who leave at handover; it is captured before they go or not at all. analysis
- Entry condition
Design decisions have been taken whose reasons are not in the documents.
- Inputs
The decision, deviation and change records, and the people who made them.
- Activities
Record the reasons and the accepted compromises against the assets they affect, before the delivery team disbands.
- Outputs
A record of reasons and accepted compromises, linked to asset identifiers.
- Evidence
The dated record and who supplied each entry.
- Decisions
Record complete enough to release the people who hold it, or not yet.
- Exceptions
Knowledge that could not be captured is listed, so the operator knows where the record is silent.
- Receiver
The operator and asset management.
- What returns
Gaps the operator later finds are returned to the next project’s capture plan.
Who acts
Project managementprepares; technical owner
Who organises capture is the organisation’s choice. your organisation decides
Operatoraccepts; participant
The operator accepts the record as usable.
Link to this stepWhere this publication examines it
- Framework domains
- Articles
Step 4 of 7: Operational acceptanceDecide that the organisation, not only the asset, can run the service, and record what it accepted and on what conditions.
Stage 03 · step 04 of 07
- Located in
- Stage 03 · Handover & Transition
- Follows
- Testing and commissioning
What governs it
Operational acceptance is the organisation’s own decision under its own arrangements; none of the contract forms, standards or regulations the method relies on defines it as an event. analysis
The criteria and the authority for operational acceptance are the organisation’s choice. your organisation decides
In UK central government, Gate 4 confirms arrangements for handover from the Senior Responsible Owner to the operational business owner, and expects handover responsibilities to be documented and agreed by both parties. required
Applies to United Kingdom, central government
Gate 4 Review: Readiness for Service (workbook), Purpose of the Gate 4 Review; question 2.4
The Gate 4 workbook describes the gate review as independent guidance to Senior Responsible Owners; the review informs the decision and is not the decision. required
Applies to United Kingdom, central government
Gate 4 Review: Readiness for Service (workbook), The Gate Review Process
Timing
May come after Certification and issue of the taking-over certificate
The organisation may accept the asset for operation after taking over; nothing in the contract makes the two the same day.
Reasoned from Cotovelea, Tsaturova and Glover, Differences between the Civil and Common Law, Part 2: Delay Damages and Taking-Over, slide quoting Sub-Clause 11.9
May come before Certification and issue of the taking-over certificate
It may also fall before, where the organisation decides to operate part of the works early.
- Entry condition
Testing and commissioning records, and the operating organisation’s readiness.
- Inputs
Test records, accepted information, the custody record and the readiness of people, contracts, spares and systems.
- Activities
Check readiness against the criteria the organisation set, and record conditions and who owns them.
- Outputs
An operational acceptance decision, with conditions where they apply.
- Evidence
The decision record and the readiness evidence it rested on.
- Decisions
Accept for operation, accept with conditions, or defer.
- Exceptions
Operating before acceptance, where it happens, is recorded as a decision with its risks and owner.
- Receiver
The operator and asset management.
- What returns
Conditions that remain open after a year are evidence for the next readiness plan.
Who acts
Operatoraccepts; progression authority
Who accepts for operation is the organisation’s choice. your organisation decides
Operatorbecomes accountable; technical owner
The organisation names who answers for the service from acceptance. your organisation decides
Assurancereviews; participant
Whether a readiness review informs the decision is the organisation’s choice where no regime requires one. your organisation decides
Sponsor or investment owneris notified; participant
The sponsor is notified, because the service whose benefits it answers for is now in operation.
Records it uses
Lifecycle decision and conditions record; Authority view; Operating-obligation register
Link to this stepWhere this publication examines it
- Framework domains
- Glossary
Step 5 of 7: Entry in the technical asset registerGive each asset an identity in the register the operator works from, traced to the project record it came from.
Stage 03 · step 05 of 07
- Located in
- Stage 03 · Handover & Transition
- Follows
- Asset-information acceptance
What governs it
A controlled asset identifier and an entry in the technical register exist before any operating, maintenance or financial process depends on the asset record. analysis
Which function makes the entry, who approves it, and by when, are the organisation’s decisions; the method sets no deadline. your organisation decides
- Entry condition
Accepted asset information.
- Inputs
Accepted information, identifiers set in the requirements, and the project crosswalk.
- Activities
Enter each asset, and trace it to the project record and to the financial record in both directions.
- Outputs
Register entries with identifiers that the project, finance and operations records share.
- Evidence
The crosswalk between project, technical and financial records.
- Decisions
Entry made, or held pending information.
- Exceptions
Assets that cannot be traced in both directions are listed for reconciliation.
- Receiver
Maintenance planning, finance and asset management.
- What returns
Identifier problems found here are returned to the information requirements template.
Who acts
Asset managementprepares; technical owner
Who maintains the technical register is the organisation’s choice. your organisation decides
Financeverifies; participant
Finance verifies the trace to the financial record.
Records it uses
Link to this stepWhere this publication examines it
- Glossary
Step 6 of 7: Cessation of capitalisation and transfer from work in progressStop adding cost to the asset when it is capable of operating as intended, and move it out of work in progress into its class and components.
Stage 03 · step 06 of 07
- Located in
- Stage 03 · Handover & Transition
What governs it
The Ministry of Finance’s asset guide for Saudi government entities sets out a work-in-progress procedure, offered as guidance that each entity adapts to its own organisation and systems: the finance department owns the process and accumulates cost under a project code; the projects department supplies the start memorandum, monthly progress reports, the asset documents and its recommended allocation of cost to assets and components; and the finance department prepares an asset classification report for review and approval under the entity’s authority matrix, then transfers the approved project costs from work in progress to the relevant asset records and starts depreciation. analysis
Reasoned from Saudi Ministry of Finance, comprehensive manual for the census and valuation of assets of government entities, Arabic, section 7, p. 200; section 7.2, pp. 204–208
The guide uses two formulations without reconciling them: cost stops being added to the carrying amount when the asset is ready to be placed in service, in the location and condition to operate as intended; and the procedure exists to move the cost held as projects under implementation to an asset when operation and use begin. Initial handover appears in it only as a point of coordination between finance and the projects department, and the guide does not make it the event that clears work in progress.
Reasoned from Saudi Ministry of Finance, comprehensive manual for the census and valuation of assets of government entities, Arabic, section 7.2, pp. 204 and 207
Where the date the asset became available for use and the date operation or use began differ, the entity’s governing reporting framework decides the accounting treatment. Both dates are recorded, with the criterion applied and the reason for applying it; neither is silently taken as the other.
Contractual receipt and accounting recognition are separate controlled events, and receipt is not of itself the recognition event. The organisation keeps a crosswalk recording for each asset, where applicable: the contractual receipt event and its date; the date the asset was available for use; the date operation or use actually began, where different; the controlled asset identifier; the accumulated project cost; the accepted asset information; the custodian; the accounting criterion applied; and the capitalisation approval, with the reason for any difference between the dates.
Under IPSAS 45, recognition of costs in the carrying amount ceases when the item is in the location and condition necessary for it to be capable of operating in the manner intended by management. required
Binding only where it is adopted or contracted
IPSAS 45, property, plant and equipment, paragraph 17
Under IPSAS 45, costs incurred while an item capable of operating in that manner has yet to be brought into use are not included in its carrying amount. required
Binding only where it is adopted or contracted
IPSAS 45, property, plant and equipment, paragraph 17
IPSAS 5 expenses borrowing costs as they are incurred and, as an allowed alternative, capitalises those directly attributable to a qualifying asset, suspending capitalisation and expensing the cost during extended periods in which active development is interrupted, and ceasing it when substantially all the activities necessary to prepare the asset for its intended use or sale are complete. For an entity reporting under IFRS, IAS 23 requires those costs to be capitalised, with the same suspension and the same point of cessation. required
Binding only where it is adopted or contracted
IPSASB, 2025 Handbook of International Public Sector Accounting Pronouncements, IPSAS 5, paragraphs 14, 17 to 18, 34 and 36; Commission Regulation (EU) 2023/1803 adopting certain international accounting standards, IAS 23, paragraphs 8, 20 and 22
Under IPSAS 21, an asset becoming idle and a decision to halt construction before the asset is complete or in a usable condition are indications of impairment, while a project delayed or postponed to a specific future date may stay in work in progress and is not treated as halted; IPSAS 26 carries the same two indications for cash-generating assets. For an entity reporting under IFRS, IAS 36 names an asset becoming idle among its indications of impairment and does not name halted construction. required
Binding only where it is adopted or contracted
IPSASB, 2025 Handbook of International Public Sector Accounting Pronouncements, IPSAS 21, paragraphs 27(d), 27(e) and 31; IPSAS 26, paragraph 25(e) to (f); Commission Regulation (EU) 2023/1803 adopting certain international accounting standards, IAS 36, paragraph 12(f)
Timing
May come before Operational acceptance
The test is capability, not acceptance or use, so cost accumulation can stop before, on or after the operational acceptance date.
Reasoned from IPSAS 45, property, plant and equipment, paragraph 17
May come before Certification and issue of the taking-over certificate
Nothing in the capability test refers to a certificate, so it can be met before, on or after taking over.
Reasoned from IPSAS 45, property, plant and equipment, paragraph 17
- Entry condition
Evidence that the asset is in the location and condition to operate as intended.
- Inputs
Test and commissioning records as evidence of capability, and the work in progress balances.
- Activities
Decide the capability date on evidence, split cost into significant parts, and transfer the balance.
- Outputs
Capitalised components with a date, a cost and an identifier shared with the technical register.
- Evidence
The evidence relied on for the capability date and the basis for the split into components.
- Decisions
Capitalise from a stated date, or hold in work in progress with the reason.
- Exceptions
An asset in use but not capitalised, or capitalised but not capable, is recorded and corrected.
- Receiver
The financial asset register, and asset management for reconciliation.
- What returns
The split into components is reviewed when the first part is replaced.
Who acts
Financeapproves; progression authority
Who approves capitalisation, and how soon after the asset is available for use, is set by the organisation’s financial delegation. your organisation decides
Engineeringverifies; participant
Engineering supplies and verifies the evidence of capability; the date is an accounting judgement made on it.
Asset managementis notified; participant
Asset management is notified so the technical and financial registers stay reconciled.
Records it uses
Link to this stepWhere this publication examines it
Step 7 of 7: Start of depreciationStart charging the asset’s cost over its useful life from the date the standard sets, on lives the entity can justify.
Stage 03 · step 07 of 07
- Located in
- Stage 03 · Handover & Transition; Runs into Operations & Asset Management
- Releases to
- Operating performance and cost evidence
What governs it
Under IPSAS 45, depreciation of an asset begins when it is available for use, that is, when it is in the location and condition necessary for it to be capable of operating in the manner intended by management. required
Binding only where it is adopted or contracted
IPSAS 45, property, plant and equipment, paragraph AG27
IPSAS 45 requires the residual value and useful life of an asset to be reviewed at least at each annual reporting date. required
Binding only where it is adopted or contracted
IPSAS 45, property, plant and equipment, paragraph 48
Under IPSAS 45, each part with a cost significant in relation to the total cost of the item is depreciated separately. required
Binding only where it is adopted or contracted
IPSAS 45, property, plant and equipment, paragraph 41
Timing
May coincide with Cessation of capitalisation and transfer from work in progress
Depreciation begins on the same location-and-condition test that ends capitalisation, so the two dates normally coincide. analysis
Reasoned from IPSAS 45, property, plant and equipment, paragraph 17; paragraph AG27
May come before Operation and maintenance under established requirements
Under IPSAS 45, depreciation begins when the asset is available for use, which can be before it is brought into use.
Reasoned from IPSAS 45, property, plant and equipment, paragraph AG27
- Entry condition
A capitalised asset with components and useful lives.
- Inputs
The capitalisation date, the components, and useful lives with the basis for each.
- Activities
Set each component’s useful life and method, and record the basis for the life chosen.
- Outputs
A depreciation schedule per component.
- Evidence
The basis for each useful life, including which end of any published range was taken.
- Decisions
The useful life and method for each component, within the reporting framework and any national manual that binds the entity. your organisation decides
- Exceptions
A life later found wrong is changed as an accounting estimate, not by restating the start date.
- Receiver
Finance and asset management.
- What returns
Observed condition and replacement are returned to the annual review of useful lives.
Who acts
Financeapproves; progression authority
Who sets useful lives is set by the organisation’s financial delegation. your organisation decides
Asset managementrecommends; participant
Asset management recommends lives from engineering evidence.
Records it uses
Link to this stepWhere this publication examines it
- Framework domains
- Glossary

Seam · between stage 03 and stage 04
Custody
- Before the releasing side lets go
Information has been accepted into the receiving systems, not only delivered. analysis
The reasons and compromises held by the delivery team have been recorded before the team disbands.
- Before the receiving side takes over
The organisation accepts the asset for operation against criteria it set, with conditions recorded. your organisation decides
In UK central government, Gate 4 expects handover responsibilities and arrangements to be documented and agreed by both parties. required
Applies to United Kingdom, central government
Gate 4 Review: Readiness for Service (workbook), question 2.4
The accounting events at this seam follow their own criteria; none of them is completed by operational acceptance or by a certificate.
Reasoned from IPSAS 45, property, plant and equipment, paragraphs 17 and AG27
- Who receives
The operator, asset management and finance, each for its own record.
Steps at this seam Outstanding work and defects after taking over; Asset-information acceptance; Knowledge capture; Operational acceptance; Entry in the technical asset register; Cessation of capitalisation and transfer from work in progress; Start of depreciation; Contract closeout: final certification and release of security
Step 1 of 1: Contract closeout: final certification and release of securityClose the contract: confirm outstanding work and defects are done, issue the final certificate or receipt the contract requires, and release security on the contract’s terms.
Seam · step 01 of 01
- Located in
- Seam · Custody; Runs into Operations & Asset Management
- Releases to
- Operating performance and cost evidence
What governs it
Under FIDIC 2017 Sub-Clause 11.9, as quoted in a FIDIC-published presentation, only the Performance Certificate is deemed to constitute acceptance of the Works. required
Binding only where it is adopted or contracted
Cotovelea, Tsaturova and Glover, Differences between the Civil and Common Law, Part 2: Delay Damages and Taking-Over, slide quoting Sub-Clause 11.9
Under FIDIC 2017, as Tyson summarises Sub-Clause 11.10, both parties remain liable after the Performance Certificate for obligations unfulfilled at that date. required
Binding only where it is adopted or contracted
Tyson, FIDIC 2017: Clause 11, Defects After Taking Over, Howard Kennedy, Sub-Clause 11.10, p. 5
Under Saudi Arabia’s 2019 law the final guarantee is kept until the contractor has performed its obligations and the project is finally received, «يستلم المشروع استلاماً نهائياً». required
Applies to Saudi Arabia, government entities Text read: consolidated Arabic, third edition.
Saudi Government Tenders and Procurement Law and its Executive Regulations, consolidated Arabic text, third edition, Law Article 61(4), p. 75; Executive Regulations Article 128(4)
Saudi Arabia’s 2026 law, which replaces the 2019 law 120 days after its gazettal on 4 September 2026, keeps the same rule: the final guarantee is kept until obligations are performed and the project is finally received. required
Applies to Saudi Arabia, government entities Text read: as gazetted 4 September 2026, not yet in force.
Government Tenders and Procurement Law, new law published in Umm Al-Qura 22/3/1448 (4 September 2026), Arabic, Article 59(3); Articles 100 and 101
Where EXPRO’s preliminary and final handover procedure for Saudi government entities applies, the final handover certificate is deemed to constitute final acceptance of the works and also the release of the contractor’s performance security. required
Applies to Saudi Arabia, government entities applying the EXPRO national manuals
EXPRO, National Manual for Projects Management, EPM-KD0-PR-000019, Preliminary and Final Handover Procedure, section 6.6, p. 8
Timing
May overlap Operation and maintenance under established requirements
Closeout runs while the asset is in service; the defects period and any warranty period overlap operation rather than ending inside handover. analysis
May come after Asset-information acceptance
Under the 2017 FIDIC Red Book, a contractual no-objection to as-built records is required at taking over; the organisation’s own information acceptance is a separate event with its own timing.
Reasoned from Tyson, FIDIC 2017: Clause 10, Employer’s Taking Over, Howard Kennedy, Sub-Clause 10.1
- Entry condition
The defects period, or its national equivalent, has run, and the outstanding work list is closed or dealt with.
- Inputs
The closed outstanding-work list, accepted as-built records, and the security instruments held.
- Activities
Confirm each condition the contract sets for final certification, then certify and release security as it provides.
- Outputs
A final certificate or receipt, and released or retained security with reasons.
- Evidence
The certificate, the receipt minutes where a committee is used, and the record of security released.
- Decisions
Certify and release, certify and retain part, or withhold with reasons.
- Exceptions
Obligations still unfulfilled at final certification are listed, since liability for them survives it.
- Receiver
The contractor, finance and the operator.
- What returns
Defects and disputes at closeout are returned to the next contract’s requirements.
Who acts
Project managementis notified; participant
Which party certifies is set by the contract and its Particular Conditions; the certifier may sit outside the organisation, and project management receives and administers the certificate on its side. your organisation decides
Operatorverifies; participant
The operator confirms in-service performance during the defects period.
Financeapproves; progression authority
Release of security and final payment follow the organisation’s financial delegation. your organisation decides
Link to this stepWhere this publication examines it
- Framework domains
- Glossary

Stage 04 · 5 steps
Operations & Asset Management
Knowing what you own, and what it costs to keep. Where it is, what condition it is in, and what it will cost to keep.
The steps, in dependency order
Step 1 of 5: Operation and maintenance under established requirementsRun and maintain the asset under the requirements accepted at handover, and keep its records true.
Stage 04 · step 01 of 05
- Located in
- Stage 04 · Operations & Asset Management
What governs it
For organisations that adopt ISO 55001:2024, the revised Clause 8.1 covers life cycle processes including utilisation, maintenance, improvement, renewal and disposal, as ISO/TC 251’s guidance describes it. analysis
Reasoned from ISO/TC 251, Updated Guidance on Asset Management System Requirements, ISO 55001:2024, Clause 8.1 (revised)
IPSAS 45 recognises the costs of day-to-day servicing in surplus or deficit as incurred, not in the carrying amount of the asset. required
Binding only where it is adopted or contracted
IPSAS 45, property, plant and equipment, paragraph AG13
How maintenance requirements are derived, including RCM and FMEA. outside this method
Why Maintenance engineering is a discipline this publication does not teach. The method records that requirements were established, accepted and executed.
Timing
May come after Operational acceptance
Whether the organisation operates only after its own acceptance, or operates earlier under recorded conditions, is its choice. your organisation decides
- Entry condition
Custody has passed and the operator holds the information it accepted.
- Inputs
Accepted operating and maintenance requirements, the register, warranties and the conditions still open.
- Activities
Execute the maintenance regime, record what is done and found, and keep the register in step with the asset.
- Outputs
Records of operation, maintenance, condition, failure and cost.
- Evidence
Work records made at the time, with the date each record was last confirmed true.
- Decisions
Changes to the maintenance regime, within the organisation’s asset management decision criteria. your organisation decides
- Exceptions
A requirement found unworkable in service is recorded and returned to the requirements template.
- Receiver
Asset management, for performance and renewal decisions.
- What returns
Operating cost and failure records feed the performance evidence and, through it, the next investment decision.
Who acts
Operatorprepares; technical owner
Who operates and maintains is the organisation’s choice, in-house or contracted. your organisation decides
Asset managementbecomes accountable; progression authority
The organisation names who answers for the asset base. your organisation decides
Records it uses
Link to this stepWhere this publication examines it
Step 2 of 5: Operating performance and cost evidenceMeasure what the asset actually does and costs, in terms comparable with what the business case said it would.
Stage 04 · step 02 of 05
- Located in
- Stage 04 · Operations & Asset Management
What governs it
The OECD recommends that adherents collect, store and manage data over the entire life cycle of the asset and monitor its performance against service targets. required
Binding only where it is adopted or contracted
OECD, Recommendation of the Council on the Governance of Infrastructure, recommendation viii)b
IPSAS 45 requires useful lives and residual values to be reviewed at least at each annual reporting date. required
Binding only where it is adopted or contracted
IPSAS 45, property, plant and equipment, paragraph 48
That review can only be more than a formality if it draws on evidence of the asset’s condition and use, which is what this step produces. analysis
- Entry condition
The asset is in operation and its records are being kept.
- Inputs
Operating, maintenance, condition and cost records, and the business case estimates.
- Activities
Compare actual performance and cost with the estimates and service targets, and record the differences and their causes where known.
- Outputs
A performance and cost record comparable with the business case.
- Evidence
The records used, and when each was last confirmed true.
- Decisions
Which measures to report, and how often, within any reporting rule that binds the organisation. your organisation decides
- Exceptions
Where the records cannot support a comparison, that is reported as a finding, not filled by estimate.
- Receiver
Asset management, finance and the sponsor.
- What returns
The comparison is the evidence returned to the next investment decision.
Who acts
Asset managementprepares; technical owner
Who assembles the evidence is the organisation’s choice. your organisation decides
Financeverifies; participant
Finance verifies the cost figures against the accounts.
Sponsor or investment owneris notified; participant
The sponsor is notified, because the outcome is theirs.
Records it uses
Link to this stepWhere this publication examines it
Step 3 of 5: Benefits realisationEstablish whether the outcome stated at the start is being achieved, and why or why not.
Stage 04 · step 03 of 05
- Located in
- Stage 04 · Operations & Asset Management
What governs it
In UK central government, Gate 5 confirms that the benefits set out in the business case are being achieved and that the operational service is running smoothly. required
Applies to United Kingdom, central government
Gate Review 5: Operational Review and Benefits Realisation (workbook), purpose
In UK central government, Gate 5 expects the project’s senior responsible owner to hand over to the operational business owner, typically within a year of the start of the operational service, after which the business owner is responsible for ensuring the expected benefits are delivered; the review confirms that accountability for benefits continues, that post-closure governance is agreed, and that workstreams continuing after closure have clear lines of accountability. required
Applies to United Kingdom, central government
Gate Review 5: Operational Review and Benefits Realisation (workbook), Gate 5 link to other Gate Reviews; Purpose of the Gate 5 Review; questions 5.1 and 5.2
Before the project closes, every continuing benefit has a named post-closure owner, a reporting route and a record that the transfer has taken effect. analysis
In UK central government the management case of a business case sets out benefits realisation arrangements and a monitoring and evaluation plan. required
Applies to United Kingdom, central government
HM Treasury, The Green Book, 2026 edition, summary of the five cases, Management case (PDF page 20)
HM Treasury’s evaluation guidance treats benefits management and evaluation as complementary disciplines.
Reasoned from HM Treasury, Magenta Book: Central Government guidance on evaluation, section 1.7.1
In UK central government, Gate 4 expects a benefits realisation plan setting out the activities, timeline, tools and resources needed to realise the planned benefits. required
Applies to United Kingdom, central government
Gate 4 Review: Readiness for Service (workbook), Project Documentation
Timing
May overlap Contract closeout: final certification and release of security
In UK central government a Gate 5 review is held around handover and again 6 to 12 months after it, and can be repeated through the life of the service, so benefits review can run while the contract is still being closed out.
Reasoned from Gate Review 5: Operational Review and Benefits Realisation (workbook), purpose and timing
- Entry condition
An outcome statement with a measure, and an asset in operation.
- Inputs
The outcome statement, the evaluation plan from the business case, and performance evidence.
- Activities
Measure the outcome against the statement, and evaluate the difference rather than only report it.
- Outputs
A benefits and evaluation record.
- Evidence
The measures, the period, and who measured them.
- Decisions
Continue, change how the asset is used, or record that the outcome will not be achieved.
- Exceptions
Where no outcome was ever stated, that absence is the finding.
- Receiver
The sponsor and whoever appraises the next investment of the same kind.
- What returns
The evaluation is returned to the appraisal of later proposals.
Who acts
Sponsor or investment ownerbecomes accountable; progression authority
The sponsor or senior responsible owner may keep accountability for benefits after closure or transfer it under the organisation’s governance arrangements; the temporary project manager is not assumed to own benefits realisation once the project has closed.
Asset managementprepares; technical owner
Who measures benefits in operation is the organisation’s choice. your organisation decides
Assurancereviews; participant
Whether an independent review examines benefits is the organisation’s choice where no regime requires one. your organisation decides
Records it uses
Link to this stepWhere this publication examines it
Step 4 of 5: Renewal or replacement decisionDecide whether to maintain, renew or replace, on recorded criteria and on evidence of condition and cost.
Stage 04 · step 04 of 05
- Located in
- Stage 04 · Operations & Asset Management
What governs it
Under IPSAS 45, when a part is replaced and the replacement meets the recognition criteria, the carrying amount of the replaced part is derecognised. required
Binding only where it is adopted or contracted
IPSAS 45, property, plant and equipment, paragraph AG14
For organisations that adopt ISO 55001:2024, renewal is among the life cycle processes the revised Clause 8.1 addresses, as ISO/TC 251’s guidance describes it. analysis
Reasoned from ISO/TC 251, Updated Guidance on Asset Management System Requirements, ISO 55001:2024, Clause 8.1 (revised)
How renewal is optimised or deterioration is modelled. outside this method
Why Renewal engineering technique is outside this publication’s scope; the method records the decision, its criteria and its evidence.
- Entry condition
Performance, condition or cost evidence that raises the question.
- Inputs
Performance and cost evidence, the useful lives assumed, and the organisation’s decision criteria.
- Activities
Apply the recorded criteria; where renewal is a new investment, start it as a new need with its own case.
- Outputs
A renewal decision, and where needed a new outcome statement.
- Evidence
The decision record and the evidence it relied on.
- Decisions
Maintain, renew, replace, or dispose.
- Exceptions
Renewal driven by failure, not by plan, is recorded as such.
- Receiver
Inception, for a new case; finance, for the replaced part.
- What returns
The life actually achieved is returned to the useful-life review and to the next estimate.
Who acts
Asset managementrecommends; technical owner
Who recommends renewal is the organisation’s choice. your organisation decides
Gate or approving authorityapproves; progression authority
Which post holds this authority, and its limits, are set by the organisation’s own delegation of investment authority. your organisation decides
Financeis notified; participant
Finance is notified to derecognise replaced parts.
Records it uses
Lifecycle decision and conditions record; Outcome-feedback record
Link to this stepWhere this publication examines it
Step 5 of 5: Disposal and derecognitionTake the asset out of service, the register and the accounts on recorded decisions, and meet the obligations that were estimated at the start.
Stage 04 · step 05 of 05
- Located in
- Stage 04 · Operations & Asset Management
What governs it
Under IPSAS 45 the carrying amount is derecognised on disposal, or when no future economic benefits or service potential are expected from its use or disposal. required
Binding only where it is adopted or contracted
IPSAS 45, property, plant and equipment, paragraph 62
Under IPSAS 45, the gain or loss on derecognition is included in surplus or deficit when the item is derecognised. required
Binding only where it is adopted or contracted
IPSAS 45, property, plant and equipment, paragraph 63
Under IPSAS 44, an asset that is to be abandoned is not classified as held for sale, and one temporarily taken out of use is not accounted for as if abandoned; an asset classified as held for sale is measured at the lower of its carrying amount and fair value less costs to sell, and is not depreciated while so classified. For an entity reporting under IFRS, IFRS 5 sets the same rules, and classifies an asset as held for sale when its carrying amount will be recovered principally through a sale transaction rather than through continuing use. required
Binding only where it is adopted or contracted
IPSASB, 2025 Handbook of International Public Sector Accounting Pronouncements, IPSAS 44, paragraphs 20, 21, 22 and 33; Commission Regulation (EU) 2023/1803 adopting certain international accounting standards, IFRS 5, paragraphs 6, 13, 14, 15 and 25
The OECD’s definition of the life cycle of public infrastructure runs through operation and maintenance to decommissioning. analysis
Reasoned from OECD, Recommendation of the Council on the Governance of Infrastructure, definitions
Timing
May come before Renewal or replacement decision
Because IPSAS 45 derecognises an item on disposal or when no service potential is expected from it, disposal does not need a prior renewal decision.
Reasoned from IPSAS 45, property, plant and equipment, paragraph 62
- Entry condition
A decision that the asset, or a part, will no longer be used.
- Inputs
The disposal decision, the dismantling and restoration obligation estimated at recognition, and the register entries.
- Activities
Decommission, remove the asset from the technical register and derecognise it in the accounts, each on its own record.
- Outputs
Closed register entries and a derecognition record.
- Evidence
The decision, the decommissioning record and the derecognition entry, each dated.
- Decisions
Dispose, mothball, or transfer to another use.
- Exceptions
An asset no longer in use but still on either register is recorded and reconciled.
- Receiver
Finance, asset management, and whoever estimates the next asset’s end-of-life cost.
- What returns
Actual decommissioning cost is compared with the obligation estimated at recognition.
Who acts
Gate or approving authorityapproves; progression authority
Which post holds this authority, and its limits, are set by the organisation’s own delegation of disposal authority. your organisation decides
Asset managementprepares; technical owner
Who prepares the disposal is the organisation’s choice. your organisation decides
Financeprepares; participant
Finance prepares the derecognition under the reporting framework. your organisation decides
Records it uses
Lifecycle decision and conditions record; Operating-obligation register; Outcome-feedback record
Link to this stepWhere this publication examines it

Return loop
Back to the next investment decision
- Before the releasing side lets go
Evidence of performance, cost, benefits, life achieved and information gaps has been compared with what the business case assumed. analysis
- Before the receiving side takes over
In UK central government, appraisals should draw on evidence from previous evaluations. required
Applies to United Kingdom, central government
HM Treasury, The Green Book, 2026 edition, paragraph 1.10
The next case shows which returned evidence it used; evidence nobody used has not been returned.
- Who receives
Whoever prepares the next need, business case, estimate and requirements.
Steps at this seam Evidence returned to the next investment decision
Step 1 of 1: Evidence returned to the next investment decisionSend what operation showed back to the decisions that will be taken again: need, case, estimate, requirements and useful lives.
Return loop · step 01 of 01
What governs it
In UK central government, appraisals should draw on evidence from previous evaluations. required
Applies to United Kingdom, central government
HM Treasury, The Green Book, 2026 edition, paragraph 1.10
HM Treasury’s evaluation guidance says the outputs and learning from earlier evaluations should be fed in at the rationale and objectives stage. required
Applies to United Kingdom, central government
HM Treasury, Magenta Book: Central Government guidance on evaluation, section 1.4
In UK central government, Gate 5 expects lessons to be provided to the departmental portfolio office for portfolio learning. required
Applies to United Kingdom, central government
Gate Review 5: Operational Review and Benefits Realisation (workbook), lessons
Where ISO 19650 is adopted, the appointing party compiles lessons learnt for future projects at project close-out. required
Binding only where it is adopted or contracted
UK BIM Framework, Information management according to BS EN ISO 19650, Guidance Part 2, Parties, teams and processes for the delivery phase of the assets, activity 5.8.2 (PDF page 18)
None of the external requirements the method relies on requires the organisation’s own operating cost and life data to feed its next estimate; this publication argues that they should, because reference-class forecasting depends on outturn data of exactly that kind. analysis
- Entry condition
Performance, benefits, renewal or disposal evidence exists.
- Inputs
Performance and cost comparisons, the benefits evaluation, the lives actually achieved, and information gaps found in operation.
- Activities
Send each item of evidence to a named destination, and record that it arrived.
- Outputs
Updated estimating data, requirements templates, useful-life assumptions and evaluation evidence.
- Evidence
A record of what was returned, to which destination, and when.
- Decisions
Which destinations the organisation maintains, and who owns each. your organisation decides
- Exceptions
Evidence with no destination is recorded as unreturned, not kept as a list of lessons nobody reads.
- Receiver
Whoever prepares the next need, case, estimate and tender.
- What returns
The loop closes when the next business case cites the evidence returned here.
Who acts
Asset managementprepares; technical owner
Who sends evidence back is the organisation’s choice. your organisation decides
Project developmentis notified; participant
Those preparing the next case are notified of what has been returned.
Financeis notified; participant
Finance is notified of lives achieved, for the annual review.
Records it uses
Link to this stepWhere this publication examines it
Who acts, by family
Twelve families of work, not job titles, each acting in one of three capacities. Each family below lists the steps at which it acts.
Capacities
- technical owner
- Owns the technical content of the step and answers for it.
- progression authority
- Holds the authority to let the lifecycle move past the step, or to stop it.
- participant
- Takes part without owning the content or deciding.
Actions
- prepares
- Produces the item and is answerable for its content.
- verifies
- Confirms the item against stated criteria and records how.
- reviews
- Examines the item and reports, without deciding on it.
- challenges
- May require an answer before the step proceeds; the answer is recorded.
- recommends
- Advises the family that decides, on the record.
- approves
- Exercises delegated authority to commit or to proceed.
- certifies
- Issues a certificate where a contract or rule assigns that act to it.
- accepts
- Agrees on the record that the item meets what it was asked for.
- becomes custodian
- Takes physical or informational care of the asset from this point.
- becomes accountable
- Answers for the outcome from this point, whoever holds custody.
- is notified
- Is told, with a record that the notice was given.
Sponsor or investment ownerOwns the reason for the investment and the outcome it is meant to produce.acts at 6 steps
- Need and outcomebecomes accountable; progression authorityyour organisation decides
- Options and business caserecommends; progression authorityyour organisation decides
- Sanction and the authority to stopbecomes accountable; progression authorityyour organisation decides
- Operational acceptanceis notified; participantanalysis
- Operating performance and cost evidenceis notified; participantanalysis
- Benefits realisationbecomes accountable; progression authorityanalysis
Project developmentTurns a need into options, a case and a definition that can be sanctioned.acts at 3 steps
- Need and outcomeprepares; technical owneryour organisation decides
- Options and business caseprepares; technical owneryour organisation decides
- Evidence returned to the next investment decisionis notified; participantanalysis
Project managementDirects delivery of the sanctioned scope to its baseline.acts at 8 steps
- Commitment: award and release of the baselinebecomes accountable; technical owneryour organisation decides
- Design basis control and design acceptanceapproves; progression authorityyour organisation decides
- Controlled baseline, change, deviation and configurationapproves; progression authorityyour organisation decides
- Certification and issue of the taking-over certificateis notified; participantyour organisation decides
- Outstanding work and defects after taking overapproves; progression authorityyour organisation decides
- Asset-information acceptanceis notified; participantanalysis
- Knowledge captureprepares; technical owneryour organisation decides
- Contract closeout: final certification and release of securityis notified; participantyour organisation decides
EngineeringOwns the design basis, the technical record and testing to it.acts at 4 steps
- Design basis control and design acceptanceprepares; technical owneryour organisation decides
- Controlled baseline, change, deviation and configurationverifies; participantanalysis
- Testing and commissioningprepares; technical owneryour organisation decides
- Testing and commissioningverifies; participantyour organisation decides
- Cessation of capitalisation and transfer from work in progressverifies; participantanalysis
Project controlsKeeps the baseline, measures progress and forecasts cost and time.acts at 2 steps
- Controlled baseline, change, deviation and configurationprepares; technical owneryour organisation decides
- Financial recognition and measurementverifies; participantanalysis
Commercial and procurementSets the contracting route, runs award and administers the contracts.acts at 4 steps
- Delivery and contracting strategyprepares; technical owneryour organisation decides
- Operating and information requirements into tenderprepares; technical owneryour organisation decides
- Commitment: award and release of the baselineprepares; technical owneryour organisation decides
- Application for taking overis notified; participantyour organisation decides
FinanceBudgets, pays, records and accounts for the asset.acts at 14 steps
- Options and business casereviews; participantyour organisation decides
- Sanction and the authority to stopis notified; participantyour organisation decides
- Design basis control and design acceptancereviews; participantanalysis
- Certification and issue of the taking-over certificateis notified; participantanalysis
- Transfer of care of the worksis notified; participantanalysis
- Entry in the technical asset registerverifies; participantanalysis
- Financial recognition and measurementprepares; technical owneryour organisation decides
- Cessation of capitalisation and transfer from work in progressapproves; progression authorityyour organisation decides
- Start of depreciationapproves; progression authorityyour organisation decides
- Contract closeout: final certification and release of securityapproves; progression authorityyour organisation decides
- Operating performance and cost evidenceverifies; participantanalysis
- Renewal or replacement decisionis notified; participantanalysis
- Disposal and derecognitionprepares; participantyour organisation decides
- Evidence returned to the next investment decisionis notified; participantanalysis
OperatorRuns and maintains the asset once it is in service.acts at 16 steps
- Need and outcomereviews; participantanalysis
- Options and business casechallenges; participantanalysis
- Delivery and contracting strategyreviews; participantanalysis
- Operating and information requirements into tenderreviews; participantanalysis
- Commitment: award and release of the baselineis notified; participantanalysis
- Design basis control and design acceptancereviews; participantanalysis
- Controlled baseline, change, deviation and configurationis notified; participantanalysis
- Testing and commissioningreviews; participantanalysis
- Certification and issue of the taking-over certificateis notified; participantanalysis
- Transfer of care of the worksbecomes custodian; technical owneryour organisation decides
- Outstanding work and defects after taking oververifies; participantanalysis
- Asset-information acceptanceverifies; participantanalysis
- Knowledge captureaccepts; participantanalysis
- Operational acceptanceaccepts; progression authorityyour organisation decides
- Operational acceptancebecomes accountable; technical owneryour organisation decides
- Contract closeout: final certification and release of securityverifies; participantanalysis
- Operation and maintenance under established requirementsprepares; technical owneryour organisation decides
Asset managementDecides how the asset base is managed over its life to meet objectives.acts at 9 steps
- Entry in the technical asset registerprepares; technical owneryour organisation decides
- Cessation of capitalisation and transfer from work in progressis notified; participantanalysis
- Start of depreciationrecommends; participantanalysis
- Operation and maintenance under established requirementsbecomes accountable; progression authorityyour organisation decides
- Operating performance and cost evidenceprepares; technical owneryour organisation decides
- Benefits realisationprepares; technical owneryour organisation decides
- Renewal or replacement decisionrecommends; technical owneryour organisation decides
- Disposal and derecognitionprepares; technical owneryour organisation decides
- Evidence returned to the next investment decisionprepares; technical owneryour organisation decides
Information or data ownerSets what information is required and accepts it into the receiving systems.acts at 4 steps
- Operating and information requirements into tenderprepares; technical owneranalysis
- Design basis control and design acceptancereviews; participantanalysis
- Application for taking overis notified; participantanalysis
- Asset-information acceptanceaccepts; progression authorityyour organisation decides
AssuranceExamines whether the other families did what the lifecycle required of them.acts at 4 steps
- Delivery and contracting strategyreviews; participantrequired
- Sanction and the authority to stopreviews; participantyour organisation decides
- Operational acceptancereviews; participantyour organisation decides
- Benefits realisationreviews; participantyour organisation decides
Gate or approving authorityHolds the delegated authority to let the lifecycle proceed, or to stop it.acts at 6 steps
- Delivery and contracting strategyapproves; progression authorityyour organisation decides
- Sanction and the authority to stopapproves; progression authorityyour organisation decides
- Operating and information requirements into tenderapproves; progression authorityyour organisation decides
- Commitment: award and release of the baselineapproves; progression authorityyour organisation decides
- Renewal or replacement decisionapproves; progression authorityyour organisation decides
- Disposal and derecognitionapproves; progression authorityyour organisation decides
Method records
Six blank records: decisions and their conditions, who holds authority, deliverables and their evidence, review findings through to closure, the obligations operation will carry, and the evidence operation returns. The first four were published with the method. They score nothing, rate nothing and read no other tool’s output. Every decision entered in them is the organisation’s, in its own words.
The records are blank. Nothing entered in them is sent to Projects Advisors or recorded by this site. Use them for your own organisation’s records; do not republish them as your own. What the licence allows
Lifecycle Control Pack
The Lifecycle Control Pack is the six records kept together: the four published with the method, the operating-obligation register and the outcome-feedback record. Each can be used on its own. Together they follow an obligation from the step that creates it into operation, and evidence from operation back to the next decision. analysis
The records cross-reference one another by identifier only. An obligation may point to the deliverable or decision on which it depends, and returned evidence may point to the decision that used it. No data or calculations pass between the records: no record copies or aggregates another record’s data, or uses it as an input to a calculation.
The six records, in the order the pack keeps them
- Lifecycle decision and conditions record Published with the methodWhat was decided, against which criteria, under whose authority, and on what conditions?
- Authority view Published with the methodWho may act at each step, in which capacity, and on what authority?
- Deliverable and evidence register Published with the methodWhat was required, who delivered and accepted it, and against which criteria?
- Operating-obligation register Added with the Control PackWhich obligations will operation carry, where did each come from, and who carries it?
- Outcome-feedback record Added with the Control PackWhat did operation show against what was assumed, where was it sent, and was it used?
- Finding, response and closure record Published with the methodWhat did the review find, what limited it, what was the reply, and is it closed?
Excel workbook of all six records, one sheet each in the order listed here, with headings and no data. The Arabic Control Pack workbook
Excel workbook of the four records published with the method, one sheet each, with headings and no data. The Arabic workbook
Published with the method
Lifecycle decision and conditions record
The question it answers What was decided, against which criteria, under whose authority, and on what conditions?
All 13 fields, with what each holds
Fields of the lifecycle decision and conditions record Field What it holds Set by Entry Lifecycle step The step at which the decision is taken, named as the method names it, so that the record can be found from the step.
The method Decision requested What the decision-maker was asked to decide, as the request put it, before any answer was given.
The method Options considered The options put to the decision-maker, including doing the minimum where that was one of them.
The method Criteria, and where each came from The criteria the decision was to be taken against, each with its origin: an external requirement, the business case, the organisation’s policy or the decision-maker.
The method Evidence relied on The documents and records the decision relied on, by reference, so that they can be retrieved as they stood when it was taken.
The method Decision taken, in the organisation’s words What was decided, as the organisation recorded it.
The method Authority exercised, and by which family The authority exercised, and the function family that exercised it.
The method Delegation reference The reference to the organisation’s own delegation under which that authority was held.
Your organisation Conditions attached Each condition attached to the decision, written so that whether it has been met can later be shown.
The method Owner of each condition Who answers for meeting each condition.
The method Date each condition must be met The date by which each condition is to be met.
A date.
The method Recorded dissent Any dissent a participant recorded, as they put it, and who recorded it.
The method Date the decision is to be reviewed When the decision is to be looked at again, where the organisation sets such a date.
A date.
Your organisation Exceptions and matters not yet decided
A decision taken outside the delegation, or without the information its criteria called for, is recorded as it was taken, with the gap stated; the record is not completed after the event to make the decision look as it should have been.
A condition not met by its date stays on the record with its owner until it is met or the decision is taken again; a question nobody has yet decided is not entered as a decision.
Where management accepts a risk or a departure instead of acting on a finding, the acceptance is recorded in the lifecycle decision record with its conditions, or as a deviation or concession, together with the authority that accepted it; it is not a separate findings record.
projects-advisors.com/method · The records are blank. Nothing entered in them is sent to Projects Advisors or recorded by this site. Use them for your own organisation’s records; do not republish them as your own.
Published with the method
Authority view
The question it answers Who may act at each step, in which capacity, and on what authority?
All 7 fields, with what each holds
Fields of the authority view Field What it holds Set by Entry Lifecycle step The step the assignment applies to, named as the method names it.
The method Function family The family of work that acts at the step, from the method’s twelve; a family, not a job title.
The method Action What the family does at the step, in the method’s words: prepares, verifies, reviews, challenges, recommends, approves, certifies, accepts, becomes custodian, becomes accountable or is notified.
The method Capacity The capacity in which the family acts: owner of the technical content, holder of the authority to let the lifecycle proceed, or participant.
One of: technical owner, progression authority, participant.
The method Basis of the assignment Where the assignment comes from: the organisation’s delegation, a contract, or a regime that requires it.
The method Delegation reference The reference to the delegation, contract clause or rule that makes the assignment.
Your organisation Who holds it in this organisation The post or unit that holds the assignment in the organisation.
Your organisation Exceptions and matters not yet decided
An assignment the step needs and nobody holds is recorded as a gap against the step, not left blank, so that the step cannot proceed on an authority nobody was given.
Where one post holds both the technical ownership and the authority to proceed at the same step, the view records that as the organisation’s decision and who made it, rather than merging the two capacities.
projects-advisors.com/method · The records are blank. Nothing entered in them is sent to Projects Advisors or recorded by this site. Use them for your own organisation’s records; do not republish them as your own.
Published with the method
Deliverable and evidence register
The question it answers What was required, who delivered and accepted it, and against which criteria?
All 13 fields, with what each holds
Fields of the deliverable and evidence register Field What it holds Set by Entry Identifier The organisation’s identifier for the deliverable, unique within the register.
Your organisation Deliverable What is to be delivered: a document, a model, a test record, a manual, training, spares or data.
The method Where it was required Where the deliverable was required, with its clause: the contract, the information requirements, a specification or a rule.
The method Lifecycle step The step at which the deliverable is due or relied on.
The method Prepared by Who prepares the deliverable.
The method Verified by Who checks it against its acceptance criteria, where that is a different party.
The method Accepted by Who accepts it for the organisation.
The method Receiving system The system or register the deliverable is accepted into, such as the asset register, the maintenance system or the document store.
Your organisation Acceptance criteria, as set before tender The criteria for accepting the deliverable as they stood when the tender was issued, so that acceptance is tested against what was asked for.
The method Acceptance decision, as the organisation recorded it The acceptance decision in the organisation’s own words, with any conditions attached to it.
The method Date made The date this entry was made.
A date.
The method Made by Who made this entry.
The method Retention How long the deliverable is kept, under the organisation’s own retention rules.
Your organisation Exceptions and matters not yet decided
A deliverable not yet received, or received and not accepted, stays on the register with its owner until it is resolved; it is not removed to make the register look complete.
Where a deliverable is accepted against criteria other than those issued with the tender, the entry records the change and who approved it.
projects-advisors.com/method · The records are blank. Nothing entered in them is sent to Projects Advisors or recorded by this site. Use them for your own organisation’s records; do not republish them as your own.
Added with the Control Pack
Operating-obligation register
The question it answers Which obligations will operation carry, where did each come from, and who carries it?
All 17 fields, with what each holds
Fields of the operating-obligation register Field What it holds Set by Entry Identifier The organisation’s identifier for the obligation, unique within the register.
Your organisation Obligation What must be done, kept, provided or paid, written so that whether it is being met can later be shown.
The method Asset, system or component What the obligation attaches to, by the organisation’s own identifier.
Your organisation Step that created it The lifecycle step at which the obligation was created, named as the method names it.
The method What sets it, with its clause The contract, the requirements issued with the tender, a condition of a recorded decision, an accounting standard, a law, or the organisation’s own policy, with the clause or paragraph.
The method Carried by The party that carries the obligation now.
The method Allocation Whether a named party carries the obligation. An obligation nobody carries is entered as such, not left out.
One of: allocated to a named party, not yet allocated.
The method Inherited in operation by The party that will carry the obligation in operation, where it is not the party that carries it now.
The method Receiving system The system in which operation will hold the obligation, such as the maintenance system or the contract register.
Your organisation Event that starts the obligation The event at which the obligation begins, as specified by the instrument that creates it. Taking over, transfer of care, operational acceptance, register entry, recognition, capitalisation, depreciation and closeout are distinct; none replaces another.
The method Date of that event The date on which the event that starts the obligation occurred.
A date.
The method When it ends, or how often it recurs When the obligation ends, or the interval at which it recurs, as set by the instrument that creates it.
The method Related entry in another record The identifier of the entry the obligation depends on in another record, such as a deliverable or a condition of a decision. A cross-reference only: no data are copied from it and nothing is calculated from it.
The method Evidence it is being met Dated evidence, recorded by operations, that the obligation continues to be met.
The method Discharged on The date the obligation ended or was discharged, on that evidence.
A date.
The method Date made The date this entry was made.
A date.
The method Made by Who made this entry.
The method Exceptions and matters not yet decided
An obligation first found in service is entered against the step that should have created it, with the date it was found; it is not dated back to that step.
A condition attached to a decision stays in the decision and conditions record. The register holds an obligation only where it continues beyond the decision, and points back to the decision’s entry.
An obligation that no party has been allocated is recorded as unallocated and goes to the decision-maker, not left to be found at handover.
In Delivery and contracting strategy
Obligations still unfulfilled at final certification are listed, since liability for them survives it.
In Contract closeout: final certification and release of security
A requirement found unworkable in service is recorded and returned to the requirements template.
projects-advisors.com/method · The records are blank. Nothing entered in them is sent to Projects Advisors or recorded by this site. Use them for your own organisation’s records; do not republish them as your own.
Added with the Control Pack
Outcome-feedback record
The question it answers What did operation show against what was assumed, where was it sent, and was it used?
All 14 fields, with what each holds
Fields of the outcome-feedback record Field What it holds Set by Entry Identifier The organisation’s identifier for the entry, unique within the record.
Your organisation Step the evidence came from The lifecycle step at which the evidence arose, such as operating performance and cost, benefits realisation, a review of useful life, renewal or disposal.
The method Asset, system or component What the evidence is about, by the organisation’s own identifier.
Your organisation What was assumed, and where What the earlier estimate, business case, requirement or useful-life assumption said, with a reference to the document that said it.
The method What operation showed What operation showed, over which period, and who measured it, entered as found. Nothing is calculated between this and what was assumed.
The method Cause of any difference, where known The cause of a difference between the two, where it is known.
The method What limits the comparison What limits the comparison, such as missing or unconfirmed records, a change of scope, or a period too short to show the effect.
The method Records relied on The records the entry relies on, by reference, so that they can be retrieved as they stood.
The method Sent to Where the evidence is sent: estimating data, a requirements template, useful-life assumptions, an evaluation, or the appraisal of a later proposal.
Your organisation Owner of that destination Who owns the destination the evidence is sent to.
Your organisation Sent on The date the evidence was sent.
A date.
The method Arrival recorded on The date its arrival was recorded at the destination.
A date.
The method Used in The later decision, estimate or requirement that used the evidence, by reference.
The method Reason given for not using it Where the receiving decision did not use the evidence, the reason it gave.
The method Exceptions and matters not yet decided
A difference between what was assumed and what was observed is entered as found. The record does not calculate the difference, and passes no judgement on the estimate or on whoever made it.
Evidence with no destination is recorded as unreturned, not kept as a list of lessons nobody reads.
In Evidence returned to the next investment decision
Where the records cannot support a comparison, that is reported as a finding, not filled by estimate.
projects-advisors.com/method · The records are blank. Nothing entered in them is sent to Projects Advisors or recorded by this site. Use them for your own organisation’s records; do not republish them as your own.
Published with the method
Finding, response and closure record
The question it answers What did the review find, what limited it, what was the reply, and is it closed?
All 17 fields, with what each holds
Fields of the finding, response and closure record Field What it holds Set by Entry Identifier The organisation’s identifier for the record.
Your organisation Record type Which of the four kinds of record this is. A question the review has not yet answered is none of them.
One of: evidenced finding, limitation, disagreement, recommendation.
The four record types are the method’s arrangement of what the review standards ask to be reported separately: evidenced findings, limitations, disagreements and recommendations.
Reasoned from Government Auditing Standards, 2024 revision, GAO-24-106786, Comptroller General of the United States, paragraphs 8.116, 9.20, 9.23 and 9.52; INTOSAI, ISSAI 3000, Performance Audit Standard, Requirement 130
The method Governing regime, if any The standards or rules the review is carried out under, where one governs it.
The method Step, domain and test examined The lifecycle step, the framework domain and the test the record concerns.
The method Criteria, where relevant to the objectives What the condition was compared with, where the review’s objectives call for it.
The method Condition found, where relevant to the objectives What was found, where the review’s objectives call for it.
The method Cause, where established and relevant Why the condition exists, where that was established and matters to the objectives.
The method Effect, where established and relevant What the condition leads to, where that was established and matters to the objectives.
The method Limitations on the evidence What limited the evidence, so that the record claims no more than the evidence supports.
The method View of the responsible party The view of the party whose work was examined, recorded beside the finding and not merged into it.
The method Reviewer’s reasons for disagreeing, where it applies Where the reviewer disagrees with that view, the reviewer’s reasons.
The method Management response What management says it will do, or why it will not act.
The method Organisation’s own classification, if it uses one The organisation’s own classification of the record, where it uses one.
Whether to classify results, and on what scheme, is the organisation’s choice; the method supplies no scale. your organisation decides
Your organisation Action owner Who owns each agreed action.
The method Due date When each action is due.
A date.
The method Closure evidence, dated The dated evidence, obtained after the action, that the condition has changed.
The method Closed on The date the record was closed on that evidence.
A date.
The method Exceptions and matters not yet decided
A question the review has not yet answered stays in the review’s internal issues log and is not a findings record; if it still limits a conclusion when the report is issued, it is reported as a limitation.
In Recording what the testing found
Where management accepts a risk or a departure instead of acting on a finding, the acceptance is recorded in the lifecycle decision record with its conditions, or as a deviation or concession, together with the authority that accepted it; it is not a separate findings record.
In Management response and disagreement
Because follow-up is an examination of what was done, closure rests on evidence obtained after the action, not on management’s statement that it was taken.
projects-advisors.com/method · The records are blank. Nothing entered in them is sent to Projects Advisors or recorded by this site. Use them for your own organisation’s records; do not republish them as your own.
Adopting the method
How an organisation starts to use the method, including partway through a programme already under way. Each step says what is done, and marks what the organisation decides.
The review method
Any part of this lifecycle can be reviewed. The review method sets out how a reviewer, independent or internal, scopes, tests, reports and follows up, under whichever rules govern the review.
Sources
- ISO/TC 251, Updated Guidance on Asset Management System Requirements, ISO 55001:2024 Rev 3; read 2026-09-26. Free. The committee stating why each 2024 change was made.
- ISO/TC 251 Asset management, ISO 55001 project page ISO 55001:2024, key changes for the 2024 edition; read 2026-10-01. Free. The committee’s own list of what changed in the 2024 edition, clause by clause; not the requirement text.
- ISO/TC 251, ISO 55001:2024 update overview (presentation hosted by the Institute of Asset Management) 13 August 2024, conference presentation; read 2026-10-01. Free. The committee’s slides on the 2024 changes; a summary of the standard, not its text.
- HM Treasury, The Green Book, 2026 edition 2026 edition, published 5 February 2026; read 2026-09-05.
- HM Treasury, International Guide to Developing the Project Business Case 2018; read 2026-09-24. Free in full. The Five Case Model as HM Treasury published it for use outside the United Kingdom; the financial case exists to demonstrate affordability and funding and to resolve funding gaps across the life span of the scheme. EXPRO’s Outline and Full Business Case procedures list it as their first reference. Read 24 September 2026.
- Gate 2 Review: Delivery Strategy (workbook) gov.uk workbook, updated 20 August 2026; read 2026-10-01. Free. The questions a UK central government Gate 2 review asks of a delivery strategy before commitments are made to suppliers.
- Government Tenders and Procurement Law, new law published in Umm Al-Qura 22/3/1448 (4 September 2026), Arabic gazetted 4 September 2026; in force 120 days after publication; read 2026-09-05. Free in full, 101 articles, in the Official Gazette. Article 100 replaces Royal Decree M/128 (1440); Article 101 brings it into force 120 days after publication; Article 99 requires new Executive Regulations within the same period. Article 2 names life cycle cost, execution quality, operational efficiency and risk management among the law’s objectives. Article 59, read on 25 September 2026, keeps the final guarantee at 5% of the contract value, lodged within 15 working days of notice of the award and held until the contractor has performed its obligations and the project is finally received. Read on 5 September 2026.
- Gate 4 Review: Readiness for Service (workbook) gov.uk workbook, updated 20 August 2026; read 2026-10-01. Free. The current edition of the readiness for service workbook; the earlier OGC edition is listed separately.
- EXPRO, National Manual for Projects Management, EPM-KTC-PR-000001, Project Turnover of Facility/Infrastructure Procedure EPM-KTC-PR-000001, Rev 003; read 2026-10-01. Free from the authority’s knowledge centre, as one procedure of the national manual. It applies to government entities that use the national manuals.
- UK BIM Framework, Information management according to BS EN ISO 19650, Guidance Part 2, Parties, teams and processes for the delivery phase of the assets Edition 6, February 2021; read 2026-10-01. Free in full. The UK BIM Framework’s guidance on the delivery phase under ISO 19650: how information requirements are issued with the tender, and how the appointing party reviews and accepts what is delivered. The method’s statements about ISO 19650 rest on this guidance.
- UK BIM Framework, Information management according to BS EN ISO 19650, Guidance Part 3, Operational phase of the asset life-cycle, edition 1 UK BIM Framework guidance, current series; read 2026-09-25. Free in full, published September 2020 by the UK BIM Framework with BSI permission to quote the standard. This is the nearest thing the series has to a published rationale, and it is where the standard is described as voluntary and as conveying no obligation unless a contract or an organisational policy creates one. It also names the transfer of information from the project information model to the asset information model at the start of the operational phase, which is the turnover package under its proper name.
- Gate 3 Review: Investment Decision (workbook) gov.uk workbook, updated 20 August 2026; read 2026-10-01. Free. The questions a UK central government Gate 3 review asks before the investment decision and contract award.
- Howard Kennedy, FIDIC 2017: Clause 5, Design FIDIC 2017 second edition, clause commentary; read 2026-10-01. Free. Howard Kennedy’s commentary on Clause 5, the contractor’s design obligations under the 2017 forms. The method relies on it for one point, as the commentary summarises Sub-Clause 5.2: approval or review of the Contractor’s Documents does not relieve the Contractor of any obligation or responsibility.
- Tyson, FIDIC 2017: Clause 10, Employer’s Taking Over, Howard Kennedy FIDIC 2017 second edition, clause commentary; read 2026-10-01. Free. Tyson’s commentary on Clause 10, taking over under the 2017 forms. The method relies on it for two points, as the commentary summarises them: what Sub-Clause 10.1 requires for taking over, and what a taking-over certificate for a part identifies under Sub-Clause 10.2.
- Saudi Government Tenders and Procurement Law and its Executive Regulations, consolidated Arabic text, third edition third edition, the law in force until the new law takes effect; amendments to the regulations after this edition are not consolidated in it; linked as the Internet Archive’s copy of 1 October 2026 since the Ministry moved its site; read 2026-11-02. Free in full, in Arabic, from the Ministry of Finance: each article of the 2019 Law printed beside the regulations that implement it, 117 pages. The enacted text on securities and receipt. Law Article 61(1) sets the final guarantee at 5% of the contract value within 15 working days of notice of the award, and 61(4) keeps it until the contractor has performed its obligations and the project is finally received. Regulations Article 101 requires the final guarantee to be extended in construction contracts where maintenance and warranty work runs «لما بعد انتهاء سنة الضمان المشار إليه في الفقرة (1) من المادة (الثامنة والعشرين بعد المائة)»; Article 111 pays a final statement of not less than 10% in public construction contracts after initial receipt; Article 128 sets a warranty period of not less than one year from initial receipt, keeps the warranty for shortcomings not dealt with at initial receipt, and makes final receipt follow the end of that period and the delivery of drawings, equipment specifications and project documents.
- EXPRO, National Manual for Projects Management, EPM-KD0-PR-000019, Preliminary and Final Handover Procedure EPM-KD0-PR-000019, Rev 004; read 2026-10-01. Free from the authority’s knowledge centre, as one procedure of the national manual. It applies to government entities that use the national manuals.
- Cotovelea, Tsaturova and Glover, Differences between the Civil and Common Law, Part 2: Delay Damages and Taking-Over slides 2 and 9, conference presentation; read 2026-09-25. Free, a conference presentation published by FIDIC. Slide 2 quotes Sub-Clause 10.1 on taking over, and slide 9 quotes Red Book Sub-Clause 11.9: only the Performance Certificate is deemed to constitute acceptance of the Works.
- Tyson, FIDIC 2017: Clause 11, Defects After Taking Over, Howard Kennedy FIDIC 2017 second edition, clause commentary; read 2026-09-25. Free. A clause-by-clause commentary that quotes the periods, including the two-year cap on extending the DNP. It also lists a Notice of No-objection to the as-built records as a new precondition to the Performance Certificate. That is the position in the 2017 Yellow and Silver Books, whose Sub-Clause 11.9 adds it. The 2017 Red Book differs: its Sub-Clause 10.1 makes the as-built and O&M No-objection conditions, where they apply, conditions of taking over, and its Sub-Clause 11.9 does not add that Notice.
- IPSAS 45, property, plant and equipment 2023, effective 1 January 2025; read 2026-09-01. Free in full, with its Basis for Conclusions in the same document. Replaced IPSAS 17 from 1 January 2025.
- IPSASB, 2025 Handbook of International Public Sector Accounting Pronouncements 2025 edition, published 5 May 2025; read 2026-11-02. Free to download, in three volumes. It carries the standards as published to 31 January 2025, among them IPSAS 5 on borrowing costs, IPSAS 19 on provisions, IPSAS 21 and IPSAS 26 on impairment, and IPSAS 44 on assets held for sale.
- Commission Regulation (EU) 2023/1803 adopting certain international accounting standards OJ L 237, 26 September 2023; read 2026-11-02. Free, Official Journal text. The IAS and IFRS standards and the IFRIC interpretations as adopted in the European Union, in one annex, including IAS 16, IAS 23, IAS 36, IAS 37, IAS 40, IFRS 1, IFRS 5 and IFRIC 1. Amendments the IASB issued after the Regulation are not in it.
- Saudi Ministry of Finance, comprehensive manual for the census and valuation of assets of government entities, Arabic Second edition, approved 10 September 2022; the rendering the Ministry hosted, linked as the Internet Archive’s copy of 23 September 2026 since the Ministry moved its site; read 2026-11-02. Free, in Arabic only. Section 5.2, pages 78 to 152, prints the classification of non-current assets with a capitalisation threshold and a minimum, maximum and default useful life for each asset type. Page 76 asks each entity to set its lives within the published range, taking account of the manufacturer, the use and the expected benefit, and to submit them to the central committee for approval. English asset names on this site are a Projects Advisors translation.
- OECD, Recommendation of the Council on the Governance of Infrastructure OECD/LEGAL/0460, 17 July 2020; read 2026-10-01. Free in full. A recommendation to the governments that adhere to it; it binds no organisation.
- Gate Review 5: Operational Review and Benefits Realisation (workbook) gov.uk workbook, updated 20 August 2026; read 2026-10-01. Free. The questions a UK central government Gate 5 review asks once the asset is in operation, including whether the expected benefits are being realised.
- HM Treasury, Magenta Book: Central Government guidance on evaluation May 2026; read 2026-10-01. Free in full. HM Treasury’s guidance on evaluation in UK central government, the companion to the Green Book.
- Government Auditing Standards, 2024 revision, GAO-24-106786, Comptroller General of the United States 2024 revision; read 2026-09-04. Free in full. Effective for performance audits beginning on or after 15 December 2025.
- INTOSAI, ISSAI 3000, Performance Audit Standard ISSAI 3000, 2019; read 2026-10-01. Free in full. The requirements for performance audits carried out by supreme audit institutions that apply the ISSAIs; it binds no other reviewer.