Appearance
Allocations
The Allocations view is a Gantt-style resource calendar. Each row is a person — employee, contractor, or vacancy. Each bar is an allocation to a team or project, with a start, an end, and an FTE value. Gaps between bars are availability. Stack heights tell you who is over-allocated. The whole thing is editable in place.
This is the screen replacement for whatever spreadsheet your engineering managers currently fight over every Monday.
What you can see
- Sidebar — every person on your roster, grouped by team. Filter by job role, geography, skill, custom attributes.
- Timeline — horizontal bars for each allocation, coloured by project or team. Today line in the middle.
- Inherited allocations — when a team is allocated to a project, every person on that team gets a derived bar at the corresponding effective FTE. Direct project allocations show on top.
- Project filter — narrow the view to one project to see only the people allocated to it.
The toolbar lets you change the date range, switch the grouping (team, project, geography, role), and toggle filters.
Editing allocations
Click any bar to edit it. Drag the edges to extend or shorten. Drag the body to move it. Right-click for the full context menu — split allocation, delete, change project, copy.
New allocations are created by dragging across an empty area on a person's row. The dialog asks which team or project, the FTE value, and a date range.
TIP
FTE allocations are not capped at 1.0 — the system will let you over-allocate and flag it visually with a colour change. That flexibility is intentional. Sometimes you need to plan a 1.2 FTE quarter while a hire backfills.
How allocations work
Two kinds, both stored alongside each other:
| Type | Source | Target | Used when |
|---|---|---|---|
| Direct | Employee, Contractor, Vacancy | Team or Project | The person is assigned to this team/project specifically |
| Inherited | Team | Project | Computed from team-to-project allocations multiplied by each member's team FTE |
The Gantt shows both. Inherited bars are visually distinct — usually lighter, sometimes hatched — so you know they were derived rather than placed by hand.
Direct project allocations sit on top of inherited ones. If Jane is on the Payments team at 0.6 FTE, and Payments is on Billing V2 at 0.5 FTE, Jane has an inherited 0.3 FTE bar on Billing V2. Add a direct 0.2 FTE allocation for Jane to "Hackathon Project" and that shows as a separate bar.
What the bars cost
Hover any bar to see the cost contribution: salary (or rate) × working days × FTE × overhead. The cost flows up the cost attribution chain into the team and project totals you see on the analytics and finance screens.
Editing in scenarios
Allocations are scenario-aware. Drag a bar inside a scenario and the change lives in the scenario only — your live allocations stay where they were until the scenario is merged. The Gantt shows scenario edits with a visual marker so you know what is staged versus what is live.
Use the scenario comparison view to see allocation deltas between two scenarios at a glance.
Where to go next
- Effort tracking — what people actually did versus what was allocated.
- Teams — how teams are structured and how team-to-project allocations work.
- Assignments API — programmatic create, update, delete.
- Scenarios workflow — modelling allocation changes safely.