Craft Pay-Band and Rate-Sheet Governance

An industrial contractor’s pay rules have to work by craft, skill level, certification and client site. A helper’s next step, a journeyman’s approved premium, a zone allowance and a negotiated site rate can each follow a different rule. When those rules sit in separate spreadsheets, it can be hard to tell which version is approved, when it takes effect and who may change it.

Grahall helps turn those rules into a governed pay structure and rate-sheet process. The aim is to give HR, operations, payroll and estimating a consistent set of approved inputs, while keeping employee pay, client billing and bid assumptions distinct.

What We Design

• Craft bands and progressions: job families, helper and journeyman levels, progression criteria, ranges and exception authority.
• Certification premiums: eligibility and approval rules for credentials such as NCCER certifications, including how validity and expiration affect a client-approved premium.
• Per-diem, zone and site rules: separately defined components, eligibility, effective dates and approved combinations, aligned with the client’s policies and reviewed with its payroll and tax advisers as needed.
• Client-site rate sheets: negotiated terms linked to the relevant contract, site, craft and period, with separate employee pay and client billing fields.
• Governance: named owners, approvals, effective dates, version history, exception records and controlled release of changes.

One Approved Rate Version, Two Uses

Payroll needs the approved pay components for the work performed, at the right site and on the right date. Estimating needs a labor-cost basis for a bid, including approved assumptions about burden, allowances and expected rate changes. A client billing rate is a separate commercial term; it is not automatically an employee’s pay rate.

We define how the same approved rate version supports both uses, where the calculations differ, and how changes are reconciled. For example, a newly approved certification premium may affect an eligible employee’s pay and future labor-cost estimates without changing an already negotiated client billing rate. The rules determine that treatment, and authorized people approve exceptions.

What You Get

A craft and progression catalog, pay-component definitions, governed rate-sheet templates, an approval and exception matrix, and a version and effective-date policy. The implementation specification sets out required fields, payroll and estimating mappings, access roles, test cases and acceptance criteria. Exports, interfaces and automated checks are included only where agreed in the implementation scope.

Grahall’s Methodology, Client-Selected Engineering

Grahall leads the compensation methodology, pay design, governance and client relationship. The client approves policy and rates and chooses who builds any supporting system.

The proposed delivery model includes Fellowship Automation LLC as an optional engineering provider for a system deployed in the client’s own cloud. Fellowship is a separate, related-party firm, not a Grahall division. The relationship, any financial interests and any compensation arrangements are disclosed before selection. Advisory and engineering responsibilities and fees are separately identified, and the client may choose its own team or another provider.

The client retains ownership of its data. Hosting, access, security, support and handover arrangements are agreed before a build starts. Software ownership, licensing and rights to reusable methods are addressed separately in the contract; a client-cloud deployment does not by itself determine those rights.

Start With a Defined Pilot

Start with selected crafts and sites. Inventory the current rate sheets and approval rules, settle the pay design, and test a representative set of normal changes and exceptions. Where a build is included, payroll and estimating owners verify the outputs before approving use.

The aim is to develop reusable templates and configuration patterns so later deployments need less work from scratch. Each client’s rules still require validation, and its confidential data and negotiated rates remain its own. This is a proposed service and delivery model, not a claim that a packaged product has already been deployed.

How to Measure Value

Agree a baseline before the pilot: time to approve and release a rate change, payroll exceptions traced to incorrect rate inputs, time spent reconciling rate-sheet versions, and time to refresh labor assumptions for a bid. Compare the pilot results with that baseline before deciding whether to expand. Savings and delivery timelines depend on the agreed scope and starting conditions.

Common Questions

Does this replace our payroll or ERP system?
The scope starts with pay methodology and rate governance. It defines approved inputs for existing payroll, ERP and estimating processes. Whether to use existing system features, controlled templates or a custom application is a design decision; integrations require a separate agreed scope.

Do we have to use Fellowship Automation?
No. The client chooses the engineering provider. Fellowship is a proposed option, with the related-party relationship disclosed before selection and any build governed by its own scope and terms.

Will software or AI decide what an individual worker earns?
The client sets pay policy and authorizes pay decisions. Any system applies approved rules and routes exceptions to authorized people. AI is not required for the offering and is not an independent decision-maker on an employee’s pay.

Related Grahall Services

Job Architecture, Pay Structures and HR Data Readiness | ERP and HCM Selection Advisory | Client-Side Implementation Delivery | Total Rewards Strategy Services

To discuss a scoped pilot, contact Ali Riyaz at ali.riyaz@grahall.com or 603.205.5033.

Grahall does not provide legal or tax advice.