Delivery
Engagements, consultants, staffing, bench, utilization, timesheets, and the handoff from a won deal.
By Sebastian StreiffertPublished Jan 10, 2026Updated May 4, 20269 min read
What you can do here
Delivery is the half of the business that starts when a deal is won: the work you sold, the people doing it, how booked they are, and the hours behind the invoice.
It sits on the same records as the sales side, so the client on an engagement is the same company your pipeline worked, and a won deal can hand itself over instead of being retyped into a spreadsheet.
| What you need to know | Where to look |
|---|---|
| "We just won this. Who is doing it?" | Handoffs, then Staffing |
| "Who is free in three weeks?" | Bench |
| "Are we busy enough to hire?" | Utilization |
| "Is this project going to land on budget?" | Portfolio, then the engagement |
| "Whose hours are missing?" | Timesheets |
| "We might win these two. Can we staff them?" | Demand |
The pages
| Page | What it is for |
|---|---|
| Dashboard | The delivery numbers in one place. |
| Portfolio | Every engagement: client, dates, staffing, budget, health. |
| Consultants | Your people: employees and subcontractors, skills, capacity, rates. |
| Staffing | Who is booked on what, week by week. |
| Bench | Who is free now, and who rolls off soon. |
| Utilization | How booked the team is against your target. |
| Timesheets | Weekly time entry and approvals. |
| Handoffs | Won deals that have no engagement yet. |
| Demand | Roles that need covering, including on deals not yet won. |
| Planning | The sprint tracker for the delivery work itself. |
Consultants, Portfolio, Demand, and Handoffs are tables like Contacts and Companies, with a search box and a live count on the filter row and the page's buttons at its right end.
Hand a won deal to delivery
A won deal with no engagement waits on Handoffs. Handing it over carries the contract, the roles you sold, the dates, and the margin target across, so delivery starts from what Sales actually closed rather than a fresh guess.
Mark the deal Won
Link the final contract
List the roles you sold
Set the dates and the owner
Run an engagement
An engagement is one piece of delivered work for one client, with a billing model, a budget, a period, and a health signal.
| Tab | What is on it |
|---|---|
| Overview | Staffing, dates, budget, progress. |
| Staffing | Who is on it, at what share of their week. |
| Milestones | Dated deliverables you can share with the client. |
| Knowledge | What the team has recorded about this work. |
| Contracts | The agreements behind it. |
| Billing | What has been billed against the budget. |
Staff the work
- 1One row per person: Their next few weeks at a glance
- 2Colour is the load: Free, under target, on target, overbooked
- 3Assignments: A share of the week, with dates and a rate
Staffing
The grid shows each person's allocation across the coming weeks. An assignment carries a share of their week, a period, a rate, and whether it is billable.
Bench
Three views: who is free now and from when, who rolls off in the next few weeks, and a forecast. This is the page to open before you promise a start date.
Demand
Demand is a role waiting for a person: skills, seniority, hours a week, dates, rate, and how confident you are. Roles on deals you have not won yet sit here as tentative, which is how pipeline shows up in resourcing before it is real.
Try a plan in a scenario first, then apply it once it holds together. Nothing is committed until you do.
Watch how booked the team is
Utilization compares booked time against capacity and against the target you set, with logged hours as a third line once timesheets are in use. The stats row shows this week, the target, who is on leave, and what idle time is costing per week.
Settings → Workspace → Features → Delivery.Log and approve time
Time goes against an assignment, not against a project in the abstract. That is what makes the hours line up with what was sold.
- My Time: fill in the week, then submit it.
- Approvals: submitted weeks queue here to approve or send back with a reason.
- Compliance: who has not submitted yet.
- History: past weeks.
When something looks wrong
| What you see | What to do |
|---|---|
| A won deal is not on Handoffs | It already has an engagement. Look for it in Portfolio. |
| Handoff will not complete | It needs an active contract on the deal, at least one sold role with hours, dates, and an owner. |
| Nothing to log time against | You are not staffed on anything yet, or your user is not linked to a consultant. |
| Utilization looks off | Check the target and the bench threshold in delivery settings before assuming the numbers are wrong. |
| A date is refused on a timesheet | It falls outside the assignment period. Ask for the assignment dates to be extended. |
Quick reference
Was this article helpful?
