Prepare the scope before an incident
Agree monitored brands, important people, languages and priority sources with the client. Include common false matches and exclusions. Define who is available to assess an alert and who has authority to approve a response.
Keep escalation contacts current and agree the delivery channel for urgent briefs. A monitoring tool cannot compensate for an outdated contact tree. Run a tabletop exercise with sample material to check that the process works outside the account manager's normal routine.
Triage relevance and urgency separately
First verify that the material refers to the client and is not an unrelated name match, quotation or recycled story. Then assess the allegation, source context, spread and potential impact. An increase in volume is a reason to investigate, not proof of a coordinated campaign.
Distinguish observed facts, source claims and analyst interpretation in your notes. If identity, timing or authenticity remains uncertain, make that uncertainty part of the briefing. Do not fill evidence gaps with a more confident narrative.
Preserve the material needed for a decision
- Original URL, platform and collection time.
- Relevant text or permitted capture with surrounding context.
- Whether the content is original, a repost or a reference to another source.
- Changes observed after collection.
- The analyst's interpretation and its supporting observations.
Use appropriate access and retention rules for collected material. Keep client-sensitive investigation notes separate from public-facing reports. A working source record should let another authorized team member understand what was seen and when.
Write a concise incident brief
| Brief section | Question it answers |
|---|---|
| What happened | What is actually observable? |
| Why it matters | Which client interest could be affected? |
| What remains uncertain | What needs confirmation? |
| Recommended next step | Who should decide or act? |
| Next update | When will the assessment be reviewed? |
Offer proportionate options such as further verification, a prepared response, operational correction or escalation to the client's specialist team. Publication is a client decision under the agreed workflow.
Review the response and the monitoring rules
After the incident, compare the first useful signal, the alert time and the first informed decision. Identify missed sources, noisy terms and delays in ownership. Avoid turning an illustrative dashboard score into a measured business outcome.
Update the client brief, escalation tree and monitoring terms. Keep lessons specific enough to change the next response: a new exclusion, a source added to scope or an approver given a backup.
Rehearse the first incident brief
Use clearly labeled sample material for a tabletop exercise. Produce a short brief with observable facts, uncertainty, the decision required and the next update. Time the handoff so a missing contact or unclear owner can be corrected before an incident.
Acceptance criteria. A useful rehearsal ends with a named decision-maker able to inspect the evidence and explain the proposed action. Track collection time separately from publication time. Preserve the distinction between source allegations and the agency’s own assessment throughout the brief.
Turn these requirements into a shortlist with our guide to the reputation monitoring tools for agencies. Compare each product against the workflow your agency will actually deliver.
Common questions
Does a mention spike prove a reputation attack?
No. A spike can reflect ordinary news coverage, a genuine service issue, a false match or coordinated activity. Investigate the sources and context before assigning a cause.
What should an agency send in the first crisis alert?
Send the observable issue, supporting sources, potential relevance, known uncertainties, the decision needed and the next update time.
A negative story is spreading while the client approver is offline. What should our first agency briefing contain?
Send observed facts, source context, uncertainties, the decision needed and a planned next update to the agreed backup. Use the existing escalation agreement; a volume spike alone does not justify publishing a response.
Continue your fieldwork
This guide provides an operational planning framework. Product capabilities and commercial terms are documented in the linked comparison; validate your own requirements in a pilot.