Is the generated PDF really the current WH-347 form?
Yes. It's the Department of Labor's actual WH-347, revision January 2025, OMB No. 1235-0008. It's not redrawn and it's not an approximation that looks close enough. Both pages, including the Statement of Compliance, are filled from the same data you enter once.
How current are the wage determinations?
As current as SAM.gov itself. Rates are fetched live from SAM.gov at the moment you look one up or check a rate against it, matched by the WD number on your contract. Nothing is cached on our side and nothing is typed in from a rate table maintained by hand. If SAM.gov has updated a determination, that's what you see the next time you check it.
The parser reading those determinations was tested against 5 real wage determinations from 5 different states, 385 table rows total. It read 385 of 385 correctly. Details on how that test worked are on the about page.
How are superseded wage determinations handled?
SAM.gov marks every wage determination active or inactive in its own data. That status is read directly and shown as a warning when a determination is inactive, not folded into a success message. You see it before you rely on the rate, not after.
What happens if SAM.gov is unreachable?
The check fails visibly, with a specific error, instead of silently falling back to a guess: connection failures, a determination that doesn't exist, SAM.gov rate limiting requests, or a response that can't be read all show their own message. There is no cached copy behind the scenes to fall back to and paper over an outage.
If SAM.gov is down or slow, the honest options are to wait and retry, check sam.gov directly, or enter rates manually and verify them once the outage clears. There is no third option where the tool quietly shows you a number it isn't sure of.
Who is liable if a certified payroll report is wrong?
You stay in control of what gets filed, and that comes with the responsibility too. The tool checks your numbers against public wage determination data and flags what looks wrong, but you're the one who signs the Statement of Compliance, and you remain responsible for the accuracy of what you submit to a contracting officer. The service is provided as is, and liability is limited as described in the terms. Same as a calculator, a spreadsheet, or an accountant's software: the tool checks the arithmetic and the published rule, the signature is still yours.
Can I see the history of an old report, or track changes to it?
Not yet, and it's worth saying plainly rather than around: each week's payroll is currently a single editable record, no separate version history. If you edit a payroll after filing it, the previous values aren't retained anywhere in the product. Keep your own copy of a payroll before changing it post-filing, the same way you would with a spreadsheet you edit in place.
It's on the list to build. If a locked, audit-trailed version of a filed week matters for how you work, tell me, that kind of feedback is what decides what gets built next.