What does HOTO stand for?

HOTO stands for Handover/Takeover. It is the Australian Department of Defence's process for transferring a completed construction project from the contractor to Defence and the EMOS facility-management contractor responsible for ongoing operations.

How is HOTO different from a standard construction handover?

A standard private-sector handover transfers keys, as-builts, and a defect list. Defence HOTO requires structured evidence against the HOTO Plan and Checklist and HOTO Data Provision Checklist, including ERIK quality compliance, asset records, training and operational readiness, and acceptance by the downstream EMOS contractor.

Which HOTO Plan and Checklist version applies to my project?

The version is specified in the project's Head Contract. As of mid-2026, v7.3 is the most current public version. Projects signed earlier may still use v5.5, v6.1, v6.3, or v7.1. Check the contract documents; never assume the latest version applies.

Who is responsible for the HOTO submission?

The Managing Contractor or Head Contractor usually owns the HOTO submission. Subcontractors contribute discipline-specific evidence; the Consultant HOTO, where appointed, reviews; SMEs sign off on technical content; the EMOS contractor confirms operational readiness; Defence accepts.

When does the HOTO process start?

At project mobilisation. Defence describes HOTO as a process that starts with project planning and continues until the end of the defects liability period. Treating HOTO as a closing-phase activity is the single most-common cause of failure.

What happens if Defence rejects the HOTO submission?

Practical Completion is not certified. The Contractor remains on the hook for the project until the HOTO submission is rectified, which can extend a project by weeks or months. Liquidated damages may apply depending on the contract. The Defects Liability Period clock does not start until HOTO is accepted.

How does HOTO relate to the Operations and Maintenance Manual?

An Operations and Maintenance Manual (OMM) must be created and provided to Defence during HOTO. A complete OMM is necessary but not sufficient for HOTO acceptance because HOTO also requires asset register data, commissioning records, training materials, warranty registers, and other project evidence beyond the OMM scope.

Can software handle HOTO compliance on its own?

No. Software enforces structure, captures metadata and provides an audit trail, which is where most HOTO failures occur, but a competent project quality manager remains essential. Platforms like Procom remove the manual chasing of subcontractor documentation that historically consumed weeks at handover, but cannot substitute for engineering judgement on what evidence is appropriate.

The HOTO Process for Australian Defence Construction

What HOTO Means

HOTO stands for Handover/Takeover. It is the formal process by which a Defence construction project transitions from the building contractor’s responsibility to the Department of Defence and its appointed Estate Maintenance and Operations Services (EMOS) provider.

Unlike a private-sector handover, where the keys, the as-builts and a defect list might be enough to call a project complete, Defence HOTO requires a structured Evidence Folder demonstrating that the asset meets ERIK quality standards, that all DAMIS-aligned asset records have been captured and that the EMOS contractor can operate the asset from day one without re-discovering its design intent.

HOTO is the leading cause of late practical-completion certifications on Australian Defence construction projects. It is also the leading cause of disputes during the Defects Liability Period. The reason is consistent: contractors plan the construction phase in detail and treat HOTO as something that happens at the end. By Defence’s design, HOTO is a programme of evidence collection that runs alongside construction from day one.

A well-run HOTO is invisible. A badly-run HOTO causes withholdings, contract extensions and reputational damage with Defence’s project teams.

HOTO Stakeholders and Their Responsibilities

The HOTO process touches every party on a Defence construction project. Each has a defined role inside the ERIK quality framework.

Contractor (Managing Contractor or Head Contractor)

Owns the Evidence Folder. Responsible for collating subcontractor records, presenting completed checklists to Defence and resolving non-conformances raised during HOTO inspections. On most Defence projects the Contractor is also the Consultant HOTO coordinator unless a separate party is appointed.

Consultant HOTO

A nominated role on projects run through Procom’s four-tier Defence approval workflow. Reviews and approves Evidence Folder content before it is submitted to Defence. Acts as a second-line check between the Contractor’s quality team and the Defence-side acceptance process.

Subcontractor

Provides discipline-specific evidence: commissioning records, manufacturer literature, warranty certificates, training materials, as-built drawings, asset register entries. Most HOTO rejections trace back to a subcontractor submission that is structurally non-compliant: the right information in the wrong template, or with a missing signature.

Subject Matter Expert (SME)

Reviews specialist content (fire systems, security, defence-specific systems) for technical correctness before it enters the Evidence Folder. Has approval authority on the nodes assigned to their discipline.

EMOS / PPS contractor

The downstream consumer of the Evidence Folder. Once HOTO is accepted, the asset enters the EMOS contractor’s maintenance regime. EMOS contractors have an effective veto: if the Evidence Folder doesn’t give them the operational information they need, they will refuse the asset’s transition, and Defence will side with them.

Department of Defence

The customer. Has final acceptance authority. Reviews against the HOTO Plan and Checklist current at contract signing (commonly v6.3 or v7.1 today; v7.3 is the most current public version as of mid-2026).

The HOTO Phase Sequence

The HOTO Evidence Folder v6.3 and later versions are explicit that HOTO is not a single-stage process at the end of construction. It runs across three sequenced phases.

Phase 1: Planning & Development

Begins at project mobilisation. Establishes the HOTO Management Plan, identifies which Evidence Folder template applies (Buildings, Base Infrastructure, GDL or a hybrid) and confirms the version (v6.3 Planning & Development, v7.1 or v7.3 if the project is recent enough). The Contractor nominates the Consultant HOTO if the contract specifies one. EMOS contractor briefings begin here.

Phase 2: Construction

Evidence is gathered concurrent with construction work. Inspection and Test Plans (ITPs) are executed; non-conformance reports are raised and closed; as-built drawings are kept current. The HOTO Evidence Folder v6.3 Construction phase template defines what must be captured during construction rather than retrofitted at the end.

The single most-impactful project decision is here: HOTO records are either captured progressively or they’re not captured at all. Subcontractors who promise to “compile it later” rarely deliver complete records, and the resulting last-minute scramble is the leading cause of HOTO failures.

Phase 3: Acceptance

The Evidence Folder is finalised and submitted to Defence. The Contractor walks Defence and the EMOS contractor through each section of the checklist. Defects raised here are categorised and either rectified before Practical Completion or carried into the Defects Liability Period. Warranty start dates are confirmed (always from Practical Completion, never from supply or installation date). Asset records are transferred into the EMOS contractor’s CMMS and onward to DAMIS.

HOTO Plan and Checklist v7.3: What’s Inside

Defence publishes the current HOTO Plan and Checklist alongside the Estate Project Handover Takeover Policy. The checklist defines the evidence required at each project node. Each checklist item has:

An item number (e.g. 1.0 Project Start Meeting, 4.5 Commissioning Records)
A title describing the artefact required
A specific evidence requirement (e.g. “signed minutes including all subcontractor representatives”)
A project lifecycle phase tag (Planning & Development, Construction, Acceptance)

The checklist runs to several dozen line items across mechanical, electrical, hydraulic, fire, security, building fabric and project-management disciplines. It is structured so that each item maps to a specific asset, system or governance artefact, and so that a reviewer can confirm completeness without re-reading the underlying technical documents.

Procom’s platform includes the HOTO Help Information System, a context-sensitive help layer that displays the v7.3 evidence requirements alongside each node in the manual structure. A subcontractor uploading evidence to a node sees the criteria for that exact item without needing to consult the master checklist offline.

For projects on earlier checklist versions (v5.5, v6.1, v6.3), Procom’s HOTO Help System carries the version-specific criteria. The platform displays the requirement matching the project’s contract version, not the most recent one.

Official Defence Resources

Defence lists the following resources for the Estate Project Handover Takeover Policy. Project teams should use the official Defence source for the current files and contract-specific requirements.

Common HOTO Failures (and how to avoid them)

Drawn from anonymised observations across Australian Defence construction handovers, the recurring HOTO failure modes are:

1. Treating HOTO as a closing-phase activity

The most common and most expensive failure. Subcontractors are not briefed on HOTO obligations until late in construction; they then attempt to retrofit records that should have been captured at the point of installation. The fix is to flow HOTO requirements through subcontract terms and brief subcontractors at award, not at handover.

2. Missing or unsigned commissioning evidence

A system is installed, tested and operational, but the witness sheets are unsigned, undated or missing the subcontractor’s QA stamp. At HOTO acceptance this triggers rejection. The fix is to enforce signature workflows in the platform: uploads without the required signatures are blocked, not flagged.

3. As-built drawings inconsistent with NCRs

The drawing shows the original design; the non-conformance report closed out a variation; the Evidence Folder contains both, and they contradict. The fix is a single source of truth for as-built drawings with NCR cross-references tracked in the same platform.

4. Warranty start dates from installation, not Practical Completion

Subcontractors stamp warranties from supply or install date, but Defence requires them from Practical Completion. The fix is a mandatory warranty start-date field in the asset register that defaults to PC and requires explicit override.

5. Asset register format misaligned with DAMIS

The Contractor uses their own asset numbering; Defence requires DAMIS-aligned identifiers. Retrofitting at HOTO is impossible at scale. The fix is to configure the asset register schema at project mobilisation against the specific DAMIS instance for that project, not at handover.

6. Evidence Folder content copied from previous projects

Subcontractors copy a folder from a prior job, change the cover sheet and submit. Defence reviewers catch this routinely. The fix is template lockouts on site-specific fields and explicit Contractor review of every subcontractor folder before submission.

HOTO and Adjacent Frameworks

HOTO is one piece of a larger Defence project-management ecosystem. Understanding the boundaries prevents Contractors from over-scoping or under-scoping their HOTO deliverables.

ERIK: The Estate Resources Information Kiosk (ERIK). HOTO sits inside ERIK as the assurance process; ERIK defines the quality standards every HOTO deliverable must meet.
EMOS: Estate Maintenance and Operations Services. The contractors who inherit the asset after HOTO acceptance. Their CMMS and DAMIS feed are the downstream consumers of the Evidence Folder.
Defects Liability Period (DLP): The 12-24 month period after HOTO during which the Contractor remains responsible for defect rectification. HOTO marks the start of the DLP clock.
Operations and Maintenance Manual (OMM): Defence requires an OMM during HOTO to support sustainment, compliance and estate management obligations. A complete OMM is necessary but not sufficient for HOTO acceptance.

For the full lifecycle view, see the Defence handover guide.

How Procom Helps with HOTO

Procom’s platform is built around the HOTO Evidence Folder structure. Specifically:

HOTO Help Information System: Context-sensitive help displaying v7.3 (or earlier version) evidence requirements inline with every node. Subcontractors see the criteria for their exact item without consulting the master checklist.
Defence templates: OMM building template, OMM base infrastructure system template, HOTO Plan and Checklist versions and GDL Data Gathering Folder structures. Pre-configured structure matching Defence requirements.
Four-tier Defence approval workflow: a Defence-specific approval flow that takes each item from subcontractor draft through project review, Consultant HOTO internal review and SME dual approval to final client sign-off, with reject-and-resubmit paths at each gate. Aligns with ERIK contract templates.
Subcontractor submission portal: Uploads missing required metadata (signatures, dates, drawing references) are blocked at the upload step, not rejected at HOTO acceptance.
Activity audit trail: Every state transition, signature and document version recorded for Defence-grade auditability.
OMM Volume Splitting: Auto-split at 200 MB per the Defence OMM Submission Engineering Guide v2.0 §40-42, ensuring exports comply with Defence file-size handling requirements.

Procom is Brisbane-based, with experience across Australian Defence construction handovers. Learn more about Procom’s defence O&M manual platform or read the broader Defence handover guide.

The HOTO Process for Australian Defence Construction: A Practical Guide