From Audit Staff to Audit Professional: Build the Skills That Create Audit Quality
Audit & Assurance: Staff Two — September 2–3, 2026
Presented by John C. Blackshire, Jr.
The first year of an auditor's career teaches the mechanics of auditing.
The next stage should teach the auditor how to think like an auditor.
There is an enormous difference between an audit staff member who knows how to complete an assigned procedure and one who understands:
Why am I performing this procedure? What risk am I addressing? What evidence do I need? What does an exception mean? And does my work actually support my conclusion?
Corporate Compliance Seminars' Audit & Assurance: Staff Two program on Wednesday–Thursday, September 2–3, 2026 is designed for auditors making that transition.
Presented by John C. Blackshire, Jr., this two-day live webinar provides 12 CPE credits and concentrates on the practical skills developing financial auditors need: internal controls, ITGCs, data analytics, fraud risk, financial audit procedures, professional skepticism, communication, and audit workpapers.
Audit Quality Begins With the People Doing the Audit
When we discuss audit quality, attention naturally goes to the engagement partner, audit manager, quality review, and firm methodology.
But consider who actually performs much of the detailed audit work.
Staff auditors may be responsible for obtaining evidence, testing transactions, performing walkthroughs, documenting controls, conducting analytical procedures, identifying exceptions, and preparing the workpapers ultimately reviewed by senior members of the engagement team.
The CCS program begins by examining the audit team itself—including the engagement partner, quality-assurance function, manager/supervisor/senior, and the role of audit staff.
The message for developing auditors is important:
You are not merely completing work assigned by someone else. You are contributing evidence to an audit conclusion.
That requires judgment.
Learn to Think in Terms of Risk
One of the most important transitions for a developing auditor is moving away from checklist auditing.
A procedure should not be performed simply because:
“That's what we did last year.”
The auditor should be able to connect the work:
Business Objective
↓
Risk
↓
Internal Control
↓
Financial Statement Assertion
↓
Audit Procedure
↓
Audit Evidence
↓
Conclusion
Once an auditor understands that chain, auditing starts making much more sense.
Instead of asking:
“How many invoices do I need to test?”
the auditor begins asking:
“What am I trying to establish from this test?”
That is professional development.
COSO: Understand the Controls Before You Test Them
Internal control is a major component of Staff Two.
The program addresses the COSO Internal Control Framework, including risk assessment, tone at the top, control activities, information and communication, and monitoring.
For developing auditors, COSO provides a framework for understanding that controls are more than signatures and approvals.
Suppose the auditor sees a manager's initials on a reconciliation.
The inexperienced auditor may conclude:
“Reviewed—control performed.”
The developing professional asks:
What exactly did the manager review?
What risk was the review designed to address?
What would cause the manager to investigate?
What evidence demonstrates the review occurred?
Is the control precise enough to detect the type of misstatement we are concerned about?
That is a very different level of auditing.
Financial Auditors Need to Understand ITGCs
Modern financial reporting depends on information systems.
Consequently, a financial auditor cannot simply say:
“I'm not an IT auditor.”
Staff Two introduces Information Technology General Controls, including IT risk assessment, IT governance, day-to-day information security, and controls affecting the financial-reporting process.
Why does that matter?
Because financial auditors routinely rely upon:
System-generated reports
Automated calculations
Electronic approvals
ERP data
Interfaces
User access
Application controls
If the information supporting an audit procedure comes from technology, the auditor needs to understand enough about that environment to recognize when technology risk affects audit evidence.
Data Analytics Should Become Part of the Auditor's Toolkit
Today's developing auditors also have capabilities previous generations of staff auditors did not.
One of the most important is audit data analytics.
The CCS program addresses analytics during audit planning, fieldwork, and year-end procedures.
Instead of looking only at a small number of transactions, auditors can increasingly analyze larger populations for:
Unexpected trends
Outliers
Duplicate transactions
Unusual journal entries
Period-end activity
Unexpected account relationships
Transactions requiring additional investigation
The objective is not technology for technology's sake.
It is using technology to ask better audit questions.
Fraud Changes How the Auditor Thinks
Fraud considerations are another major part of the September 2–3 program.
The agenda addresses knowing the client, understanding the business model, and segregation of duties as part of considering fraud during a financial audit.
A conventional audit question might be:
“Could this account contain an error?”
The fraud-oriented auditor adds:
“Could someone intentionally manipulate this account and make the transaction appear legitimate?”
That changes the auditor's perspective.
Consider a transaction with complete documentation.
The auditor should still be capable of asking:
Who initiated it?
Who approved it?
Does the transaction make economic sense?
Could management override the control?
Is the supporting documentation reliable?
Is there contradictory evidence?
This is where professional skepticism stops being a phrase in an auditing standard and becomes audit behavior.
Learn the Financial Audit Procedures Staff Actually Perform
Staff Two also gets into the practical financial-audit work assigned to developing auditors.
The program covers procedures involving areas such as cash and cash equivalents, accounts receivable, inventory valuation, and accounts payable.
This is where auditors need to learn the relationship between the account, assertion, risk, and procedure.
For example, the principal concern for one account might be existence.
For another it might be completeness.
For another:
Valuation.
The auditor needs to understand why different accounts require different audit approaches.
That understanding is much more valuable than memorizing an audit program.
Audit Evidence Is the Foundation
John C. Blackshire, Jr. has also written for CCS about the importance of audit evidence, emphasizing that audit evidence is not simply a collection of signed documents stored in a workpaper file. It is the foundation supporting the auditor's conclusions.
That principle should be embedded early in an auditor's career.
A document isn't automatically persuasive evidence simply because management gave it to the auditor.
The auditor needs to ask:
Is it relevant?
Is it reliable?
Does it address the assertion?
Is there contradictory evidence?
Do I have enough evidence?
That is how the auditor moves from document collection to evidence evaluation.
Workpapers Should Tell the Audit Story
The Staff Two agenda specifically includes techniques for producing clear and accurate audit workpapers.
A good workpaper should allow an experienced reviewer to understand:
Objective → Risk → Procedure → Evidence → Results → Exceptions → Conclusion
The reviewer should not have to track down the preparer and ask:
“What were you trying to prove?”
Nor should the reviewer have to guess why the documented evidence supports the conclusion.
A workpaper is where the auditor's professional reasoning becomes visible.
Learn What to Do When You Find an Exception
Auditing becomes considerably more interesting when the answer is not what the auditor expected.
Suppose you test 25 transactions.
Twenty-three pass.
Two fail.
Now what?
The inexperienced auditor may document:
“Two exceptions noted.”
The developing professional starts asking:
Are the exceptions similar?
Why did they happen?
Did the control fail?
Could the problem exist elsewhere in the population?
Does the exception affect our risk assessment?
Do we need additional testing?
Does this indicate a control deficiency?
Who needs to know?
That is where audit judgment begins to develop.
Professional Skepticism Is a Learned Skill
Professional skepticism does not mean assuming that management is dishonest.
It means refusing to substitute an assertion for evidence.
Management says:
“That was a one-time exception.”
The auditor asks:
“How do we know?”
Management says:
“The system prevents that.”
The auditor asks:
“Can we test it?”
Management says:
“We corrected the problem.”
The auditor asks:
“What evidence demonstrates the corrective action?”
Management says:
“We've always done it this way.”
The auditor asks:
“Does it effectively address the risk?”
That questioning mindset separates the developing audit professional from someone merely completing procedures.
Soft Skills Are Audit Skills
Auditors do not obtain all their evidence from spreadsheets.
They obtain information from people.
That makes communication a technical audit competency.
The CCS program includes communication, status reporting, interpersonal skills, and professional skepticism as part of developing staff competency.
A developing auditor needs to learn how to ask:
“Walk me through what happens next.”
rather than:
“Do you follow the policy?”
The first question produces information.
The second frequently produces:
“Yes.”
Good interviewing, active listening, follow-up questions, and the ability to recognize when an answer does not make sense are all part of audit tradecraft.
AI Is Raising the Expectations for Developing Auditors
There is another issue facing auditors entering the profession in 2026.
Artificial Intelligence is changing audit work.
AI can help auditors develop questions, analyze information, summarize documents, brainstorm risks, improve workpaper narratives, evaluate unusual relationships, and challenge preliminary conclusions.
But AI creates an important distinction.
AI can help a competent auditor work faster. It cannot substitute for understanding auditing.
If an auditor doesn't understand risk, AI-generated audit procedures may look impressive without addressing the engagement risk.
If an auditor doesn't understand evidence, an AI-generated conclusion may sound convincing without adequate support.
If an auditor doesn't understand internal control, AI cannot make that auditor competent simply by generating a COSO analysis.
Developing strong fundamentals therefore becomes more important as AI becomes more capable, not less.
Why Learn From John C. Blackshire, Jr.?
CCS describes its programs as practical training taught by practitioners, with emphasis on what auditors actually do, where organizations fail, and how professionals can identify risk and test controls. The CCS site identifies John C. Blackshire, Jr. as one of its instructors and contributors, and his recent CCS writing has addressed audit evidence and the development of auditors from technical practitioners into audit leaders.
That perspective fits Staff Two particularly well.
The objective isn't simply to teach another set of auditing definitions.
It is to help the developing auditor understand the audit process as an integrated professional discipline.
Build the Auditor Before You Need the Senior
Public accounting firms sometimes expect experience alone to develop staff.
Experience matters enormously.
But experience without structured development can also reinforce weak habits.
The better progression is:
Perform the Procedure
↓
Understand the Procedure
↓
Understand the Risk
↓
Evaluate the Evidence
↓
Recognize the Exception
↓
Determine the Next Audit Step
↓
Defend the Conclusion
↓
Eventually Supervise Others
That progression does not happen automatically.
It needs to be taught, practiced, reviewed, and reinforced.
Who Should Attend?
CCS identifies the program as particularly appropriate for first-year auditors, early-career audit staff, and professionals transitioning into financial auditing.
It should be especially valuable for accounting firms seeking to strengthen staff working on financial statement audits and for professionals who are ready to move beyond introductory audit concepts.
The program provides 12 NASBA-approved CPE credits over two sessions. Each day runs from 9:00 a.m. to 3:00 p.m. Central Time, with a 30-minute lunch break.
Join John C. Blackshire, Jr. on September 2–3, 2026
Corporate Compliance Seminars' Audit & Assurance: Staff Two will be presented Wednesday–Thursday, September 2–3, 2026.
The two-day program concentrates on the competencies that help turn a new audit staff member into a developing audit professional:
Internal Controls.
COSO.
ITGCs.
Data Analytics.
Fraud.
Financial Audit Procedures.
Audit Evidence.
Professional Skepticism.
Workpapers.
Communication.
The objective is not simply to teach someone how to complete an audit program.
It is to develop auditors who understand why the work is being performed, what evidence is needed, and what the results actually mean.
That is the foundation of audit quality.
Comments