JOC Procurement
JOC Audit Preparation: What OIG Looks For
9 min read · PreCon JOC
JOC programs are audited more frequently than traditional procurements — and when auditors arrive, they know exactly where to look. The flexibility that makes JOC efficient (fewer competitive bids, pre-established unit prices, rapid task order issuance) also creates the conditions for cost manipulation if documentation is weak. This guide covers what state auditors and OIG investigators actually examine, the most common findings, and how to build a program that is defensible before the first request ever arrives.
Why JOC programs draw audit scrutiny
JOC is a sole-source delivery mechanism once a contractor is awarded. After award, every task order goes to the same GC at their locked coefficient — there is no competitive rebid. This concentrates contract value with one vendor over years, and it creates a structural opportunity for overbilling that doesn't exist in hard-bid contracting.
Auditors also know that the RS Means coefficient structure is not widely understood inside the agencies that use it. When procurement staff turns over, institutional knowledge of what a compliant task order looks like can disappear entirely. Programs that were well-managed under one procurement director become vulnerable when that person leaves.
What auditors request on day one
A JOC audit typically opens with a document production request. These are the items that arrive in the first request letter:
- —The solicitation and all addenda
- —All coefficient submissions received — not just the winning bid
- —The evaluation scoring sheet and the award recommendation
- —The award letter and board approval documentation
- —The signed JOC contract, including all exhibits (unit price book, ACF formula, NPP terms)
- —Every task order issued during the audit period, including the GC's line-item proposal
- —Independent cost estimates or engineer's estimates produced before or concurrent with each task order
- —Inspection records and quantity verification sign-offs for each task order
- —Payment records for each task order
- —Any change orders or task order modifications
- —Correspondence between agency staff and the GC regarding task order scope
The audit starts with the gap: which of these can you produce, and which cannot be located? Every missing document is a finding. Missing task order proposals mean the agency paid for work without approving a scope. Missing inspection records mean quantities were billed without verification.
The most common audit findings in JOC programs
Task orders issued without prior written proposals
Work was started, or even completed, before the GC submitted a line-item proposal for agency review. Without a pre-work proposal, there is no basis for auditing whether the quantities billed match the quantities ordered. This is the single most common high-severity finding.
Non-pre-priced work without competitive quotes
Task orders contained NPP line items above the program's threshold — or the program had no NPP threshold at all — and no competitive quotes were obtained. NPP work is priced at the GC's F7 coefficient with no RS Means benchmark, making it the easiest vector for cost inflation. Auditors will total all NPP line items across the program period and compare to the NPP cap.
Coefficient applied incorrectly to task order pricing
The GC's coefficient was applied to a cost base other than RS Means bare costs — for example, applied to the GC's own material quotes instead of the RS Means unit price. This inflates every line item by an additional layer of markup. Sometimes this is unintentional; sometimes it isn't.
No independent cost estimate before task order approval
The agency approved task orders based solely on the GC's proposal, with no owner-side cost check. Best practice — and some state statutes — require an independent cost estimate or engineer's estimate before approval. Without one, the agency has no basis to dispute the GC's quantities or unit rates.
Quantity overbilling on approved line items
The GC billed quantities that exceed what was physically installed. Field inspection records (if they exist) show the discrepancy. When inspection records don't exist, auditors estimate overbilling from project photography, square footage, and industry standards. The resulting questioned costs are often higher than actual overbilling because the agency can't rebut the estimate.
Task order total exceeds program limits
Individual task orders exceeded the statutory or contractual maximum task order dollar amount. Some states cap JOC task orders by statute; others leave it to the program contract. Exceeding the cap can void the task order entirely, requiring the work to be re-bid competitively — often after it's been completed.
Missing or incomplete ACF calculation documentation
The evaluation doesn't show how each submission's ACF was calculated, or the formula applied doesn't match the solicitation's stated formula. Even when the award itself was correct, missing documentation generates a process finding.
What a defensible JOC program looks like
A program that survives an audit isn't one where nothing went wrong. It's one where the documentation is complete enough to prove what happened, and where the controls are strong enough that any deviation is visible and was addressed. These are the structural elements that make a program defensible:
Every task order has a line-item proposal on file before work starts
The GC's proposal, with quantities and unit prices referencing RS Means codes, is received and approved in writing before any work begins. This is non-negotiable. Without it, every payment is an unauthorized expenditure.
An independent cost estimate exists for every task order above a threshold
The agency produced its own RS Means-based cost estimate before reviewing the GC's proposal. Set the threshold at a level that is realistic to maintain — $25,000 is a common floor. The ICE doesn't have to be perfect; it has to prove the agency exercised independent judgment.
NPP work is tracked separately and capped
Every NPP line item is identified as NPP in the task order file. The aggregate NPP total across all task orders in the program year is calculated and confirmed to be within the program's NPP cap. Any NPP item above the quote threshold has competitive quotes on file.
Field inspection sign-off on quantities before payment
An agency representative (not the GC) confirmed installed quantities and signed off before each payment was released. The sign-off record names the person, the date, and the quantities confirmed. Photographs of completed work, dated, support the record.
The audit log is immutable and complete
Every decision — award, task order approval, modification, payment release — is timestamped and attributed to a named person. The log cannot be edited after the fact. If your program runs on spreadsheets and email, you don't have this.
Coefficient application is traceable from proposal to payment
The task order file shows how the GC calculated each line item price (RS Means code × quantity × coefficient × appropriate factor), and those calculations match the approved coefficient from the award. Any deviation is documented and justified.
Audit-readiness checklist
Run through this list before an auditor contacts you — not after. Many of these gaps take months to fix proactively, but can't be fixed retroactively once the audit has started.
Program documents
- Current solicitation, all addenda, and final signed contract are retrievable in under 10 minutes
- ACF formula matches the signed contract — not a later interpretation
- RS Means edition named in the contract matches the edition used in task order pricing
Award documentation
- All submissions received are on file — not just the winning bid
- Evaluation shows the ACF calculation for each submission
- Board or approval authority approval is documented with a dated resolution or memo
Task order files
- Every task order has a GC proposal with RS Means codes and quantities
- Every task order has an independent cost estimate or engineer's estimate from before approval
- Every task order approval is signed by an authorized agency representative
- NPP line items are identified separately; aggregate NPP is within program cap
- Task order total does not exceed the program's maximum task order dollar limit
Payment records
- Field inspection sign-off with named inspector, date, and confirmed quantities exists for each payment
- Payment records tie to approved task order amounts, not to GC invoices alone
- Any payment hold or dispute has a dated record of resolution
Audit-ready JOC management
OIG-ready from day one
PreCon JOC logs every action with actor, timestamp, and before/after values in an immutable audit trail. Task order proposals, independent cost estimates, and payment approvals are stored in the platform — not scattered across email and shared drives.
Set up your program →