A senior associate sends a Provided by Client (PBC) list on a Monday morning. Two weeks later, six items are still open, and the associate is drafting a third email that starts with "following up on the items below." This happens on nearly every audit engagement running right now. The response inside most firms is always the same: send it again, escalate to the controller, maybe loop in the partner. Look closer at what's actually missing from that list. One line item reads "Accounts Payable (AP) aging." The client has four reports that could answer to that name, and no way to know which one the auditor wants. The client didn't lose the request. The request never told them what to do.
Most firms put their energy into managing the follow-up: a reminder on day three, a call on day seven, an email to the Chief Financial Officer (CFO) on day ten. Almost none of that energy goes into the request itself once it's out the door. A Suralink survey of accounting firm clients found that 70% of clients say vague or unclear requests, not their own disorganization, are the main reason for delays. Request list management, at most firms, means tracking who's responded, not whether the client could actually understand what was being asked.
The Cost Shows Up Inside the Audit Engagement
One miscommunication delays a single item. Five or six, and the close date itself starts to move. According to Suralink's client research, 62% of clients hit that second number, five or more miscommunications in a single audit engagement. Each one starts the same way: a request goes out, the client sends back something close, and the item sits open until someone catches the mismatch. That back and forth doesn't just cost the hour it takes to resend an email. Vague requests add 14.4% to total engagement time, according to the same research. On a six week audit, that's most of an extra week spent waiting on documents that would have come back right the first time. All because the request never said what "right" meant.
What a Clear Request Looks Like
A request that says "AP aging" asks the client to guess. A request that spells out the report, the period, and the format does not.
Vague request:
- "Send bank statements."
- "Need the depreciation schedule."
- "Reconciliation for cash."
Clear request:
- "Bank statements for [account name, last four digits], for [month/year], PDF as issued by the bank."
- "Fixed asset depreciation schedule for [fiscal year], showing beginning balance, additions, disposals, and ending balance by asset class."
- "Cash reconciliation for [account], [period], including the bank statement, the general ledger detail, and any reconciling items over $500."
It comes down to one thing: whether the client, who never sat in on the planning meeting, could read the line and know exactly what to attach.
Reducing Back and Forth Beats Following Up Harder
When Suralink's client research asked clients what would improve their engagements most, 65% said reducing back and forth, ahead of faster turnaround, better software, or a nicer portal. Most accounting firm software, or audit management software, automates the parts around the request: reminders, deadline tracking, an overdue list. None of it rewrites the line item that made the request unclear in the first place. Request list management starts before the list goes out: someone reads each line the way the client will, not the way the team already does.
Where Suralink's Document Prescreen Agent Fits
Uploaded documents are checked against what the request actually specified. The Prescreen Agent then flags a mismatch before the file reaches a reviewer's queue. It won't write the request for the firm, it simply catches the gap between what was asked for and what came back. Catching it early takes seconds. Missing it costs hours.
The client who sent the wrong bank statement three weeks ago probably read that request exactly as it was written. The wording just left room for more than one right answer. The real fix happens earlier than that: a clear request, written before anyone has to chase anything down.