Browse articles
Set your team's availability
Add a staff member and shape their work pattern, the weekly hours that become the capacity line you'll read everywhere on the schedule.
What you'll achieve
Add a staff member with a work pattern so Monument knows their real weekly availability, the baseline of their capacity line on the schedule.
You'll end up with: A staff member on file with an accurate work pattern, ready to be resourced and scheduled.
Every capacity number starts with one setting
When Monument tells you someone's overbooked, or shows what a stage costs to staff, all of it traces back to one thing you set here: how many hours a person actually works each week. Get that wrong and every downstream number, capacity, cost, utilisation, inherits the mistake. Get it right, and resourcing has solid ground to build on.
We'll add Priya Sharma, a Senior Architect joining Northlight Architects, and shape the working week that becomes her capacity everywhere else on the schedule. (You're already on the team, creating the workspace added you as the first staff member automatically.)
A work pattern is a real week, not a label
It would be easy for Monument to ask "full-time or part-time?" and leave it there, but that throws away exactly the information the schedule needs. Instead, a work pattern is the actual days Priya works and the hours on each of them, Monday to Friday, 9:00 to 17:30, say. That weekly total becomes the baseline of her available hours, which is what draws the capacity line across her lane in the resource swimlanes later on. A four-day week isn't a category, it's a smaller capacity line, every single week.
Whatever employment type you pick for someone, full time, part time, contractor, is descriptive only. It labels the relationship but sets nothing about their hours. The work pattern grid is the only thing that actually determines capacity.
Add the person
- 1
Click Add Resource to open the Add New Team Member dialog.
- 2
Enter the name, Priya Sharma, and a job title, Senior Architect.
Shape the working week
This grid is the part that actually matters. Each weekday carries a checkbox and a pair of start and end times, and a running weekly total in the header updates the instant you change anything.
- 1
Leave Monday to Friday ticked at their default hours and watch the total settle at 42.5h/week.
- 2
Untick Friday to make her part-time instead, and the total drops in real time to 34.0h/week.
- 3
Tick Friday again to restore her full week, and click Add Team Member.
A capacity line that reads too high or too low almost always traces back to this grid, not to any setting elsewhere. Untick a day or trim its hours until the weekly total matches reality, rather than trying to fix it through the employment type.
Troubleshooting
- A part-timer's capacity looks like a full week. Employment type alone changes nothing. Open their work pattern and untick days or shorten hours until the weekly total is accurate.
- Everyone shows as fully booked the moment they're added. Adding staff does not spread existing allocations. Check each person's work pattern, employment dates, and allocations to find the demand driving their utilisation.
Where this fits next
Priya now has a real working week, so her capacity line is accurate wherever she shows up. From here: group people so you can assign and rate them together in resource pools, set what her hours cost and charge in rates and rate history, keep her availability honest with leave and holidays, then read it all on the Gantt in balance capacity in the swimlanes.