PBC Request Tracking and Client Follow-Up: A System That Keeps Fieldwork on Schedule

Most audit overruns trace to late client items. The list itself is rarely the problem. The problem is that nobody owns the follow-up, the status lives in email, and the first sign of trouble arrives when staff arrive for fieldwork and find nothing to test. A tracker with a cadence turns the list into a managed process. For the list contents see the general PBC list guide and the area lists linked from it.

The tracker

One shared sheet or workflow tool, one row per request, with these columns:

The audit purpose column keeps the list honest. If nobody can name the procedure, drop the request.

Set due dates in a kickoff meeting

Walk the list with the client's controller. Agree due dates item by item, and have the controller assign owners. A list sent by email with a single global deadline produces a pile on the last day. A list reviewed in a call produces ownership.

Record the agreed dates in the tracker. Send the tracker, not a different document, as the confirmation.

Quality check on receipt

Accepting a document is a step, not an event. On receipt, check:

• Right period and entity.
• Ties to the trial balance, with the tie shown.
• Complete: all pages, all accounts, all months.
• In the format requested, usable without retyping.
• Generated by the system and not manually altered, where reliability matters.

If an item fails, mark it partial and send back within a day, with the specific gap. A bad item discovered two weeks later costs a week.

Follow-up cadence

A fixed rhythm removes the need to decide each time.

Tell the client in the kickoff that this cadence exists. It stops escalation from feeling like a surprise.

Prioritize what blocks work

Not every late item has the same cost. Classify:

• A items: the trial balance, the aging, bank statements, the count listing. Fieldwork cannot start without them. Chase first.
• B items: contracts, invoices on request, schedules. Needed during testing. Late items delay particular tests.
• C items: representation support, subsequent period items, legal letters. Time-bound by the calendar.

If an A item is late, re-plan the sequence: do other areas first, and tell the partner so the staffing plan can change.

Ask for partial deliveries

A complete item two weeks late is worse than a partial item on time. Ask for what exists now: the first nine months, one location, the largest accounts. Mark the status partial and keep the rest due.

Record the effect of late items on the audit

Late or missing items can affect the audit beyond the schedule. The auditor may need to perform alternative procedures, expand testing, or consider whether the lack of information is a limitation on scope. Keep a short log:

• Item, how late, the reason given.
• The effect on procedures performed and conclusions.
• Whether the matter bears on the control environment, for the governance communication. Significant difficulties in obtaining information, such as significant delays in receiving required information, are items the auditor tells those charged with governance about.

A client that repeatedly produces requested records late or refuses a requested document is giving the auditor evidence about management. Treat it that way.

Fees and scope

If delays push work out of the planned window, the engagement letter can address additional fees. Raise it early and in writing, before the work is done, not after. See audit engagement letter.

Worked example

A tracker with 86 requests for a December year end audit. At week three:

The two open A items are the inventory count listing and the AR aging, both due six business days earlier. The manager already called the controller at two business days past due, and the partner escalated to the CFO at five days. The CFO promises both by Friday. The manager re-plans: the senior starts payroll and debt testing, which depend only on received items, and the staff assigned to inventory work shift to a different client for the week. The tracker's notes record each call and the revised dates.

Close the tracker at completion

At completion, the tracker should show every item as accepted or not applicable. Items still open need an explanation in the file. The accepted items link to the workpapers where they were used, and the final tracker goes into the audit file as evidence of the information the audit relied on. See engagement completion checklist.

Lessons for the following engagement

Record which items were late and why. The next engagement's list can change: ask for them earlier, ask a different owner, or ask for a different format. A short debrief with the client's controller after the audit improves the next cycle.

CORAA prepares ready-to-review audit files for US CPA firms; the firm keeps the client, the review and the signature. See /us.

Sources

• AICPA, AU-C Section 260, The Auditor's Communication With Those Charged With Governance (significant difficulties encountered during the audit)
• AICPA, AU-C Section 500, Audit Evidence; AU-C Section 230, Audit Documentation
• U.S. Government Accountability Office, Financial Audit Manual, Volume 1 (GAO-26-108577), June 2026: gao.gov (FAM 550, communication of significant difficulties such as delays in receiving required information)

AU-C references are to AICPA Professional Standards, paraphrased here; read the standard itself before relying on a requirement. This page is guidance, not professional advice. Report an error