Deliverable Quality Control

A checking routine for consulting work before the client sees it: numbers tied to sources, consistent pages, fact checks, confidentiality sweeps, a final read-through and a recorded sign-off.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Then open the Marketplace in the app, search for Deliverable Quality Control, and click Install. It goes into your own files, and works offline from then on.

What it installs.

1

Pillar

1

Area

50

Projects

200

Starter tasks

📋 Management Consulting

Deliverable Quality Control

Checking work before a client sees it: numbers tied to sources, consistent pages, fact checks, a final read-through and a sign-off routine.

  1. Error baseline from your last three deliverables
  2. Personal pre-send checklist for client documents
  3. Source tagging convention for every number
  4. Version naming and final folder rules
  5. Formatting standards crib sheet
  6. Checking roles agreed at engagement start
  7. Error severity scale for client work
  8. Proofreading set-up for screens and print
  9. Confidentiality sweep before files leave the firm
  10. Daily tie-out of pages you changed
  11. Weekly consistency sweep of the working deck
  12. Pre-send gate for anything leaving the team
  13. Error log and monthly root cause review
  14. Fact-check tracker for claims and quotes
  15. Cross-workstream numbers reconciliation
  16. Weekly peer review swap
  17. Footnote and source line upkeep
  18. Sign-off record for each client release
  19. Template and master slide hygiene check
  20. Tying slide numbers back to the model
  21. Totals, rounding and percentages that add up
  22. Proofreading in separate passes
  23. Chart integrity checks
  24. Consistent terms, units and currencies
  25. Pasted and linked model outputs check
  26. Reviewing a colleague's pages with useful comments
  27. Checking external data and public sources
  28. Choosing a deck checking tool or add-in
  29. Live links versus pasted values decision
  30. Change freeze rule before big readouts
  31. Team quality checklist by deliverable type
  32. Independent check rule for high-stakes numbers
  33. Working well with the document production team
  34. Print, PDF and accessibility readiness
  35. Quality pass on a steering committee pre-read
  36. Full quality review of the final report
  37. Handling a round of client redlines
  38. Translated deliverable quality check
  39. Review after an error reached the client
  40. First month as the deck checker on a team
  41. Quality control across time zones
  42. Reviewing a team's work as a manager
  43. Checking your own work without a second pair of eyes
  44. Late-night and weekend checks under fatigue
  45. Bringing new joiners into the team's quality routine
  46. Master number book for a large deliverable
  47. Quality metrics for a practice or office
  48. Audit trail for publicly released reports
  49. Verifying AI-drafted text and numbers
  50. Teaching a quality control session to the office

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

Error baseline from your last three deliverables

This is a team plan, best installed into a shared workspace so everyone with a role in it can see and own their tasks. Before building a checking routine, find out which mistakes you actually make.

First tasks

  • Pick three recent deliverables that went through several rounds of comments
  • List every correction made to them, with client details stripped out
  • Sort each correction into an error type and count the types
  • Note who caught each error and at which stage

Personal pre-send checklist for client documents

Relying on memory at eleven at night is how a draft goes out with tracked changes still visible. A one-page checklist, built from your own error baseline and kept short enough to run in fifteen minutes, turns the final check into a routine instead of a hope.

First tasks

  • Draft the checklist from your three most common error types
  • Add the file checks: comments, tracked changes, hidden slides and file name
  • Run the checklist on the next document you send and time it
  • Review the checklist against the errors you made last quarter @recurring(quarterly)

Source tagging convention for every number

When a partner asks where a figure came from, the answer should take seconds, not an hour of searching through models and emails. A simple convention, where every number on a page carries a source note or a cell reference in the speaker notes, makes tie-outs fast and protects you when a client challenges a figure.

First tasks

  • Write a one-paragraph tagging rule for source lines and speaker notes
  • Agree short codes for the model, data files and interview notes
  • Tag every number on one section of the current deck
  • Ask a colleague to trace three numbers using only the tags

Make it yours.

Install Deliverable Quality Control, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.