For commercial-lines account managers and operations leads at independent P&C agencies of 8 to 50 staff, with construction, staffing, manufacturing, or trucking books: for every auditable policy in the agency's book, Audit Shepherd drives the client's premium-audit packet to complete and internally consistent before the carrier's noncompliance deadline — then checks the carrier's worksheet against the packet for known error classes inside the dispute window.
How it works
- Add an audit case — client, carrier, policy type, and expiration; deadlines default to the 20-day agency-input window and the ~50-day noncompliance clock, and both are editable
- Work the packet checklist — payroll by class code/state, 941s, sub COIs, driver/vehicle schedules — with each item tracked as it is received
- Run the consistency check across the entered document totals — payroll against 941s against schedules — with every difference flagged
- Keep the chase log against the deadline, and watch every open case on the deadline board
- Diff the carrier's worksheet against the packet — carrier figure against packet figure, line by line
- Tag each difference by its known error class, inside the dispute-window countdown
- Print the packet summary and the diff report
The scope — completeness, consistency, and chasing only
Audit Shepherd's scope is settled, and it is narrow on purpose: completeness, consistency, and chasing only. It drives a packet to complete, checks the packet's own figures against each other, and keeps the chase on record against the deadline.
It gives no audit or classification advice. It does not say which class code applies to a business, and it does not judge a carrier's audit — it flags where figures differ, and the agency decides what a difference means.
The packet — driven to complete before the deadline
Every auditable policy in the agency's book opens an audit case: client, carrier, policy type, and expiration. Deadlines default to the 20-day agency-input window and the ~50-day noncompliance clock, and both are editable for the case.
The packet is worked against a checklist, and each item is tracked as it is received — so what is still missing is never a matter of memory. The chase log is kept against the deadline, and the deadline board shows every open case against its noncompliance deadline.
- Payroll by class code/state
- 941s
- Sub COIs
- Driver/vehicle schedules
Consistency — the packet checked against itself
Before a packet is complete, its entered document totals are checked across each other: payroll against 941s against schedules. A figure that does not agree with the packet's other figures is flagged as a difference — flagged, not changed, and not explained away.
A packet counts as ready when it is complete and internally consistent: every checklist item received, and every flagged difference accounted for in the packet's own record.
The worksheet check — inside the dispute window
After the audit, the carrier's worksheet is checked against the packet: carrier figure against packet figure, line by line. Each difference is tagged by its known error class, and the check runs inside a dispute-window countdown, so the time left to dispute is counted in the open.
The five known error classes are the only tags the check applies:
- Class-code reassignment
- Uninsured subcontractor inclusion
- Overtime not excluded
- Officer inclusion/exclusion
- Rate mismatch
Proof on paper
Each case closes with two printable records: the packet summary — the complete, consistent packet as it stood — and the diff report, the worksheet check line by line with each difference tagged by its error class.
Where it stands — the honest state
Audit Shepherd is forming its first agency pilot group now. The door below is an agency pilot application — applying starts a pilot conversation; it does not create an account, and it is not a sign-up for a running service.
Three things stand before live client work, and none of them is in place yet. First, the client packet portal and chase sending: there is no live client portal today, and Audit Shepherd does not contact clients or carriers today — what exists is the case, the checklist, the consistency check, and the record. Second, AMS integrations: Audit Shepherd is not connected to any agency's AMS today — not Applied Epic, not AMS360, not HawkSoft, not EZLynx. The application below asks which AMS your agency runs because that answer informs the integration queue; access to any AMS is gated per agency, on that agency's own authorization. Third, the carrier checklist library behind the packet checklist is a maintained library, and keeping it current is a standing operations commitment — its seed is built only from requirements stated in writing, carrier by carrier.
No price has been set. A price range exists in our market research as a hypothesis; it has not been validated and it has not been decided, so no price is shown here and there is nothing to buy on this page.
The scope does not change in the pilot: completeness, consistency, and chasing only — no audit or classification advice, in the pilot or after it.
Agency pilot application
This is an agency pilot application — an application to join Audit Shepherd's first agency pilot group, not an account sign-up and not a purchase. Tell us who to reach, your agency, the AMS your agency runs today, and how many auditable policies your book carries in a year. The AMS answer informs the integration queue; no AMS integration exists today. We will be in touch about the pilot group.