AUD Area I.F Study Notes: Communicating with Management and Those Charged with Governance

I.F.1 Planned scope and timing of an engagement

What “planned scope and timing” communication is

When you audit or attest, you’re not working in a vacuum—you’re working in a governance structure where management prepares the information and those charged with governance (TCWG) oversee management and financial reporting. Planned scope and timing communication is the auditor’s discussion with TCWG (and often management) about how the engagement will be carried out and when key work and deliverables will occur.

Under U.S. auditing standards, this is a required communication concept. In the AICPA (clarified) standards, it’s addressed in AU-C 260, The Auditor’s Communication With Those Charged With Governance. For public company audits under PCAOB standards, the parallel requirement is AS 1301, Communications with Audit Committees.

At a practical level, this communication is often done early in the audit—sometimes at an audit committee meeting—where you explain your audit strategy at a high level.

Why it matters

Communicating the planned scope and timing is not just etiquette; it supports audit quality and governance oversight.

  1. TCWG can’t oversee what they don’t understand. If the audit committee/board is responsible for oversight, they need a clear picture of what the auditor is planning to do, including where the auditor will focus and why.
  2. It improves coordination and reduces surprises. Timing discussions help management and TCWG plan for PBC (provided-by-client) schedules, key meetings, and deadlines—reducing last-minute scrambling.
  3. It reinforces independence and transparency. Explaining the approach and the role boundaries helps avoid misunderstandings (e.g., management thinking the auditor will “help design controls” or “decide the accounting”).
  4. It supports a two-way flow of information. TCWG may share concerns about fraud risks, related parties, pressure points, or prior control issues—information that can directly affect risk assessment and audit procedures.
Who you communicate with: management vs. TCWG

A common exam trap is assuming “management” and “TCWG” are interchangeable. They’re related but distinct roles.

  • Management runs the company day-to-day and is responsible for preparing the financial statements and designing/maintaining internal control.
  • Those charged with governance (TCWG) are responsible for overseeing the entity’s strategic direction and accountability, including financial reporting and internal control oversight. Examples include the board of directors or audit committee.

In some smaller entities, the same individuals may serve in both roles (e.g., owner-managed business). Even then, questions may still ask you to identify which communications are “to TCWG.”

What you typically communicate about scope and timing (and what you don’t)

The point is to provide a meaningful overview—not a step-by-step audit program. Overly detailed descriptions can be counterproductive and, in some cases, could risk the effectiveness of unpredictable procedures.

Scope-related items often include:

  • The overall audit strategy: the broad approach (e.g., reliance on controls vs. primarily substantive testing, use of interim testing).
  • Areas of significant risk or heightened attention (high level): for example, revenue recognition, estimates, business combinations, or complex financial instruments.
  • The extent of component involvement (if applicable): using component auditors, locations, or business units.
  • Use of internal auditors (if the external auditor plans to use their work) and/or specialists (valuation, actuarial, IT).
  • The concept of materiality and how it influences the nature/extent of procedures—often explained qualitatively rather than with an exact threshold, depending on circumstances.

Timing-related items often include:

  • Planned timing for interim work and year-end fieldwork.
  • Planned timing for required meetings and deliverables (e.g., when the auditor expects to discuss significant findings).
  • Deadlines for management’s schedules and when the auditor needs draft financial statements.

What you generally avoid:

  • Providing a checklist-level description of exactly which procedures will be performed on which dates.
  • Disclosing details that would make procedures predictable in a way that could reduce audit effectiveness.
How the communication works in practice (step-by-step)

A useful way to understand this is as a sequence of planning and feedback loops:

  1. Plan internally first. You start with preliminary planning: understanding the entity, preliminary analytics, risk assessment, and engagement staffing.
  2. Draft an audit strategy. This includes major focus areas, potential reliance on controls, and timing.
  3. Communicate with TCWG early. You explain the plan at a level appropriate for governance oversight.
  4. Listen and adjust. TCWG may flag concerns (e.g., a new compensation plan affecting revenue recognition incentives, new IT system, whistleblower allegations). That information can change your risk assessment and planned procedures.
  5. Update communications as needed. If the scope or timing changes significantly (e.g., a late acquisition, restatement risk, unexpected control breakdown), the auditor updates TCWG.

A frequent student misconception is thinking communication is a one-time “kickoff.” Standards treat it as part of an ongoing relationship—especially when circumstances change.

AICPA vs. PCAOB emphasis (helpful comparison)

Both frameworks require communication with governance, but public company audits often have more formal audit committee interactions.

TopicAICPA (AU-C 260)PCAOB (AS 1301)
AudienceTCWG (board/audit committee or equivalent)Audit committee
Scope & timingRequired to communicate planned scope and timingRequired to communicate an overview of the audit strategy, including timing
StylePrinciples-based; tailor to entityMore prescriptive in some areas; audit committee focus

For exam purposes, you’re usually being tested on the concept: the auditor must communicate the planned scope and timing to governance and keep them informed.

“Show it in action” examples
Example 1: Planning meeting with an audit committee (scope + timing)

You’re the auditor of a mid-sized manufacturer. In the planning meeting with the audit committee (TCWG), you communicate:

  • Timing: interim control walkthroughs in October; year-end fieldwork in January; audit report targeted by mid-February.
  • Scope highlights: focus on inventory valuation (standard cost updates, obsolescence reserves) and revenue cut-off due to large quarter-end shipments.
  • Resources: involvement of an IT specialist because the company implemented a new warehouse management module.

The audit committee responds that there were significant turnover issues in shipping in December and that management received a customer complaint about invoice accuracy. You update your risk assessment for revenue and cut-off and adjust planned testing.

Why this example matters: It illustrates the two-way nature of communication—scope/timing discussion helps you identify risks you might not have fully appreciated.

Example 2: Small entity where management = TCWG

You audit a closely held business where the owner is also the CEO and the only board member.

You still communicate scope and timing—your communication is just directed to the same person wearing two hats. A question might ask whether AU-C 260 still applies. Conceptually, yes: the auditor must ensure appropriate governance communications occur, even if the governance structure is minimal.

What can go wrong (common pitfalls)
  • Overpromising: Saying you will “catch all fraud” or “verify every transaction.” The audit provides reasonable assurance, not a guarantee.
  • Confusing audit strategy with audit program: TCWG needs the big picture; they don’t need a procedural script.
  • Not updating TCWG when circumstances change: A major late adjustment, unexpected risk, or change in timetable should prompt refreshed communication.
  • Communicating only to management: Many required communications must go to TCWG (not just the CFO).
Exam Focus
  • Typical question patterns:
    • Scenarios asking who must receive the planned scope and timing communication (management vs. TCWG vs. both).
    • Questions describing an audit plan change and asking whether the auditor should update TCWG.
    • Matching items (e.g., use of specialists, significant risks, timetable) to “scope and timing” communication.
  • Common mistakes:
    • Treating TCWG as synonymous with management; choose “audit committee/board” when governance oversight is implied.
    • Picking an answer that provides excessive procedural detail rather than an overview.
    • Forgetting the communication is ongoing—changes in strategy/timing can trigger additional communication.

I.F.2 Internal control related matters

What “internal control related matters” communication is

During an audit, you inevitably learn things about the client’s internal control over financial reporting—even if the audit is not an examination of internal control effectiveness (as it is in some integrated audits for issuers). The standards require you to communicate certain control issues to management and TCWG.

The key idea: when the auditor identifies deficiencies in internal control, the auditor evaluates their severity and communicates the more important ones—especially significant deficiencies and material weaknesses—to the appropriate parties.

In the AICPA standards for financial statement audits, this is primarily addressed in AU-C 265, Communicating Internal Control Related Matters Identified in an Audit. For PCAOB audits, the analogous standard is AS 1305, Communications About Control Deficiencies in an Audit of Financial Statements.

Why it matters

Internal control communication is about preventing repeated financial reporting failures.

  • Controls are management’s responsibility, but governance oversees them. Auditors don’t “own” the controls, but they are often the independent party most likely to identify breakdowns that could lead to misstatements.
  • Deficiencies drive risk. Control problems can change your audit approach (more substantive testing, different timing, more unpredictability).
  • Users expect governance to be informed. Especially for serious issues (material weaknesses), it’s not acceptable for those overseeing reporting to be unaware.

A major misconception is that auditors only communicate control issues if a misstatement actually occurred. In reality, a control deficiency can require communication even if no misstatement is found, because the deficiency increases risk.

Core definitions (learn these cold)

Standards use a severity hierarchy. On the exam, questions often revolve around the best classification and who must be told.

  • Control deficiency: A control is missing or not operating as designed such that employees may not prevent, or detect and correct, misstatements on a timely basis.
  • Significant deficiency: A deficiency (or combination) that is less severe than a material weakness yet important enough to merit attention by TCWG.
  • Material weakness: A deficiency (or combination) such that there is a reasonable possibility that a material misstatement of the financial statements will not be prevented, or detected and corrected, on a timely basis.

Two points students often mix up:

  1. “Reasonable possibility” does not mean “more likely than not.” It means more than remote—i.e., the risk is meaningfully possible.
  2. A material weakness is tied to the risk of a material misstatement; a significant deficiency can be important even if it doesn’t rise to that level.
How auditors identify control deficiencies (the mechanism)

You usually find control issues while performing procedures such as:

  • Understanding processes and performing walkthroughs.
  • Testing operating effectiveness of controls (when planning to rely on controls).
  • Performing substantive testing that reveals errors suggesting a control didn’t work.
  • Observing segregation of duties issues, lack of review controls, missing approvals, poor IT access controls, etc.

Importantly, the auditor is not required to find all deficiencies. The audit is designed to obtain reasonable assurance about the financial statements, not to provide comprehensive control assurance (unless it’s an integrated audit of ICFR).

Evaluating severity: what pushes a deficiency “up the ladder”?

Severity depends on two dimensions:

  1. Magnitude: How big could the potential misstatement be? Could it be material?
  2. Likelihood: How likely is it that the control failure could lead to a misstatement that won’t be caught timely?

Factors that often increase severity include:

  • The deficiency relates to an area with subjective estimates (allowance, impairment, fair value).
  • It involves senior management or indicates management override potential.
  • It affects multiple accounts/assertions or a core process (revenue, closing process).
  • There are compensating controls (these can reduce severity if they effectively address the risk).

A classic exam move is to give you a deficiency and ask whether it is a significant deficiency or material weakness. You should mentally ask:

  • Could this lead to a material misstatement?
  • Is there a reasonable possibility it wouldn’t be prevented or detected timely?
Required communications: who, what, and how
Who receives the communication

While specifics vary by framework, the general pattern is:

  • Management: receives communications so they can remediate.
  • TCWG (e.g., audit committee/board): receives communications about significant deficiencies and material weaknesses, because they oversee management’s control responsibilities.

For issuers, PCAOB standards focus communications to the audit committee.

What must be communicated

At minimum, communications typically include:

  • Identification of significant deficiencies and material weaknesses found during the audit.
  • An explanation that the purpose of the audit was to express an opinion on the financial statements—not to provide assurance on internal control—and therefore the auditor may not have identified all deficiencies.

Auditors may also communicate other deficiencies to management (often in a management letter), but the “must communicate to TCWG” threshold generally starts at significant deficiencies.

Written vs. oral

Under AU-C 265, communications of significant deficiencies and material weaknesses are required to be in writing to management and TCWG.

Oral discussions can happen throughout the audit (and they often do), but the required communication is formalized in writing.

Timing requirements (commonly tested)

Timing is where exam questions often get very specific.

AICPA (AU-C 265)

The auditor must communicate significant deficiencies and material weaknesses in writing no later than 60 days following the report release date (the date the auditor allows the report to be used).

This does not mean the auditor should wait—serious issues are typically communicated earlier. But the standard provides an outside deadline.

PCAOB (AS 1305)

For audits under PCAOB standards, significant deficiencies and material weaknesses are communicated in writing to the audit committee prior to the issuance of the auditor’s report.

If you see a public company audit fact pattern and the question asks “by when,” the safe instinct is: before the audit report is issued.

Relationship to the audit approach (how this affects what you do next)

Once you identify a significant deficiency or material weakness, it changes the audit in practical ways:

  • You reassess risk of material misstatement and may revise planned procedures.
  • You may increase substantive testing or adjust timing closer to year end.
  • You consider whether the deficiency indicates a risk of fraud or management override.
  • You remain independent: you can recommend improvements at a high level, but you cannot design or implement controls for the client.

A subtle but important point: communicating deficiencies does not automatically change your financial statement audit opinion. Your opinion is on the financial statements. However, the deficiency may lead to more audit work, and if misstatements are found and not corrected, that can affect the opinion.

“Show it in action” examples
Example 1: Significant deficiency found—how it’s communicated

During your audit, you learn that bank reconciliations are performed, but they are not reviewed by a supervisor, and unreconciled differences sometimes remain for months. You test cash and do not find a material misstatement.

  • You evaluate the deficiency: lack of review increases the risk errors or fraud could go undetected.
  • You consider magnitude/likelihood: cash is significant, and delays are recurring.
  • You determine it rises to a significant deficiency.

Communication: You provide a written communication describing the significant deficiency to management and TCWG. You clarify that the audit wasn’t designed to identify all control deficiencies.

Key learning: No material misstatement was found, but communication is still required because the control issue is important for governance oversight.

Example 2: Material weakness due to poor segregation of duties

In a small entity, the controller can create vendors in the system, approve invoices, and initiate payments. There is no independent review, and the owner rarely reviews disbursements.

  • Magnitude: disbursements affect expenses and cash; potential misstatement could be material.
  • Likelihood: the opportunity for fraud is significant; there are no compensating controls.

This pattern often indicates a material weakness, especially if the amounts are large and oversight is weak.

Communication:

  • Under AU-C 265: written communication to management and TCWG no later than 60 days after report release date.
  • Under PCAOB: written communication to the audit committee before issuing the auditor’s report.
What commonly goes wrong (and how to avoid it)
  • Thinking “deficiency” requires a known misstatement. A deficiency is about what could go wrong, not only what did go wrong.
  • Misclassifying severity. Students often label everything “material weakness.” Use the two-axis test: magnitude + likelihood.
  • Forgetting the writing requirement. Significant deficiencies and material weaknesses require written communication.
  • Missing the timing rule. AU-C allows up to 60 days after report release; PCAOB requires before report issuance.
  • Crossing the independence line. You can communicate and recommend, but you cannot take over management’s responsibility by designing/implementing controls.
Exam Focus
  • Typical question patterns:
    • Classification questions: given a scenario, identify whether it’s a control deficiency, significant deficiency, or material weakness.
    • Communication logistics: who must be informed (management, TCWG/audit committee), whether it must be written, and by when.
    • Standards comparison items: differences in timing between AICPA (AU-C 265) and PCAOB (AS 1305).
  • Common mistakes:
    • Selecting an answer that communicates only to management when TCWG must also be informed.
    • Missing that AU-C uses the report release date (not the report date) for the 60-day deadline.
    • Assuming auditors must find all deficiencies—audits are not designed for exhaustive control deficiency detection.