Quarter Close Drill Dr Goh Quarter Close Drill Dr Goh

The Quarter-Close Drill: 25 Checks That Prevent Close Chaos

Run this 25-check quarter-close drill to catch recon gaps, cut-off risk, and missing evidence before your close collapses under pressure.

Run this 25-check quarter-close drill to catch recon gaps, cut-off risk, and missing evidence before your close collapses under pressure.

The Quarter-Close Drill (What it is)

A Quarter-Close Drill is a fast pre-close scan that tells you, in 20 minutes, whether your close will be calm — or whether it will explode into rework, late nights, and missing evidence.

Most close failures come from three root causes :

  1. Ownership is unclear (people assume someone else did it)

  2. Reconciliations break (mystery balances grow)

  3. Evidence is missing (panic before sign-off)

This drill catches those early.

How to run the drill (20 minutes)

  • Print or open your checklist.

  • Answer each check as PASS / FAIL / N/A.

  • Any FAIL becomes a task with an owner + due date.

Run it 3 times:

  • T-7 days before quarter close (first pass)

  • Day 2 of close (second pass)

  • Before final sign-off (final confirmation)

The 25 checks (grouped)

A) Ownership & accountability (5)

  1. Every close-critical task has a named Owner.

  2. Every close-critical task has a named Reviewer.

  3. Deadlines are visible (calendar or tracker), not “in someone’s head”.

  4. Dependencies are explicit (Task A must finish before Task B).

  5. An escalation rule exists (what happens if a critical task is late).

Why this matters: close chaos is usually not technical—it’s missing accountability.

B) Reconciliations & High-Risk Accounts (8)

  1. Top 10 high-risk accounts are identified (cash, AR, revenue, interco, accruals).

  2. Each high-risk account has a recon deadline earlier than the rest.

  3. Recon includes: opening balance + movements + closing balance.

  4. Material variances have an explanation (short, factual).

  5. Supporting documents are attached (not “will send later”).

  6. Recon is reviewed and signed off (not just prepared).

  7. Aged items have a plan (no indefinite carry).

  8. Manual journals affecting high-risk accounts are reviewed.

Why this matters: broken recons create “mystery balances” that kill close speed.

C) Cut-off & Completeness (6)

  1. Revenue cut-off is checked (timing, shipment/service, recognition).

  2. Expense cut-off is checked (accrual completeness).

  3. Intercompany cut-off is checked (match, eliminate, explain differences).

  4. Key estimates have a documented basis (assumptions, method).

  5. One-off transactions are flagged and reviewed (unusual items).

  6. Management adjustments are approved with evidence.

Why this matters: The cut-off is where quarter-close audits focus.

D) Evidence & Sign-Off Readiness (6)

  1. Every critical recon/journal has evidence attached.

  2. Evidence naming is consistent (easy to find later).

  3. Evidence is stored in a shared system, not personal inboxes.

  4. Review sign-off is recorded (who approved, when).

  5. Final close pack has a clear “complete” mark (no ambiguity).

  6. You can trace any number to: recon → evidence → approval within minutes.

Why this matters: “audit-ready” means evidence is organised, not “available somewhere”.

What To Do If You Fail 5+ Checks

If 5 or more checks fail, your close risk is high. Do this immediately :

  • Create a “Close Stabilisation” list: Top 5 failures only

  • Assign each one to an owner + deadline in the next 48 hours

  • Re-run the drill after Day 2

Next Step (CTA)

If you want the complete system (samples, tiers and deployment-ready structure):

Read More
Controller Dr Goh Controller Dr Goh

Audit Readiness

Learn the evidence-ready close standard : what to capture, how to structure approvals, and how to build a traceable audit trail without panic.

Evidence-Ready Close : What Auditors Expect (and Where Teams Break Under Pressure)

The harsh truth about audits

Auditors don’t reward effort. They reward evidence.

In a quarter close, teams usually break in one of two ways :

  • They did the work but can’t prove it (missing attachments, unclear approvals), or

  • They didn’t do the work consistently (different standards per person).

An evidence-ready close fixes both.

The Evidence Triad (Simple & Reliable)

For any close-critical item, you need three things :

1) What Happened

  • The recon, journal, or report that shows the number.

2) Why It Happened

  • A short explanation (variance note) + policy basis if relevant.

3) Who Approved It

  • A reviewer sign-off with date/time (or documented approval).

If any part is missing, you are not evidence-ready.

The 10 Evidence Failures That Trigger Audit Pain

  1. No reviewer sign-off recorded.

  2. Evidence exists but is not linked to the recon/journal.

  3. Attachments are stored in email threads, not a shared archive.

  4. File names don’t match the close item (impossible to trace).

  5. Large variances have no explanation.

  6. High-risk accounts have incomplete support (cash/AR/revenue/interco).

  7. Intercompany differences aren’t explained with evidence.

  8. Estimates have no documented basis.

  9. One-off transactions are not flagged and approved.

  10. “Final close pack” is unclear (what is included, what is complete).

How To Become Evidence-Ready In 30 Minutes

Step 1 — Define “Close-Critical”

Pick 10–20 close-critical items (accounts, journals, reports).

Step 2 — Set The Evidence Rule

Each item must have :

  • recon/journal/report

  • supporting document(s)

  • approval (review sign-off)

Step 3 — Use One Consistent Naming Pattern

Example pattern :

  • YYYY-Q#_Close_ItemName_Owner_ApprovedDate

Step 4 — Make The Archive One Place

Evidence must live in one shared location—not scattered.

The “New Hire Test” (Best Evidence Standard)

Ask :

If a new controller joins tomorrow, can they understand and defend the close within 30 minutes using the evidence pack?

If the answer is “no”, you will struggle under audit pressure.

Next step (CTA)

If you want an evidence-ready close system packaged as a deployable operating model :

Read More