Risk and scenario mapping
We list the incidents that could plausibly reach your stakeholders, rank them by likelihood and reach, and set severity tiers so your team knows which response applies before anyone has to argue about it.
Performance Marketing · 18 Crisis Communications
We prepare the statements, roles and channels your organisation needs before an incident, then work alongside your team while it plays out. The output is a set of documents your people can use at 2am without calling us first.
You own accounts, data and IP Monthly reporting Reply within one business day
OlDevs is a full-stack technology and marketing studio in Vancouver, BC, and crisis communications is the discipline we use to prepare what an organisation says when something goes wrong.It covers the work done before an incident and the work done during one: mapping plausible scenarios, writing a holding-statement library, naming the roles in an escalation chain, preparing spokespeople, building a dark site and channel response templates, monitoring and triaging while the event is live, then running the post-incident review. We build these programmes for councils, government bodies, associations and franchises across Canada and the United States, in English and French. Every document, template and account stays yours.
Key facts
18 · Crisis Communications
Six pieces of work. Take all of them, or start with the scenario map and the statement library and add the rest later.
We list the incidents that could plausibly reach your stakeholders, rank them by likelihood and reach, and set severity tiers so your team knows which response applies before anyone has to argue about it.
Scenario map · Severity tiers · Stakeholder map · Trigger criteria · Risk register
Pre-approved first statements for each scenario tier, written and signed off while nobody is under pressure. Each one has blanks for facts, a named approver and a plain rule for when it can go out.
Holding statements · Approval rules · Fact blanks · Legal review · EN/FR versions
One page that says who is notified, who decides, who writes, who publishes and who covers each role when the first person is unreachable. Names and numbers, not job titles alone.
Named roles · Deputies · Notification tree · Decision rights · Contact sheet
Practice sessions for the people who will speak: message discipline, bridging, what not to say, and handling questions you cannot answer yet. Recorded, reviewed, repeated until the answers hold up.
Media training · Message discipline · Mock interviews · Q&A prep · Camera practice
A hidden page on your site that can be published in minutes, plus matching templates for email, social channels, phone scripts and internal notes. Built, tested and left ready in your CMS.
Dark site · Social templates · Email templates · Phone script · Staff note · CMS handover
During an incident we watch the channels, sort what needs a reply from what does not, and draft as facts arrive. Afterwards we write the review: timeline, decisions, gaps and changes to make.
Channel monitoring · Triage · Live drafting · Incident log · Post-incident review
Process
Scoping call
We ask what you are exposed to, who your stakeholders are and what already exists on paper. You get a written scope and a quote before any work starts.
Scenario map
Two workshops with your team produce the scenario list, severity tiers and stakeholder map. We circulate the draft, take your corrections, and lock the version everyone will work from.
Build
We write the statement library, the escalation chain and the channel templates, then build the dark site in your CMS. Weekly demos show the work while it is still changeable.
Rehearsal and handover
A tabletop exercise runs one scenario end to end with the real people. We fix what breaks, train the spokespeople, and hand over every file and login to your team.
Live response and review
If an incident happens we join your channel, monitor, triage and draft alongside your team. When it closes we write the post-incident review and update the library.
How we work
Design, engineering, writing and marketing sit in the same studio in Vancouver. One person is accountable for the engagement, and you always know who is holding the file.
Documents, templates, the dark site, monitoring accounts and every login are yours from the first day. Nothing sits in an OlDevs account you cannot reach or take with you.
You see the work every week while it is still being written, not as a finished binder at the end. Corrections in week two are easier than corrections in week eight.
Every message gets an answer within one business day, incident or not. During a live incident we agree a faster response window in writing before the engagement starts.
Statements, templates, briefing notes and the dark site can be produced in English and French, reviewed by the same team, so the two versions say the same thing.
The dark site and every page we publish for you meets WCAG 2.2 AA, so a statement stays readable on a screen reader and still loads on a slow connection when traffic spikes.
Who it's for
Organisations where a single incident reaches several audiences at the same time, and where the wrong first sentence is hard to walk back.
A service failure, a safety event or a contentious decision reaches residents, staff, media and elected officials at once. The sequence and the wording both matter, and both need deciding in advance.
Members expect to hear from you before they read about it elsewhere. We build the member-first sequence, the board briefing note and the statement that follows it publicly.
One location's incident is read as the whole brand's failure. Franchisees get a script and a boundary: what they may say locally, what they must not say, and what routes to head office first.
You have a binder from a previous agency and no confidence in it. We test it against real scenarios, keep what works, rewrite what does not and rehearse the rest.
12+
Years of studio experience since 2014
5
Response channels templated per scenario: web, email, social, phone and staff
EN/FR
Statements, templates and briefing notes produced in both languages
Works well with
We build the media list, mine the stories inside your organisation, write the releases and kits, pitch them, and prepare the people who speak.
Explore02We monitor reviews, brand search results and every place your organisation is described, then correct what is wrong and publish what is missing.
Explore03Stakeholder mapping, consultation programmes, member newsletters, and board and funder reporting in English and French.
ExploreInsights
Practical writing from the team that would be doing it.
Passwords gave way to passkeys, privacy law arrived in force, accessibility got deadlines and AI added new risks. What changed through 2026 and the checklist to…
Attribution decides which marketing gets credit for a sale. No model is perfect; the aim is a fair, consistent method that shows where budget actually works.
Model fees are the smaller share of a copilot's running cost. Tokens, latency, monitoring and guardrails are the larger one, and they decide whether it stays…
FAQ
A scenario map with severity tiers, a holding-statement library covering each tier, a one-page escalation chain with named people and deputies, response templates for web, email, social, phone and internal use, a dark site built in your CMS, and a record of the rehearsal. Everything is delivered as editable files in your own systems, in the formats your team already uses.
You do, from the first day. The documents are written in your systems under your accounts, the dark site lives in your CMS, and any monitoring tools are set up in your organisation's name with your billing. If we stop working together you keep everything without asking for a handover, because the handover already happened. Nothing is held back to make renewing easier for us.
Against agreed operational measures, not sentiment scores. Time from first alert to first published statement. Proportion of enquiries answered within the window you set. Whether the escalation chain was followed and where it broke. Whether staff and members heard from you before external channels. Whether the dark site held traffic without failing. We set these measures at scoping, record them during the incident, and report them in the post-incident review.
Every engagement is quoted after a scoping call, because the work depends on how many scenarios you need covered, how many audiences you speak to, whether you need French, and whether we are also on call during incidents. We put the scope, the deliverables and the response commitments in writing before anything starts, so you are approving a defined piece of work rather than an open retainer.
Both, and they are scoped separately. Preparation is a defined project with an end date. Live response is a standing arrangement with agreed contact points, an agreed response window and named people on our side. Some clients take preparation only and run incidents themselves, which is a reasonable outcome if the rehearsal went well. Others keep us on call. You can start with preparation and add live cover later.
No. Your spokespeople speak, and we prepare them to do it. We write the statements, run the practice sessions, sit in the room during the response and handle the drafting, but the voice on the record is yours. Media relations, including proactive pitching and ongoing journalist contact, is a separate discipline we also offer, and it is scoped on its own.
Sometimes, and we will tell you within one business day whether we can. Starting mid-incident means we work with what exists: your facts, your approvals and your channels. We can draft, monitor and triage immediately, but scenario mapping and rehearsal come afterwards. Send what you have and who is authorised to approve wording. If we are not the right fit at that moment we will say so rather than take the work.
Let’s connect
Tell us what you’re building. We’ll reply within one business day with next steps and a tailored quote — no obligation.
Thanks — we’ll reply within one business day.