These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Resource Planning System
- Features
- Rates and forecasts
Rates and forecasts
Use reviewed effective rates to explain the value of forward staffing commitments.
OverviewActive rate cards×
Resource Planning System · Rates and forecasts
New
Active rate cards
Rate cards
| Rate card code | Practice | Region | Effective from | Effective to | Approved by | |
|---|---|---|---|---|---|---|
| US-DATA-2026 | Change enablement | Northeast | 20 Oct | Mateo Valdez | ||
| US-ARCH-2026 | Change enablement | Southeast | 22 Oct | Iris Chen | ||
| US-QA-2026 | Enterprise applications | Midwest | 23 Oct | Iris Chen | ||
| US-DELIVERY-2026 | Delivery operations | West | 16 Oct | Evan Sato | ||
| US-INTEGRATION-2026 | Delivery operations | South | 21 Oct | Evan Sato |
6 of 6 records
US-DATA-2026Rate cards · RC-38800
NortheastPracticeChange enablement
Effective from20 Oct
Approved byMateo Valdez
Finance approved byLeila Haddad
What you can do
Master data setup
Admin and Practice Leads configure Practices (one per delivery practice with a practice lead and US region scope), Roles (the demand language — Senior Engineer, Tech Lead, Solution Architect — each with a Level and default bill rate), Skills (the Technical / Functional / Industry / Language / Methodology catalog with proficiency scale), and the initial rate cards with rate card rows per Practice per Region per Role. Rate card activation requires Practice Lead + Finance co-approval stamped on the rate card before Status: Draft → Active; the prior active card’s effective to is set automatically.
Assignment generation
On approval the assignment-on-approval workflow fires: a code node creates an Assignments row (Resource, Project, Role, rate card resolved from Practice + start date, bill rate resolved from rate card rows and frozen on the Assignment, cost rate snapshotted from resource cost rate, allocation pct carried from the request) plus N assignment periods rows (one per week from start date to end date at the requested allocation pct). 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 assignment periods and effective time actuals into one Utilization row per Resource (available hours, allocated hours, actual hours, billable hours, non billable hours, utilization pct, billable utilization pct). Right after, bench-detection scans the latest Utilization plus forward-booking coverage and writes a Bench row for every Resource whose forward-4-week average utilization pct falls below the bench threshold (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.
What your team sees
- Active rate cards. Open the current records for this module within your assigned role and permitted scope.
What it keeps track of
Data model- Rate cards
- Versioned rate cards per Practice (and optionally per US region). A rate card has effective dates and a set of rate card rows. The active card on
Assignments.StartDateprices the assignment. - Rate card rows
- Per-Role rate row inside a rate card. The lookup grain for pricing an Assignment.
- Assignments
- The staffing record — a Resource on a Project at a Role at an allocation percentage over a date span. Spawned from an approved resource request. The unit of capacity consumption.
- Assignment periods
- Week-by-week allocation rows for an Assignment. Generated on approve; the granular hours that roll up into weekly capacity and Utilization. Reconciled to actuals from
pm-timebytime-sync-from-pm-time. - Practices
- Organizational practice unit — a Practice owns a set of Resources, Roles, and rate cards. Examples: Data Engineering, Cloud Infrastructure, Business Consulting, Design.
Who uses it
Permissions- Finance
- Prepares rates.
- Practice Lead
- And a distinct Finance reviewer co-approve. authorized planners read the approved rates.
Set up Resource Planning System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.