End the PBC chase before it eats your audit
The file arrived. The work is still blocked. A better prepared-by-client process starts with requests people can answer and ends with evidence the engagement team can actually use.
By Clark · October 14, 2026 · Updated October 14, 2026 · 3 min read
Make the first request worth answering
A request for “the revenue detail” leaves the client to guess the entity, period, report, and format. Every missing detail creates another exchange before the team can begin its work. Write requests around the task the recipient needs to complete.
For example, ask for the specified entity’s transaction detail for the agreed reporting period, with the fields your team needs, in the approved format. Name the client contact and the engagement team member who can resolve questions. Confirm the scope with the team before sending the request.
- Name the entity, period, and requested record
- Explain the required format and relevant fields
- Assign an owner, due date, and place for questions
Received is a starting point
Separate receipt from the team’s assessment of whether the submission answers the request. A file can arrive on time and still cover the wrong period, omit a requested tab, or require clarification. Treat those conditions as visible follow-up work.
Consider statuses such as requested, received, needs clarification, and ready for the assigned procedure. Each status should explain the next action and its owner. “Ready” means ready for that next step; it does not establish the sufficiency or appropriateness of audit evidence.
Carry the answer into the workpaper
Keep the request, response, file version, and clarification together as the team starts work. If a client replaces a schedule, identify the replacement and the work that needs to be revisited. A reviewer should not have to search an inbox to understand which version was used.
For PCAOB engagements, AS 1215 addresses documentation of procedures, evidence, conclusions, and preparation and review. A tidy request list supports coordination, but it does not replace that documentation. Follow the requirements and methodology applicable to the engagement.
Count the follow-ups you can avoid
Start with one recurring group of requests. Rewrite ambiguous items, assign owners, and agree what each status means with the client contact. Track clarification rounds, time spent locating files, and requests reopened after receipt.
At the end of the cycle, review the most common causes of rework. Turn those lessons into better request templates for the next engagement. The aim is a more useful first response and a clearer handoff into the work, not simply a faster green checkmark.
Sources and scope
- PCAOB AS 1215: Audit Documentation
Paragraphs .04–.06A address the purpose, source, procedures, conclusions, and preparation and review record for PCAOB engagements. The workflow suggestions in this article are editorial guidance, not additional requirements or a substitute for the standards applicable to your engagement.