How Account Teams Qualify Whether a Client Request Is a Revision or a New Project

The client email arrives. "Hey, we were thinking about adding a version for the European market. Could we also update the main spot to include the new product? Oh, and the social cuts need to be in vertical format now."

Is this a revision? Or three new projects?

If your account team does not have a framework for answering that question before they respond, they are going to promise something they cannot price. And by the time it goes to the creative team, everyone assumes someone else figured out the scope.

Qualifying whether a client request is a revision or a new project is one of the most valuable skills an account team can have. Here is the framework.

Start with what was already agreed

Every qualification starts in the same place: the original SOW and the current project approval status.

What was delivered and approved? If the main spot is approved and locked, any change to it is not a revision within the original scope. It is a new project, or at minimum a change order. If the spot is still in revision rounds, adding a new deliverable to the round is scope expansion, not a revision.

Pull up the current project status before you respond to the client. If you are using PlayPause, you can see exactly which versions are approved, which are pending feedback, and how many rounds have been used. That status tells you where you stand before you open the negotiation.

The three-question qualifying framework

When a client request comes in, run it through three questions before responding.

Question 1: Does it require new assets, new shoots, or new concepts?

If the answer is yes, it is a new project. A European market version that requires new voiceover recording, re-scored music, and legal-compliant text changes is a new deliverable. It might be a smaller project than the original, but it is not a revision. A new concept, even a spin-off from the existing one, is definitely a new project.

Question 2: Does it touch a deliverable that is already approved?

If the main spot is locked and the client wants to change it, that is a change order at minimum. The locking and approval record in PlayPause makes this unambiguous: if there is a timestamped approval on V3, any change to V3 is not covered by the original scope. How agencies prove a client approved a video in a dispute explains why that documentation matters.

Question 3: Does it expand the number of deliverables?

If the SOW specified a 60-second spot and three social cuts, and the client is now asking for vertical versions in addition, those vertical cuts are new deliverables. They are not revisions to the existing cuts. They are new assets that require their own editing, sizing, safe-zone adjustments, and delivery.

How to respond without killing momentum

The account team's job is not to say no. It is to say yes in a way that protects the agency's margin and the client's budget.

When a request comes in that you have qualified as a new project, respond warmly and quickly: "Great idea. The European version and the new vertical cuts would be scoped separately since they are new deliverables. I can have an estimate to you by end of week. In the meantime, let me confirm the status of the current approved assets so we are all aligned before we proceed."

This response does three things. It acknowledges the request positively. It names the commercial reality (these are new scope) without being defensive. And it keeps the project moving on the current deliverables while the new scope is being qualified.

For the current revision round, you continue. For the new request, you scope it. You do not mix them.

Why this protects the client relationship

A lot of account managers avoid this conversation because they think it will feel transactional. In practice, the opposite is true.

Clients who work with agencies that clearly qualify scope come to trust them. They know that if something is in scope, it will get done. They know that if something is new scope, they will hear about it before it becomes a billing surprise. That clarity is what long-term client relationships are built on.

Clients who get quiet agreement to "just add this" and then receive an unexplained invoice line item are the ones who feel blindsided and push back at billing. The qualification conversation prevents the invoice dispute.

For the broader context of how this fits into managing client expectations, managing client expectations when a 15-second ad requires four rounds covers the expectation-setting work that complements the qualification framework.

Training the account team to use the framework

One person knowing this framework is not enough. The whole account team needs to use it consistently, or a client will route around the account manager who asks questions and go straight to the CD or the editor.

Make the framework part of your onboarding. Practice qualifying sample requests in team meetings. Build a one-page reference card. And most importantly, use your approval workflow records as the anchor: the account team can always answer "is this in scope?" by looking at what is currently approved versus what was originally scoped.

For building the SOW language that makes scope qualification easy, what agencies should put in their SOW to define video approval and completion is the companion read.

PlayPause gives your account team a live view of approval status across all active projects. At $19 per month for the Agency plan, the visibility it provides pays for itself the first time an account manager catches a scope expansion before it becomes a free round. Start free at /pricing and give your account team the tools to say yes, correctly, every time.