Construction employee scheduling software assigns each task to workers who hold the trade tickets and safety certifications that task requires, dispatched in the order the local agreement sets, at the classification the project is paying for. The decision it makes is not who is free: it is who is allowed on that task, on that site, today.
The ticket decides who gets the task. The site decides the rate.
Trade tickets with expiry dates. Union hall dispatch order. Safety certifications an inspector will ask for by name. A wage classification that has to match the work actually performed on that project. Checked while the crew is being built, not after payroll finds it.
A crew moves across town by mid-morning, and only some of your people can go.
The dispatch board is a whiteboard and a group text.
An availability list hands you a name. It will not tell you the three things that decide whether the name is usable:
- Whether they hold the fall-protection ticket the task requires.
- Whether their equipment-operator certification is still current.
- Whether the move pushes them past an hour threshold the local agreement prices at a premium.
WorkAxle settles all three before the crew is dispatched. Available-worker lists are computed from the role, skills, and certifications on the worker profile, so someone without the ticket never appears for work that requires it. Moving a worker to another site checks what that site and that task require.
Tickets carry effective dates. A renewal alert fires while the ticket is still valid. Once it lapses, expiry triggers automatic reclassification and the rule engine flags the assignment.
The engine warns, it does not lock the superintendent out. The judgment call still gets made, with the rule on screen and the override written to the log. That log is what a failed inspection later asks you to produce.
The same logic assembles the crew in the first place. Crews assembled by trade, ticket, and union hall rules is one engine doing one job, with rotations and remote sites handled in the same place.
Dispatch order is a contract term, not a courtesy.
Local agreement rules, seniority, premiums, and overtime thresholds are codified once and enforced while the crew list is generated. Several agreements can run side by side in one engine, which matters the moment one project carries a local the next project does not.
For a task nobody has taken, the call list is the record:
- Eligible workers open in an order you can sort by seniority date or rotation.
- Each call is logged with a status, a note, and a timestamp.
- The assignment is made on acceptance, and every overtime offer attempt is logged automatically.
That is what makes dispatch order provable rather than remembered. When a grievance arrives four months later, the sequence is a query, not an archaeology project.
Union hall dispatch order, trade tickets, and site-specific safety rules sit in the same rule engine, which is the combination that counts when the inspector is already on site.
The hour has to land on the site where the work happened.
Workers clock in from mobile, and each punch is validated against the assigned site's geofence. A punch from outside the boundary is flagged for review, so the hour ties back to the site, the job, and the classification it was worked under.
Hours also accumulate centrally. A worker who spends Monday and Tuesday on one project and Wednesday on another carries one running total, so overtime and rest thresholds apply across every assignment they hold rather than per site. Cross-site coverage stops quietly breaking a rule that only surfaces in a reconciliation.
Premiums and differentials are applied at the point of time classification. The number is right when the punch lands, which is why the export needs no spreadsheet in between.
The classification is a payroll obligation before it is a crew decision.
On a prevailing wage project, the classification of work actually performed is what the weekly record has to certify, per worker and per covered contract. That record is only as good as the hours behind it, so the classification has to be attached when the assignment is made, not reconstructed on Friday.
- Classifications and prevailing wage rates are codified per project and applied to the hours worked on that site, so the rate is correct at the point of capture.
- Configuration is effective-dated, so a new wage determination can be staged with a start date and activate without touching crews already dispatched.
WorkAxle sits upstream of the filing. It produces and holds the hours record, and your payroll system produces and signs the submission. What the regulation asks for in its own words is set out on the certified payroll software page.
Prevailing wage and labor rules vary by contract and by jurisdiction, and they change over time. Verify against the contracting agency and the wage determination that applies to your own projects. Nothing here is legal advice.
Bring one week and one project. We will classify it live.
Your wage determination, your local agreement, and the crew that split across two sites on Wednesday. We walk it on your numbers, not a sample data set.
Where several agreements already run in one engine.
A national airport-operations security provider, Canada
Multiple collective agreements running side by side, a fixed contract start date, and no soft launch. The provider went live across major Canadian airports in eight weeks, against an industry norm of twelve to twenty-four months. It reported 100% ROI within two months of go-live, a 22% reduction in workforce-management administration costs, and 14% fewer error corrections.
The rule depth is the part that transfers. Several agreements, seniority-driven dispatch, and certifications gating assignment were configured rather than custom-coded, which is why they stood up fast. WorkAxle implementations run 4 to 5 times faster than legacy systems, which quote 18 to 24 months.
The construction vertical in full, including geofenced time capture and audit readiness across job sites, sits on the construction operations page.
Frequently asked questions about construction employee scheduling software
What is construction employee scheduling software?
Construction employee scheduling software assigns each task to workers who hold the trade tickets and safety certifications that task requires, dispatched in the order the local agreement sets, at the classification the project is paying for. It computes available-worker lists from the role, skills, and certifications on the worker profile, tracks tickets in effective-dated fields so expiry flags the assignment, validates each punch against the assigned site's geofence, and logs every assignment, offer, and override for audit.
How is it different from a general crew scheduling app?
A general crew app answers who is free. A construction operation needs to know who is allowed on that task, on that site, today. That depends on the trade tickets and safety certifications the task requires, the union hall dispatch order and seniority rules in the local agreement, the hour threshold the worker is approaching across every site they have worked this week, and the wage classification the project carries. Those checks run while the crew list is being built rather than in a reconciliation after payroll.
Can it stop a worker with an expired ticket from being dispatched?
Tickets and certifications carry effective dates. A renewal alert fires while the ticket is still valid, and expiry triggers automatic reclassification, so the worker drops out of the eligible list for any task that requires it. A superintendent who needs to make a judgment call can still override, with the rule shown and the override logged. That log is what a failed inspection later asks you to produce.
Does it handle union hall dispatch order and local agreement rules?
Yes. Local agreement rules, seniority, premiums, and overtime thresholds are codified once and enforced while the crew list is generated, and several agreements can run side by side in one engine. For a task nobody has taken, eligible workers open as a call list you can order by seniority date or rotation, and each call is logged with a status, a note, and a timestamp. Every overtime offer attempt is logged automatically, which is what makes dispatch order provable rather than remembered.
Does it produce certified payroll for prevailing wage jobs?
No. WorkAxle is not a payroll system and does not produce or sign the filing. It sits upstream of it. Classifications and prevailing wage rates are codified per project and applied to the hours worked on that site, configuration is effective-dated so a new wage determination activates without touching crews already dispatched, and the hours record exports per worker, per classification, and per contract. What the regulation asks for in its own words is set out on the certified payroll software page.
Bring the crew move your current system cannot make cleanly.
See how job-site hours get captured.
Mobile clock-in validated against the site geofence, premiums applied at capture, and hours tied to the project they were worked on.
See how one operation did it.
Multiple collective agreements, a fixed start date, live across major Canadian airports in eight weeks.
Bring your hardest ticket requirement.
Your projects, your trade certifications, your local agreements and wage determinations. We will walk it live.