RunResourcing
This is what a free week looks like.
Work does not arrive in a calendar. It arrives in the room.
Pressure is not a colour. It is the room you no longer have.
Resourcing
There is only so much room — move the work and watch it close
Week 5 — Over capacity1 week is over capacity. Move the commitment into a week with room and the breach closes.
Mudo’s own twelve-week forward frame and its state vocabulary — unallocated, available, near capacity, over capacity. Load is drawn as a proportion of each week’s own capacity, as a diagram. No person, project or hour is real.
In short
AvailableAvailable now to practices on a qualifying plan.- What it is
- A practice-wide view of who is allocated to which project, over what period, and where there is capacity or overload next week.
- Who it is for
- Practice managers and directors deciding on a Monday whether the studio can take the job that came in on Friday.
- What is different
- Resourcing reads the programme rather than sitting beside it. When a stage moves, the resourcing picture moves with it instead of becoming quietly wrong.
- Availability
- Available on every plan, including the free Starter tier.
- How it connects
- Resourcing draws on programme for when work happens and on timesheets for what actually happened, and feeds the workload the Brain reflects.
Part of Run.
Verified against the Mudo application on .
The Monday morning problem
Most practices rebuild their resourcing picture by hand, weekly, from memory and a few conversations. It takes an hour and it is out of date by Wednesday, because the programme it was based on moved on Tuesday.
The work is not hard. It is just impossible to keep current by hand, which means the practice is always planning against a picture of last week.
Allocation that reads the programme
Because resourcing and programme are the same model, the plan does not need rebuilding. A stage that moves takes its allocation with it.
This is the difference between a resourcing tool and resourcing inside a practice system: the tool needs to be told, and the system already knows.
Where the plan meets what happened
Timesheets record what actually occurred. Comparing the two is how a practice discovers that a job it thinks is profitable has quietly absorbed three weeks of somebody's time.
Common questions
How does Mudo manage project resourcing?
Resourcing shows allocation across every live project on one view, drawn from the same programme data the projects hold. Because allocation and programme are one model, a stage that moves changes the resourcing picture rather than leaving a plan that no longer matches the work.
Can I see who has capacity next week?
Yes, that is the question the view is built to answer. It shows allocation forward across the practice, so the decision about whether to take on a new job is made against the real picture rather than an impression of it.
What is the difference between resourcing and timesheets?
Resourcing is the plan, who is supposed to be working on what. Timesheets are the record of what actually happened. Holding both lets a practice see where the two diverge, which is usually where a fee is being lost.
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.
- /resourcingThe resourcing screen, behind the projects feature gate.
Where the room comes from
Nobody makes more weeks. Mudo shows you which ones are still yours.
Free for solo practices: one user, two projects, no card.