Compare Service Rate Cards Across Sites on a Like-for-Like Basis

Which roles are comparable across sites?

Start with a work description that the site owner can confirm; for each proposed role, record the tasks, required capability, responsibility, supervision and evidence of suitability. Ask suppliers to map their own titles into that description and flag partial matches. Keep a role unmatched where the proposed person or service lacks a required capability. A shared job title should be an input to review, with the underlying scope retained beside it.

For digital and technology services, SFIA’s framework-owner guidance describes skill-and-level rate cards for resource comparisons. It also says the framework does not define an organization’s jobs or cover every product-specific skill, qualification and industry requirement. Use it where its scope fits, then add the actual technical and site requirements. An industrial trade or regulated task needs its own relevant qualification evidence and responsible reviewer; a digital-skills level does not establish equivalence.

Keep seniority and task allocation explicit in the proposed mapping. Ask whether the work requires independent diagnosis, supervised execution, specialist approval or a named lead. Record which responsibility is included in the price and which triggers a different charge. Use the same approved role definition in the bid sheet, staffing proposal and service schedule so the commercial comparison can be traced to what the site expects to receive.

How should geographic labor evidence be used?

Use an occupational wage measure to investigate a labor assumption; the BLS technical notes for the current OEWS estimates describe occupation-and-area wage statistics assembled from survey panels over a multiyear window, with model-based estimation. They measure employee gross straight-time pay and exclude specified premium pay and benefits. Their occupational groups do not establish a supplier’s seniority tiers, available workers, overhead or profit. Retain the estimate’s reference date and population with the comparison.

Identify where the proposed work will actually be performed and the labor market the supplier expects to use. Ask about on-site attendance, remote delivery, travel, mobilization and any site-specific access or competence requirement. Select a geographic comparison only after that delivery basis is understood. Avoid multiplying an entire bill rate by a wage or consumer-price ratio as a default normalization rule; the treatment of each commercial component needs its own stated assumption and agreement.

What belongs inside the hourly price?

Separate the price structure from the wage observation. Federal time-and-materials provisions, within their federal acquisition scope, describe hourly rates containing wages, overhead, general and administrative expenses, and profit. That is a useful illustration of why an employee wage and a contract selling price measure different things. A private buyer must inspect the actual offer and agreement rather than assume the federal composition or rules apply to every supplier.

Ask each bidder to state the inclusions, exclusions and triggers relevant to the proposed service. Retain ordinary hours, overtime billing, minimum call-outs, travel time, expenses, supervision, tools and any separately charged support. A supplier may decline to disclose its internal margin; the comparison can still require clear selling-price inclusions and comparable delivery commitments. Keep statutory worker-pay obligations separate from what the buyer has commercially agreed to pay the supplier, with appropriate contract and employment expertise reviewing any jurisdiction-specific issue.

How can a common scenario expose differences?

Build an authored comparison register for the actual procurement; ask the site owners to approve a reference workload and staffing assumptions before ranking the offers. Where demand is uncertain, evaluate an agreed range or an alternative scenario and show which assumption changes the outcome. Leave unresolved terms visible instead of substituting a convenient estimate. The register below organizes that review; it is a proposed decision aid, not a validated benchmark or an official pricing standard.

For a hypothetical comparison, take the same approved mix of ordinary work, specialist attendance and exceptional call-outs to each bidder. Extend the offered rates using those role-hours, then add the separately chargeable items under each offer’s stated conditions. Show exclusions and uncertain quantities alongside the total. If one offer provides a different service scope, retain it as an alternative proposal until the technical owner confirms whether a direct comparison is appropriate.

How should blended and named-resource offers be tested?

Treat the staffing commitment as part of the proposed service; for a blended offer, ask which capability mix the charge assumes and what substitutions the agreement permits. For tiered or named-resource pricing, verify the mapping and the conditions for replacement or escalation to another role. Run the same reference workload under each permitted mix. Keep the commercial scenario distinct from an assertion about which individual will be more productive; that requires evidence from the work itself.

The systematic service-productivity review explains why provider efficiency alone leaves out customer inputs and service quality. It synthesizes diverse service literature and does not estimate the performance of a particular facilities contract. For this comparison, ask the technical owner to define acceptable outputs and identify buyer dependencies such as access, information and approval. Review those requirements beside the modeled charge so the preferred hourly schedule does not silently redefine the service being bought.

Which escalation terms need a separate review?

The BLS ECI escalation guidance asks contracting parties to identify the cost component, an appropriate series, reference periods and adjustment frequency, and to provide for missing data. It cautions against seasonally adjusted series for escalation agreements. Use those statistical distinctions to frame a review with the contract owner. The guidance does not write a commercial clause, impose an annual cap or prove how much a particular supplier’s costs changed.

Retain the exact series identifier, base and comparison periods, the component being adjusted and the agreed formula in the working record. Ask the contract owner to resolve any cap, floor, downward movement, revision, discontinuation and notification treatment. Test an adjustment against the signed wording before applying it. Keep index-driven changes separate from a negotiated scope change so the next reviewer can see why the price moved and which authority accepted it.

What should be approved before award?

Take the role mapping, comparison register, supplier clarifications and unresolved assumptions into the structured RFQ workflow. Keep the separate supplier-risk assessment linked to actual capability and delivery evidence. Ask the technical owner to accept the service scope, finance to review the scenario and treatment of uncertainty, and the contract owner to confirm the commercial terms before the authorized award decision. Retain the evaluated version for subsequent invoicing and change reviews.

How should AI agents assist the comparison?