Communication templates for Broadcom audits.

Communication during a Broadcom audit is one of the underappreciated dimensions of audit defence. The headline activity — entitlement reconstruction, methodology challenge, settlement negotiation — gets the attention. But the communication discipline that surrounds those activities, both inside the customer organisation and across the audit interface, frequently determines whether the substantive defence work produces its intended outcome. Sloppy communication leaks information, weakens positions, and creates internal disalignment that the audit team exploits.

This article gives a working communication template for organisations facing or under Broadcom audit. The templates are not legal documents; they are operational artifacts that have held up across the engagements we have observed. They are designed for adaptation to the customer's specific context, not for direct verbatim use.

Why communication discipline matters

Broadcom audit teams build their case partly from formal customer disclosures and partly from informal communication signals. An engineer's offhand comment on a discovery call, a procurement manager's email about a planned deployment, a CIO's quote in a trade publication — all of these become inputs to the audit team's framing. Customers who manage communication tightly preserve more of the defensible ground; customers who do not, lose ground continually through the audit lifecycle.

The communication discipline has three dimensions: internal communication (how the audit response team talks to itself), upward communication (how the CIO talks to the C-suite and board), and external communication (how the customer talks to the audit team, the broader Broadcom relationship, and any external stakeholders).

Internal communication

Internal communication during an audit needs to be tight enough to produce coordinated response and broad enough to capture the technical and commercial detail the response requires. The template that works is a small core audit response team with disciplined communication norms, surrounded by a broader extended team whose communication into the audit response is filtered through the core.

The audit response team kickoff

Within 48 hours of the audit notice, the audit response team should meet for a structured kickoff. The kickoff should establish the team membership, the single point of contact with the audit team, the communication norms, and the initial response priorities. A working agenda includes audit notice review, contractual basis confirmation, team role assignment, communication protocol agreement, immediate action priorities, and meeting cadence.

Standing meetings

The audit response team should meet at a defined cadence — typically weekly for the first month, then bi-weekly or monthly depending on audit pace. The standing meeting is where the substantive work gets coordinated, decisions get made, and the team alignment gets maintained.

The meeting agenda should include audit status update, work-stream progress (entitlement reconstruction, methodology analysis, contractual review), upcoming decisions requiring team input, external communication requirements, and risk and escalation flags. The meeting should produce a structured status update that informs the broader internal communication.

Single point of contact discipline

The most important internal communication discipline is that all communication with the audit team flows through a single designated point of contact. The point of contact role is typically held by the procurement or vendor management lead, supported by the legal and CIO functions.

The communication template for this discipline is a clear internal directive to all staff: any audit-team contact must be routed through the designated point of contact. The directive should specifically prohibit independent communication with the audit team, including responses to LinkedIn outreach, attendance at audit-team-organised webinars, and one-off questions in support tickets.

Upward communication

The CIO needs to keep the executive team and the board appropriately informed about the audit without over-amplifying concern or under-disclosing material risk. The template that works is structured, periodic communication with explicit escalation triggers.

Executive briefing template

An executive briefing on the audit status, delivered at appropriate cadence (typically monthly during active audit), should cover audit phase and timeline, current exposure range, defence progress against the exposure, key decisions ahead, and resource and budget requirements. The briefing should be concise — typically a single page or short slide deck — and should not require executive action between briefings unless explicitly flagged.

Board communication

The board communication template was covered in detail in our board presentation article. The key communication discipline at the board level is to position the audit as a managed commercial defence engagement, not as a compliance failure being remediated. The framing affects everything that follows.

Escalation triggers

The communication template should specify escalation triggers — events that produce immediate communication to the executive team or board regardless of the normal cadence. Typical triggers include audit-team scope expansion beyond contractual basis, exposure exceeding pre-defined threshold, audit settlement structure decisions, and any external visibility (press, regulatory, customer concerns).

External communication with the audit team

Communication with the audit team itself is where the most direct customer position-loss happens. The template that works is formal, written, scope-disciplined, and routed through the single point of contact.

Initial response to audit notice

The initial response to the audit notice should acknowledge receipt, confirm the contractual basis of the audit, and propose an initial kickoff meeting between the parties. The response should not engage substantively with the audit-team's initial requests; that engagement should follow the kickoff meeting once the contractual basis is confirmed and the response process is agreed.

A template structure for the initial response: acknowledgement of audit notice, reference to the underlying contract clause supporting the audit, request for the audit-team's lead and supporting staff identification, proposal of an initial kickoff meeting at a specified time, and contact information for the customer's designated point of contact. The response should be brief, formal, and unambiguous.

Data request responses

Data request responses are where the customer position is most frequently weakened by over-disclosure. The template discipline is to respond precisely to what is asked, to scope the response to what is contractually required, and to flag any requests that exceed the contractual scope.

A working template for a data request response includes a clear scope statement (what data is being provided and the contractual basis for providing it), the data itself in the format requested, any scope objections (requests that exceed the contractual audit scope and the customer's position on them), and confirmation of the customer's reservation of rights for any items not addressed in the current response. The response should not include voluntary disclosure beyond what is requested.

Methodology challenges

When challenging the audit-team's methodology, the communication template should be precise, evidence-based, and contractually grounded. The challenge should identify the specific methodology element being disputed, the contractual or industry-standard basis for the dispute, and the alternative methodology the customer is proposing. The challenge should not engage in broader rhetoric about the audit posture; it should be a focused, defensible challenge to a specific methodological choice.

Settlement communication

Settlement communication is the most consequential external communication and warrants the highest level of communication discipline. The template should be structured around a settlement proposal that includes the proposed settlement amount, the structure (cash, subscription credit, term commitment), the closing agreement language, and the future-audit protections.

The settlement communication should be authorised by the CIO and reviewed by legal counsel before transmission. Sloppy settlement communication produces settlement outcomes that are materially worse than the underlying defensive position would have supported.

External communication beyond the audit team

Customers under Broadcom audit also face communication decisions about external stakeholders beyond the audit interface. The template that works is conservative disclosure within the constraints of any applicable disclosure obligations.

Broader Broadcom relationship

The customer's relationship with Broadcom outside the audit — account team, customer success, sales — continues during the audit and needs to be managed. The communication discipline is that the audit-related communication stays inside the audit team channel and does not bleed into the broader relationship. Account team conversations about renewals, roadmap, or product engagement should not reference the audit status.

Internal stakeholders

Beyond the audit response team and the executive team, broader internal stakeholders (business units, application owners, operations teams) sometimes need to know enough about the audit to support the response. The template discipline is need-to-know communication: provide what the stakeholder needs to participate effectively, no more.

External stakeholders

For most enterprises, Broadcom audit communication with external stakeholders (customers, regulators, the press) is exception-only and tightly controlled. The default position is no external communication about the audit. Exceptions arise where regulatory disclosure obligations apply (rare), where reputational consequences require proactive communication (rarer), or where the audit has become external for other reasons (rare).

The settlement closing communication

When the audit closes, the closing communication establishes the durable record of the engagement. The template should produce a closing agreement that documents the settlement terms, the scope closure, the future-audit protections, and the confidentiality provisions. The closing agreement language affects the customer's position in subsequent audits and renewals; sloppy closing agreements produce ongoing exposure that more careful closing language would have prevented.

The template summary

The communication templates discussed in this article — internal kickoff agenda, standing meeting structure, single point of contact discipline, executive briefing format, escalation triggers, initial audit response, data request response, methodology challenge, settlement communication, closing agreement — together constitute the communication framework that supports effective audit defence.

None of the individual templates is particularly complex. The discipline of using them consistently across the audit lifecycle is what produces the cumulative benefit. Customers who improvise communication during audits routinely produce worse outcomes than customers who follow a structured framework, even when the underlying defensive case is equivalent.

The bottom line

Communication is the connective tissue of audit defence. The substantive work of entitlement reconstruction, methodology challenge, and settlement negotiation gets the attention; the communication discipline that surrounds that work determines whether the substantive defence produces its intended outcome.

The templates in this article are starting points, not finished documents. Each customer needs to adapt them to specific contractual basis, specific stakeholder structure, and specific audit characteristics. But the framework — internal discipline, structured upward communication, scope-disciplined external communication — is portable across the customer engagements we have observed, and the benefit of following it is consistent across audit outcomes.