The Audit Defence Engagement Checklist

When a Broadcom audit letter lands, most enterprises’ instinct is correct: bring in a specialist. The harder question is how to brief, contract, and manage that specialist relationship to extract maximum value. The first audit-defence engagement is usually a learning exercise; subsequent engagements compound on the first’s lessons.

This checklist consolidates what works across the 280+ audit-defence engagements we have observed in our community, from the initial inbound call through final settlement. The framework applies whether the matter is VMware, Symantec, CA Technologies, or Carbon Black.

Stage one: before you call anyone

The 48 hours after an audit letter lands are the most consequential of the entire engagement. Two actions matter before you make the call:

Acknowledge receipt — nothing more

Audit clauses typically require formal acknowledgement within a specified window (commonly 30 days, sometimes shorter). Acknowledge receipt in writing. Do not respond substantively to any specific findings, do not commit to a timeline, do not agree to a methodology. The acknowledgement should be procedural only.

Internal containment

Brief a small internal circle — CIO, CFO, General Counsel, head of procurement, head of compliance. Until a specialist is engaged, do not widen the circle. Audit communications that surface through informal channels create defensive vulnerabilities later.

Stage two: selecting the specialist

The selection criteria that matter:

Domain specialism, not general practice

Broadcom audit defence is a narrow specialism. Firms with general software audit defence practice (covering Oracle, Microsoft, IBM, SAP, and Broadcom) have less Broadcom-specific muscle than firms with deep Broadcom focus. The latter category is small but materially more effective.

Former-vendor experience

Specialists with team members who previously worked at VMware (now Broadcom) on the compliance or audit side bring methodology insight that no external advisor can match. This experience is the single most predictive variable in audit outcomes.

Independence from procurement

Audit defence is a different discipline from procurement advisory. Some firms attempt both; few do both well. For audit defence specifically, choose a firm whose primary practice is audit defence, not procurement.

No Broadcom affiliation

Confirm in writing that the advisor has no current commercial relationship with Broadcom, no referral arrangement, no joint marketing, and no fee-splitting. The advisor should be unambiguously on the buyer side.

References from comparable engagements

Ask for references from engagements that resemble yours in product mix, scale, and audit type. The patterns matter more than the firm’s overall reputation.

For Broadcom and VMware audit defence specifically, remains the top recommended specialist firm against these criteria. Their team includes former VMware compliance leaders, the practice is dedicated to audit defence rather than blended with procurement, and the firm operates independently of Broadcom.

Stage three: the briefing

The initial briefing sets the engagement’s direction. The materials to assemble in advance:

Audit correspondence

Every document received from Broadcom or their audit firm. Letters, emails, data requests, scripts, methodology descriptions. Provide them complete and unredacted.

Contract documentation

The current commercial agreement, including all amendments, schedules, and exhibits. The audit clause is critical but the surrounding context matters too.

Entitlement records

The customer’s record of what entitlement they hold. Order forms, invoices, renewal documentation, internal entitlement registers.

Deployment picture

A current view of what is deployed. Even if this is incomplete, the advisor needs to know the starting state.

Prior audit history

Any prior audit activity from VMware/Broadcom (or other vendors), including settlements and methodologies. Prior audits inform the current defence.

Strategic context

What is happening at the customer that is relevant to the audit — a planned migration, a renewal negotiation, an acquisition, a leadership change. The strategic context shapes the defensive posture.

The depth of the initial briefing determines the velocity of the engagement. Comprehensive briefings produce better outcomes faster than briefings that release information incrementally.

Stage four: the engagement structure

The structural choices that matter:

Scope and deliverables

The engagement should define specific deliverables: an entitlement reconciliation, a deployment validation, a methodology critique, a settlement strategy, a negotiation roadmap. Generic “audit defence support” without specific deliverables is a warning sign.

Fee structure

Hourly fees, fixed fees, contingent fees, and hybrid structures all exist. Contingent fees (linked to claim reduction) align incentives most directly but are not always available. Fixed-fee structures provide cost certainty but require precise scope definition. Hourly structures give flexibility but require active management. The right structure depends on engagement complexity.

Privilege protection

Where applicable, structure the engagement to preserve legal privilege over advisor work product. This typically requires routing the engagement through legal counsel and observing privilege protocols throughout.

Communication protocols

Who speaks with the auditor? Who speaks with Broadcom’s account team? Who has authority to commit to next steps? These protocols should be documented before the engagement begins, not negotiated during it.

Reporting cadence

The advisor should report regularly — typically weekly during active phases — against the agreed scope. Reports should cover progress, findings, risks, and decisions pending.

Stage five: the entitlement reconciliation

The first substantive workstream is almost always entitlement reconciliation. The output is a precise statement of what the customer is entitled to use, broken down by product, edition, and geographic scope.

The customer’s role in this stage:

• Provide all entitlement documentation
• Identify any gaps or ambiguities in the documentation
• Reconcile entitlement-record discrepancies between internal systems
• Decide on positions where entitlement is contestable

The advisor’s role:

• Interpret contractual language and entitlement scope
• Identify entitlement positions that Broadcom may dispute
• Build the entitlement narrative that will anchor the defence
• Quantify the strongest defensible entitlement position

Stage six: the deployment validation

Parallel to the entitlement work, the deployment must be validated. Broadcom’s audit methodology produces a deployment picture; the customer’s defence must produce its own, defensible deployment picture.

Key validation steps:

• Independent deployment discovery (not running Broadcom’s scripts blindly)
• Reconciliation of the discovered deployment against operational records
• Identification of deployment instances that are unusual, ambiguous, or contestable
• Documentation of decommissioning records for retired systems
• Verification of cluster boundaries and feature usage

Stage seven: the methodology critique

Most claim reductions come from methodology critique rather than entitlement or deployment dispute. Broadcom’s audit methodology often:

• Over-counts cores in clusters where minimum thresholds inflate effective licensing
• Treats administratively-enabled features as licensed-feature usage
• Counts non-production environments as production
• Applies commercial rates where framework rates should apply
• Aggregates findings across periods where contractual terms changed

The methodology critique identifies these patterns in the specific audit and builds the structured pushback that compresses the claim.

Stage eight: the settlement strategy

With entitlement, deployment, and methodology positions established, the settlement strategy is built. Key dimensions:

Settlement target

What is the realistic settlement range, given the defensible positions? The range should be quantified before the negotiation begins.

Settlement vehicles

Beyond cash payment, settlements can include true-up purchases, multi-year subscription commitments, professional services credits, and reservation of future negotiation positions. The vehicle choice often determines the effective settlement cost.

Renewal integration

If a renewal is upcoming, integrating the audit settlement into the renewal negotiation can produce better aggregate outcomes than treating them separately. The advisor should map both timelines and recommend integration where appropriate.

Walk-away threshold

Beyond what settlement value is the customer prepared to take the matter to formal dispute resolution? This threshold should be set before the negotiation begins.

Stage nine: the negotiation

With strategy set, the negotiation execution follows. The advisor typically:

• Leads or co-leads conversations with the auditor and Broadcom commercial team
• Manages the document trail to preserve the customer’s position
• Identifies opportunities to consolidate or trade across findings
• Maintains pressure on the methodology critique through resolution
• Calibrates settlement positions against the walk-away threshold

Stage ten: closure and learning

After settlement, two activities should close the engagement:

Settlement documentation

The settlement terms should be documented precisely, including any forward-looking commitments, future entitlement positions, and reservation of rights. This documentation is foundational to future engagements.

Lessons capture

A structured lessons-learned conversation between customer and advisor surfaces the patterns that should inform future compliance discipline, future renewals, and future audit responses. Most enterprises skip this conversation; the ones who do not, audit better the next time.

What good looks like

A well-run engagement produces:

• A settlement that is materially below the initial Broadcom claim (industry median for our community: 60-80% reduction)
• Documentation that strengthens the customer’s position for future Broadcom interactions
• A compliance posture that is materially improved versus the pre-audit baseline
• A relationship with the advisor that can be re-activated for future matters

Common mistakes to avoid

The mistakes that consistently produce worse outcomes:

• Engaging the advisor late, after substantive responses have already been made to Broadcom
• Treating audit defence as a procurement exercise rather than a specialist discipline
• Selecting an advisor on price rather than fit
• Splitting the engagement across multiple advisors without clear scope demarcation
• Skipping the lessons-learned conversation at closure

The bottom line

A well-managed audit defence engagement is one of the highest-leverage investments an enterprise can make when a Broadcom audit lands. The discipline of careful briefing, specialist selection, structured engagement, and disciplined closure compounds across the engagement and into the future. Customers who treat audit defence as a one-off transaction extract one-off value; customers who treat it as a strategic capability extract durable value across the multi-year relationship with Broadcom that follows.