The Agency QA Playbook: Stop Shipping Work That Comes Back

Published on March 22, 2026 · 10 min read

Every agency has a dirty secret hidden in their project management tool: revision rounds. Look at any completed project and count the back-and-forth. Two rounds? Acceptable. Four rounds? That’s a problem. Six or more? You’re doing the project twice — and getting paid once.

Rework is the silent margin killer. It doesn’t show up on your P&L as a line item. It shows up as projects that took 40 hours but were scoped for 25. As team members who are always busy but never ahead. As a founder who reviews everything personally because “it’s faster than fixing it later.”

The solution isn’t better talent (though that helps). It’s a QA process that catches problems before they reach the client. Build quality into the system, not the people, and you’ll ship better work in less time. QA is a core pillar of any delivery operations system.

Why Rework Kills Margins (The Math)

Let’s make this concrete. Say you’re a design agency billing $150/hour, and a typical landing page project is scoped at 20 hours ($3,000).

Now multiply that across every project in a month. If you’re running 10 projects and averaging 3+ revision rounds, you’re leaking $8,000-$12,000 per month in unbilled rework. That’s $100K+ per year.

And it’s not just money. Rework destroys morale. Your team feels like nothing they do is ever good enough. They start waiting for client feedback before putting in real effort because “they’ll change it anyway.” Quality spirals down, revisions go up, and the cycle feeds itself.

Build QA Into Process, Not People

Most agencies handle QA one of two ways: either the founder reviews everything (creating a bottleneck), or nobody reviews anything (creating quality problems). Both are broken.

The fix is systematic QA — a defined process with clear checkpoints, standards, and accountability that doesn’t depend on any single person. Here’s the framework:

The Three-Gate QA System

Every deliverable passes through three gates before it reaches the client:

  1. Self-review (Gate 1). The creator reviews their own work against a checklist before submitting it. This catches the obvious stuff — typos, broken links, brand inconsistencies — that wastes everyone’s time when it gets flagged later.
  2. Peer review (Gate 2). A team member who didn’t create the work reviews it with fresh eyes. They check for quality, alignment with the brief, and anything the creator might have missed because they’re too close to the work.
  3. Final review (Gate 3). The account lead or project manager reviews the work against the original brief and client expectations. This isn’t about design opinions — it’s about strategic alignment. Does this deliver what the client asked for?

Three gates sounds heavy. In practice, Gate 1 takes 5-10 minutes (it’s a checklist). Gate 2 takes 10-20 minutes (a focused review). Gate 3 takes 5-10 minutes (a strategic check). Total added time: 30-40 minutes per deliverable. Compare that to the hours you lose in revision rounds when unchecked work ships to a client.

The Pre-Delivery Checklist

The self-review checklist is the foundation of your QA system. It should be specific to each deliverable type. Here’s what a good one looks like:

Web design deliverable checklist

Copywriting deliverable checklist

Create one checklist per deliverable type your agency produces. Keep them in your SOP library where everyone can access them. Update them when you discover new common mistakes.

The Peer Review System

Peer review is where QA gets real. The creator is too close to their work to see its flaws. A fresh pair of eyes catches what familiarity misses.

How to structure peer reviews

  1. Assign reviewers in advance. Don’t rely on “can someone look at this?” Assign a specific reviewer when the project kicks off. Rotate reviewers so the same people don’t always pair together.
  2. Give reviewers the brief. A reviewer can’t assess quality without knowing the objective. Share the original brief, client feedback, and any relevant context before the review.
  3. Time-box it. A peer review should take 15-20 minutes, not an hour. The reviewer is checking for quality and alignment, not redesigning the work. If the review takes longer than 20 minutes, the work probably isn’t ready for review.
  4. Use structured feedback. Don’t just say “this doesn’t feel right.” Require reviewers to categorize feedback:

Making peer review a habit

Peer review fails when it’s optional. Make it a non-negotiable step in your delivery workflow. Nothing moves to client presentation without a peer review. No exceptions.

Yes, this creates a dependency. Yes, it requires coordination. But the alternative — shipping unchecked work and dealing with the revision cascade — costs far more time and money.

Revision Cap Policy

A revision cap isn’t about being rigid with clients — it’s about setting clear expectations and protecting your margins. Here’s how to implement one without damaging client relationships.

How to set revision caps

Include revision caps in your contracts and proposals. Be specific:

“This project includes two rounds of revisions per deliverable. Each revision round includes a consolidated set of feedback submitted within 3 business days of delivery. Additional revision rounds are billed at $X per round.” Key elements:

Define what a “round” is. One consolidated set of feedback, not a drip of individual comments over two weeks.

How to communicate revision caps

Frame revision caps as a quality measure, not a limitation:

“We include two revision rounds because our QA process ensures the initial delivery is very close to final. Most of our clients use one round or less. If we find we need more extensive changes, we’ll discuss options with you before proceeding.”

This positions your agency as confident in your quality (because you have a QA process) while being transparent about boundaries.

Tracking revisions

Track revision counts per project, per client, and per team member. This data tells you:

Common QA Mistakes to Avoid

Mistake 1: Founder as sole quality gate

If you’re the only person who can approve work, your QA system is really just you. And you’re the bottleneck. Remove yourself from delivery by training your team on your quality standards and trusting the system.

Mistake 2: Reviewing everything at the same depth

A $2,000 social media package and a $25,000 website redesign don’t need the same level of review. Scale your QA intensity to the project’s value and risk level. High-value, high-visibility work gets all three gates. Lower-risk work might skip Gate 3.

Mistake 3: No checklist, just vibes

“Does this look good?” is not QA. Subjective quality assessment is important, but it should layer on top of an objective checklist. Check the measurable things first (brand compliance, spelling, functionality), then evaluate the subjective things (does the design feel right, is the copy compelling).

Mistake 4: Treating all feedback as equal

Client feedback that says “change the blue to a slightly different blue” is not the same as “this doesn’t address our core message.” Teach your team to categorize feedback by impact and address the strategic issues first.

Measuring QA Effectiveness

You can’t improve what you don’t measure. Track these metrics monthly:

Review these metrics in your monthly operations review. If revision rounds are increasing, your QA system has a gap. If first-pass approval rates are climbing, your process is working.

Start Here

You don’t need to implement everything at once. Start with these three moves this week:

  1. Create one pre-delivery checklist for your most common deliverable type. Keep it under 15 items.
  2. Mandate peer review on the next three projects. Assign specific reviewers and give them 20 minutes.
  3. Add revision caps to your next proposal. Two rounds, consolidated feedback, 3-day window.

These three changes will reduce your revision rounds within 30 days. From there, build out the full three-gate system and start tracking the metrics. Not sure where your rework is actually coming from? An Ops Audit will map your revision patterns and show you the root causes.

Quality isn’t about working with perfect people. It’s about building a system that produces consistent results regardless of who’s doing the work. That’s what separates agencies that scale from agencies that stall.

Ready to fix this?

Rework is bleeding your margins and you can feel it. Our Ops Audit measures your actual revision costs and builds the QA system that stops the leak.

Start with an Ops Audit → Learn about Delivery Operations →