Quality Assurance (QA)

Quality assurance (QA) in professional services is the systematic process of applying review gates, testing protocols, and approval steps to deliverables before they are submitted to a client, to confirm the work meets contracted standards.

QA is embedded in the delivery workflow rather than applied at the end. It is preventive by design, contrasting with quality control, which is inspective.

QA vs quality control

These terms are often used interchangeably, but they are distinct:

• Quality assurance (QA): process-oriented. Builds steps into the delivery workflow to prevent defects from being introduced. Examples: template standards, mandatory peer review before draft submission, automated testing in a CI pipeline.
• Quality control (QC): inspection-oriented. Reviews finished or near-finished work to catch defects before client delivery. Examples: senior review before a final report goes out, user acceptance testing before a system goes live.

Firms with mature delivery operations use both. QA reduces the volume of defects that QC must catch; QC provides a final check that the QA process worked as intended.

Common QA mechanisms in services delivery

The specific mechanisms depend on the nature of the deliverable, but the following appear across most professional services contexts:

• Peer review: a second practitioner reviews a deliverable before it leaves the team. Even a 30-minute review by a colleague catches a large proportion of presentation, logic, and completeness errors.
• Senior sign-off: a principal or partner reviews client-facing work before submission. This gate is particularly important for deliverables that carry commercial or reputational weight.
• Checklists: structured confirmation that required elements are present, covering required sections, formatting standards, and data accuracy. Checklists are most effective when they are specific to the deliverable type.
• Test plans: for technology deliverables, a defined set of functional and regression tests that must pass before the deliverable is submitted.
• Client review gates: scheduled approval steps where the client formally confirms that work meets their expectations before the team advances to the next phase. These are typically written into the statement of work as milestones.

The cost of poor QA

Rework is one of the most expensive costs in a services business because it is unplanned and typically unrecoverable on fixed-fee engagements. A deliverable requiring two rounds of significant rework may consume 30 to 50 percent more hours than the original estimate. On a 30 percent margin project, that rework can eliminate the margin entirely.

Poor QA compounds over an engagement. A defective deliverable that reaches a client damages the relationship, increases scope disputes, and can result in write-offs or disputed invoices downstream. Repeated QA failures across multiple engagements show clearly in a firm’s realization rate over time, because unplanned rework hours are worked but cannot be billed.

QA and delivery documentation

Effective QA depends on clear acceptance criteria established at the start of the engagement. Without an agreed definition of what “done” looks like, reviewers have no objective standard against which to assess the work. Project plans that include explicit QA checkpoints help ensure review steps are not skipped under schedule pressure.