Rates and forecasts

Master data setup

Admin and Practice Leads configure Practices (one per delivery practice with a PracticeLead and US region scope), Roles (the demand language — Senior Engineer, Tech Lead, Solution Architect — each with a Level and DefaultBillRate), Skills (the Technical / Functional / Industry / Language / Methodology catalog with ProficiencyScale), and the initial RateCards with RateCardRows per Practice per Region per Role. RateCard activation requires Practice Lead + Finance co-approval stamped on the RateCard before Status: Draft → Active; the prior active card’s EffectiveTo is set automatically.

Assignment generation

On approval the assignment-on-approval workflow fires: a code node creates an Assignments row (Resource, Project, Role, RateCard resolved from Practice + StartDate, BillRate resolved from RateCardRows and frozen on the Assignment, CostRate snapshotted from Resources.CostRate, AllocationPct carried from the request) plus N AssignmentPeriods rows (one per week from StartDate to EndDate at the requested AllocationPct). The workflow then writes the Resource into the matched pm-projects project as a project member via the connected record service so the team appears in the project workspace. The Resource and Project Manager are emailed.

Utilization rollup and bench detection

Weekly on Monday, utilization-rollup aggregates the prior week’s closed or frozen AssignmentPeriods and effective TimeActuals into one Utilization row per Resource (AvailableHours, AllocatedHours, ActualHours, BillableHours, NonBillableHours, UtilizationPct, BillableUtilizationPct). Right after, bench-detection scans the latest Utilization plus forward-booking coverage and writes a Bench row for every Resource whose forward-4-week AverageUtilizationPct falls below the BenchThreshold (default 60%). Practice Leads get a digest; the bench-clearing motion (cross-Practice loan, investment work or training time) starts from the Bench Report.

Price a new assignment across a rate revision

An approved rate card applies to a practice, region, role and effective interval. Resolve the card using the assignment’s start date and preserve the resulting rate on the assignment. A new catalog rate does not reprice an assignment that was already accepted.

Finance can prepare a proposed revision, but the preparer cannot supply either independent approval. Practice Lead and a separate Finance reviewer sign the same submitted version. If the proposed dates overlap another active card, resolve the overlap before activation so a staffing decision has one applicable rate.

Forward-booked revenue multiplies the relevant planned billable hours by their frozen assignment rates. This is a forecast of staffing value. It is not proof that work was delivered, an invoice was sent or revenue was recognized. Cost-rate visibility remains more restricted than quoted bill rates, including in exports and candidate comparisons.