This reference covers the main views and filters in Global Resourcing, where project milestones show up, and the capacity terms used when planning staff work.
Views and filters
Control | Purpose |
Staff | Shows the staff timeline across the projects available to you. |
Project Programs | Shows the cross-project programme board (URL includes view=breakdown). This is where you can see milestones across projects in one place. |
Projects panel | Lists projects that can be inspected alongside the timeline. Toggle project panel shows or hides it. |
Search projects | Finds projects in the project panel. |
Project role filters | Filters the project panel by assigned roles, such as project manager. The roles depend on account configuration. |
Weeks and Days | Changes the timeline scale. |
Search by staff and Staff | Finds or selects the people displayed. |
Resource Type | Filters staff by resource type. |
Team | Filters staff by team. |
Project milestones
There is no separate all-milestones list outside Resourcing today. Use the surfaces below.
Where | What you get |
Global Resourcing → Project Programs | Cross-project view of programmes and milestones. You can use this as a deadlines board without adopting full staff allocation planning. |
Project → Resourcing tab | Milestones on that project’s resourcing timeline (milestone lane). |
Project Key details | Milestones for that project, alongside dated deliverables on the project page. |
Account admins set milestone types (name and colour) under Settings before people can add milestones on projects.
Who can open Resourcing
Global Resourcing (Staff and Project Programs) needs the account-role Global Resourcing View permission.
The Resourcing tab on a project needs account-role Project Resourcing View or Edit, or the person’s project role on that job needs Resourcing View or Edit.
See Drum Permissions for the full permission list.
Capacity terms
Term | Definition |
Working hours | The hours in the person’s configured work schedule. A full week is not universally 40 hours. |
Standard hours | Staff Capacity Standard for a date range. See the formula below. |
Effective hours | The target hours available for billable work, based on the person’s schedule and billable target. |
Available hours | The capacity still available for the period after the commitments and unavailable time counted by the view. |
Allocation | Hours planned for a staff member’s work over particular dates or weeks. |
Overflow | Work that exceeds the capacity or weekly amount being used by a scheduling operation. Its distribution depends on the scheduling settings; it is not a guarantee that every excess hour is automatically moved. |
For example, a person with a 40-hour schedule and an 85% billable target has 34 target billable hours before other commitments are considered. A different schedule produces a different figure.
How Staff Capacity Standard is calculated
Staff Capacity Standard for a date range is the sum of scheduled work-day hours in that range.
For each day, Drum uses the person’s work schedule. Non-working days (for example weekends on a typical Monday-Friday schedule) contribute zero. The daily hours are scaled so a full week totals the person’s standard weekly hours. Observed public holidays in the person’s holiday region also contribute zero.
Leave reduces available capacity, not Standard. Standard stays on the scheduled work-day sum above.
Examples for a 40-hour Monday-Friday schedule (8 hours per work day):
A month with 21 work days: 21 x 8 = 168 hours.
A month with 22 work days: 22 x 8 = 176 hours.
Part-time or uneven schedules sum their own scheduled daily hours the same way. If the daily columns and the weekly total disagree, the weekly total wins and is shared across the scheduled work days.
This Standard figure is what the Staff Capacity Utilisation report and Insights utilisation widgets use for the period.
Public holidays and holiday region
A public holiday is skipped in Standard when that date is an observed holiday for the person’s effective holiday region.
The region used is the staff member’s Public holiday region when one is set. If that field is blank, Drum uses the account’s public holiday region.
That per-person state or country region is the model. Set VIC, NSW or another listed region on the staff record when people sit in different states. The account default covers everyone else.
If a month still looks like every weekday counted, and you expected a weekday public holiday to drop out of Standard:
Check Public holiday region on the staff record.
If it is blank, check the account default.
Refresh the Staff Capacity report after you change a region.
A weekday public holiday reduces Standard when that date is on the observed holiday list for the person’s state or country region.
Assignment is not capacity
A staff assignment identifies who is associated with the work. It does not establish that the person has enough time available or reserve a particular week. The timeline, other work, leave and relevant calendar commitments provide the scheduling context.
Related reference
Project task resourcing reference defines budgeted, planned and actual hours.