A project rate card is a governed table of role-based cost and billing assumptions. Useful entries identify role or band, skill, location, cost rate, billing rate, currency, effective date, and owner. The card supports repeatable estimates only when definitions, access, approvals, versioning, and exceptions are documented.
In plain words
A rate card is a list of the hourly rates the firm uses, by role and level, with the date each rate starts and who approved it. Everyone who estimates uses the same card, so two people pricing the same job get the same answer.
Who this helps: Finance staff who maintain rates, presales consultants and project managers who price work.
Questions this guide answers:
- What is a project rate card?
- What should a rate card include?
- How often should a rate card be updated?
What is a project rate card?
A project rate card gives estimators a controlled way to translate resource effort into cost or client-facing value. It is not merely a list of prices. The card should identify what each rate represents, the unit to which it applies, the date from which it is valid, and who is permitted to view or change it.
Two firms can use the same label and mean different things. A "cost rate" might include only direct compensation, or it might include employer on-costs, non-productive time, and allocated overhead. A "billing rate" might be a standard list rate, an agreed client rate, or a project-specific exception. The definition belongs beside the data or in a linked policy.
The UK government's service-costing guidance emphasizes transparency, consistent allocation, validation, and version control. Those principles are especially relevant when rate-card data passes from finance to presales and then delivery: the value must carry enough context to be interpreted consistently.
Which fields make a rate card useful?
| Field | Purpose | Control question |
|---|---|---|
| Role or band | Connects work to a repeatable capability level | Are adjacent levels distinct enough to price? |
| Skill or discipline | Distinguishes cost or price where specialisation matters | Is the tag defined and used consistently? |
| Location | Identifies the geography or delivery model behind the assumption | Does the label describe a governed category? |
| Cost rate | Converts planned or actual effort to internal labor cost | Which cost components are included? |
| Billing rate | Supports time-based pricing or a commercial reference | Is it list, client, or project specific? |
| Unit and currency | Prevents invalid arithmetic | Are hourly and daily values clearly separated? |
| Effective date | Preserves which assumption applied at approval | Will a new entry replace history or start a new period? |
| Owner and status | Identifies accountability and whether the entry is approved | Who validates and retires it? |
A compact card may not store every field in one table, but the information should be traceable. Avoid free-text variants that mean the same thing, such as "Sr Consultant," "Senior Consultant," and "SC," unless a governed mapping connects them.
Rate card example: a small IT role card
The rates below are fictional and demonstrate structure only. They are not market data or pricing recommendations.
| Role variant | Band | Skill | Location | Cost/hour | Billing/hour | Effective |
|---|---|---|---|---|---|---|
| Strategy Lead | Lead | Strategy | Onshore | $95 | $180 | 1 Jul 2026 |
| Implementation Consultant | Senior | Delivery | Onshore | $70 | $145 | 1 Jul 2026 |
| Data Analyst | Intermediate | Analytics | Offshore | $38 | $90 | 1 Jul 2026 |
If the estimate uses 40 lead hours at USD 95, 160 consultant hours at USD 70 and 240 analyst hours at USD 38, direct labor is (40 × 95) + (160 × 70) + (240 × 38) = USD 24,120. This costs the stated hours; it does not establish how those hours were estimated. Add the other applicable project costs without counting the same expense twice. Parametric effort estimation needs a supported relationship between a measurable work driver and effort.
A later rate change should normally create a new effective entry. Replacing the July values with October values would make the original estimate difficult to reproduce. When a client-specific billing rate is negotiated, record it as an exception or separate governed entry rather than silently changing the standard rate.
What do you do when a role has no rate on the rate card?
A missing rate is an unresolved input, not a zero-cost resource. If an estimate quietly treats it as zero, real work disappears from the cost and the deal looks better than it is. Blank, zero and “copied from a similar role” are three different situations, and the review record should say which one applies.
Scenario: Pilar finds a missing specialist rate
Pilar, a presales consultant, is pricing a USD 70,000 fixed-fee project. The plan has 400 hours of consultants at USD 60 and 200 hours of a data-security specialist. The rate card has no row for the specialist, so the sheet shows no cost for those hours.
- Notice. The sheet shows USD 24,000 of labor (400 × 60) and a labor-only margin of (70,000 − 24,000) ÷ 70,000 = 65.71%. A margin that good on a security-heavy job is a warning sign.
- Flag. She marks the 200 hours as “rate missing” so nobody reads the result as final.
- Ask. She asks the finance owner of the rate card for an approved rate or a supplier quote.
- Test while waiting. She runs the gap at three temporary rates (table below), labelled as assumptions.
- Decide. The presales lead sees that the margin could be as low as 31%, so the quote waits for the approved rate.
| Specialist assumption | Total labor cost | Labor-only margin |
|---|---|---|
| Zero (missing, unflagged) | USD 24,000 | 65.71% |
| USD 80 an hour | USD 40,000 | 42.86% |
| USD 100 an hour | USD 44,000 | 37.14% |
| USD 120 an hour | USD 48,000 | 31.43% |
The missing rate accounts for almost 29 percentage points of apparent margin (65.71% against 37.14% at USD 100). Add other costs and revenue-based charges to every row the same way before approving. Do not repair the gap by assigning a cheaper generic role unless that role can really do the work: the rate and the skill both have to be valid.
What a fallback-rate policy should say
- When a temporary rate may be used: exploratory pricing only, never a firm quote.
- Source: an approved comparable role or a supplier quote, so a guess does not look like an approved number.
- Owner and expiry: who approved it and when it must be replaced.
- Visibility: a flag on the affected hours and totals so reviewers see the exposure.
- Recalculate before commitment, and keep the earlier version so the first estimate can still be reproduced.
How do you keep a rate card accurate?
- Publish written definitions for cost rate, billing rate, overhead, unit, and location.
- Assign an owner who approves additions, changes, exceptions, and retirement.
- Restrict sensitive cost-rate access to roles that require it; see how to share margin without showing pay rates.
- Use effective dates and retain enough history to reproduce approved estimates.
- Validate currency and unit before rates are used in calculations.
- Review duplicate or overlapping role variants.
- Document client-specific, project-specific, or manually overridden rates.
- Check that overhead is not included in the rate and then added again.
- Schedule periodic review, while allowing controlled updates when conditions change.
The Local Government Association's fee-calculator guidance illustrates that true staff cost can include salary, employer on-costs, non-productive time, and overhead, depending on the purpose and local model. HMRC's service-pricing guidance separately notes that service price can reflect factors beyond cost. Together, these sources reinforce why cost and billing fields need distinct definitions.
What does the Managed Margin rate card store?
Managed Margin keeps resource profiles by designation, seniority, specialization and delivery location, each with an hourly planning rate in the workspace currency. Profiles can be added directly or imported from a CSV or Excel file: every row is previewed and nothing is written until the whole file is confirmed. A changed rate becomes a new rate identity, and finalized pricing strategies keep the rate they used as a snapshot.
Individual employee actual costs are separate, optional and protected by their own permission; client billing rates are set per project or service order with dated ranges. Governance of the underlying numbers remains the customer’s responsibility.
For the conceptual distinction, read project cost rate vs billing rate. To apply the card, see bottom-up project cost estimation or project pricing software.
Real example: a finance partner fixes inconsistent estimates
An illustrative story with invented figures, to show how the idea works in a real office.
Daniel, a finance partner, notices that two presales consultants priced similar jobs and used USD 55 and USD 62 for the same role. Neither rate was approved for the date of the estimate: both had been copied from older files, so he first checks what each was valid for.
He builds a one-page rate card: role, level, rate, unit, start date and approver. A senior analyst is USD 65 from 1 July. He asks everyone to use only the card.
The next two estimates for a similar job (an invented result, not evidence of a typical improvement) differ by only 3%, and the difference is explained by hours, not by rates.
When do you build a rate card, and what comes before and after?
| Stage | Owner | Checkpoint |
|---|---|---|
| Build or revise | Finance, with HR for employment inputs | Definitions for cost rate, billing rate, unit and location are written down |
| Approve | A named finance owner | Each row has an effective date, a status and an approver |
| Use in estimates | Presales consultants | Only approved rows are used; a gap is flagged, not filled informally |
| Handle exceptions | Finance with the presales lead | Client-specific and manual rates are recorded as exceptions with an owner |
| Review | Finance, on a schedule and when costs change | A new effective row is added; history is not overwritten |
Rate cards: frequently asked questions
How often should rates be reviewed?
Set a review interval proportionate to rate volatility and materiality; annual review is one possible policy. Revisit rates sooner when compensation, supplier costs, working calendars or relevant assumptions change materially.
How do missing rates get handled?
With a flagged fallback and approval, as in the missing-rate section above.
What is a project rate card?
A governed table of role-based rates (cost, billing or both) with the unit, currency, effective date, owner and approval status. Everyone who estimates uses the same card, so two people pricing the same job get the same answer.
Continue the sequence: guides to read next
- Parametric Estimating in Project Management, With an Example: estimating from a driver such as interfaces or screens
- Resource-Based Estimating: How to Estimate Project Cost: estimating cost from roles, hours and rates
- Cost Rate vs Billing Rate: Costing and Rates Explained: the two kinds of rate in the card
- How to Share Project Margin With Sales Without Showing Salaries: controlling who sees rates
Sources and methodology
- UK Government, Service Costing in Government. Used for transparency, consistent allocation, validation, and version-control principles.
- Local Government Association, Fee calculator guidance. Used for examples of cost components that can inform hourly staff cost.
- HM Revenue & Customs, Pricing of services. Used for the distinction between cost input and broader service-pricing factors.
- The sample card and calculation are original. Product claims were reviewed against the current Managed Margin application on 26 September 2026.