Obligation to feature
Where the duties meet the software.
Most vendors describe this in general terms. We publish it, because you should be able to check the claim rather than take it on trust.
| Obligation | Applies | How TBM addresses it |
|---|---|---|
| Dutyholder appointment and cooperation | Both | Appointment register with alerts on gaps between appointments, written appointments and acceptance held against each project. |
| Competence of dutyholders | Both | Competence records for individuals and organisations, with expiry alerts and supply chain vetting. |
| Building control approval before works | Both | Submission pack builder with completeness checks, and a frozen snapshot of exactly what was submitted. |
| Golden thread creation and maintenance | Both | Structured information register with version control, provenance to a named dutyholder role, and verification workflow. |
| Change control during construction | Both | Guided classification, impact assessment, and tracking of notifications and responses. |
| Mandatory occurrence reporting | Both | Capture to report workflow with the statutory clock surfaced from the moment of discovery. |
| Completion and handover | Both | Completeness assertion, known gaps declared, and a verified export the receiving party can check independently. |
| Building registration and key information | England | Registration tracker and structured forms matching the submission schema. |
| Safety case and building assessment | England | Risk register linked to controls, safety critical assets and supporting evidence. |
| Resident engagement and complaints | England | Strategy publication, request and complaint handling with response clocks. |
| Information kept accurate and up to date | Both | Integrity dashboard, staleness detection, and scheduled verification of the audit chain. |
This mapping is maintained against published regulations and guidance, and each rule in the platform carries a citation to its source. It is not legal advice, and it does not replace the judgement of a competent person.
What we deliberately do not do
No design authoring, no BIM modelling, no general document management, and no regulatory advice. Staying narrow keeps the product honest about what it is responsible for.