County and trade context
Compare classifications against the supplied Illinois county schedule instead of relying on a generic statewide rate.
Review county, trade, wages, fringes, hours, and required payroll fields before preparing the Certified Transcript of Payroll workflow.
A clean Illinois workflow starts by tying the worker record to the applicable county and trade, checking the supplied wage and fringe requirement, and resolving incomplete fields before portal entry begins.
Illinois maintains an online Certified Transcript of Payroll Portal and publishes county prevailing-wage schedules. WagePilot focuses the launch workflow on payroll readiness before portal entry or template import.
Compare classifications against the supplied Illinois county schedule instead of relying on a generic statewide rate.
Calculate discrepancies deterministically and show the source row and supplied rate evidence.
Find incomplete worker, classification, hours, rate, and gross-pay fields before portal preparation.
Preserve the finding and proposed next action so the person filing can resolve it upstream.
Add county, project type, and the applicable prevailing-wage schedule.
Use CSV, XLSX, or an existing certified payroll PDF.
Correct incomplete fields, classification mismatches, and numerical discrepancies.
Use the cleaner payroll for the Illinois Certified Transcript of Payroll workflow.
Validation boundaryIllinois compliance rules and portal readiness are not fully evaluated. A qualified reviewer must check applicable overtime schedules, fringe restrictions and reporting fields. No Illinois portal submission or import-template validation is provided.
Use a WH-347, CSV, XLSX, or payroll export.
Rules handle arithmetic; contextual review handles ambiguity.
Clean entries disappear into the background.
What did WagePilot find?Why was it flagged?What evidence did it use?
You are shown the reasoning—not asked to trust a black box.The agent does the work. You keep the authority.
Recurring certified payroll for your own workforce.
Multiple projects and subcontractor review.
Higher project and submission volume.
No. The launch workflow starts with a PDF, CSV, or XLSX export. Your payroll system remains the source.
No. The diagnostic does not file anything. Material decisions and regulated submissions remain with you.
The item is surfaced with review limitations, supporting evidence, and a recommended next action for human review.
Yes. Findings show the source, supplied rule evidence, calculation where applicable, review limitations, and next action.
Code performs deterministic comparisons against wage rules you supply. The MVP does not automatically identify the legally applicable determination.
Files are held only while the review runs and are deleted when it finishes. PDF files are sent to OpenAI for structured extraction and the temporary uploaded file is deleted after processing. Unless your organization turns on the optional, encrypted keeping of originals in Settings, WagePilot does not keep payroll files.
Yes. Start with one payroll and one project without creating an account or entering a credit card.
The initial diagnostic runs a narrow supplied-rules review. California, Illinois, and New York pages describe their reporting workflows, but WagePilot does not claim complete 50-state rules or filing support.
Get a useful initial review before choosing a plan. No credit card required.