LearnGrok
Prompts
PromptIntermediatePrompting

Audit evidence tracker for close sign-off

Create a close evidence tracker from timetables, reconciliations and audit requests for controllers and audit teams.

5 min read

Nothing here is financial advice, and none of it replaces your own checks.

Use these prompts to turn close documents into one evidence record that can be reviewed in a status meeting. They are for financial controllers and audit teams handling period-end close. Nothing here is financial advice, and none of it replaces your own checks or the decisions of the qualified people responsible for the close.

Start with the master tracker. Then use the narrower prompts only where the meeting needs an answer: ownership, overdue work, exceptions or sign-off blockers. This order matters. A blocker list built from unstructured reconciliations is harder to trace back to source evidence.

Key point

Start with source references

Every tracker row needs a document name, worksheet, task ID, request ID or other source reference. Without it, the tracker is a to-do list, not audit evidence.

1. Prepare the three input documents

Before pasting anything, export or copy the latest version of each document:

  1. The close timetable, including task IDs, dates, owners and review steps.
  2. The reconciliation register and any individual reconciliations with open breaks.
  3. The auditor request log, including request references and requested support.

Keep the period end visible in each input. If your group has several entities, retain the entity name on every row. Do not paste a redacted summary if the original register contains the owner, reviewer or due date needed to test completion.

If you are providing files rather than pasted text, check the handling available in your workspace. File and input support can differ by version, so consult the xAI documentation overview before relying on a file workflow for a close-critical task.

Watch out

Do not merge unlike items too early

A balance sheet reconciliation, a control review and an auditor request may relate to the same account, but they can require different evidence and different reviewers.

2. Build the tracker before chasing people

Run Build the master evidence tracker against the three source documents. It gives every evidence item a row and distinguishes the evidence itself from its owner, reviewer and sign-off effect.

Read the rows marked Missing or Conflict first. They often reveal a basic problem: the timetable says a task is complete, but the reconciliation register has no reviewer, or the auditor request identifies support that has not been logged.

Do not overwrite the source documents to make them fit the tracker. Instead, retain the disagreement in the Exception or open point field. This gives the controller or reviewer a clear item to resolve and preserves the audit trail.

Check

A usable tracker has a route back to evidence

Pick five rows at random. You should be able to find the named source, identify the owner and reviewer, and see what evidence would move the item forward.

3. Use the right follow-up prompt

The prompts after the master tracker have different jobs. Run only the one that answers the immediate meeting question.

If you need to know Use this prompt Take to the meeting
Who must supply or review missing evidence Find missing ownership and support The unassigned evidence table and questions list
What needs action today Triage overdue close evidence P1 actions and escalation routes
Whether reconciliation breaks are properly documented Test unresolved exceptions The exceptions register and follow-up list
What prevents a documented sign-off discussion Prepare the sign-off blocker list The decision record and agenda

Use a stated current date for overdue triage. Otherwise, an item can look late simply because the input is from a prior close cycle. If the date is unclear, keep it unclear. Do not make up a deadline to make the table look complete.

4. Check the output against the source

The most convincing-looking row can still be wrong. Check the output in three passes.

  • Identity check: Confirm entity, account, reporting period and task or request reference against the original document.
  • Evidence check: Open the cited support. Verify that it is the requested reconciliation, review record, schedule or response, rather than a similarly named prior-period file.
  • Status check: Compare Complete or Resolved with the preparer evidence and the reviewer conclusion. Completion without review evidence is not the same as a completed review.

Pay particular attention to grouped rows. The master prompt may link documents concerning the same account or process. Confirm that they genuinely describe the same obligation. If one request covers a control and another covers a balance, split them into separate tracker rows in your working file.

Check

Test the claimed blockers

For each item marked Blocks sign-off, ask: what exact evidence is absent, who can provide it, and which source says it is required? If any answer is missing, the blocker needs further investigation.

5. Record decisions outside the generated text

Use the sign-off decision record as meeting support, not as the signed record itself. After the meeting, update the controlled tracker or close checklist with the decision, decision maker, date, evidence received and remaining conditions. Retain the source files and the meeting record according to your organisation's retention process.

Do not ask the model to determine whether an exception is immaterial, whether an accounting treatment is appropriate, or whether sign-off should proceed. The prompts deliberately leave those decisions to the responsible controller, reviewer, auditor or other qualified person.

When it does not work

If the tracker produces too many Missing fields, paste the underlying register rather than a summary, and include column headings. If it creates duplicate rows, provide the timetable task ID, account, entity and auditor request reference so related items can be matched. If status or ownership is wrong, correct the controlled source record first, then rerun the relevant prompt with the updated extract.

If the output cannot be traced to a document, do not use it as evidence. Mark the item for investigation, keep the source reference blank rather than guessed, and take it to the close meeting for assignment.

Copy-ready prompts

5 prompts. Open one to read it, or take the whole pack.

1Build the master evidence trackerUse this first, once you have the current close timetable, reconciliation list and auditor request log.
Create a master audit evidence tracker for the reporting period [period end]. Use only the three source documents below.

CLOSE TIMETABLE
[paste the close timetable]

ACCOUNT RECONCILIATION REGISTER
[paste the reconciliation register]

AUDITOR REQUEST LOG
[paste the auditor request log]

Return one Markdown table, sorted first by sign-off blocker, then due date, then workstream. Include these columns exactly: Tracker ID | Workstream | Entity | Account or process | Evidence required | Source reference | Owner | Reviewer | Due date | Status | Exception or open point | Auditor request reference | Sign-off impact | Next action | Last evidence date.

Use these status values only: Not started, In progress, Submitted, Under review, Complete, Blocked, Not applicable. Use these sign-off impact values only: Blocks sign-off, Requires review, Does not block sign-off.

Create one row for each distinct item of required evidence. Link related timetable tasks, reconciliations and auditor requests in the same row where they concern the same account, process and entity. Do not assume that a reconciliation proves a control was performed.

If a field is absent, write Missing, not Unknown. If source documents conflict, write Conflict in the relevant field, quote both source references in the Exception or open point column, and set Sign-off impact to Requires review. If a due date has passed relative to [today's date], set Status to Blocked only when the evidence is also missing or unresolved. Otherwise retain the source status.

After the table, add a section titled `Items needing controller decision` with a numbered list of rows that have Missing, Conflict, no Owner, no Due date, or Blocks sign-off. For each, state the Tracker ID, the missing decision, and the source reference. Do not provide financial advice or make a sign-off decision.
2Find missing ownership and supportUse this after the master tracker exists. It produces a short assignment list for the close meeting.
Review the audit evidence tracker below for missing ownership, missing review responsibility and unsupported completion claims.

AUDIT EVIDENCE TRACKER
[paste the current tracker]

Return three Markdown tables.

Table 1 title: `Unassigned evidence`. Include: Tracker ID | Workstream | Evidence required | Missing field | Proposed accountable role | Why assignment is needed | Due date | Sign-off impact.

Table 2 title: `Completion claims without support`. Include: Tracker ID | Account or process | Current status | Evidence required | Support missing or insufficient | Owner | Reviewer | Sign-off impact | Required next action.

Table 3 title: `Ownership conflicts`. Include: Tracker ID | Conflicting owners or reviewers | Source references | Decision required | Interim status.

Treat Owner, Reviewer, due date, source reference, supporting file reference, preparer sign-off and reviewer sign-off as separate fields. A status of Complete is not sufficient support by itself. Mark a completion claim as unsupported if the tracker does not identify evidence and a source reference or supporting file reference.

Do not invent names, roles, dates or evidence. Where no proposed accountable role can be inferred, write `Controller to assign`. Where an Owner and Reviewer are the same person, flag this as a segregation point for review, not as an error. End with a numbered list titled `Questions for the close meeting`, limited to 10 questions and ordered by sign-off impact. Do not provide financial advice.
3Triage overdue close evidenceUse this on the day of a close status meeting, with a stated reporting date and current date.
Triage overdue and at-risk audit evidence for the period end [period end], using [today's date] as the assessment date.

CURRENT AUDIT EVIDENCE TRACKER
[paste the current tracker]

CLOSE TIMETABLE, IF UPDATED
[paste the latest timetable or write Not available]

Return a Markdown table titled `Close evidence triage` with these columns exactly: Priority | Tracker ID | Entity | Account or process | Evidence required | Owner | Due date | Days overdue or remaining | Current status | Reason for risk | Dependency | Immediate action | Escalate to | Sign-off impact.

Include items where: the due date has passed and status is not Complete or Not applicable; the due date is within [number] calendar days; status is Blocked; an exception is unresolved; Owner is Missing; or Sign-off impact is Blocks sign-off.

Set Priority only as P1, P2 or P3. Use P1 for any item that Blocks sign-off, has no owner and is due or overdue, or has an unresolved exception with no documented next action. Use P2 for Requires review items due within the stated period or overdue. Use P3 for all other included items.

Calculate days only where both a valid due date and [today's date] are supplied. If dates are unclear, write `Date unclear`, do not calculate, and state the ambiguity in Reason for risk. Do not infer whether an item is material, whether an adjustment is needed, or whether sign-off should occur.

After the table, provide a section titled `P1 actions for today` with one bullet per P1 item. Each bullet must state the owner, the evidence needed, the dependency and the escalation route. If there are no P1 items, write `No P1 items identified from the supplied tracker`.
4Test unresolved exceptionsUse this for reconciliations and close controls that contain breaks, aged items, reviewer comments or unexplained balances.
Create an exceptions register from the reconciliation evidence below. The purpose is to show which exceptions have enough documented support to move through review and which require action before close sign-off.

RECONCILIATIONS AND SUPPORT
[paste account reconciliations, exception logs, reviewer comments and supporting notes]

CURRENT AUDIT EVIDENCE TRACKER, IF AVAILABLE
[paste the relevant tracker rows or write Not available]

Return one Markdown table with these columns exactly: Exception ID | Entity | Account | Reconciliation period | Exception description | Amount or quantity stated | Ageing stated | Root cause stated | Evidence reference | Preparers response | Reviewer conclusion | Owner | Target resolution date | Current resolution status | Link to tracker ID | Sign-off impact | Information missing.

Use these Current resolution status values only: Open, Evidence received, Under review, Resolved subject to review, Resolved, Cannot assess. Use these Sign-off impact values only: Blocks sign-off, Requires review, Does not block sign-off, Cannot assess.

Extract stated facts only. Preserve amounts, currencies, dates and account names exactly as supplied. Do not calculate materiality, propose accounting treatment, conclude that a balance is correct, or decide that an exception is immaterial. If evidence indicates resolution but no reviewer conclusion is present, use `Resolved subject to review`. If the source does not state an owner, target date, root cause or evidence reference, record Missing in that field.

Then add a section titled `Exception follow-up` with a numbered list. Include every exception that is Open, Cannot assess, Missing an owner, Missing evidence reference, or Blocks sign-off. For each item, state the exact document or confirmation needed next.
5Prepare the sign-off blocker listUse this before the controller or audit clearance meeting. It turns the tracker into a decision record, without making the decision for them.
Prepare a close sign-off blocker list from the evidence tracker and the exceptions register below.

AUDIT EVIDENCE TRACKER
[paste the current tracker]

EXCEPTIONS REGISTER
[paste the current exceptions register]

Return a Markdown table titled `Sign-off decision record` with these columns exactly: Decision record ID | Tracker ID or Exception ID | Entity | Account or process | Blocking condition | Evidence currently held | Evidence still required | Named owner | Reviewer or decision maker | Due date | Dependency | Current status | Recommended meeting question | Source reference.

Include only items that meet at least one condition: Sign-off impact is Blocks sign-off; status is Blocked; an exception is Open or Cannot assess; required evidence is Missing; owner is Missing; a source conflict is recorded; or a reviewer conclusion is absent for an item marked complete or resolved.

Do not label any item as cleared, approved, immaterial or ready for sign-off. In `Recommended meeting question`, ask a factual question that identifies the decision or evidence required, for example whether a named reviewer has completed their conclusion. If there is insufficient information to determine whether an item blocks sign-off, include it and write `Sign-off impact not evidenced` in Blocking condition.

After the table, write a section titled `Meeting agenda`, with these headings in order: `1. P1 blockers`, `2. Missing ownership`, `3. Evidence awaiting review`, `4. Decisions to document`. Under each heading, list the relevant Decision record IDs only. If none apply, write None.

Last checked against xAI’s own pages on 2026-08-21. Grok changes quickly; anything version-specific should be confirmed upstream before you rely on it.

More in Prompting

Found something out of date?

Grok changes quickly and this page is a snapshot. If something here is wrong, or you know a better resource, send it over.

Suggest a link →

Advertise on LearnGrok

$420.69one-time, for a 30-day run

Square works best. PNG, JPEG or WebP, up to 2 MB.

Stripe on the next step. Live once approved.