PCAOB AS 1215: If It Is Not Documented, Can You Prove the Audit Work Was Performed?

John C. Blackshire, Jr.
12 hours ago
7 min read

Audit Documentation Training — September 29 and December 1, 2026

An auditor can perform an excellent audit procedure, reach the correct conclusion and still have an audit-quality problem.

Why?

Because the workpaper does not demonstrate what the auditor actually did.

That is the problem addressed by PCAOB Auditing Standard AS 1215 — Audit Documentation.

Corporate Compliance Seminars' PCAOB AS 1215: Audit Documentation is a focused 1-CPE Auditing webinar designed to help auditors understand the PCAOB's requirements for preparing, reviewing and retaining audit documentation. The program covers documentation of audit procedures, evidence, findings and conclusions, along with documentation quality and review.

Upcoming sessions are:

Tuesday, September 29, 2026

Tuesday, December 1, 2026

PCAOB AS 1215: Audit Documentation — Corporate Compliance Seminars

Audit Documentation Is the Evidence of the Audit

The PCAOB describes audit documentation as the written record supporting the auditor's conclusions and representations. It also facilitates planning, performance, supervision and review of the engagement.

That makes the workpaper much more than an administrative record.

It answers a fundamental question:

What evidence demonstrates that the auditor actually performed sufficient work to support the conclusion?

Consider the difference between these two workpaper statements:

“Reviewed revenue. No exceptions noted.”

versus:

“Selected 40 revenue transactions from the population using the sampling methodology documented in WP R-2. For each item, agreed the transaction to the customer order, shipping documentation, invoice and general ledger. Three exceptions were identified and evaluated in WP R-6. Based upon the procedures performed and resolution of the exceptions, no material misstatement was identified.”

The second tells the reviewer something about what actually happened.

That is the objective.

The Experienced Auditor Test

One of the most important concepts in AS 1215 is what might be called the experienced auditor test.

The documentation must contain enough information for an experienced auditor with no previous connection to the engagement to understand:

The nature of the procedures performed
The timing of those procedures
Their extent
The results
The evidence obtained
The conclusions reached

The documentation must also permit that auditor to determine who performed the work, when it was completed, who reviewed it and when it was reviewed.

That provides auditors with a practical test for every significant workpaper:

Could another experienced auditor understand exactly what I did without having to ask me?

If the answer is no, the documentation probably needs improvement.

A Workpaper Should Tell a Story

Strong audit documentation has a logical progression:

Audit Objective

→ Risk

→ Financial Statement Assertion

→ Procedure Performed

→ Evidence Obtained

→ Results

→ Exceptions

→ Evaluation

→ Conclusion

A reviewer should not have to hunt through ten unrelated files to understand why the auditor reached a conclusion.

AS 1215 requires documentation to be appropriately organized and to provide a clear link to significant findings or issues.

The workpapers should therefore tell the story of the audit.

“Per Inquiry of Management” Is Usually Only the Beginning

One of the easiest documentation traps occurs when the auditor writes:

“Per discussion with management, no issues were identified.”

What does that establish?

It establishes that management said something.

It does not necessarily establish that the auditor obtained sufficient appropriate evidence supporting management's assertion.

A stronger workpaper explains:

Who was interviewed?
What was asked?
What was represented?
What evidence corroborated the representation?
Were contradictory facts identified?
What conclusion did the auditor reach?

Documentation quality and audit-evidence quality are closely connected.

Document What You Actually Did

The PCAOB requires documentation to demonstrate that the work was actually performed. AS 1215 requires documentation of the procedures performed, evidence obtained and conclusions reached with respect to relevant financial statement assertions.

That means:

“Tested controls.”

is inadequate.

Which controls?

What population?

What sample?

What attributes?

What evidence?

What exceptions?

What conclusion?

The workpaper needs enough specificity to establish the relationship between procedure, evidence and conclusion.

Document the Exceptions

Auditors naturally like clean workpapers.

Everything reconciles.

No exceptions.

Control effective.

Move on.

Real audits are frequently messier.

Suppose the auditor tests 40 transactions and identifies four exceptions.

Those exceptions should not disappear merely because the auditor ultimately concludes they do not create a material misstatement.

The documentation should demonstrate:

What happened

→ Why it happened

→ How the exception was evaluated

→ Whether additional procedures were necessary

→ What evidence was obtained

→ Why the final conclusion remained appropriate

The difficult items are often where documentation matters most.

Contradictory Evidence Cannot Simply Disappear

This is particularly important.

The PCAOB's basis for AS 1215 specifically discusses information that is inconsistent with or contradicts the auditor's final conclusions.

Suppose most evidence supports management's accounting estimate, but one significant piece of evidence points in the opposite direction.

The workpaper should not simply document the supporting evidence and ignore the contradiction.

The auditor needs to evaluate it.

That is part of professional skepticism.

A useful audit trail is:

Contradictory Evidence Identified

→ Investigated

→ Additional Evidence Obtained

→ Professional Judgment Applied

→ Resolution Documented

→ Conclusion Supported

That can become extremely important when an engagement is subsequently inspected.

Who Performed the Work?

AS 1215 also requires the documentation to clearly demonstrate:

Who performed the work
When the work was completed
Who reviewed the work
When the review occurred.

These requirements support accountability throughout the engagement.

The documentation establishes not only what was done but who was professionally responsible for doing and reviewing it.

Review Notes Are Part of Audit Quality

Imagine an audit senior reviews a workpaper and asks:

“What evidence supports this conclusion?”

The staff auditor provides additional evidence.

The senior is satisfied.

Review note closed.

Good.

But the final workpaper should stand on its own.

Closing the review note should not leave behind a workpaper that still fails to explain the conclusion.

The objective isn't to get rid of review comments.

It is to resolve the underlying audit-quality issue that caused the comment.

Documentation Supports Supervision

Audit documentation is also fundamental to engagement supervision.

Partners and managers cannot personally perform every audit procedure.

They rely on documentation to determine:

What did the staff auditor do?

Was the procedure performed correctly?

Were significant exceptions identified?

Was appropriate evidence obtained?

Were difficult judgments appropriately evaluated?

Does the evidence support the conclusion?

That is why poor documentation is not simply a staff-level problem.

It can become an engagement supervision problem.

Documentation Supports Engagement Quality Review

The same issue applies to the Engagement Quality Reviewer.

The EQR needs to understand significant judgments and determine whether adequate evidential support exists for significant conclusions.

AS 1215 expressly recognizes engagement supervisors and engagement quality reviewers among those who may review audit documentation to understand how the engagement team reached significant conclusions and whether those conclusions have adequate evidential support.

Poor documentation therefore weakens another important audit-quality control.

And Then Comes the PCAOB Inspector

There is a practical reason every PCAOB auditor should care about AS 1215.

Your workpapers may eventually be examined by someone who was not in the room when the audit occurred.

The PCAOB specifically describes audit documentation as fundamental to meaningful inspection and other quality reviews.

The inspector cannot know:

“We discussed this extensively.”

The inspector sees the documentation.

That leads to one of the most useful rules in PCAOB auditing:

Do not depend upon your memory to explain an audit that the workpapers should explain themselves.

Documentation Is Not About Producing More Paper

There is an important distinction here.

Better audit documentation does not necessarily mean more documentation.

A 30-page workpaper filled with irrelevant information can be worse than a concise five-page workpaper establishing:

Objective
Procedure
Evidence
Exceptions
Judgment
Conclusion

The goal is not volume.

The goal is clarity, relevance and sufficient support.

CCS's AS 1215 program focuses specifically on documentation requirements, maintaining documentation quality and conducting effective reviews.

AI Creates a New Documentation Risk

Artificial intelligence makes AS 1215 even more relevant.

AI can help auditors:

Summarize documents
Organize evidence
Draft workpaper narratives
Analyze data
Develop audit procedures
Improve writing

Those capabilities can improve efficiency.

But they also create a danger.

AI can produce a beautifully written workpaper describing a procedure that was not actually performed.

That is unacceptable.

The fundamental AS 1215 principle still applies:

The workpaper must document the work the auditor actually performed and the evidence actually obtained.

AI can help document the audit.

AI cannot manufacture the audit.

The December 2026 Amendments Make This Training Especially Timely

There is another important reason PCAOB auditors should revisit AS 1215 during 2026.

The PCAOB states that amendments to paragraphs .09 and .11 of AS 1215 become effective December 15, 2026.

That makes the December 1, 2026 CCS session particularly timely—just two weeks before the effective date.

Firms should understand not only the existing documentation requirements but how AS 1215 fits into the PCAOB's evolving audit-quality environment.

Seven Questions to Ask Before Closing a Workpaper

Before signing off, ask:

What audit objective was I trying to accomplish?
What procedure did I actually perform?
What evidence did I obtain?
What exceptions or contradictory evidence did I identify?
How did I resolve those matters?
Does the evidence logically support my conclusion?
Could an experienced auditor with no connection to this engagement understand all of this from my documentation?

If number seven produces hesitation, the workpaper probably isn't finished.

Two Opportunities to Attend in 2026

Corporate Compliance Seminars' PCAOB AS 1215: Audit Documentation is a Basic-level, Group Internet-Based program providing 1 CPE credit in Auditing. The program is offered from 1:00 p.m. to 2:00 p.m. Central Time, requires no prerequisites or advance preparation, and costs $70 per attendee.

Tuesday, September 29, 2026

A timely opportunity for PCAOB audit professionals preparing for the year-end audit cycle to sharpen their documentation practices before the workpapers are created.

Tuesday, December 1, 2026

Particularly timely for CPA firms because amendments to AS 1215 paragraphs .09 and .11 become effective December 15, 2026.

The Bottom Line: Make the Workpaper Speak for Itself

Audit documentation should answer five fundamental questions:

What did you do?
Why did you do it?
What evidence did you obtain?
What did you find?
Why does the evidence support your conclusion?

The audit trail should be clear:

Risk

→ Audit Objective

→ Procedure

→ Evidence