Content approval process for agencies: outsourced articles

Your clients sit on drafts for weeks, and your own team re-reads every article line by line before it goes out. The content approval process an agency needs for long-form articles is different from the one for social posts: fewer items, more facts, more places for a review to drift into taste. This guide sets out the rules, the two review stages and the feedback structure that let you review by exception instead of re-editing every draft.

Why approval on outsourced articles stalls

Approval stalls when nobody has been told what they are approving.

Check these four causes first:

• No named approver. The draft goes to three people. Each assumes another will answer.
• No definition of "approved". One reader checks facts, another rewrites headlines to match their own style, and the draft never settles.
• Feedback scattered across email. Comments arrive in separate threads, some in a call, some in a chat message. Nobody holds the full list.
• The agency re-reads everything. If your team re-edits each draft before the client sees it, you add days and still have no shared standard for "good enough".

Each cause has a fix that costs nothing but a decision. The next sections make those decisions in order.

Set the rules before the first draft

Put these rules in the client agreement or onboarding document, not in a mid-project email. They are far easier to agree before anyone has a draft to defend.

Name one approver per client

One person has the final say. Others may comment, but they send comments to the approver, who consolidates them. Add a named backup for holidays and illness.

Example wording: "Approval comes from [name]. If [name] is unavailable, [backup] approves. Comments from anyone else are treated as input until the approver confirms them."

Define what approval covers

Approval covers four things: facts are correct, the draft matches the brief, the voice matches the agreed voice document, and nothing contradicts what the client knows about its own business. It does not cover personal preference on wording that meets the voice document.

Example wording: "Approving a draft means confirming it is accurate, on brief and in voice. Changes of taste after approval count as a new request."

Agree turnaround and what silence means

Pick a review window, such as five working days, and write down what happens when it passes. Two options work. Silence can mean a reminder and then an escalation to a second contact. Or it can mean deemed approval for low-risk topics. Deemed approval suits some clients and not others, particularly in regulated fields, so choose per client and put it in writing.

Two review stages: agency check, then client sign-off

A content approval process works best when the agency and the client do not look at the same things. Split the work by what each can actually judge.

Stage	Reviewer	Looks at	Does not look at
1. Agency check	Your account lead or editor	Brief fit, sources behind every number, voice, anything that conflicts with what you know about the client	Line-level style preferences
2. Client sign-off	The named approver	Facts about their own business, product claims, anything legal or sensitive, final yes or no	Rewriting for taste

Stage one is where you catch what only an agency knows: that the client dropped a service line last quarter, that a competitor is off-limits, that the brief's angle changed on a call. The client then receives a draft that has already passed your standard, and can spend their time on what only they know.

Keep stage one short. If it takes longer than the client's review window, you have rebuilt the bottleneck inside your own team. The next section shows how to shorten it without skipping checks.

Review against evidence, not against taste

Re-reading a whole article for "does this feel right" has no end point. Checking it against three fixed references does.

Check the draft against the brief

Open the brief and tick off its parts: the target query, the angle, the outline, the reader, the call to action, the do-not list. A miss here is a brief miss, and you can name it as one.

Open the cited sources for any number

Every figure should carry a citation you can open. Click through for each number and confirm the source says what the article says. If a number has no source, it should not be in the draft.

This is how we work on our side. Our editor is a separate session, not the writer. It checks facts and numbers against their sources and fails drafts with invented facts or uncited numbers [1]. Because that check happens before a draft reaches you, your own pass can concentrate on the sources that matter most to the client rather than on every sentence.

Use a score and a pass mark

Our editor fails any draft that scores below 80 out of 100 or fails any of the pass/fail checks. The rubric behind the score has 20 criteria: 16 are scored 0 to 5 and weighted, normalised to 100, and four are pass/fail checks [1]. A pass mark gives you a starting point: a draft above it has met a stated standard, and your review can focus on exceptions. You can read the criteria in our published rubric.

A score has limits, and we would rather say so. It does not know your client. It cannot tell that the founder dislikes a certain phrase, that a case study is under embargo, or that the brief's angle has quietly shifted. That knowledge is yours, and it is the reason stage one exists. The score lets you spend your attention there instead of on checking that sources exist.

Structure client feedback so round two is the last

Ask for one consolidated round from the named approver, sorted into three categories:

1. Factual error. Something is wrong. Fix it at once and note the correct source.
2. Brief miss. The draft does not do what the brief asked. The agency fixes it at no cost to the client's revision allowance.
3. Preference. The draft is accurate and on brief, but the approver would say it differently. Accept what is cheap and clearly better; decline the rest politely, pointing to the approval definition.

Two rounds is a reasonable ceiling to agree: one for the consolidated feedback and one to confirm the fixes. We have no study that says two is the right number, so treat it as a working practice and adjust per client.

Number your versions (v1, v2, final) and keep all feedback in one place, whether that is a shared document or a ticket. State your reopen rule up front: once approved, a draft reopens only for a factual error or a legal issue, not for taste.

What a draft-mode publishing flow looks like

Whatever CMS you use, the safest pattern is that articles arrive as unpublished drafts and nothing goes live until the agency or client has approved it. That keeps the approval step real: a draft sitting in the CMS is not a published page, so a slow review costs you time but never puts an unapproved article in front of readers.

Record who approved, on what date and which version. A one-line note in the ticket is enough.

Common mistakes and what to track

• Version drift. The client comments on v1 while you are editing v2. Number versions and send only the latest.
• Lost email. Feedback buried in old threads. Copy it into one place.
• Approvers who change. A new contact reopens settled decisions. Re-confirm the approval definition when the person changes.
• No escalation. Silence has no consequence. Write the reminder schedule and the second contact into the agreement.

Track three numbers per client: days in review, rounds per article, and the share of drafts approved with no edits. If days or rounds rise, check your rules before blaming the client. A rising share approved with no edits tells you the brief and voice document are doing their job.

FAQ

What should an agency content approval process include? A named approver, a definition of what approval covers, two review stages, one consolidated feedback round, version numbers and a rule for silence.

How many rounds of revisions are reasonable? Two is a sensible limit: one round of consolidated feedback, one to confirm the fixes. Adjust per client.

What if a client goes quiet? Send a reminder at a set point, then escalate to the backup contact. Agree in advance whether silence ever counts as approval.

Who should approve? Both, in sequence. The agency checks brief fit, sources and voice. The client confirms facts about its own business.

How do you review an outsourced or AI-written article quickly without skipping checks? Check it against the brief, open the source behind every number, and look at the score and pass mark. That replaces a line-by-line re-edit for most drafts, but your knowledge of the client still needs a look at stage one.

What tool do you need? A shared place for versions and comments is enough: a document, a ticket or your project tracker. The rules matter more than the software.

What to do now

Pick your slowest client. Name their approver, write the one-sentence definition of approval, and set a review window. Then change your own stage one so it checks the brief and the sources rather than every sentence.

See how white-label works for agencies

Sources

1. Rankwrite editorial rubric — Rankwrite, 2026-01-01

This article was researched, written and edited by AI under human supervision, and checked against Rankwrite's public editorial rubric.