Analysis · Audit & Assurance

The PCAOB cut the audit documentation window from 45 days to 14, and the workflows that survive that change are the ones that produce their own evidence while the work is happening.

Someone asks who reviewed a piece of audit work, and when. On a well‑run engagement the answer is in the file. On a great many engagements the answer lives in a reviewer’s memory, a sign‑off buried in an email thread, or a spreadsheet cell that was updated at some point by somebody.

That gap has always been uncomfortable. It is now costly. The PCAOB has cut the period for assembling a complete and final set of audit documentation from 45 days after the report release date to 14. The accelerated window applies to the largest registered firms for fiscal years beginning on or after 15 December 2024 and to other registered firms a year later, with further provisions of the amended standard effective 15 December 2026. AS 1215 is unambiguous about what the assembled file has to show: that the work was performed, who performed it, who reviewed it, and the date of that review. Seven years of retention follow from the report release date.

Two weeks is not much time to reconstruct a history nobody was keeping.

What the file must show
14 days
to assemble a complete and final set of audit documentation after the report release date, reduced from 45
What inspections found
39%
of PCAOB inspections in 2024 identified a Part I.A deficiency, down from 46 percent in 2023
What the file must show
7 years
retention, with the file demonstrating who performed the work, who reviewed it, and when
What inspections found
52%
at annually inspected non‑affiliated firms, against 20 percent at the US Big Four

Figure 1. PCAOB, AS 1215 and the report on 2024 inspection activities published 31 March 2025. A Part I.A deficiency does not mean the financial statements were misstated. It means inspectors concluded the firm had not obtained sufficient appropriate evidence to support its opinion in the area reviewed.

Your Documentation Deadline · Try ItAS 1215, as amended

The trajectory is encouraging. Preliminary 2025 results show further improvement, with Deloitte and EY both reported at 5 percent, EY down from 28 the year before. But the spread across firm tiers is wide, and the profession is being asked to evidence more, faster, from a smaller bench. Accounting graduates fell to 55,152 in the 2023 to 2024 academic year, down 6.6 percent, though undergraduate enrollment has since risen for three straight years.

Why Reconstruction Is the Weak Point

Documentation failures are rarely failures of diligence. The work was done, and usually done well. What went wrong is the sequence.

The evidence gets assembled at the end, from memory, from inboxes, and from trackers that were updated when someone remembered. By then the reviewer has moved to another engagement, the status field has been overwritten twice, and the question of what a number was before someone changed it has no answer anywhere in the system. The file is not a record of the audit. It is a reconstruction of the audit, produced under deadline by people recalling events from weeks earlier.

A 45‑day window forgave a lot of that. A 14‑day window forgives much less.

The file is not a record of the audit. It is a reconstruction of it, produced under deadline by people recalling events from weeks earlier.

Eight Builds, One Chain

The Miles Masterclass Power Automate for Audit Workflows, built across two parts by Griffin Lickfeldt, is useful here for a reason that is easy to miss on a first pass. It contains eight separate builds, and the interesting thing is not any one of them.

Part one covers how audit work enters and moves: a scheduled reminder that nudges whoever owns an overdue procedure, an escalation that routes a newly created audit log to the right department owner, an exception intake that turns a submitted form into a categorized record, and a duplicate detection flow that reads a transaction file and points an auditor at what warrants a look. Part two covers what follows review: sign‑off, a sweep that closes stale items, a change history, and archival.

The masterclass is explicit that these are not eight isolated automations. One flow’s output is the next one’s trigger. A record marked reviewed starts the approval; approval sets it to completed; completed starts the archive. What has actually been built is the lifecycle of an audit finding, from assignment to retention.

Assigned →Scheduled sweep nudges whoever owns an overdue procedure
Captured →Exception logged and routed to the owner for that department
Signed off →Approval requested, decision written back to the record
ArchivedFolder moved out of the active workspace on completion

Figure 2. One flow’s output is the next one’s trigger. The two shaded steps are where the documentation comes from, because each writes a named decision and a timestamp at the moment it happens rather than at the end of the engagement.

Evidence as a By‑Product

Two of the builds matter more than the rest, and neither is the flashiest.

The sign‑off flow sends a formal approval to the log’s original owner, waits for the answer, and writes the outcome back to the record. The result is not a faster approval. It is a named approver and a dated decision attached to the item, created at the moment the decision was made, with nobody having decided to record anything.

The change history flow goes further. Whenever a tracked field changes, it captures the timestamp, whether the record was created or updated, which field moved, the old value, and the new value, and appends that as a row in a running log. That is a contemporaneous record of how a record became what it now says, which is precisely the question that is unanswerable when someone asks three months later.

Reconstructed at the endRecorded as it happened
Ask around who reviewed itApproval record naming the approver
Search the thread for a sign‑offDecision written back to the record
Trust that the status is currentTimestamp on every status change
Try to recall the earlier valueOld value and new value both stored
Hunt for the working folderFolder moved to archive on completion

Figure 3. The same five questions, answered two ways. The right column costs nothing extra at the time, because the record is a by‑product of the step rather than a task that follows it.

One caveat, because auditors will reach for it immediately. These builds run on Excel, Dataverse and SharePoint and are shaped for internal audit and engagement management. Moving a SharePoint folder does not satisfy AS 1215 for a public company audit file, and nobody should present it that way. The transferable point is timing, not tooling. A record created at the moment of the event is evidence. The same fact retrieved from memory two weeks later is testimony.

Audit in progress

Active

Working folder, live tracker, status changing as the audit runs.

Report released → 14 days

Archived

Folder moved the moment the record is marked completed, evidence intact.

Seven‑year retention

Retained

Seven years from the report release date under AS 1215.

Figure 4. Archival is not housekeeping. It is the point at which a working file becomes a retained record, and doing it on a status change rather than on a reminder is what keeps the two categories from mixing.

The Flows Join the Control Environment

There is an obvious objection, and auditors should press it. A workflow that assigns owners, records approvals, and closes items for inactivity is performing control activities. It belongs inside the control environment, not beside it.

The ordinary questions apply. Who can edit and publish a flow, and is that the same person whose work it approves. What happens when it fails silently, the characteristic failure of scheduled automation. How changes are authorized and recorded. The masterclass gives an unglamorous illustration that this is not theoretical: partway through a build it notices a SharePoint trigger has been deprecated and routes around it. Connectors age, and a flow nobody owns is a control nobody is maintaining.

The standard setters are moving in the same direction. The IAASB’s revision of ISA 500 on audit evidence, still at exposure draft stage with comments requested by 15 December 2026, is being modernized explicitly for the use of automated tools and techniques by both the entity and the auditor. The question of what counts as reliable evidence when a system produced it is being asked formally, and firms that have never inventoried their own automations will be answering it from a standing start.

The deeper shift is quieter. Audit has always treated documentation as work that follows the work. Shortening the window to 14 days does not make that sequence faster. It makes it untenable, and the alternative is not more discipline at the end. It is a process that leaves a trail behind it as it runs.

To see how these eight workflows are built and chained together, from checklist reminders through sign‑off, change history and archival, watch Power Automate for Audit Workflows on Miles Masterclass.

Sources

  1. Miles Masterclass, Power Automate for Audit Workflows, Parts 1 and 2.
  2. PCAOB, AS 1215: Audit Documentation (amended; provisions effective 15 December 2026). pcaobus.org
  3. PCAOB news release, 31 March 2025: report on 2024 inspection activities and Part I.A deficiency rates. pcaobus.org
  4. Thomson Reuters, 2026: Big Four firms show significant improvement in PCAOB audit inspection results for 2025. tax.thomsonreuters.com
  5. IAASB, ISA 500 series project page. iaasb.org
  6. Journal of Accountancy, accounting graduate pipeline data from the AICPA Trends report. journalofaccountancy.com

A note on the calculator

Dates are simple calendar arithmetic from the report release date. Check the effective date that applies to your firm and fiscal year before relying on either window.