Browse articles
- Getting started
- Project finances
- Billing by the hour
- Practice finances
- Grouping fees
- Budgeting project costs
- Claim an expense
- Recording revenue entries
- Recording project expenses
- Purchase orders
- Approving expenses
- Going further
- Construction cost fees
- Recurring fees
- Billing expenses
- Contingencies and discounts
- Billing progress claims
- Project templates
- Overheads
- Getting started
- Billing milestones
- Sending an invoice
- Billing logged time
- Month-end invoicing
- Fee proposal templates
- Writing a fee proposal
- Getting a proposal signed
- Link invoices that are already in Xero
- Going further
- Payments and overdue invoices
- Connect your accounting system
- Fee groups on invoices
- Tax codes and accounts
Balancing workloads
Read the resource swimlanes on the schedule, their capacity lines, utilisation, and red overflow, then rebalance work so the programme stays deliverable.
What you'll achieve
Staff the schedule so every person and group stays inside real capacity, catching and clearing over-utilisation before it becomes a missed deadline.
You'll end up with: A schedule where every swimlane sits at or under its capacity line, with over-utilisation caught and rebalanced before it becomes a real problem.
Before you start
Allocating people is one thing. Keeping them busy is another
This is step 3 of Staff the project.
Dragging an allocation onto someone's row takes a second. Doing it forty times across a programme without quietly stacking two jobs onto the same person in the same week, that's the part that actually decides whether a schedule is a real plan or an optimistic drawing. The resource swimlanes exist for exactly that check: every person and group gets a lane that shows what's been allocated against what they genuinely have.
We'll work on Riverside Apartments, where Sarah Chen is carrying Concept Design and has also been allocated to the Client Workshops. The two collide in the same week, her lane goes red, and we'll find it and clear it.
What the lane is actually measuring
A swimlane is doing one calculation, and it helps to see it explicitly. Available hours start from a person's work pattern, the hours they're rostered on a normal week, minus public holidays and firm closures. That result draws the capacity line across their lane, and it isn't a flat number, it dips whenever a holiday or closure lands.
Leave works differently: an approved, or even still-pending, leave request doesn't move the capacity line, it shows up as its own blocked-out band on the lane instead. Allocated hours add up every band dragged onto that lane, leave included, stacking up for those days. Divide one by the other and you get utilisation: at or under 100 percent the lane is healthy, past it, the lane turns red because more is allocated, leave counted in, than the person actually has.
A utilisation percentage is a useful glance, but the swimlane is where you actually resource, because it shows capacity week by week across the whole timeline. That's what tells you not only that someone's over-allocated, but exactly which week to fix.
Read a lane a few different ways
- 1
Point at Schedules in the rail and choose Project schedule.
- 2
Click the Team schedule panel's header to expand it. It starts collapsed under the Gantt.
- 3
Choose Stacked above the lanes, so each person gets one lane with their total load.
- 4
Choose Split by project to see which job is claiming a person's hours within their lane.
Sarah can look perfectly fine on Riverside Apartments alone and still be over-allocated, because a different project is quietly eating the rest of her week. A person's lane sums whatever the schedule currently has loaded, but a Project filter narrows that load down to one project's work, resource lanes included, so a filtered view still can't show her real total. Clear the Project filter first, then choose Stacked to see the truth about her total load.
A group lane, say the Architect team, starts with the sum of every member's available hours, then accounts for hours already committed to individual members and other lanes for the same group. Allocate the group heavily in one week and the whole lane can tip red even though no single person looks maxed out individually, because the shared total is what's actually being spent.
Spot the red, then clear it
Over-utilisation is rarely a single bad decision. It's usually two entirely reasonable allocations landing on the same person in the same week.
- 1
On Sarah Chen's lane, one week shades red where Concept Design and the Client Workshops overlap.

- 2
Open the clashing allocation to see the problem stated plainly: Over-allocated in this period.
- 3
Choose Split by project, switch to Daily, and click the Concept Design bar on that clashing week.
- 4
Click Reassign. The window opens on the whole allocation, so choose Priya Sharma in Move the work to and set Dates to the clashing week. Everything outside those days stays with Sarah.

- 5
Click Move. The hand-out commits as you submit it, so those four days become Priya's allocation straight away and the save bar disappears.
- 6
Open Priya's week. Her combined week now reads twelve and a half hours a day, fifty hours in total, so the overload has moved with the work.

- 7
Change Type to Fixed total and set Total hours to thirty-two so Priya reaches eight hours a day and the warning lifts.
- 8
Click Save to keep Priya's balanced week while Sarah keeps the surrounding work.
Handing one week to somebody else is not the only fix. Spreading the same work across more weeks or a lighter stretch clears the red equally well. Either way, the goal is the same: get every affected week back under its capacity line without disturbing work that was never the problem.
Leave doesn't shrink the capacity line the way a holiday does, it shows up as its own blocked-out band and counts as allocated time for that week. An allocation that was perfectly fine last week can tip red the moment someone requests time off, even before it's approved. If a lane suddenly goes red with nothing new allocated on it, look for a leave band first, and read it as real context rather than a scheduling mistake.
Troubleshooting
- A lane is red but no single band looks large. The lane totals everything allocated that week, several small allocations plus leave can add up the same as one big one.
- A group lane is red while every member individually looks fine. Group capacity is shared, so combined demand can tip the group over before any one person does.
- You cleared the red on this project, but the person's still shown as over-allocated elsewhere. A Project filter narrows the whole schedule to that project's work, resource lanes included, so it hides rather than greys out everything else they're on. Clear the Project filter, then choose Stacked to see their true total.
- The week you handed over came with an over-allocation warning. The hand-out keeps the hours the plan held for those dates. Open the new allocation and right-size it, as this walkthrough does, rather than expecting the warning to clear on its own.
Where this fits next
You'll know it worked when no lane shows red. Next, find what you need on a busy schedule. To keep the capacity lines accurate, set up your team and their working weeks, and record leave and public holidays.
Related articles
Search Monument help
Search help articles and open a result.