What you will learn
- What firm project management covers, beyond task lists
- How fees, stages, and profitability are tracked per project
- What resourcing and programme management look like in a design firm
- How portfolio views support directors' decisions
- How to phase a system from one studio to a whole firm
What architecture firm project management is
Firm project management software connects the project and the business. Each project carries a fee, staged against design phases, a team resourced across those phases, a programme of deliverables, and time recorded against it. The system shows directors whether projects are on fee, on programme, and staffed — and where the portfolio is overcommitted before it becomes a crisis.
Resourcing is the distinctive problem. Design staff move between projects as phases peak, and a resourcing view that shows only current allocation misses the peaks coming in three weeks. The system should forecast demand by phase, so hiring, overtime, and project sequencing decisions happen early.
Core features
Fee, programme, and resourcing in one view define the product.
- Project records with fees, stages, and scope
- Fee tracking: invoicing, work in progress, and profitability
- Resourcing: staff allocation, availability, and demand forecasting
- Programme tracking: milestones, deliverables, and stage gates
- Time recording linked to projects and phases
- Portfolio dashboards for directors and studio leaders
How it is built
Start with projects, fees, and time for one studio, then add resourcing depth.
- Projects: records, fees, stages, and deliverables for one studio
- Time and fees: recording, invoicing, and profitability views
- Programmes: milestones, stage gates, and deliverable tracking
- Resourcing: allocation, availability, and demand forecasting
- Portfolio: firm-wide dashboards, utilisation, and pipeline views
Technology choices
A web-based system with simple time recording suits design firms, because timesheets are the data everything else depends on, and a timesheet system staff avoid produces fictional profitability figures. Recording should take minutes, not a weekly chore.
Fee and programme data should be linked, not parallel: stage completion, time spent, and fee claimed should reconcile, so profitability is a calculation from real records.
Challenges to plan for
Timesheet honesty is the foundation. If staff record time against the wrong project or phase, every downstream figure misleads. The system should make correct recording easy — recent projects first, sensible defaults — and managers should review time weekly, not monthly.
Pipeline optimism distorts resourcing. Unconfirmed projects should be shown as pipeline with probability, not as committed work, or resourcing will be planned against work that never arrives.
Who it is for, and its limits
Firm project management fits architecture firms, engineering consultancies, and multi-discipline design firms. It fits firms where fee and resourcing decisions currently run on spreadsheets and experience alone.
The software does not win work or design buildings. It shows whether the firm can deliver its portfolio profitably; winning work and doing design stay with the firm's people.
What a first release looks like
A first release should cover one studio with project records, fees, time recording, and profitability views. Resourcing forecasting and portfolio dashboards come later, once time recording is trusted — reviewed weekly by managers — for a full quarter. The release must be proven on the studio's actual fee and timesheet cycle, including invoicing, because a system that cannot survive invoicing week will be abandoned.
Consider a studio with twelve live projects approaching a fee-stage boundary. Time recorded against each project and phase shows three projects over their fee allowance for the current stage, and the director renegotiates scope on one and re-plans resourcing on the others before the stage closes. Resourcing views show two projects peaking in the same fortnight, and the director sequences a start date rather than overloading the team. If profitability is still calculated in a spreadsheet at quarter end, the system is not the record.
A mistake worth avoiding
The mistake worth avoiding is letting timesheet data go unreviewed until month end. By then, misallocated time is forgotten, corrections are guesses, and profitability figures for the month are built on allocations nobody can defend. The discipline is weekly time review: managers reviewing their team's time every week, while the work is still fresh, correcting allocations and spotting overruns early. A firm that reviews time monthly will discover fee overruns a month late, when renegotiation is hardest; a firm that reviews weekly can act while the project can still be recovered.
Frequently asked questions
How is project profitability calculated?
From fee, time recorded, and costs against each project and phase, so directors see which projects earn their fee and which do not.
Why forecast resourcing?
Because design demand peaks by phase. Forecasting shows peaks weeks ahead, so staffing, hiring, and sequencing decisions happen before a crisis.
How are pipeline projects handled?
Shown separately with probability, so resourcing plans distinguish committed work from work that may not arrive.
Can directors see the whole portfolio?
Yes, through portfolio dashboards: fees, utilisation, programme status, and pipeline, with drill-down to projects and studios.
How much does it cost to build?
Cost depends on studio count, fee complexity, and resourcing depth. One studio's system is far smaller than a firm-wide platform, so confirm with a scoped quote.