Deployment Audit
Every area of your estate, measured from your own repository by the read-only collector your administrator runs, then judged against the full rule library and the benchmark set. The result is a comprehensive scored, prioritized report across all six pillars — delivered inside two weeks, priced below, no discovery phase.
Teams arrive at this engagement under different names — a Tableau deployment review, a Tableau environment audit, an annual Tableau health check. Whatever yours is called internally, this is that engagement, done with the measured-not-asked method in How to Audit a Tableau Environment. The audit covers six pillars. Every finding lands in exactly one.
01
How fast views load, and how often scheduled work completes. We measure TP95 view load times, not averages. We split query time from render time, so the fix lands with the right team. We measure extract refresh outcomes, failure concentration — the few workbooks behind most failures — and recurring error patterns.
02
What the platform runs on, and whether it is enough. Node topology and process layout. Cores and memory per node. Backgrounder sizing against Tableau's documented guidance. Peak concurrency against provisioned capacity. Disk runway at the observed growth rate.
03
What your capacity is actually spent on. Stale and never-opened content. Refresh capacity consumed by content nobody views. Duplicate extracts of the same data. Extracts larger than their use justifies.
04
How data moves, and when. The live-versus-extract mix. Full versus incremental refreshes. Schedule density and anchoring — how much work shares the same start times. Refresh windows measured against your business hours.
05
How the content itself is built. A structural inspection of workbooks you choose to supply: custom SQL, calculated fields and LODs, filter design, embedded versus published data sources, image weight, device layouts.
06
Who can do what — and what happens when something goes wrong. Permission complexity. Content with no identifiable owner. Dormant licenses. Access token hygiene. Authentication posture. Recovery readiness.
Every finding is labeled by how we know it. Measured: read from your repository, platform configuration, or logs. Inspected: found in workbooks you supply. Attested: taken from configuration or your statement — SSO enforcement, DR intent. The label tells you exactly how much weight each finding carries.
Included in every audit
Everything the repository records about your workload, plus your platform's topology, version, licensing, key settings and per-node hardware. Collected by scripts your administrator runs and previews — nothing leaves your network unseen.
Optional, findings-triggered
Log-level analysis for the questions measurement raises but cannot answer — proposed only when your numbers justify it, never sold by default.
Optional
A structural inspection of workbooks you choose: the design decisions behind your slowest and most important content, with specific fixes.
The full method, including what each script reads, is public.
An executive summary written for the person who signs, not only the person who runs the platform. Then the evidence behind it. The Health Score is always shown with its data coverage. If the available history is too thin to rate honestly, the rating is Insufficient Data — not a guess.
Inside the report
200+ measurements · six pillars · every finding paired with a recommendation
Deployment Audit · report
74/100Watchlistdata coverage 86%
Pillar · Finding · Evidence · Recommendation · Effort · Impact · Priority · Owner · ETA
6 workbooks cause most refresh failures
45 of 1,166 jobs failed · 90d → Fix credentials, re-point sources · BI platform team · wk 1
4 AM window overloaded
TP95 queue wait 23 min · 90d → Move a third of the 6 AM batch · Tableau admin · wk 2
55 items unopened in 90+ days
12.7 GB · snapshot → Archive after owner review · Content owners · wk 4
31 workbooks have no identifiable owner
content inventory · snapshot → Assign owners before archive review · BI governance · wk 3
Illustrative report fragment — not from any single customer environment.
The elapsed time is under two weeks; the demand on your team is measured in hours.
A short scoping call, then your administrator runs the read-only collector — about 20 minutes — and previews the summary file before sending it.
Your aggregates run against the full rule library and the benchmark set. We come back with questions only if the numbers raise them.
Report, deck, workbook, and action list, walked through with your team — every finding citing the measurement that produced it.
Deployment Audit
from $6,000
Fixed scope, fixed price, agreed before we start.
Larger estates
from $12,000
Which tier yours is, we'll tell you in the scoping call — before you commit to anything.
Weighing this against what your support plan may already include? See what an annual technical health review is and how a deployment review compares with an independent audit.
Yes. If you have been searching for a Tableau deployment review, a Tableau environment audit, an annual Tableau health check, or a health check review, this is that engagement. The name differs because the method does: most reviews score a questionnaire, while this audit measures your repository — job outcomes, queue waits, load times, storage, concurrency — through a read-only script your own administrator runs. Every finding cites the measurement behind it, which is the part an interview-based review cannot give you.
We fix findings too: schedule redesign, process reconfiguration, stale-content cleanup, capacity changes. But remediation is sold only after the audit, at a day rate — never bundled, never assumed.
That ordering is deliberate. Because the audit is priced on its own, its findings never have to justify a bigger engagement. The action list is written so your own team can execute it without us; if you want help, the day rate is there.
Next step
A short call: platform, scale, symptoms, and which tier fits. Or start smaller with the free Health Snapshot.