Build the Reference File Before You Edit Anything: the Production Infrastructure PR Firms Keep Missing
An overhead view of several printed documents arranged on dark clipboards, with smartphones and a coffee cup on a grey work surface.
By Gabriel Tan | April 2026
A company was going through a rebrand. New name, new positioning, new visual identity. Fifteen documents needed to go out within the same fortnight: updated website copy, a press release, client letters, an internal memo to staff, partner communications, social media copy, a media kit, and pitch decks for two different audiences. Seven people across the firm were drafting different pieces.
Within the first week, the problems surfaced. One writer referred to the company by its old name in paragraph three of a client letter. Another used the previous tagline in a pitch deck. Two documents described the rebrand as a "refresh" while three others called it a "new direction," which carried a different implication entirely. The tone in the staff memo was casual and excited. The tone in the client letter was formal and cautious. The social media copy sat somewhere in between and matched neither.
The instinct was to start editing immediately. Open each document, fix the problems, get them out the door. Fifteen documents, fifteen sets of edits, done by end of week.
That instinct is wrong. Here is why, and what to do instead.
The problem with editing first
When seven people edit fifteen documents without a shared reference, each person makes different choices. One writer describes the rebrand as a strategic evolution. Another frames it as a response to market changes. A third implies the old brand was not working, which contradicts the narrative the CEO approved. Someone uses terminology from the old brand guidelines that should have been retired. Someone else introduces new language that has not been approved.
Each document gets edited in isolation. Each editor applies their own judgment. The inconsistencies only surface when someone reads all fifteen documents side by side, which usually happens after half of them have been sent.
At that point, the firm either recalls and re-edits (expensive, embarrassing), or lives with the inconsistency and hopes nobody notices (risky, unprofessional). A rebrand where the company's own communications cannot agree on what to call itself or why the change happened is worse than no rebrand at all.
The problem is not that the editors are bad at their jobs. The problem is that no single reference defines what "right" looks like across all fifteen documents. Without that reference, consistency is impossible regardless of how talented the team is.
The first-principles move: build the reference file first
Before touching a single document, build one reference file that every editor works from. This takes less than a day. The fifteen documents come together faster after the reference file exists than they would have if editing had started on day one. This file is the production infrastructure PR firms keep skipping.
The reference file has four sections. Here is what goes into each one and how to build it.
Section 1: terminology rules
A two-column list. Left column: approved terms. Right column: terms that are banned and why.
To build it, gather every document that has been drafted so far. Read through and list every term used to describe the company, the rebrand, the old brand, the new positioning, and the company's products or services. You will find variations. Some are harmless preferences. Others carry strategic or legal risk.
For each term, decide: approved, banned, or conditional (acceptable in some contexts but not others). Write the approved alternative next to every banned term. If a term is conditional, note the specific context where it is allowed.
This section prevents the most visible errors. A rebrand that uses the old name in its own announcement materials signals a company that has not thought through its own change.
Section 2: narrative framework
The core message, broken into parts, that every document must reflect.
For the company rebrand, the narrative had three parts: why the change was happening (the company had outgrown its original positioning, not because the old brand failed), what it meant for clients (same team, same service standards, new capabilities), and what the new brand represented. The narrative explicitly prohibited two framings: never position the rebrand as a reaction to a problem, and never imply the old brand was deficient.
To build this, answer three questions. What is the core message? What are the two to three supporting points every audience needs to hear? What framings are explicitly prohibited?
Three to five sentences for the core message. One sentence per supporting point. One sentence per prohibited framing. This is the backbone every press release, internal memo, client letter, and social post draws from.
Every document will emphasise different parts of the narrative depending on the audience. But no document should contradict the narrative.
Section 3: audience registers
Different audiences need different emphasis, but all audiences need a common core so the message does not drift.
For the rebrand, seven audiences needed communication: staff, existing clients, prospects, partners, media, industry bodies, and social media followers. Each had different concerns.
Staff needed clarity about what was changing operationally and reassurance about what was staying the same. Existing clients needed confirmation that their service, team, and terms were unaffected. Prospects needed to understand the new positioning. Partners needed confirmation that business relationships were continuing. Media got the announcement with the narrative framework and a media kit.
To build this section, list every audience. For each, write one sentence describing their primary concern. Note which parts of the narrative framework should be emphasised for that audience.
The common umbrella appears in every document. The tailored emphasis changes per audience. This structure ensures that if a staff member reads the client letter, or a journalist sees the partner communication, the messages are consistent. Different in emphasis, identical in substance.
Section 4: communication tone
Different document types require different registers. An internal memo reads differently from a client letter, which reads differently from a press release, which reads differently from a social media post.
Three registers were defined for the rebrand. Internal (direct, energetic, plain language, focused on what is changing). External formal (measured, confident, forward-looking). External conversational (warm, accessible, shorter sentences, used for social and community-facing content).
To build this, group your document types by register. For each register, write two to three rules: default sentence length, formal or conversational, contractions acceptable, how direct.
This section prevents the situation where an internal memo sounds like a press release, or a social media post sounds like a legal document.
Lock the reference file, then produce
Once all four sections are written, the reference file is locked. No further changes without sign-off from the project lead. This is the single source of truth for every document in the project.
From this point, every editor works from the same reference. Terminology is consistent. The narrative is consistent. Audience emphasis is consistent. Tone is consistent.
The fifteen documents came together faster after the reference file was built than they would have if editing had started on day one. The writers were not faster. Nobody was guessing. Every decision that should be made once was made once.
When to use this method
Any time multiple people are producing output that should sound like it came from one voice. The rebrand is one example. Here are others.
Press releases across multiple clients. Each client has a brand voice guide. The firm's editorial standard, anti-AI checklist, and QA checklist are shared. The reference files stack.
Monitoring reports from different analysts. If three analysts produce reports for the same client and they read differently, the problem is not the analysts. It is a missing format guide and QA checklist.
Newsletter editions across months. Build the voice and format reference file once. Maintain quarterly.
Crisis communications. Statements to media, clients, staff, regulators, and social media within 24 to 48 hours. Without a locked narrative, terminology rules, and audience registers, the statements contradict each other. Build the reference file first, even under time pressure.
Event briefings for different stakeholders. CEO briefing, media briefing, sponsor briefing for the same event need a narrative framework and audience register map before anyone starts writing.
The pattern is the same. Multiple documents. Multiple writers. One voice required. Build the reference file first. Lock it. Then produce against it. That is the agency workflow most communications firms still run without.
How to build your first reference file this week
Pick a project or client where multiple people produce output that should be consistent but is not.
Terminology rules: 60 minutes. Narrative framework: 30 minutes. Audience registers: 30 minutes. Communication tone: 20 minutes.
Total time: under three hours. Lock it. Share it. The first set of documents will tell you whether it is specific enough. If inconsistencies still appear, the file is missing something. Add it. Within one to two iterations, the file stabilises.
Consistency is a system outcome, not a talent outcome. The reference file does the work that used to require a senior editor reviewing every document and catching every variation manually.
When your team produces documents, is there a single reference file that defines what "right" looks like across all of them? Or is each writer making different choices every time?
Gabriel Tan is the founder of Mekong Bridge Advisory. He builds structured execution systems for PR and communications firms.
