A structure people can maintain
We agree minimum metadata, naming and owners. We avoid folder trees so deep that teams end up emailing copies instead.
Storing files is only one part. They also need naming, approval ownership, revision distribution and evidence of what was current when a decision was made.
Drawings and models with revisions
Approved contracts, quotations and orders
Minutes, photographs and issues
Supplier and subcontractor documents
Final manual, as-built and project close-out
We agree minimum metadata, naming and owners. We avoid folder trees so deep that teams end up emailing copies instead.
Each status has a meaning and an action. When a revision is published, affected people are identified, the previous one is removed from current views and history is retained.
An issue links drawing, photo, owner and response. A delivery note links order and project. The document stops being an isolated attachment and begins to explain a transaction.
Tell us how you work and what you would like to change.
At CADT, we help you decide where to start.