---
name: audit-request-list-plan
description: "Use when the user has received an auditor’s or reviewer’s document request list (a PBC list) and wants it organized into a plan: each request restated plainly, its likely source, an owner slot, lead time, and the clarifying questions to send the auditor. Triggers: PBC list, audit request list, audit prep, prepared by client, review engagement requests, first audit."
metadata:
  lane: use
  requires: "none"
  source: https://harbinger.finance/skills/audit-request-list-plan
  updated: "2026-11-18"
---

# Turn an auditor’s request list into a working plan

Sort an audit or review request list by lead time and owner, with each request restated in plain English and the questions to send back.

## When to use it

When the request list arrives and it's eighty lines in the auditor's shorthand. Most of the work in audit prep is logistics: knowing which requests take three weeks because someone outside the company has to answer, which are a report you can run today, and which are ambiguous enough to ask about before you spend a day on the wrong thing.

The assistant sorts and restates. It doesn't know what you have on file, so it never marks a request as done or available, and it shouldn't tell you what your auditor will accept. That's a question for the auditor, and the prompt has it write those questions.

**Where it works.** Any AI assistant. No setup.

## Ask the user for

- The request list, pasted as text.
- The period under audit and the date fieldwork starts.
- The systems the records live in.
- Who is available to help, by role.

Ask for anything missing before you start. Never invent a figure to fill a gap.

## Do this

Carry out the request below. Fill each [bracketed] item from what the user gave you.

Organize this audit request list into a working plan. The period is [period], and fieldwork starts [date].

Our records are in: [accounting, payroll, billing and document systems].
People available: [roles].

For every request, in the auditor's original numbering:
1. Restate it in one plain sentence: what they want and for which dates.
2. Say where it most likely comes from: a standard report, a document on file, a schedule someone has to build, or a third party.
3. Suggest which role would own it. Leave the owner blank if none of my roles fits.
4. Give a lead time: same day, a few days, or weeks. Anything that depends on someone outside the company (bank confirmations, legal letters, lender statements) is weeks.

Then:
5. Order the whole list by when work has to start to be ready for fieldwork, longest lead time first.
6. Group requests that the same report or schedule answers, so nothing is prepared twice.
7. List every request that is ambiguous, with the question to send the auditor, one sentence each.

Don't mark anything as complete or available. You can't see our files. Don't tell me what the auditor will accept. Keep their numbering so I can answer by number.

Request list:
[paste the request list]

## Before you hand it over

Tell the user which of these checks they still need to make:

- Compare the restated requests against the originals. If a restatement narrows what was asked, the original wins.
- Send the questions before you start the ambiguous items.
- Put a named person and a date on every line. The assistant suggests roles only.
- Track status yourself. Nothing here knows what has been delivered.

The assistant drafts. The person whose name is on the work approves it.

## What a good answer looks like

**Start this week (weeks of lead time)**
- **#14 Bank confirmations.** They want balances confirmed directly by each bank at year-end. Third party. Owner: controller. Send the authorization forms now.
- **#31 Legal letter.** A letter from outside counsel on open matters. Third party. Owner: blank (who manages counsel?).

**Start two weeks before fieldwork (a few days each)**
- **#8 Fixed asset roll-forward.** Additions, disposals and depreciation for the year, tied to the general ledger. A schedule to build. Owner: controller.
- **#22 Deferred revenue schedule.** Contract by contract, opening to closing balance. A schedule to build. Owner: controller.

**Same day**
- **#1 to #5** Trial balance, general ledger detail, year-end aging reports. Standard reports. Owner: staff accountant.

**One report answers several**
- The general ledger detail for #2 also answers #17 and #26. Run it once, for the full year.

**Ask the auditor**
- #19 "Support for significant estimates": "Which estimates do you consider significant for this engagement?"
- #27 "Related party listing": "Do you want transactions for the year, balances at year-end, or both?"

---

From the Harbinger FinLab skill library: https://harbinger.finance/skills/audit-request-list-plan
