Why most "BIM automation" breaks at handover — and what fixes it
Tested versus taped-together — the difference shows the day after we leave. A walkthrough of how we document deliverables so they survive.
Most automation that ships to an architecture office quietly dies within a fortnight. Not because the logic was wrong, but because it was never built to be handed over.
Taped-together versus tested
A script that runs once on the author's machine is a demo. A deliverable runs on someone else's project, with their naming, their templates, and their edge cases — and it keeps running after the person who wrote it has gone.
The difference is documentation and testing, treated as part of the deliverable rather than an afterthought.
What we hand over
Every automation engagement ships with a repository, written documentation, and a short walkthrough video. The project team can adjust, re-run, and trust it — which is the whole point.