PCAOB Audit Quality Starts With the Staff: Why Financial Auditors Should Attend Audit & Assurance: Staff Two
- John Blackshire
- Aug 18
- 7 min read
Live Webinar — Wednesday–Thursday, September 2–3, 2026
A PCAOB-regulated audit is not performed only by the engagement partner.
Much of the evidence gathering, walkthrough work, testing, documentation, analytical work, and day-to-day interaction with the client is performed by staff auditors.
That creates a fundamental audit-quality issue:
The quality of the engagement ultimately depends, in part, on the competence of the people performing the audit procedures.
For firms performing audits under PCAOB standards, developing staff auditors cannot be treated as an informal process of simply assigning work and hoping experience eventually produces competence.
Corporate Compliance Seminars' Audit & Assurance: Staff Two program on Wednesday–Thursday, September 2–3, 2026 is designed to help early-career financial auditors strengthen the practical skills they need as their responsibilities increase. The two-day live webinar provides 12 CPE credits and covers internal controls, ITGCs, data analytics, fraud, analytical procedures, financial audit procedures, workpapers, professional skepticism, and the responsibilities of the audit team.
PCAOB Auditing Is an Evidence Business
At its core, an audit is about evidence.
PCAOB AS 1105 establishes that the auditor must plan and perform the audit to obtain sufficient appropriate audit evidence to support the opinion expressed in the auditor's report. Audit evidence includes information supporting management's assertions as well as information contradicting those assertions.
That sounds straightforward.
In practice, it requires judgment.
A staff auditor needs to learn the difference between:
Obtaining a document
and
Obtaining audit evidence.
Those are not necessarily the same thing.
The auditor must understand:
Why the procedure is being performed
Which assertion is being tested
What risk the procedure addresses
Whether the evidence is relevant
Whether the evidence is reliable
What an exception means
Whether additional procedures are necessary
How the conclusion should be documented
These are skills that have to be developed.
Staff Auditors Need to Understand the Entire Audit Team
One of the first subjects in the CCS program is the structure of the audit team, including the engagement partner, quality-assurance function, manager/supervisor/senior, and staff auditor.
That is particularly relevant in the PCAOB environment.
PCAOB AS 1201 establishes requirements for supervision of the audit engagement, including supervision of engagement-team members so that their work is performed as directed and supports the conclusions reached.
Supervision, however, does not eliminate the staff auditor's responsibility to perform competent work.
The staff auditor needs to understand:
What am I testing?
Why am I testing it?
What evidence do I need?
What could go wrong?
What should I do when the results aren't what I expected?
A staff auditor who merely executes last year's workpaper is not developing the judgment needed for increasingly complex PCAOB engagements.
Understanding Internal Control Is Fundamental
The Staff Two program introduces auditors to the COSO Internal Control Framework, including risk assessment, tone at the top, control activities, information and communication, and monitoring.
That foundation is important even when the auditor is not performing an integrated audit of internal control over financial reporting.
The financial auditor needs to understand how transactions move through the organization:
Objective
↓
Business Process
↓
Risk
↓
Control
↓
Financial Statement Assertion
↓
Audit Procedure
↓
Evidence
Without that connection, control testing can deteriorate into checklist auditing.
The staff auditor sees that someone signed a document and concludes that the control worked.
The better auditor asks:
What was that person supposed to review?
What risk was the review intended to mitigate?
What evidence demonstrates that the review actually occurred at the required level of precision?
That is a considerably more mature approach to auditing.
Staff Auditors Cannot Ignore ITGCs
Modern financial reporting depends on information technology.
That means even financial auditors who do not consider themselves IT auditors need a working understanding of Information Technology General Controls.
The CCS Staff Two program addresses IT risk assessment, IT governance, day-to-day information security, and internal controls affecting financial reporting.
Why does that matter?
Because an auditor may be relying on:
System-generated reports
Automated calculations
Electronic approvals
Interfaces
Access controls
Application controls
A beautifully designed business-process control may provide weak assurance if the underlying technology environment cannot be trusted.
Professional Skepticism Is a Behavior, Not a Phrase
PCAOB AS 1000 describes professional skepticism as including a questioning mind and critical assessment of audit evidence. Among other things, auditors are expected to evaluate both corroborating and contradictory evidence, remain alert to possible error or fraud, and avoid being satisfied with evidence that is less than persuasive.
This is particularly important for developing auditors.
Management says:
“That's just a one-time exception.”
The auditor should ask:
How do we know?
Management says:
“We've always done it this way.”
The auditor should ask:
Does that actually address the risk?
Management says:
“That account always reconciles.”
The auditor should ask:
What does the evidence show this year?
Professional skepticism is not distrust.
It is disciplined verification.
Fraud Requires the Staff Auditor to Think Differently
Fraud is another major component of Staff Two.
The CCS agenda includes knowing the client, understanding the business model, segregation of duties, and fraud considerations during the financial audit.
That aligns directly with the demands placed on PCAOB auditors.
AS 2401 emphasizes that professional skepticism is especially important when considering fraud risk. Auditors must maintain awareness that material misstatement due to fraud could exist regardless of prior experience with the entity or beliefs about management's honesty.
The developing auditor therefore needs to learn to move beyond:
“Does the balance reconcile?”
toward questions such as:
How could this account be manipulated?
Who has the ability to override this control?
What incentive would someone have to alter this number?
What evidence would conceal the manipulation?
That is where financial auditing begins to become audit tradecraft.
Learn to Connect Risk to the Audit Response
Another important competency for auditors working on PCAOB engagements is understanding why procedures change when risk changes.
PCAOB AS 2301 addresses the auditor's response to risks of material misstatement and emphasizes professional skepticism when gathering and evaluating evidence, particularly in response to fraud risks.
The logic should be:
Higher Risk
↓
More Persuasive Evidence Needed
↓
Audit Response Changes
That sounds obvious.
But inexperienced auditors sometimes approach an engagement as though the audit program itself were the objective.
It isn't.
The audit program is a means of responding to identified risks.
A strong staff auditor learns to understand the why behind the procedure.
Data Analytics Is Becoming Part of the Financial Auditor's Toolkit
Staff Two also addresses data analytics during:
Audit planning
Fieldwork
Year-end procedures
That capability is increasingly important.
Rather than looking only at a small number of individual transactions, auditors can use analytics to identify:
Unusual trends
Unexpected relationships
Outliers
Duplicate transactions
Unusual journal entries
Period-end activity
Unexpected account movements
Analytics does not replace audit judgment.
It can make that judgment better informed.
Get Better at Auditing the Accounts
The program moves from concepts into practical financial-audit procedures involving areas such as cash and cash equivalents, accounts receivable and allowances, inventory, and accounts payable.
This is where early-career auditors need repetition and understanding.
For every account, the auditor should be thinking:
What could go wrong?
Which assertion is affected?
What evidence would detect the misstatement?
For accounts receivable, for example, existence may be a major concern.
For accounts payable, completeness may become particularly important.
For inventory, existence and valuation can both become significant.
The procedure should follow the risk and assertion—not simply last year's workpaper.
Workpapers Have to Tell the Audit Story
Staff Two also includes techniques for creating clear and accurate audit workpapers.
A strong workpaper should allow a reviewer to understand:
Objective → Risk → Procedure → Evidence → Results → Exceptions → Conclusion
The workpaper should not force the reviewer to reconstruct what the auditor was thinking.
This is especially important in a PCAOB-regulated environment, where the audit documentation needs to support the work performed and the conclusions reached.
Why Firms Should Send Their Staff
Audit firms sometimes invest heavily in technical updates for partners and managers while assuming staff will develop primarily through engagement experience.
Engagement experience is essential.
But experience without structured learning can also reinforce bad habits.
A developing auditor needs to understand the underlying methodology before being expected to exercise increasingly sophisticated judgment.
The PCAOB's current standards reinforce the importance of competence, due professional care, professional skepticism, sufficient appropriate evidence, and proper supervision throughout an audit.
Training staff therefore isn't separate from audit quality.
Staff development is part of the audit-quality infrastructure.
Who Should Attend?
This program is particularly appropriate for:
First-year financial auditors moving into greater responsibilities
Early-career external auditors
Staff working on PCAOB-regulated issuer audits
Staff working on PCAOB-regulated broker-dealer audits
Auditors transitioning into financial-statement auditing
Firms seeking a more structured staff-development program
PCAOB standards apply to registered public accounting firms preparing audit reports for public companies and other issuers, as well as broker-dealers.
For firms operating in that environment, developing competent staff is not optional.
Audit Quality Is Built From the Bottom Up
The engagement partner signs the report.
But the engagement partner does not personally perform every audit procedure.
Audit quality depends upon a team.
The staff auditor examining the invoice matters.
The staff auditor performing the walkthrough matters.
The staff auditor testing the control matters.
The staff auditor investigating the exception matters.
The staff auditor preparing the workpaper matters.
And the staff auditor who recognizes that something doesn't make sense and asks another question may matter most of all.
That is why professional development early in an auditor's career has such a significant payoff.
Join CCS September 2–3, 2026
Corporate Compliance Seminars' Audit & Assurance: Staff Two webinar will be presented Wednesday–Thursday, September 2–3, 2026.
The program runs in two live sessions from 9:00 a.m. to 3:00 p.m. Central Time, with a 30-minute lunch break each day, and provides 12 CPE credits.
For financial auditors performing PCAOB-regulated work, this program provides an opportunity to strengthen the skills underneath audit quality:
Internal Controls.
ITGCs.
Fraud.
Data Analytics.
Audit Procedures.
Workpapers.
Professional Skepticism.
Communication.
The objective should not be to develop staff who simply know how to complete an audit program.
The objective should be to develop auditors who understand risk, controls, evidence, and why they are performing the work.
That is the auditor you want on a PCAOB engagement.
Comments