RunProgramme
A change in time is never only a change in time.
The programme is not a chart the practice keeps beside the work. It is the datum the fee, the resourcing and the deliverables are measured from.
Six stages, one line
Nothing here is evenly spaced, because no programme is.
- Concept design options
- Client concept review
- Design development package
- Authority submission
- Documentation issue
- Tender
Authority submission is the one that moves. Everything downstream of it is tied to it, which is the whole reason a date is not a private fact.
Programme
Push the submission — time is not a picture here
On its original dateDrag the red stage, or focus it and use the arrow keys.
An illustration of Mudo’s programme behaviour — its own stage vocabulary and category colours, over a generic sixteen-week span. No project, client or date is real.
Downstream
The date moved. These moved with it.
In short
AvailableAvailable now to practices on a qualifying plan.- What it is
- The project timeline: architectural stages, the dependencies between them, and the dates the rest of the project hangs from.
- Who it is for
- Project leads maintaining a programme in a spreadsheet or a Gantt tool that nothing else in the practice reads.
- What is different
- The programme is not a separate plan. It sits inside the Project Pod, so moving a stage is visible in the resourcing plan, in the fee position and in the Brain rather than only in the chart.
- Availability
- Available on every plan, including the free Starter tier.
- How it connects
- Programme drives resourcing, deliverable dates and fee stage timing. It is one of the six areas the Brain reads.
Part of Run.
Verified against the Mudo application on .
A date is never only a date
Move a stage and four things change: who is needed and when, which deliverables shift, which fee stage is claimable, and when the money arrives.
In most practices those four consequences are worked out by a person, weeks later, usually after one of them has already caused a problem.
What Mudo does about it
The programme is held in the same model as resourcing, deliverables and fees. Moving a stage is therefore not an edit to a chart; it is a change to the project, and the parts of the project that depend on it can see it.
This is the same argument the Brain makes visually, at the scale of one job.
Common questions
How does Mudo handle project programmes?
Each project holds its own programme of stages with dependencies and dates, inside the Project Pod rather than in a separate tool. Because it is part of the same model, a stage that moves is immediately visible to resourcing, to the deliverables that depend on it, and to the fee stages it triggers.
Why does connecting programme to fees matter?
Because architectural fees are claimed against stages. If a stage slips and the fee schedule does not know, the practice discovers the cash consequence a month later. Holding both in one model means the consequence is visible when the decision is made rather than when the invoice is not paid.
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.
- /projects/:projectId/program/focusPROJECT_PROGRAM_FOCUS, the programme focus view for a single project.
- /calendarThe practice-wide planner and Gantt view.
Put a date in one place and let the rest of the practice read it.
Free for solo practices: one user, two projects, no card.