UC-450
PBC Request Tracking & Evidence Chase
Matches each client upload to the audit request that raised it, tests whether it answers that request, and chases what is missing.
TBDBuild Duration
XXXXIndicative ROI
XXXXBuild Cost
XXXXValue
The Challenge
Fieldwork stalls because half the prepared-by-client list is outstanding and juniors spend days writing chase emails. It persists because requests live in a portal and the evidence arrives by email.
How It Works
- Reads the PBC request list, client portal uploads, engagement email and the audit programme.
- Matches each item to its request, scores whether it answers the assertion and dates the gap.
- Sends the chase to the named client owner and refreshes the manager's outstanding list.
What It Removes
- Manual matching of client uploads to request lines
- Writing individual chase emails to client contacts
- Rebuilding the outstanding list before status calls
Input Data RequirementsPBC request lists, client portal uploads, engagement mailbox, audit programme and assertions, prior-year request lists, client contact matrix
Output FormatLive outstanding-request list with owner and age, an automatic chase per open item, and a readiness score per audit area before fieldwork starts
“Two weeks of the job go on asking for things we already asked for and cannot prove we received”