HAWKEYE SYSTEMS

Crew Skills Matrix: How to Build One That Crews Use

Build a crew skills matrix that shows who can do what on site: layout, rating scale, evidence, expiry dates, work assignment and productivity checks.

Plan a walkthrough

A crew skills matrix is a grid with your people down the side and the work and credentials your jobs require across the top. Each cell says whether that person can do the task, how well, and for credentials, whether the proof is still valid. Built from the work you actually assign and kept current with dates and evidence, it lets a supervisor answer three questions in seconds: who can do this, who is cleared to be here, and who is one person short of a problem.

This guide walks through the layout, a rating scale you can adopt today, how to verify and update ratings, how to use the grid to assign work and plan training, and how to connect it to crew productivity numbers.

Hefieldops

Keep Field Readiness in View

Hawkeye Field Ops connects field activity with office management, helping construction teams review documented site activity and workforce readiness.

Visit Hawkeye Field Ops

TL;DR

Table of Contents

What a construction crew skills matrix shows

PIAGO describes a skills matrix as a grid with people down the side and capabilities across the top, where each cell shows whether a person can do the capability and how well. In construction, that grid usually carries two kinds of information at once. SkillsMatrixTemplate.com separates trade competence (can they do the work, scored 0 to 5) from compliance (are they carded to be here, such as plant tickets and site inductions).

The examples in much published guidance come from the UK, where cards like CSCS are the norm. In the US the equivalents are things like OSHA 10 and 30-hour cards, equipment operator certifications, fall protection and confined space training, first aid and CPR, and owner or site-specific orientations. The structure is the same: the credential, its issue date, its expiry, and where the proof sits.

A useful matrix answers these at a glance, as TrainMe’s construction guide puts it: who is qualified for what, whose credentials are current, and who is missing something they need for the work in front of them.

Two views, not one score

Keep trade skill and credential status in separate columns. A strong groundworker whose card expired yesterday is not site-ready, and a single blended number would hide that. The same logic applies to a US operator with excellent trenching ability and a lapsed excavation competent-person training record. Skill is one question. Clearance is another.

Choose the columns first

Start from the work, not from the people. PIAGO’s advice is that columns should match how the site really allocates work. Its example is “Excavator, 30–50t, trenching near services” rather than “Equipment operation.” If your superintendent says “I need someone who can run the mini-ex and locate utilities,” that is the column.

A practical column set for a general contractor or civil crew might look like this:

Group | Example columns | What the cell records

Trade tasks | Formwork, rebar placement, concrete finishing, pipe laying, trench shoring | Proficiency level

Equipment | Skid steer, excavator by class, aerial lift, forklift | Proficiency level plus operator certification status

Safety training | OSHA 10 or 30, fall protection, confined space, first aid and CPR | Completion date and expiry

Site-specific | Owner orientation, site induction, drug screen clearance | Status and date

Leadership | Crew lead, flagger, designated competent person for named hazards | Appointed, trained, evidence

Start with the 15 to 25 columns your foremen actually use to staff a week. You can add more later. PortalBase advises starting small and using defined levels rather than simple box ticks, and that is the right instinct: a grid with 80 columns and half-empty rows teaches the crew to ignore it.

Fields worth adding per record

Essential Site Skills lists a practical set of fields for a training matrix: employee name, job role, main responsibilities, required and recommended training, last completed date, refresher due date, booking status and notes. CheckSafe adds three that matter for audits: the date last checked, who checked it, and where the evidence sits.

Pick a rating scale people can apply the same way

The scale only works if two supervisors would give the same person the same rating. Two scales from published guidance are easy to adopt.

A four-level competence scale. PIAGO recommends four levels: not competent, competent with supervision, competent independently, and can train and assess others. It maps cleanly onto how crews already talk: helper, journeyman, lead.

A status scale for training records. PortalBase suggests levels such as Not trained, In progress, Trained and Verified, where Verified means a qualified person watched the performance and signed off, which enables unsupervised work.

For most construction crews, combine them. Use the four-level scale for trade tasks and equipment. Use status plus expiry for safety training and tickets. Write the definition of each level at the top of the sheet, with a one-line example of what you would see someone do at that level.

Fill it from evidence, then keep it current

The most common failure is a matrix filled from memory during one meeting and never touched again. PIAGO recommends populating cells from evidence rather than memory and putting dates on everything. CheckSafe makes the same point from the audit side: a matrix is defensible only if each rating can be backed by evidence, stored and referenced with dates and the reviewer’s identity.

A build sequence you can run in a week

  1. List everyone who works on your sites. Include labor-only, agency and subcontractor workers before they start. CTC South West’s guidance is explicit about listing everyone on site.
  2. Define the columns from the work you assign (see above) and set a required level for each task by role.
  3. Collect proof. Cards, certificates, operator evaluations, photos of credentials. Record an evidence reference once you have checked it.
  4. Rate trade skills with a foreman who has seen the work. Rate from what they have observed, and mark anything unobserved as unrated rather than guessing.
  5. Enter expiry dates for every credential that has one.
  6. Flag gaps where a person is below the required level or a credential is missing.
  7. Set a review rhythm and an owner for each crew’s rows.

The expiry column is the source of truth

Certly says the expiry-date column is the single source of truth: when a card is renewed, the row gets the new date as soon as the certificate arrives, and a missing date is a status in itself, meaning unverified. SkillsMatrixTemplate.com’s golden rule is to track validity, not just possession, because an expired certificate is a gap just like a missing skill. It adds that an out-of-date construction matrix can be worse than none, since it can put an unqualified worker on site.

For alert timing, TrainMe suggests three months ahead for long-lead cards and certificates, six weeks for annual refreshers, and a monthly review because the workforce changes constantly. Treat those as starting points and adjust to how long your own training providers take to book.

Paper, spreadsheet or software

A spreadsheet is fine for one crew and one site. It strains when you have agency labor, multiple projects and renewals landing every week. At that point, a digital skills matrix that records proficiency levels, assessor sign-off and supporting evidence in one place saves the manual reconciliation. If your pain is keeping registers current for subcontracted crews, a structured contractor onboarding process with named owners for each check keeps the data coming in at the gate rather than weeks later.

Use the matrix to assign work and close gaps

A matrix that sits in a folder is paperwork. One that supervisors open every morning changes decisions. CTC South West describes four daily uses: allocating work to competent people, checking competence before ticketed work, reviewing items that are due soon, and putting controls in place for anyone not fully competent.

A dispatch routine

KnowledgeCity outlines a five-step workflow built on verified skill data: the site scope generates a required-skills profile, the available pool is filtered by verified match, a gap report flags workers eligible for refreshers, check-in on arrival confirms the verified skill chain, and incident or near-miss data feeds back into the record. You can run a lighter version on any job:

Spot single points of failure

Read the columns, not just the rows. PIAGO warns that a capability held by only one person is a single point of failure if that person is injured, resigns or is unavailable. If only one operator is signed off on the lift, your schedule depends on their attendance. A column with a single name in it is your training priority list.

Plan training from the grid

Three patterns tell you what to book:

Book the refreshers in batches by crew so you lose one day of production, not five scattered ones.

What we think a crew matrix is really for

We see the skills matrix as the first link in a chain that runs from assignment to billing. If the record of who was qualified, who was assigned, what they did and how long they did it lives in four different places, every handoff is a place for an error or a dispute.

Our approach with Hawkeye is a connected, audit-ready record from field activity to office review. Crew scheduling, job planning, labor and equipment tracking, daily work records and workforce learning and readiness sit together, with configurable workflows that capture operational context from assignment through billing. Each handoff is meant to be clear and traceable.

A matrix is most useful when it is not a separate document someone updates on Fridays. It is most useful when readiness information sits where the assignment is made, and the same record then supports the daily log, the review and the billing documents. That is what we build for construction, field services and utilities teams.

Client

From skills to productivity numbers

Once you know who did the work, the next question is how well the crew performed. Productivity records and skills records answer different questions, but they explain each other.

Metrics to start with

The two simplest crew measures are standard in the industry. Units per labor hour is the output installed divided by the labor hours worked on it, measured in task-specific quantities, such as linear feet of pipe or cubic yards of concrete. Labor cost per unit is workers times hours times rate, divided by units installed. Neither number means much alone, so compare each against the same task on your own previous jobs. Always note the crew composition, conditions and rework for the period so the number has context. Our guide to labor productivity tracking in construction goes deeper on setting up the daily capture.

Why benchmarks need care

Public benchmarks are tempting, but comparing yourself to someone else’s number can mislead. The Construction Institute’s benchmarking report notes that benchmarking gives a basis for self-analysis and that productivity differences can be substantial across project type, size and nature. It gives the example that foundation-pouring productivity varies with foundation size. Its program has collected data from more than 200 projects since 2002.

A doctoral study on construction labor productivity benchmarking notes that productivity is often measured at three levels: industrial, project and task. For a crew supervisor, the task level is the one that matters, with the project level as a sanity check.

A 2025 meta-analysis of 27 empirical studies from 2000 to 2024 found that worker experience and skills, competent supervisors and effective communication are among the influential factors in construction labor productivity. It also reports that regional variations were prominent for most factors. In practice: compare like with like, by trade, task, location and conditions, and treat outside benchmarks as a rough reference, not a target.

Reading productivity with the matrix

When a crew’s units per labor hour drop, check the matrix before blaming effort. Was a person at “competent with supervision” running the task alone? Was the lead out and the second-in-command unrated? Did a certificate lapse and force a reshuffle? Conversely, when a crew beats its baseline, the matrix shows what mix of skills produced it, so you can repeat it. A self-updating baseline helps: one study in Construction Economics and Building updated baseline values monthly from the mean of previous monthly averages.

Where matrix records pay off beyond staffing

A current matrix does three more jobs.

Keeping a crew skills matrix alive

Habits matter more than design. These keep a matrix trustworthy:

Run it inside your field operations system

If you want readiness data to sit next to scheduling, labor tracking and daily records instead of in a separate spreadsheet, take a look at Hawkeye Field Ops. It brings crew scheduling, job planning, labor and equipment tracking, field ticketing and daily work records together, with Hawkeye Workforce Readiness for learning and readiness tracking. The construction version is on the construction page.

A demo shows how assignment, readiness and billing documents connect for your crews.

FAQ

What is the difference between a skills matrix and a training matrix?

A skills matrix rates how well people perform tasks, such as the four-level scale from not competent to can train others. A training matrix tracks courses, credentials and their expiry. On a construction site you need both, and keeping them in separate columns of one grid stops compliance from hiding inside a competence score.

How many skills should a crew matrix include?

Start with the 15 to 25 skills and credentials your foremen actually use when staffing a week of work. Write columns in the same terms they use, such as the equipment class and the task. Add more only when someone can name a decision that needs the new column.

How often should we update it?

Update it whenever something changes, such as a new hire, a completed training or a signed-off observation. Do a team review monthly, and set alerts ahead of expiry dates. One published guide suggests three months ahead for long-lead cards and six weeks for annual refreshers.

Who should rate a worker’s skills?

A foreman or lead who has watched the person do the task, ideally someone at the top level of the scale. Record the rater’s name, the date and the evidence. A rating without a reviewer and a date is hard to defend later.

Can I compare my crew’s productivity to industry benchmarks?

Only roughly. Productivity varies by project type, size, trade and location, so your own history for the same task is the stronger baseline. Use outside figures to sense-check, not to set targets.

Sources

Recommended

START WITH YOUR WORKFLOW

See your operations in action.

Walk through the handoffs that slow your team down—and see where a connected record can help.

Plan a walkthrough