Practice Notes
Notes on runninga practice.
Writing about the operational half of architecture: fees, programme, resourcing, delivery and the technology underneath. Published when there is something worth saying, not on a schedule.
The record is open, and empty
Nothing is published yet. Rather than fill the page with articles that do not exist, this is the record itself — open, with nothing on it — and the seven subjects standing beside it. Each one is a part of practice Mudo runs, and therefore a part we can write about from evidence rather than opinion.
Practice management
How a practice runs itself: the structure, the reporting, and the decisions that never appear on a drawing.
Project delivery
Stages, registers, coordination and handover. What actually moves a project from brief to built.
Fees and commercial
Fee structures, variations, invoicing, and the commercial position of a job while it is still running.
Resourcing and time
Who is on what, when a practice is quietly over-committed, and what recorded time is honestly worth.
Technology and BIM
Models, drawings and the exchange between them, including where the model stops being useful.
AI in practice
What automation can and cannot be trusted with inside an architecture practice, argued specifically.
Product thinking
How Mudo is built and why it is shaped this way. Notes from making the software, not announcements about it.
A subject becomes an entry when it carries a date and something worth saying, not before. Nothing here is scheduled and nothing is promised — a section that publishes to a calendar runs out of things it actually knows.
Already written
The reference material is finished, and it reads the way the notes will: two long guides on practice management and project delivery, and a glossary of the terms the profession uses inconsistently.
The software the writing comes out of
All of it comes from building Mudo and watching practices use it. The free Starter tier is the quickest way to see whether any of it matches your studio.