Resources

How practicesactually run.

Writing about the operational side of architecture: fees, programme, resourcing and delivery. The part of the profession nobody is taught and everybody has to work out.

What is on the shelf

4 written7 reserved

  1. Architecture practice management software

    Guide

    What architecture practice management software is, what it has to handle that generic work tools do not, and how to judge whether a system is built for architects or configured for them.

  2. Project management for architects

    Guide

    How managing an architectural project differs from generic project management: stages, approvals, consultants, registers and drawings, and what a system needs to hold.

  3. Architecture practice glossary

    Reference

    The operational vocabulary of running an architecture practice: fee stages, variations, RFIs, retainers, drawing registers and the rest, defined as practices actually use them.

  4. How Mudo compares

    Comparison

    Honest comparisons between Mudo and the general work-management platforms architects most often evaluate, written without inventing weaknesses in other people's products.

  5. Practice management

    Reserved

  6. Project delivery

    Reserved

  7. Fees and commercial

    Reserved

  8. Resourcing and time

    Reserved

  9. Technology and BIM

    Reserved

  10. AI in practice

    Reserved

  11. Product thinking

    Reserved

The reserved subjects are the ground Practice Notes will cover — each one a part of practice Mudo runs, and therefore a part we can write about from evidence rather than opinion. Practice Notes sets out what each of them means. Nothing appears on this shelf before it is written.