ISO 19650 is the international standard for managing information over the whole life cycle of a built asset. It defines naming conventions, suitability codes, document types, and information containers with surgical precision. And yet, on most construction projects, the closest thing to ISO 19650 compliance is a spreadsheet titled "Document Register v17_FINAL_USE THIS ONE.xlsx".
Oestler's Document Register is built around ISO 19650 from the ground up — not as a checkbox, but as the structural backbone of how project documentation is captured, tracked, and handed over.
Suitability Codes That Actually Mean Something
Every document in the Oestler register carries a suitability code — the ISO 19650 designation that tells you exactly what a document is approved for:
- S0 — Work in progress (not for construction use)
- S1 — Suitable for coordination
- S2 — Suitable for information
- S3 — Suitable for review and comment
- S4 — Suitable for contractor design
- S5 — Suitable for manufacture/installation
- S6 — Suitable for construction
- S7 — As-constructed (the final handover state)
The moment a document reaches S7, it is locked into the handover record. No ambiguity about which version is authoritative. No hunting through folders for the "as-built" drawing. The register shows it: document DR-001, suitability S7, signed off by the responsible engineer, date recorded.
Document Types Mapped to Work Types
The register supports a full taxonomy of construction document types, each with its own code:
- AF — Authority / Approval Forms
- CM — Commissioning records
- DR — Drawings
- M3 — Method Statements
- …and all other discipline-specific types required by the project information protocol
Every document is tagged at creation with its type, so filtering the full register for "all CM documents at S7" is a single operation — not a manual trawl. A project reaching practical completion might have thousands of documents across dozens of types. In Oestler, the complete picture is always one filtered view away.
Annexures: Structured Sign-Off, Not Email Threads
Beyond the document register sits Oestler's Annexure system — the mechanism for obtaining and recording structured sign-offs on specific packages of work. Where a document register tracks what exists, an annexure tracks who has approved it and when.
Each annexure carries a Reference ID, document type classification, creation date, and a record of all signatories. The signatory count is visible at a glance — you can see immediately whether an annexure is awaiting a signature, partially signed, or fully executed.
Signatures on paper can be disputed, lost, or forged. Signatures in Oestler are timestamped, identity-linked, and stored immutably against the project record.
Canvas Digital Signatures with PDF Export
When a signatory is invited to sign an annexure, they access a dedicated signing sheet within the platform. The interface presents the document context — what they're signing, any associated notes, and a reference ID — alongside a canvas-based signature pad. They sign with their mouse, trackpad, or finger on a touch device.
Once signed, the system:
- Records the signatory's name, date, and signature image against the annexure
- Generates a QR code linking back to the digital record
- Exports a PDF containing the signature, signatory details, document reference, and embedded QR code — suitable for physical filing or authority submission
The QR code on the exported PDF is not decorative. Scanning it returns the auditor directly to the live digital record — confirming that the document is genuine, when it was signed, and by whom. It closes the loop between the physical document and the digital truth.
Anonymous Signing: No Account Required
One of the practical barriers to digital signatures in construction is that signatories — subcontractors, client representatives, independent inspectors — often aren't platform users. Requiring every signatory to create an account kills adoption instantly.
Oestler solves this with anonymous signing links. Each annexure generates a unique, shareable URL (/sign/:docId) that any signatory can open in a browser without authentication. They see the document context, enter their name and date, apply their canvas signature, and the record is committed to the project without them ever creating an account.
The anonymous signing view is deliberately minimal: no navigation, no branding noise, just the information needed to sign confidently. It works on mobile, which matters when your inspector is standing on a scaffold with a phone in one hand.
Why This Matters at Handover
When a project reaches practical completion, the handover package isn't assembled retrospectively — it already exists. Every document at S7 is in the register. Every annexure with its full signature chain is in the system. Every QR-linked PDF is already generated.
The asset owner doesn't receive a hard drive. They receive a structured, searchable record where every document is typed, suitability-coded, and signed. Where every approval is traceable to a named individual with a timestamp. Where the QR codes on physical equipment link back to the digital record that contains everything the operations team will need for the next 30 years.
That's what digital handover is supposed to be. Oestler makes it the default, not the exception.