About
Compliance you can trace.
DC Copilot began where a lot of good tools do — with a real, repeated frustration on real projects.
Design compliance goes well beyond the Building Code. Government agencies publish detailed design standards — hundreds of specific provisions for clearances, heights, counts and finishes — and a lead designer is expected to hold all of it across every sheet of a set. In practice the knowledge sits in long PDFs and with a handful of specialists, and a miss surfaces late: at submission, or on site, where it's most expensive to fix.
DC Copilot is a copilot for exactly that gap. It reads a drawing set the way a careful reviewer would — the plan for layout, the schedule for counts, the elevations for heights — measures the design from the vectors, and tests it against the published standard. Then it hands back a report where every finding is pinned to the exact clause that proves it.
The engine is built general so it can take on any published standard. We launch it narrow — one module, done thoroughly — because a curated, verified corpus of standards is the hard part, and the moat.
What we hold to
Principles, not just features.
Citation-first, always
No finding without the verbatim clause and reference behind it. If we can't cite it, we don't claim it.
An assistant, never a certifier
We surface what applies and show our working. The professional keeps the judgement and the sign-off.
Honest about sources
We reproduce ministry design standards under their licence and only reference third-party standards — never blur the two.
Narrow and deep
One standard done thoroughly beats ten done shallowly. We ship a module when its library is authored and checked.
Where we are
Early, and honest about it.
The first module — the NZ Ministry of Education Toilets & Changing Areas standard — is live, with more in development. We're a small effort building carefully: each module gets a domain-expert pass before it ships, and we'd rather tell you a check isn't covered yet than pretend it is.