The decades after handover

At handover the customer changes: no longer site management, but owner, property management or facility management. Operations is meant to turn the closing into a continuation. This line is in planning and not built yet.

The building

The project becomes a building

At handover the project is meant to become an entity of its own: the building or plant, with a reference to the history of the construction phase. The evidence is not copied, the chain stays one.

What is planned

Handover

The operator is often someone else

If another organisation runs the finished building, it should be handed over by invitation. The building organisation keeps its project and can archive it later.

What is planned

Warranty

The bridge back to construction

A reporting path is planned from the user through the operator back to the building organisation. A case would arrive there with a reference to the original evidence chain, rather than as hearsay.

01What is planned In planning

What is planned

This is the state of the plan, not the state of the software. It gets built after the beta.

Building instead of project

An entity of its own for building and plant, with a reference to the construction phase.

Taken over from handover

Handover record, plant register, room book and deadlines should travel along.

Warranty radar

Deadlines per trade and acceptance, with suggestions for inspections.

Inspection cycles

Recurring checks such as ventilation, lifts and fire safety are kept on the building.

Maintenance as evidence

A maintenance job should be evidenced like any other: checklist, photo, signature.

Building file

Plant, documents and history in one place and searchable.

Operations is not meant to become a full CAFM. Space management, contracts and keys stay out of scope; export is planned for existing CAFM systems. This page describes a plan and says nothing about approval or legal effect.

02Trust register

Trust register

Evidence over rank: every step from the spoken word to approval stays traceable, while a suggestion never takes effect on its own.

01Capture

02Structure

03Prove

FIDICVOBJCTAIAConsensusDocs

FIDIC, AIA, ConsensusDocs, JCT, VOB and custom frameworks are versioned. Chops, hanko, dojang and company stamps are recorded only as technical confirmations, with no claim of special legal effect.

A continuous evidence chain

Conversation, transcript, suggestion and human decision form a continuous chronology that is never silently overwritten.

Fair to both sides

Before evidence protects client and contractor alike. Companies can challenge scorecards; site management records the decision.

03Language

Rendered daywork report containing German, Chinese, Japanese, Korean, Thai and Hindi text

Reports in every script

Embedded Noto fonts render Chinese, Japanese, Korean, Thai and Devanagari correctly in PDF reports.

Register interest in Operations

Operations gets built after the beta. If you take over buildings and want to shape the reporting path, get in touch now.