Certified Payroll Monday: Nine Owner Portals, No Export Button, and an Agent That Can Now Click Through All of Them

Question, and answer it out loud before you keep reading: who at your company has the login to the state DOT's certified payroll site? Not the accounting system — the owner's site. The one with the password that expires every 60 days, the one that rejects an upload if a laborer's classification is spelled differently than it was last week.

In most heavy civil contractors the answer is one person, usually a payroll clerk with fifteen years there, and the second answer is that nobody else really knows how it works. That is the quiet operational risk in this trade. Every week, on every federally funded job, somebody has to log into somebody else's website and put certified payroll into it — and that website has no export button, no connection to your accounting system, and no interest in your convenience.

What Monday actually looks like in the payroll office

Payroll closes Friday in Vista or Foundation. Monday morning the clerk starts producing WH-347 forms — the federal certified payroll form, one per job per week, with every worker's classification, hours by day, gross, deductions, net, and the fringe benefit statement, signed under a statement of compliance that carries criminal penalties for a false certification.

Then the uploads begin. The county job goes into LCPtracker. The state highway job goes into AASHTOWare Project Civil Rights and Labor. The transit authority job uses Elation Systems. The city job wants a PDF emailed to a project inspector who bounces it back if the file is named wrong. The airport job wants it in B2Gnow along with the monthly DBE payment confirmations, where you also have to confirm what you actually paid every disadvantaged business subcontractor, and then chase those subs to confirm they received it. If you are the prime, you are also collecting sub-tier payrolls from six subcontractors, half of whom send a scanned photo of a handwritten form on Wednesday.

Every one of those systems rejects things. Classification not on the wage determination. Fringe rate below the determination. Apprentice ratio exceeded. A missing "no work performed" payroll for a week the crew was rained out, which the portal still expects. Each rejection is another login, another correction, another upload. And the consequence of falling behind is not a scolding: on most state and federal contracts, delinquent certified payroll lets the owner withhold your progress payment. That is a cash flow event on a business that lives on progress payments.

Computer use: what it means when there is no export button

The development that matters here landed properly in 2026. Agents can now drive a screen the way a person does — open a browser, log in, click through menus, fill fields, upload a file, read what came back, and react to it. No connection between systems required, no cooperation from the portal's owner, no waiting for a state agency to build something.

Put plainly: if a person can do the job with a keyboard and a browser window, the work can now be handed to an agent that uses the same keyboard and the same browser window. That is a bigger deal in heavy civil than in almost any other trade, because this industry runs on other people's portals — owner compliance sites, one-call locate systems, prequalification renewals, bid sites, DBE reporting — and essentially none of them will ever connect to your accounting system.

flowchart TD
  A["Friday payroll closes in Vista"] --> B["Agent builds a WH-347 for each active job"]
  B --> C["Agent logs into each owner portal in turn"]
  C --> D["Uploads payroll, signs the statement of compliance"]
  D --> E{"Portal rejects a line?"}
  E -->|Classification or fringe mismatch| F["Agent corrects, notes what it changed, resubmits"]
  F --> D
  E -->|Accepted| G["Confirmation screenshot filed to the job folder"]
  G --> H["Payroll clerk reviews the exception list at 9 a.m."]

The first Monday it runs

The clerk does not stop working. She starts later and finishes earlier. Overnight the agent has pulled the payroll register, generated eleven WH-347s, and worked through the portals one at a time. Eight went in clean. Three came back with problems, and they are sitting in a short list with a screenshot of each rejection message.

The first is a new hire coded as Laborer Group 1 when the work he performed that week was pipe laying, which the wage determination puts in a different group at a higher rate. That is a real finding, and it is exactly the kind of thing that turns into a back-wage claim eighteen months later during a compliance review. The second is a "no work performed" payroll the portal expects for a job shut down by weather — the agent flagged it rather than certifying anything, which is correct, because a compliance statement gets signed by a human being. The third is a sub who has not turned in week 31, so the agent has already drafted the reminder email to that sub's office manager and it is waiting for the clerk to hit send.

Fifteen minutes of a person's morning instead of most of a day. And critically, the knowledge of how each portal behaves stops living only in one head.

The arithmetic: hours, and then the money that arrives sooner

Two effects, and the second one is bigger. Illustrative assumptions for a contractor with eleven active prevailing-wage jobs and six subcontractors.

The $1,700 is the small version. The bad version is the season where the withholding lands the same week as a fuel bill and a bonding renewal, and you are calling the bank instead of running the job. Most owners will tell you the reason to fix this is not the clerk's hours — it is never being the reason a payment is held.

Three things not to let it click

Do not let it sign the statement of compliance unattended. That certification carries real legal weight under the Davis-Bacon Act and the person whose name is on it should have looked at what is being certified. Let the agent stage everything and stop at the signature.

Do not let it fix a classification on its own. When it thinks a worker is coded wrong, that is a question for the superintendent about what the man actually did that week, not a field for software to change. Reclassifying quietly to make a portal accept a file is how you build a very expensive problem.

Do not give it a shared login for anything where the audit trail matters. Give it its own credentials with its own name, so that when a compliance officer asks who submitted week 27, the answer is traceable. Several states now have their own AI statutes on the books — Texas and California both since 1 January 2026, with Colorado, New York, Utah, Nevada, Maine and Illinois running their own rules — and the safest posture on government-facing work is that everything an automated system did is logged and attributable.

One more practical warning: portals change. A state redesigns its upload page in February and the agent will fail. Expect that, keep the clerk's knowledge alive, and treat the first failure of the season as normal rather than as proof the idea was bad.

Frequently asked questions

Can it handle our one-call locate tickets too?

Yes, and for a lot of underground contractors that is the more valuable job. Locate tickets expire — commonly in 14 to 21 days depending on the state — and renewing them means logging into Texas811, USA North, Julie or whichever system covers you, ticket by ticket. Crews standing around waiting on locates is expensive, and the renewals are pure clicking against a list of open excavations. Same idea, different portal.

What if the portal has multi-factor authentication?

Then a person still has to approve the login, which is fine — that is thirty seconds instead of four hours. Some contractors set the agent to run while the clerk is at her desk so she can approve prompts as they come up, then walk away.

Does this work for the FHWA-1391 report?

The annual EEO report based on the July payroll period is a good candidate because it is entirely a data assembly job out of payrolls you already have. It is also the report most likely to be done badly in a rush every August, which is exactly why it is worth putting on a system that pulls from the same source every time.

Our payroll clerk is retiring in two years. Does this help with that?

That is arguably the strongest reason to do it. When the process runs as written steps rather than as one person's habits, handing it to the next hire takes a week instead of a season. Start documenting it now, while she is still there to correct what the agent gets wrong.

A note on the calls compliance work generates

Chasing sub-tier payrolls, DBE payment confirmations and inspector questions is mostly phone work, and it lands during the hours everyone in the office is doing something else. CallSphere builds AI voice and chat agents that answer the office line and web chat, take the job number and the caller's question, and book the callback with the right person instead of letting a subcontractor's office manager go to voicemail three times. It does not upload your certified payroll. It keeps the follow-up conversations from becoming the reason a submission slips another week.