How can I integrate a PBC request tracker into our audit senior workflow during fieldwork?

A good way to integrate a PBC (Prepared By Client) request tracker into audit senior fieldwork is to make it part of the daily audit operating rhythm, not a separate admin task. The goal is to help the senior manage open items, follow-ups, and evidence quality in one place.

1) Define the workflow around the tracker

Use the tracker as the source of truth for:

• Requests raised
• Owner on the client side
• Due date
• Status
• Follow-up notes
• Evidence received
• Review comments / cleared items

A simple lifecycle works well:

1. Raise request
2. Client acknowledges
3. Evidence received
4. Senior reviews for completeness
5. Cleared or follow-up requested
6. Closed

2) Build it into the senior’s daily routine

During fieldwork, the audit senior should review the tracker:

• At the start of the day: identify overdue items, blockers, and high-risk requests
• Midday: check responses and update statuses
• End of day: log follow-ups, prepare next-day priorities, and escalate chronic delays

This turns the tracker into a live workplan rather than a static list.

3) Align it with the audit program

Map each PBC item to:

• Financial statement area / assertion
• Audit procedure
• Workpaper reference
• Risk level
• Priority

This helps the senior see which missing items are affecting testing progress and which can wait.

4) Use status categories that support fieldwork decisions

Keep statuses simple and operational, for example:

• Not sent
• Sent
• In progress
• Received
• Under review
• Returned for follow-up
• Cleared
• Overdue

Add color coding if possible:

• Green = on track
• Amber = pending / at risk
• Red = overdue / blocking

5) Make it easy to escalate

The senior should use the tracker to identify:

• Items overdue beyond agreed SLA
• Requests blocking key areas of the audit
• Repeated incomplete responses
• Items requiring manager/partner intervention

You can add an escalation column with options like:

• No escalation needed
• Reminder sent
• Escalate to client lead
• Escalate to manager
• Escalate to partner

6) Link it to workpaper completion

For each request, include:

• Workpaper ID
• Testing area
• Reviewer comments
• Final conclusion

That way, the senior can quickly see whether evidence received is sufficient for sign-off or whether additional audit work is needed.

7) Establish clear ownership

Make sure each tracker row has:

• Internal owner: the audit team member responsible
• Client owner: who owes the response
• Reviewer: who signs off on the item

This prevents the senior from becoming the single point of manual follow-up.

8) Use standardized notes

The senior should update concise notes such as:

• “Client confirmed ETA Friday”
• “Received support; pending tie-out”
• “Incomplete population — requested revised file”
• “Evidence supports sample 3, 7, 9 only”

Standard language keeps the tracker clean and easy to review in status meetings.

9) Review in team check-ins

Use the tracker in:

• Daily standups
• Weekly client status calls
• Internal team reviews

Focus on:

• What’s outstanding
• What’s blocked
• What needs escalation
• What can be cleared today

10) If possible, automate alerts

If you use Excel, Smartsheet, Teams, SharePoint, or an audit platform, consider:

• Auto reminders for due dates
• Automatic overdue flags
• Dashboard views by status and risk
• Filters by preparer, area, or assignee

Simple tracker columns

A practical PBC tracker could include:

• Request ID
• Area / cycle
• Description
• Risk level
• Date requested
• Due date
• Client owner
• Internal owner
• Status
• Date received
• Review outcome
• Follow-up needed
• Escalation status
• Workpaper reference
• Notes

Best practice

The most effective integration is when the audit senior uses the tracker as:

• a scheduling tool,
• a follow-up tool,
• a risk prioritization tool,
• and a completion log.

If you want, I can also give you:

1. a sample PBC tracker template,
2. a daily audit senior workflow, or
3. a status dashboard layout for fieldwork.