Australian Defence construction project lifecycle from design through handover to operations
Pillar Guide

Defence Handover in Australia: The Complete Guide

Defence handover in Australia is the structured process for transferring a completed construction project from the contractor to the Department of Defence and the EMOS facility-management contractor responsible for operating the asset. It sits at the intersection of three frameworks: ERIK governing quality, HOTO governing the handover process itself and EMOS governing ongoing operations. This guide walks the full lifecycle in order.

By Updated 15 min read

Why this guide exists

If you’ve landed here, you’re probably one of three people:

  • A project manager on your first Defence construction project, trying to make sense of a dozen overlapping acronyms
  • An experienced commercial-construction PM who’s just been handed a Defence subcontract and discovered the rules are different
  • A subcontractor whose Managing Contractor has told them “you need to be ERIK-compliant” without explaining what that means

Defence handover is not unusually difficult, it’s unusually structured. Every artefact has a template, every approval has a defined role, every transition has a checklist. What makes it feel hard is that no single resource walks the full lifecycle in one place. This guide does.

We’ll cover: the five phases of a Defence construction project, the three frameworks that govern them, the roles you’ll encounter and the practical questions that come up most often. Each section links to dedicated guides for deeper coverage.

The Defence Handover Lifecycle

A typical Defence construction project moves through five phases. Each has its own deliverables, its own roles and its own framework citations.

Phase What happens Governing framework
1. Planning & Pre-ConstructionQMP, HOTO Management Plan, contract templates, security clearancesERIK + SoFC
2. ConstructionBuild work, concurrent evidence gathering, ITPs, NCRsERIK + HOTO v6.3 Construction template
3. Practical Completion & HOTOEvidence Folder finalisation, acceptance walkthroughs, defect listHOTO + ERIK acceptance
4. Defects Liability Period (DLP)12-24 months of defect rectification under original ContractorDLP terms + EMOS coordination
5. Estate Operations under EMOSLong-term operation, maintenance, lifecycle planningEMOS + PAS framework

The phases overlap. HOTO evidence collection (Phase 3 documentation) begins in Phase 1 and runs through Phase 2. EMOS contractor engagement (Phase 5) begins in Phase 1 because they need briefing on what they’ll inherit. Treating the phases as strictly sequential is the most common project-management mistake on Defence work.

Phase 1: Planning & Pre-Construction

The phase that determines whether the project succeeds or scrambles at HOTO. Defence-specific activities here:

Quality Management Plan (QMP) development. The Managing Contractor produces an ERIK-compliant QMP covering scope, roles, document control, audit programme, ITP framework, NCR handling and HOTO development plan. Defence reviews the QMP before construction starts; weaknesses here propagate forward.

HOTO Management Plan. Establishes which HOTO Evidence Folder version applies (v6.3, v7.1, or v7.3 depending on contract age), which Defence template (OMM Buildings, OMM Base Infrastructure, GDL) and who fills the Consultant HOTO role.

Subcontractor briefings on ERIK obligations. This is the step most contractors skip. ERIK quality flows down through subcontract terms whether or not subcontractors know it. Briefing them at award, not at HOTO, prevents 80% of late-stage compliance scrambles.

Security clearances. AGSVA-issued clearances for any staff working on sensitive sites. Lead times 3-12 months. Plan tender responses around clearance availability.

EMOS contractor identification. Knowing which prime EMOS contractor (Downer, Ventia, BGIS, Serco, Cushman & Wakefield) will inherit the asset informs O&M Manual structure, CMMS data formats and DAMIS schema decisions.

Deeper coverage: ERIK Explained covers QMP structure, ITP framework and contract templates in detail.

Phase 2: Construction

The longest phase by duration. Defence-relevant activities run alongside the build:

Concurrent evidence gathering. The HOTO Evidence Folder v6.3 Construction template defines what must be captured during construction rather than retrofitted at the end. Commissioning records, signed witness sheets, as-built drawing updates, NCR closures, manufacturer literature and warranty paperwork, all collected as work completes, not before HOTO.

ITP execution. Inspection and Test Plans are executed per discipline. Each ITP defines hold points (must stop until inspected) and witness points (must notify for inspection). Defence or Defence’s appointed Superintendent attends key hold points.

NCR raising and closure. When work doesn’t meet specification, a Non-Conformance Report is raised. Closure requires corrective action and verification evidence. Open NCRs at HOTO trigger acceptance delays.

Asset register population. Asset records are built progressively against the DAMIS-compatible schema. Retrofitting at HOTO is impossible at scale. Defence requires DAMIS-aligned identifiers and attributes from the first asset entered.

Subcontractor submission discipline. This is where platforms like Procom matter most. Subcontractors submitting via a portal that enforces the Defence template structure produce ERIK-compliant submissions on the first attempt. Subcontractors submitting via email and shared drives produce submissions that need rework at HOTO.

Deeper coverage: ERIK guide for the full Construction-phase quality framework.

Phase 3: Practical Completion & HOTO

The phase that gets contractors in trouble. Activities concentrate over a 4-8 week window:

Evidence Folder finalisation. The Managing Contractor consolidates subcontractor evidence into the unified HOTO Evidence Folder structure. Cross-references checked, signatures verified, as-built drawings reconciled with closed NCRs.

Consultant HOTO review. Where appointed, the Consultant HOTO reviews and approves the Evidence Folder before submission to Defence. Acts as a second-line check between the Contractor’s quality team and Defence acceptance.

Defence acceptance walkthroughs. Defence reviewers (and often the incoming EMOS contractor) walk through the Evidence Folder section by section. Defects raised are categorised: rectify before Practical Completion, or defer into the DLP.

Practical Completion certification. When Defence accepts the Evidence Folder, Practical Completion is certified. This triggers: warranty start dates (from Practical Completion, not install date), DLP clock start, retention release schedule and transition to the EMOS contractor.

The HOTO Checklist v7.3. The most current checklist (3503_HOTOPLANCHECKLIST_V7.3.xlsx) defines several dozen evidence items. Procom’s platform displays the v7.3 requirements inline with each node via the HOTO Help Information System.

Deeper coverage: The HOTO Process for Australian Defence Construction.

Phase 4: Defects Liability Period

The 12-24 month period after Practical Completion. Activities here are reactive rather than scheduled:

Defect intake. The EMOS contractor’s CMMS, tenant unit reports and Defence estate team feedback identify defects. Each is traced back to the original installing subcontractor for rectification.

Categorisation and triage. Defects are categorised (typically client-raised, builder-raised, trade-raised or tenant-raised) with importance levels (low / medium / high / urgent). Importance drives the response-time SLA per contract terms.

Subcontractor rectification. The original installing subcontractor performs the rectification under their DLP obligations. Documentation of rectification work feeds back into the Evidence Folder for Final Completion.

Escalation when rectification stalls. Defects exceeding response-time thresholds escalate to the Managing Contractor and Defence project team. Repeated unresolved defects can trigger withholdings.

Final Completion. At the end of DLP, when all defects are rectified, Final Completion is certified. The Contractor’s project-level liability ends; full operational responsibility transitions to the EMOS contractor.

Deeper coverage: See our DLP Maintenance Services page for how Procom handles the defects workflow during DLP.

Phase 5: Estate Operations under EMOS

The phase that runs forever (or at least for the asset’s operational life). Activities here are outside the original Contractor’s scope but inform decisions made in Phases 1-4:

Routine and reactive maintenance. The EMOS prime contractor delivers day-to-day FM: building services, mechanical and electrical systems, grounds, infrastructure. They consume the O&M Manual and asset register every working day.

Condition assessments. Periodic condition audits inform Defence capital planning. Assets approaching end-of-life are flagged for replacement under the Estate Works Program or future CFI projects.

Asset record maintenance in DAMIS. Asset attributes change over time: components replaced, capacity upgraded, status changed. The EMOS contractor maintains DAMIS records; bad initial asset data at HOTO acceptance creates ongoing operational pain for years.

Lifecycle planning. Long-term replacement and refurbishment programmes are planned over 5-50 year horizons. This is the domain of strategic asset management tools; Procom doesn’t compete here, but the data quality decisions made at HOTO feed directly into these tools’ inputs.

Deeper coverage: EMOS Defence Explained.

Roles & Frameworks at a Glance

Role ERIK responsibility HOTO responsibility EMOS responsibility DLP responsibility
Defence project teamReviews QMP, audits complianceAccepts Evidence FolderSets EMOS performance regimeApproves DLP closure
Managing ContractorDevelops QMP, integrates ITPsOwns Evidence Folder, manages submissionBriefs incoming EMOS contractorCoordinates subcontractor rectification
Head Contract subcontractorMaintains discipline QMPProvides discipline evidenceHands off to EMOS contractorPerforms warranty rectification
Subcontractor (trade)Inherits via flow-downProvides evidence to Managing Contractorn/aRectifies own scope defects
Consultant HOTOn/aReviews and approves Evidence Foldern/an/a
SMEn/aApproves discipline-specific evidencen/an/a
EMOS prime contractorAdheres to ERIK for ongoing FMAccepts asset at HOTO walkthroughOperates the assetReports DLP defects, manages rectification scheduling
Tenant unit / EMOS/PPSn/aProvides feedback at acceptanceDay-to-day end-userReports defects

Framework reference list: ERIK · HOTO · EMOS · DLP · SoFC · PAS · DAMIS · O&MM

For full definitions of any term, see our Glossary of Australian Defence Construction Handover Terms.

Where Procom Fits in the Handover Lifecycle

Procom Solutions provides a platform built around the Defence handover lifecycle. Specifically:

  • Phase 1 (Planning). Pre-configured Defence templates (OMM Buildings v1.2, OMM Base Infrastructure v1.2, HOTO Evidence Folder v5.5/v6.1/v6.3/v7.1, GDL) so QMP development and HOTO Management Plan creation start from a structurally-correct baseline.
  • Phase 2 (Construction). Subcontractor submission portal with QR-code onboarding and the HOTO Help Information System displaying v7.3 evidence requirements inline. Uploads missing required metadata are blocked at the upload step.
  • Phase 3 (HOTO). A four-tier Defence approval workflow that routes every Evidence Folder item through project review, Consultant HOTO internal review and SME dual approval before final client acceptance. OMM Volume Splitting per SEG v2.0 §40-42 for compliant large exports. Activity audit trail for Defence-grade auditability.
  • Phase 4 (DLP). Mobile-first defect tracking with importance-based escalation, automated reminders and full integration into the manual structure so each defect traces back to its originating Evidence Folder section.
  • Phase 5 (EMOS handoff). Multi-format export (PDF, DOCX, HTML, XLS) so the EMOS contractor’s CMMS can consume the data in whatever format their tooling requires.

Procom is not an FM/CAFM platform. It doesn’t replace the EMOS contractor’s CMMS or strategic asset management tools. It is the platform that prepares for the EMOS contractor’s needs during construction and DLP, then hands off cleanly. Learn more about Procom’s Defence O&M Manual Platform.

Frequently Asked Questions

What is Defence handover in Australia?

Defence handover is the structured transfer of a completed construction project from the contractor to the Department of Defence and the EMOS facility-management contractor responsible for operating the asset. It involves three frameworks: ERIK for quality, HOTO for the handover process itself, and EMOS for ongoing operations.

How long does a Defence handover take?

The HOTO submission and acceptance phase typically runs 4-8 weeks if evidence collection has run concurrently with construction. Adding the DLP, the full handover-to-Final-Completion cycle is 18-30 months from Practical Completion. Projects that retrofit HOTO evidence at the end commonly run 3-6 months over their original Practical Completion target.

What's the difference between ERIK, HOTO, and EMOS?

ERIK is the quality framework (the standards). HOTO is the handover process (the moment of transfer). EMOS is the operational framework (what happens after handover). All three apply to a Defence construction project; conflating them leads to scope confusion.

Who is responsible for the Defence handover?

The Managing Contractor (or Head Contractor on Head Contract projects) is the prime party. Subcontractors provide discipline-specific evidence under flow-down obligations. Consultant HOTO and SMEs review. EMOS contractor confirms operational readiness. Defence accepts.

What is the HOTO Plan and Checklist v7.3?

The current public Defence HOTO Plan and Checklist defines required evidence per project node. The version specified in your contract is the version that applies; never assume the latest version is in use.

Do I need AGSVA security clearance for Defence construction work?

Often yes, depending on the site sensitivity. Clearance levels: Baseline, Negative Vetting 1 (NV1), Negative Vetting 2 (NV2). Lead times 3-12 months. Plan tender responses around clearance availability. Don't bid for work requiring NV1 clearances you can't produce on time.

How does the Defects Liability Period work on Defence projects?

The DLP runs 12-24 months from Practical Completion. During this period, the installing contractor remains liable for defect rectification in their work scope. Defects are typically reported via the EMOS contractor's CMMS and traced back to the original subcontractor for rectification.

Why is so much Defence terminology in acronyms?

Defence is a large, conservative organisation whose documentation has evolved over decades. The acronym density reflects the structure of the underlying contract suite (SoFC) and the layered programmes (PAS, EMOS, CFI, Estate Works) that govern different scopes of work. Our glossary defines every term you're likely to encounter.

Related reading

This guide was last updated on 20 May 2026. Procom Solutions is a Brisbane-based provider of construction handover and O&M manual compilation software, with experience supporting Australian Defence construction projects across Capital Facilities Infrastructure and the Estate Works Program. We have no affiliation with the Department of Defence. For official Defence handover guidance, refer to defence.gov.au.

See how Procom handles the full Defence handover lifecycle

Book a 20-minute walkthrough using a sample Defence project. We’ll show how the platform structures evidence collection, manages the four-tier approval workflow and produces a HOTO Evidence Folder that Defence accepts on first submission.