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
Assigning people to roles
Split an open role allocation between two people without disturbing the rest, and read the rate Monument stamps onto the work each one takes.
What you'll achieve
Hand one week of open Architect role work to Sarah Chen and four full days to Priya Sharma, keep the role and track through the hand-outs, and read the rate Monument stamps onto Sarah's week.
You'll end up with: One week of the Documentation stage held by Sarah Chen and four days by Priya Sharma, with the Architect role and track retained and Sarah's rate stamped onto the week as it commits.
Before you start
This is step 2 of Staff the project. An open role allocation is a plan, not a finished one. Sooner or later a real person picks up part of it, and Monument lets you hand over exactly the slice they're doing, no more, while the rest of the role's work stays open behind them.
We'll pick up where plan by role left off: the Documentation stage on Riverside Apartments is allocated to the Architect role, and we'll give Sarah Chen one week of it and Priya Sharma four days.
The idea: a hand-out, not a replacement
Assigning a person to part of an open role allocation splits it rather than replacing it. The week you hand over becomes Sarah's, as an allocation of its own. Everything you did not hand out stays exactly where it was: still open on the Architect role, on its original dates. Both pieces keep the role and its track, so the plan's shape survives as names arrive piece by piece.
The hand-out settles the rates too. An allocation's rate is stamped when the work is created: Monument resolves the rate at that moment and records it on the allocation. Handing work to a person is a deliberate change, so it asks Monument to stamp that person's current rates onto the week they take. Sarah's week prices at her resolved rate, while the role work left behind keeps the rate it was planned on.
Hand one week to a person
Work from the timeline, on the same open Architect allocation you created earlier.
- 1
On Project schedule, open the Team schedule panel and choose Stacked. With Documentation open, open the Architect allocation. Its Assigned to row reads Unassigned, because the work is planned for the role and no person holds it yet.
- 2
Click Assign to open the hand-out window. It opens on the whole allocation, so set Dates to the week of September 14th, the week you are giving away.
- 3
Choose Sarah Chen in Move the work to. The window answers the question that matters: two hundred and sixteen hours stay with the Architect role.

The window is a small editor of its own: who receives the work, the dates, and the hours. Point it at one week and only that week leaves the role. Leave the dates at the allocation's own range and pick a person, and the whole allocation moves instead. Either way, the role keeps whatever the window says stays behind.
Submitting commits the hand-out
- 1
Click the Move button, which spells the move out: Move 40 of 256 hours.
- 2
The hand-out commits as you submit it, so the save bar disappears straight away. There is no draft and no Save step: Sarah's week is already written.

Every other schedule edit waits in the save bar so you can review and discard it as a batch. Handing work to a person is the one deliberate exception, because only the server holds Sarah's work pattern, holidays and leave, and only a single transaction can promise that the hours leaving the role are the hours arriving on her week. The button is never blocked by other unsaved edits. Those edits travel with the hand-out and are applied in the same transaction.
Give the next person their days
The rest of the work is still open on the role, so you can split it across as many people as you need, one hand-out at a time.
- 1
With the Architect allocation still open, click Assign again.
- 2
Set Dates to September 21st to 24th, the four days Priya Sharma works. Monument spreads what is left of the role's work evenly, so Hours per period reads 6.75 a day.
- 3
Type 8 in Hours per period, so she gets full days. The total reads 32h.
- 4
Choose Priya Sharma in Move the work to. A hundred and eighty-four hours now stay with the Architect role.
- 5
Click Move 32 of 216 hours. The role's work is now split across Sarah, Priya and the open role.
Confirm what stayed
Open Sarah's week and check that the role and track came with it.
- 1
Role still reads Architect, and Track still reads Architect Delivery: the hand-out kept both intact.

Read the rates on Sarah's week
The Charge and expense section of the open week shows what this time charges and costs.
- 1
Charge for this time reads Charge-out rate, three hundred dollars an hour, and Expense this time reads Cost rate, one hundred and fifty.

- 2
Monument priced the week when the hand-out committed, so the figures are there without a save.
A week uses the rate stamped on it when it was created or handed over; without one, it follows a rule on the task, then the person's own rate, their team's, their role's, and finally the practice's. Handing a week to Sarah stamps her rates onto it; the work that stayed on the Architect role keeps pricing from the role. To charge this one week differently, pick another rate in Charge and expense. To change what a role or person charges from a date, see rates and rate history.
Troubleshooting
- The hand-out saved itself and you expected a Save step. Moving work to a person on an allocation that already exists is one server call, so it does not wait in the save bar. Pending edits to that same allocation travel with the hand-out and are saved in the same transaction.
- You want to hand over the whole allocation, not one week. Leave the window's Dates at the allocation's own range and choose the person. The whole allocation moves, and nothing stays on the role.
- The week arrived with an over-allocation warning that should not be there. The hand-out keeps the hours the plan held for those dates; it does not shrink them to Sarah's normal working hours. Compare the planned hours with her capacity and her other allocations for the same days.
- The rate does not match the role's planned rate. The hand-out prices the week Sarah takes from her rates, not the role's. To keep a week priced at the role's rate, leave the work on the role rather than handing it over.
- You handed over work on an allocation you had not saved yet. An allocation with no server record cannot be split in one transaction, so that hand-out waits in the save bar with your other changes. Save to write it.
Where this fits next
You'll know it worked when Sarah's week sits beside the open Architect work. Next, check that nobody is overbooked. To see how the week's rate feeds the stage's revenue, read revenue from resourcing.
Related articles
Search Monument help
Search help articles and open a result.