One job
Everything below arrives against this line, and knows what else is on it.
What a Pod holds
- Programme
- Fee position
- People
- Meetings and minutes
- Registers
- Drawings
- Consultants
- Deliverables
A folder holds them. A Pod knows what they mean to each other.
The Project Pod
One project. Everything registers against it
Select a part to see what it references, and what references it
A Pod is not a folder with tabs. Its parts reference each other, and every reference shown here is one the capability record states. No project, drawing or figure is real.
Each Pod is one node in the Brain.
In short
AvailableAvailable now to practices on a qualifying plan.- What it is
- The workspace for a single project. It holds the programme, the fee position, the people, the meetings and minutes, the registers, the drawings, the consultants and the deliverables for one job.
- Who it is for
- Project architects and job captains who currently hold one project across a folder structure, a spreadsheet, an email account and a whiteboard.
- What is different
- The Pod is not a project folder with tabs bolted on. Its parts reference each other. A variation knows which fee stage it affects, a drawing knows which set it was issued in, a minute knows which action it created.
- Availability
- Available on every plan. The free Starter tier includes two projects.
- How it connects
- Each Pod is one node in the Brain. Its programme feeds resourcing, its fee stages feed invoicing, and its registers are visible in the cross-project registers.
Part of Intelligence.
Verified against the Mudo application on .
Everything a job accumulates
An architectural project generates a specific set of records, and the set is remarkably consistent between practices: a programme with stages, a fee with a structure, meetings that produce actions and decisions, questions that become RFIs, problems that become issues, changes that become variations, drawings issued in sets, consultants with their own scopes, and deliverables that must arrive on a date.
The Pod holds all of it. Not as tabs on a page, but as records that reference each other.
That includes the material side of the design. The Pod's Product Library holds the products selected for the project from the practice's own master library, and presents them as a grid, a mood board grouped by room, schedules and costs — with print and export for the meetings that still need paper. The same mood board can then reach the client and the builder through the portals, so the selection they respond to is the record, not a copy of it.
Why the connections are the point
A variation that does not know which fee stage it affects is a note. A variation that does is a commercial fact, and the fee position updates when it is agreed.
That single difference is most of what separates software built for architecture from software configured for it. The general tool can store the variation. It cannot know what it means, because it has no model of a fee stage.
Project intelligence is rule-based
The Pod surfaces findings: things worth looking at on this job. They are produced by rules over the project's own records, and every finding links back to the record that caused it.
Nothing is generated. That is deliberate: a finding you cannot check is a finding you cannot act on.
Common questions
What is a Project Pod?
A Project Pod is Mudo's workspace for a single project. It brings the programme, fee, people, meetings, registers, drawings, consultants, variations and deliverables for that job into one place, with the relationships between them preserved rather than left to the reader.
How is a Pod different from a project folder?
A folder stores files that do not know about each other. In a Pod, a variation is attached to the fee stage it changes, a drawing belongs to the set it was issued in, and an action from a meeting is the same record that appears in the actions register. The connections are the product.
Is the Project Pod the same as the Project Brain?
There is no product called Project Brain. The Project Pod is the real thing. Mudo's practice-wide intelligence is called the Brain; the per-project workspace is the Pod.
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/:projectIdRegistered as PROJECT_DETAIL with sub-routes for minutes, actions, decisions, RFIs, issues, deliverables, risks, variations, contacts, checklists and site.
Open one job and the whole job opens.
Free for solo practices: one user, two projects, no card.