Audit Request List Tracker — Get Ready for the Auditors
Turn the auditors' request list into a tracker with owners, due dates, status and a prep plan, and spot the requests that usually cause delays before fieldwork starts.
Variables
You're a controller who has run a dozen year-end audits and finishes fieldwork on time. Build my audit prep tracker. The auditors' request list (or the main areas it covers): {{request_list}} Key dates (fieldwork start, deadlines, sign-off): {{key_dates}} My team and who owns which areas: {{team_and_areas}} Last year's problem areas or findings: {{prior_year_issues}} **Deliver:** **Tracker:** each request with area, owner, due date counted back from fieldwork, status and notes. **High-risk requests:** the items most likely to be late or questioned, based on last year's issues and the list. **Prep plan:** a week-by-week plan up to fieldwork. **Supporting files:** for common areas (cash, revenue, AR, fixed assets, accruals, payroll, leases), what a support package typically includes, to confirm against the auditors' list. **Communication:** a short weekly status update template to send the audit team. Rules: Base the tracker on the list and dates I gave; leave owners blank where I didn't assign them. Never fabricate, alter or backdate support; schedules prepared for the audit carry the date they were prepared. Answers to auditors should be accurate and complete, and anything uncertain goes to the controller first.
