Staff utilisation report for architecture and design firms
Staff utilisation report for architecture and design firms, showing how each designer's hours split between project work and internal time.
Updated 2026-01-14
Why Architecture and design need a staff utilisation report
An architecture or design firm sells time as much as drawings. Fees are usually tied to a scope, and hours that go unassigned to phases or variations are hours nobody can invoice or defend. A staff utilisation report gives a principal a running picture of how each designer's week splits between chargeable project work and everything else, including model setup, internal reviews and proposal writing. That picture matters most when a team is stretched across several commissions at once. A project lead can see whether a graduate is carrying three live jobs or has room for a new brief, and whether the firm is quietly absorbing unpaid revisions. Because the report draws on timesheets and rosters that already exist, it adds little work for staff. The result is a basis for conversations about staffing, fee setting and when to decline work.
Staff utilisation report: Architecture and design in plain language
Utilisation is a simple ratio with a lot of judgement folded into it. Take the hours a person could work in a period, remove leave and public holidays, and then ask what share went to work that earns a fee. The arithmetic is the easy part. Deciding what counts as fee-earning, whether training or marketing belongs in the denominator, and how to treat a designer who spends a morning on a site visit are choices that shape the number, so a firm should write its definitions down before it compares anyone against a target.
Reporting works best when the definitions stay stable across months. A figure that jumps because someone reclassified a category tells a principal nothing about capacity. Most small firms also read utilisation alongside a second question, namely how far booked work runs ahead of available hours, because a high rate in a busy month may hide a team that cannot start the next job.
Features for this industry
- Hours split by project phase and by variation, so chargeable time can be checked against the agreed fee scope
- Utilisation rate for each designer and each project team, drawn from timesheets and rosters already in use
- Separate tracking for internal time such as proposal writing, model checks and office admin
- Capacity view for project leads deciding whether a team can take on another commission
- Regular comparison of fee-earning time with the hours booked into each live project
- Export to a shared spreadsheet so principals and project leads work from the same numbers
At a glance
| Build | Staff utilisation report |
|---|---|
| Industry | Architecture and design |
| Complexity | moderate |
| Tools | Airtable, Microsoft Power BI, Looker Studio |
| First release |
|
Examples
Commission capacity check
A project lead is weighing a new commission against a team already running two live jobs. The report shows how many hours each designer has left after chargeable project time and internal work are counted. The lead can then decide whether the team can take on the brief, or whether the start should wait.
Fixed-fee scope review
Principals reviewing a fixed-fee housing design job ask whether the hours logged against it still match the agreed phases. The report separates time spent on concept, documentation and site visits, and flags phases where effort has run past the scope. Those figures give the principal grounds to raise a variation before the remaining fee is spent.
Graduate workload check
One senior architect reviews the roster of a graduate who has been moved between three projects in one month. The report shows the graduate's billable share and the internal time added by each handover. The senior architect can then rebalance the work before the graduate's hours become unsustainable, and bring the figures to a planning meeting.
Staff utilisation report: Architecture and design in practice
The work begins with a few questions for the owner or team lead. Which timesheet system holds the hours? Which roster is the source of truth for leave? What are the billing categories, and which internal codes sit beside them? Those answers become a fixed mapping, so each person's entries land in the same bucket every cycle. Each mapping is written down, so a later change, such as a new billing category, is recorded rather than applied silently to past months.
The build then pulls the sources on a schedule into a single table, with one row per person per period. A summary view groups those rows by team and shows the billable split and the utilisation rate against available hours. Staff whose entries are incomplete appear as gaps rather than being quietly assumed, which keeps the figure honest. Results go out on a set schedule to a shared spreadsheet, where the owner and project leads can check the same numbers before a planning conversation.
The local angle
Sydney firms often work across a wide area, with projects in inner suburbs, outer districts and regional sites, so a designer's week can include a fair amount of travel. Site visits and council meetings are real project time, but they can easily be logged as internal or left unassigned. Defining a travel category before the first cycle keeps those hours from distorting the utilisation rate for people who spend more time out of the studio.
MILabs is in Sydney and works remotely, so the setup conversation can take place by video call wherever the firm's people happen to be. A firm with staff in several locations can still share one set of definitions and one spreadsheet. The question to settle early is which location or project code each entry belongs to, so that a team split across several sites is read as one team.
Frequently asked questions
- What is in the first release of a staff utilisation report for architecture and design?
- The first release imports timesheet and roster data from one agreed source per person. It splits billable from non-billable hours, works out utilisation against available hours for each person and team, and gives the owner or team lead a summary view. Results can go to a shared spreadsheet on a schedule. Later work could add a breakdown by project, alerts for teams outside an agreed range, comparisons with earlier periods and a capacity forecast.
- Do I own a staff utilisation report built for my architecture and design business?
- Ownership is set out in the written agreement for your project, which covers the report, its configuration and any custom code. The report is built around your firm's timesheet and roster sources, and it reflects the phases and billing categories you define. Questions about reusing the underlying approach for other clients can be raised in that same agreement.
- What privacy rules apply to a staff utilisation report for architecture and design?
- The report handles personal information about staff, including hours, rostered shifts and possibly leave, so Australian privacy law, including the Privacy Act 1988, is relevant. Access works best when limited to the owner, team leads and anyone who needs the figures to plan work. Which fields the report holds, how long records are kept and where exports are stored are early questions to settle. Staff should know what is recorded and why.
- What does MILabs do after delivering a staff utilisation report for architecture and design?
- After delivery, MILabs can check that the data sources are still feeding the report correctly and answer questions from the owner or team lead about what the figures show. Any further support, such as changes to the summary view or new data sources, is agreed separately and in writing. To discuss what support might suit your firm, use the enquiry form on the website.
- What features does a staff utilisation report need for architecture and design?
- The core features are a link to the timesheet and roster source, a split between project and internal hours, a utilisation rate by person and by team, and a summary view. Architecture firms also benefit from phase-level tagging so that concept, documentation and site time can be read separately, and from a clear way to record variations. Scheduled export to a shared spreadsheet helps principals and project leads work from the same numbers.
Related
read these nextUp a level
Staff utilisation report for other industries
Other builds for Architecture and design
- Client brief assistant for architecture and design firms
- Client onboarding automation for architecture and design firms
- Email triage automation for architecture and design
- Inbox to task automation for architecture and design firms
- KPI scorecard for architecture and design firms
- Meeting notes to actions assistant for architecture and design firms
- Owner dashboard for architecture and design firms
- Private document Q&A on your own server for architecture and design
- Project tracker for architecture and design firms
- Proposal first-draft assistant for architecture and design firms
- Timesheet automation for architecture and design firms
