How to map an external approval loop
How to map an external approval loop: draw the outside party as its own lane, add decline and withdraw exits, handle expiry and re-approval, and cap revision rounds.
An external approval loop is any process where the final yes belongs to someone outside your company, such as a customer, a regulator or a partner. Mapping it well means drawing that party as a lane of its own and planning for the answers you cannot control.
The short version
- Draw the external party as its own swimlane so every handoff to them shows.
- Secure consent before doing work that depends on it.
- Give the external decision three exits: approved, edits requested and declined.
- Add a step that removes draft assets when the party declines or withdraws.
- Check whether approval is still valid just before you publish.
- Cap revision rounds and say what happens at the cap.
When the decision is not yours
Most approval charts assume every decision-maker is a colleague. In an external approval loop the final yes belongs to a customer, a regulator, a partner or an influencer, and that changes the shape of the chart. You cannot set their deadline, you cannot see inside their review, and they can say no, change their mind or simply stop replying.
Four features separate a useful external loop from an internal one. The outside party gets a lane of its own, so every handoff to them and back is a visible lane crossing you can time. Decline and withdraw exits are drawn explicitly, with a step that removes draft assets. Approval can expire, so a decision is placed right before you act on it. And revision rounds need a limit, because without one a loop between you and someone you do not control can run indefinitely.
This is different from an internal review loop, where an authority inside the organisation can decide when to stop. For that pattern read /guides/how-to-map-a-review-and-resubmit-loop. The example here is a customer case study; for another outside party see /templates/influencer-content-approval-process. Contract terms, publicity rights and data rules depend on your agreements and jurisdiction, so check them with your own legal team. Response dates and round limits in the chart are placeholders.
A customer case study that needs the customer's yes
A case study from nomination to the sales kit. Notice the customer lane, the decline exit and the check that approval is still valid at publish time.
Consent comes before any writing
A customer is nominated, then "Is the customer a good candidate and free to be named?" and "Does the customer agree to take part?" each have a No exit straight to the end. Only after both Yes answers are publicity terms confirmed in the contract and a release sent. Putting consent first means nobody drafts a story that cannot be used.
Internal review before the customer sees it
The champion is interviewed, results are collected with their sources, and the story is drafted with quotes and figures flagged for checking. Customer success checks facts, tone and relationship fit, and legal reviews claims, logo use and comparisons. "Do internal reviewers require changes?" loops back to the draft, so the customer is shown a draft your own reviewers already accept.
The customer's lane and the exits you do not control
The draft goes to the customer with a response date, and the customer's own review sits in a separate Customer (external) lane because its legal and communications teams may edit. "Does the customer approve the draft?" has three exits: Approved, Edits requested and Declined. Edits requested reworks the draft and sends it back to the customer. Declined leads to a stop step that logs the decline and removes draft assets, so a withdrawal is handled rather than ignored.
Expiry, re-approval and the capped round
Approved text is verified quote by quote against what the customer signed off. "Is the approval still valid at publish time?" asks whether the approval has expired, and Expired requests re-approval of the unchanged or updated text, returning to the customer's review. The template's edits loop has no cap; adding a maximum number of rounds, with an escalation or stop after it, is the improvement to make for your own process.
How it works
Put the outside party in its own lane
Add a lane for the external party, with a named contact where you have one. Every line that crosses into or out of it marks a wait you do not control, which you can then measure.
Chart consent before the work
Draw the decisions that must be yes before anything is drafted: can this party be involved, and do they agree. Give each a No exit that ends the process cleanly.
Review internally first
Add your own checks, such as facts, relationship fit and legal, before the draft leaves the building. Loop their changes back to the draft so the external party sees a version you can stand behind.
Draw the three exits from the external decision
Label approved, edits requested and declined in Line text. Send edits back to your rework step and declined to a stop step that logs the reason and removes drafts.
Add expiry and re-approval
Place a decision just before publication asking whether the approval is still valid. An expired branch returns to the external party for re-approval. Agree the validity window with them; the length is a placeholder.
Cap the revision rounds
Add a counter or a decision after the edits step: after a set number of rounds, escalate to a named person or stop. State the number your agreement allows. The example chart does not include this, so it is yours to add.
Mistakes to avoid
Treating the external party as one more step
Without a lane, their waiting time is attributed to you. Give them their own lane.
Drafting before consent
Work done before the party agrees may be wasted. Put the consent decisions first.
Only approve and reject
Edits requested is the common answer. Without it, the chart has no way to show the loop.
Forgetting that approval can lapse
Publishing months later on an old yes can be a problem. Check validity at the moment of use.
An uncapped loop
A loop with no maximum suggests it always ends. Add a cap and an escalation.
Map your own external approval loop
Open the case study approval example as your own chart, rename the external lane to your customer or partner, and add the round limit your agreement sets.
Frequently asked questions
What is an external approval loop?
A review cycle in which the final decision belongs to someone outside your organisation, such as a customer, partner or regulator. It differs from internal review because you cannot set their timing or see their process.
How is this different from a review and resubmit loop?
In an internal loop an authority can decide when it stops. In an external loop the other party holds the decision, so you also need decline and withdraw exits, expiry and a cap. See /guides/how-to-map-a-review-and-resubmit-loop for the internal version.
How many revision rounds should I allow?
That is for your agreement with the other party to decide, and this guide does not set a number. Whatever you choose, show it on the chart with the escalation or stop that follows.
Does an approval expire?
It can, depending on your contract, the content and the jurisdiction, so check your own terms. Charting a validity check before publishing makes the question visible.
Where else does this pattern appear?
Influencer content, partner announcements, regulator submissions and customer testimonials. Compare /templates/influencer-content-approval-process or start from /templates/case-study-approval-process.