Skip to content

Handover workflows

Construction-to-operations handover works best as a sequence of capture, intake, review, validation and controlled preparation — not as a single upload.

Illustrative workflow — not a live project screenshot
  1. 01

    Evidence

    Field notes, photos, documents

  2. 02

    Proposed

    Structured candidates for review

  3. 03

    Human review

    Compare, edit, approve or request more

  4. 04

    Handover package

    Prepared outputs under control

Field Capture workflow

Starting problem
Asset details and evidence live in notebooks, photos and ad-hoc messages.
Actions
Start a capture session, record fields, attach evidence and resolve the target asset.
Human decision point
Installer or reviewer confirms proposals before they become approved handover data.
Output
Structured capture session with evidence links and missing-field visibility.

Limitation: Supported fields and modules depend on project configuration and feature flags.

Document Intake workflow

Starting problem
Closeout documents arrive in mixed formats without a consistent review path.
Actions
Upload supported documents into intake for structured candidate preparation.
Human decision point
Reviewers approve, edit, reject or request more information on proposals.
Output
Reviewable document sessions with provenance to source files.

Limitation: Supported file types and deterministic extraction only — general-purpose OCR is not a current claim.

Reviewer workflow

Starting problem
Teams need to compare current and proposed values with evidence side by side.
Actions
Open the review queue, inspect proposals, and record decisions.
Human decision point
Human approval is required; automation assists but does not replace accountability.
Output
Decisioned proposals ready for controlled change preparation.

Limitation: Availability of advanced association assistance may be pilot- and infrastructure-dependent.

Handover preparation workflow

Starting problem
Approved information still needs packaging for operations without silent mutation.
Actions
Preview controlled changes, confirm intentionally, then prepare export packages.
Human decision point
Preview is not apply — authorized confirmation is required before application.
Output
Structured handover packages and CMMS-oriented file profiles where enabled.

Limitation: Export profiles are validated per pilot; MaintainX file export remains pending final validation.