A shared creative library dies when every partner rewrites the caption.
The cut is approved. The rights field is clean. Then five organisations invent five different last lines, and the coalition is suddenly arguing five different claims.
Coalition caption pack English is the language layer of a shared library: one locked English card per asset, short enough to paste, strict enough that a late-night editor cannot “improve” the policy.
This is the language companion to our coalition shared creative library post. That one is governance, rights, and version IDs. This one is the sentences that travel with the file.
Neuwark Communications builds message systems for advocacy networks across the Philippines, Singapore, Indonesia, Thailand, and the wider APAC region, with a Singapore account office at Marina Bay Financial Centre Tower 2. This is operator English, not legal advice.
What belongs on a caption card?
Four sentences. One job each. Nothing cute.
| Line | Job | Pattern |
|---|---|---|
| Claim | Says the one thing the asset is allowed to argue | “[Who] wants [specific change] because [one reason].” |
| Proof | One checkable fact already on the claim sheet | “Source: [named public document or dated figure].” |
| Credit | Names the owner and the restriction | “Asset [ID]. Use in [territory] until [date]. Credit: [line].” |
| Ask | One behaviour | “[Do this]. Do not add a second ask.” |
A worked card:
Our coalition wants the budget hearing to keep the social-protection line intact, because the committee’s own papers show the cut lands on the same households twice.
Figure from the committee brief dated this session week; link lives on the claim sheet.
Asset BUDGET_CUTDOWN_EN_916_v03. PH + online until 31 October 2026. Credit: Coalition shared library / local partner name.
Share the hearing timetable with your chapter. Do not invent a vote count.
If a partner cannot read that card on a provincial connection, the library is a Metro toy.
Which caption words should you kill?
These five phrases show up the night a partner “localises” without a version ID.
| Kill | Why it breaks | Replace with |
|---|---|---|
| “Join the movement” | No behaviour. Sounds like a brand film. | “Send this cut to your chapter admin by 6pm.” |
| “Hold them accountable” | Accountable for what, by whom, by when? | Name the hearing, the office, or the filing. |
| “Historic” / “unprecedented” | Usually untrue by lunchtime. | Date + document. |
| “We have been assured” | Invents access. Counsel will strike it. | “We filed. We are waiting for the posted reply.” |
| Partner slogan bolted under the coalition end card | Two brands, two claims, one lawsuit risk | Locked end card only. Request a new version ID for a local lockup. |
Street-smart English sits between colonial stiffness and startup mush. “Kindly be informed that the undersigned coalition…” is unreadable. “We unlock narrative impact at scale…” is a deck. Neither survives a group chat.
How do you write credits that do not start a logo fight?
Credits are sentences, not decorations.
Rules:
- Name the licensor, not “the team.”
- Name the territory. “ASEAN” is not a licence if the field says PH only.
- Name the end date. Perpetual is a decision, not a default.
- Name the edit rights. “Crop and burn captions: yes. New claim text: no.”
- Name the dispute contact. An email that a human reads.
Template:
Owner: [org]. Territory: [PH / SG / ID / TH / listed]. End date: [date]. Allowed edits: burn captions from this card; no new claims. Credit on-screen: [exact lockup]. Dispute: [name, desk email].
If the rights field and the caption credit disagree, quarantine the asset. Do not “fix it in the post.”
What should a partner type when they need a variant?
Partners should not rewrite in the caption box.
They send one note:
Requesting version [old ID] → new ID. Language: [EN / FIL / ID / TH]. Change requested: [one line]. Claim unchanged: yes/no. Needed by: [clock].
If the claim changes, it is not a variant. It is a new master. Legal signs substance. Comms signs tone. The steward issues the ID.
Monday field kit
- Read-aloud. If you run out of breath, cut the sentence.
- Forward the card to someone outside the comms desk. If they ask “so what do we post?”, rewrite.
- Counsel drill. One question: “What would you strike?” Strike it before partners see it.
- Answer-engine drill. Search the claim in plain language. If the machine’s sentence is cleaner than yours, yours is mush.
FAQs
What is coalition caption pack English?
It is the locked English text that travels with a shared asset: claim, proof, credit, and one ask. Partners paste it. They do not improvise policy in the caption box.
Can partners write vernacular from the English card?
Yes, from the locked card, with a new version ID and a named language owner. Machine draft is allowed. Human sign-off on every policy claim is required. See our English spine for multilingual GEO.
Is this legal advice?
No. Rights fields, election restrictions, and claims about law or health need counsel in the relevant market. This page is communications craft.
What to do this week
Lock one caption card for the asset you will ship most this week. Kill the five phrases above. Issue version IDs before anyone “just tweaks the last line.”
If you want a desk that keeps coalition language honest, start at Services or Contact. More field notes: Insights.
Related: coalition shared creative library · multilingual message discipline · clip-safe debate English · crisis dark-site English