Fee, by stage
- Concept design
- Design development
- Authority submission
- Documentation
Effort, by the same stage
One structure, measured twice.
Timesheets
The work happened either way. Only attributed time can be read
- Resourcing plancannot read this time
- Fee stagescannot read this time
- Commercial picturecannot read this time
Unmapped. The hours exist, and nothing downstream can use them.
Time is recorded against the same stages the fee is structured around. The marks above carry no quantity — no hours, people, projects or rates are real.
Most practices compare two different structures and call it a variance.
Hours land in one system against one set of categories, the fee sits in another against a different set, and someone reconciles them quarterly. Recording time against the stages the fee is already structured around removes the reconciliation rather than automating it.
In short
AvailableAvailable now to practices on a qualifying plan.- What it is
- Time recording against projects and stages, and the views that show what the practice's effort actually went into.
- Who it is for
- Practices that suspect a job is losing money but cannot demonstrate where, and studios that need a defensible basis for their next fee proposal.
- What is different
- Time is recorded against the same stages the fee is structured around, so effort and fee are directly comparable rather than needing a mapping exercise.
- Availability
- Available on every plan, including the free Starter tier.
- How it connects
- Timesheets sit against the resourcing plan and the fee stages, which is what turns recorded hours into a commercial picture.
Part of Run.
Verified against the Mudo application on .
The only honest basis for the next fee
Architectural fees are quoted before the work is understood. The extent of a job is discovered while doing it.
That makes the record of where effort actually went the single most valuable commercial asset a practice has, and the one most practices do not keep, because timesheets feel like administration rather than intelligence.
Recorded against stages, not just projects
Time against a project tells you a job was expensive. Time against a stage tells you which part was expensive, which is the part you can do something about next time.
Because Mudo structures fees by stage, the comparison is direct.
Common questions
Why should an architecture practice track time?
Not to police anybody. The practical reason is that architectural fees are quoted in advance for work whose extent is discovered as it proceeds, and without a record of where effort went the next proposal is a guess. Time data is the only honest basis for pricing the next job.
Does time recording connect to fees?
Yes. Time is recorded against project stages, and fees are structured by stage, so the comparison between what a stage was worth and what it cost does not require a reconciliation exercise.
What this page is based on
Every capability described here was checked against the running application before publication. These are the parts of it you can open for yourself.
- /timesheetsThe timesheets screen in the application.
Find out where the effort actually went.
Free for solo practices: one user, two projects, no card.