adhibit
Offer // Davis-Bacon · free

Send me one week of certified payroll. You get a findings report back in two business days.

No call. No login. No access to any of your systems. Two CSV exports by email, a written report in return. It costs nothing and there is no sequence afterwards.

The check nothing else runs. The rate on your wage determination is a floor, not the floor. What you owe on a given hour is the highest of three numbers: the determination rate for that classification, the federal FLSA minimum, and your own state or local minimum wage. Determinations are revised on their own schedule and state minimums move on theirs, so the two drift apart routinely and no certified payroll system compares them for you. Florida is the live example: the state constitutional minimum is $15.00 as of 30 September 2026, while the Pinellas County heavy-construction determination in force at that date (FL20260139, rev. 1, effective 17 May 2026) still lists LABORER: COMMON OR GENERAL at $9.26 and LABORER: LANDSCAPE at $7.25. Paying the determination rate there satisfies Davis-Bacon and breaks state law in the same stroke. Whatever state you build in, tell me the county and the construction type and I run that comparison against your determination and your state's floor.

If you file certified payroll in Florida, the change lands on 30 September 2026. That makes this week the cheap time to look.

Why I'm offering this

I spend my days as a superintendent on commercial jobsites, and I build integration software for contractors. Certified payroll is where those two things meet, and it is the most under-watched compliance surface I see.

It is filed weekly, for the life of the job, signed under penalty of perjury — and almost nobody checks it before it goes out. The errors that matter are not typos. They are structural, they repeat every week once they start, and they surface in an audit long after the crew has moved on.

I would rather show you what I find than tell you what I know.

What I look at

CheckWhat goes wrong
Hours broken down by classificationIf someone works two classifications in a week and the timecard cannot show which hours were which, the breakdown is not there to be filed. A cost-code gap in your timekeeping quietly becomes a crew-week you cannot defend.
The arithmetic closesGross for all work, less deductions, equals net — exactly. Deductions come off all work and are not pro-rated to the project, so it either ties or it doesn't.
Overtime against the 40-hour weekSummed across every job, not per job — which is how it gets missed when someone splits a week between two projects.
Apprentice ratiosBy ratio group, and whether the apprentices on the payroll are actually registered.
The wage floor, not just the determinationSee the note above. This is the one nothing else checks.

What I don't do

Stated up front, because reports that overclaim are worthless.

What to send

Two files, in whatever format your system exports. If your column names differ, send them anyway — mapping them takes me thirty seconds.

1 — Timecards (one row per person, per day, per cost code)

employee_id, job_id, work_date, cost_code, hours, ot_hours

2 — Payroll (one row per person, per week)

employee_id, week_ending, gross_all_work, net_paid, [your deduction columns]

Plus a short note listing, for each job: the county, the construction type (building / residential / highway / heavy), and the wage determination number and revision if you have it to hand.

Please don't send full Social Security numbers. Last four digits, or an internal employee ID, is all I need — my tooling rejects anything longer. What happens to your data is on the data handling page.

What comes back

A written report naming every finding, with the row or date it came from, sorted into three buckets: must fix before filing, needs a decision, and for your awareness. Every item traces back to your own export, so you can check my work in a couple of minutes.

If nothing is wrong, the report says so plainly. That is a perfectly good outcome and it costs you nothing either way.

Then what

Nothing automatic. There is no drip sequence and I won't call you.

If the findings show a pattern rather than a one-off, I do a paid written diagnostic ($250–$500): I review 20–50 of your real records and return a one-page findings memo plus a scope for fixing the underlying cause. Most of the time that cause is a cost-code structure that doesn't map cleanly onto the classifications you bill against — a fixable, one-time problem rather than a permanent tax on your payroll clerk.

If it doesn't, you've had a free review and I've learned something about how your shop runs.

How to start

Email the two files to tom@adhibitsystems.com with "payroll review" in the subject. I'll confirm receipt the same day and send the report within two business days.