Skip to content

How to plan staff workload across an architecture practice

Whether the next project fits is a question about particular people on particular days. Here is a method that answers it, with a worked example for a four-person team.

5 min read · Updated November 2026

The question workload planning answers

Every practice owner asks some version of the same question: can we take this on? Answering it from team totals almost always gets it wrong. Work is done by particular people on particular days. A practice can have plenty of free hours in total while the one person who can do the job is fully booked.

Workload planning gives you, for each person and each working day ahead, the hours of work scheduled against the hours they actually have. Everything below is about building that grid and keeping it honest.

Step 1: Work out real capacity, person by person

Capacity starts with each person’s working pattern, not a standard week.

  • A daily target. The hours of project work you expect from that person on a working day. Set it below their contracted hours to leave room for email, practice meetings and administration. A director who spends half the week winning work has a lower target than someone documenting full time.
  • Working days. Part-time days and rostered days off come out.
  • Leave and public holidays. Approved leave and public holidays come out. For a cautious plan, take out leave that has been requested but not yet approved as well.

The result is a capacity for every person on every day. Don’t average it across the week. Someone away on Thursday and Friday has no capacity on Thursday and Friday, however quiet their Monday looks.

Step 2: Put the remaining work in hours

List the work committed to each person: every task on every project, with the hours left in it. Base that on how much of the task is complete, not on the hours already logged. A 40-hour task that is half done still has 20 hours of work in it, even if 35 hours have been logged against it.

The extra hours are a profitability problem, covered in our guide to measuring profitability on a fixed-fee project. They don’t make the remaining work any smaller.

If your fee proposals are priced in hours, most of this already exists: the sold hours of every accepted row are the starting estimates. Our fee proposal template shows how to price that way.

Step 3: Spread the work across the days

Each task has a start, a finish and one or more people. Spread its remaining hours across the working days between start and finish, for the people assigned to it, skipping the days they aren’t available. Add up every task for each person on each day, and you have their loading.

Spreading evenly is a simplification; real work is lumpier. But it is close enough to show the problems two to six weeks out, which is where planning earns its keep.

Step 4: Read the loading

Set loading beside capacity for every person and day.

  • Over capacity: something will slip, or someone will work late. Find the tasks on that day and move one.
  • Under capacity: room for more work, or a sign that a task finished early and the plan hasn’t caught up.
  • On target: leave it alone.

Look at the next fortnight in detail and the month after in outline. Beyond that the plan is mostly proposals and estimates, and it is better read as a forecast of demand than as a schedule.

When someone is overloaded, the fixes run roughly in this order: move a task’s dates within the project’s programme; give it to someone with room who can do it; split it between two people; and only then, renegotiate a deadline with the client.

Step 5: Test new work before you say yes

Before you accept new work or commit to a start date, put it in the plan: the stage’s hours from the fee proposal, the people who would do it, and the dates the client wants. Then look at those people on those days. If it fits, say yes, with a date you can keep. If it doesn’t, you know what has to move, or which date to offer instead.

Worked example: a four-person team

The next two weeks: ten working days, with a daily target of 7.5 hours of project work for everyone.

PersonWorking patternDaysCapacityScheduledRoom
AnnaFull time, two days’ leave in week two860 h52 h8 h
BenFull time1075 h81 h6 h over
ChloePart time, Monday to Wednesday645 h30 h15 h
DevFull time1075 h60 h15 h
Team255 h223 h32 h

A client wants design development on a new house to start in the second week. The stage was sold at 60 hours over 4 weeks, so about 15 hours of it falls inside this fortnight.

On the team total it fits easily: 32 hours of room, 15 needed. Person by person, it doesn’t, as planned. Ben ran concept design for this client and is the natural person to continue, and he is already 6 hours over. Another 15 hours makes him 21 hours over in a fortnight, nearly three days’ work.

The plan turns that into choices you can make on Monday, rather than a problem you discover on Thursday:

  • Start the stage with Dev, who has 15 hours of room, with Ben reviewing.
  • Move some of Ben’s current work to Chloe or Dev, on days they are free.
  • Offer the client a start one week later, once Ben’s current documentation is due to finish.

Keep it current

A workload plan goes stale within a week. Three habits keep it useful:

  • Update progress weekly. Remaining hours come from progress, so the plan is only as current as the progress figures.
  • Record leave as soon as it is approved.
  • Review it together. A short weekly look at the next fortnight with the people who lead projects catches most problems while there is still time to move them.

Video tutorials

See TrackerPlus at work, step by step.

Short videos for owners, staff, clients and consultants, from the first fee proposal to the final invoice.

Free for up to 2 people. Upgrade when you outgrow it.
Next in TrackerPlusPlanning & Workload

The same method, built into TrackerPlus.