Read before nine
The briefing is ready at 07:00 by default and covers the night. It is one page, for your own team, in five parts. The drawing shows its layout; the parts are numbered to match.

1
Phases that changed
Topics whose phase changed overnight, such as one that started, peaked or faded.
2
Rule firings
What crossed the lines your team set, on which item, and what was done about it.
3
Verdicts
The verdicts reached during the night on the media examined.
4
Open cases
The cases still open, with where each one stands.
5
Missed targets
Anything that went past its target, such as a draft that was not in the approver’s queue within 60 minutes.
What goes in
In the evening your team reads the daily report: the last 24 hours in full, ready at 21:00 by default. A report for any other window, such as a week, can be asked for. Every claim in it cites the record it came from, so a reader can check any line.
01
Start with the headline numbers
They are taken from the stores. A language model writes the one headline paragraph above them and nothing else; the summaries further down were already written for each trending topic and flagged verdict.
02
See what trended, and for whom
The topics that trended with the share for, against and neutral, and each one’s life: when it started, peaked and calmed down. Topics that peaked and faded inside the window are listed with both times.
03
Check the forecasts against what happened
The forecasts that fired, and how each one turned out.
04
Read the coordination findings
The findings, and the groups of accounts behind them.
05
Know which media verdicts can be used
Those of likely or high certainty, with where they rest, the item’s origin and whether an analyst has reviewed them; inconclusive ones are listed apart.
06
Account for what was done
Replies and reports sent after approval, rule firings with your team’s feedback, changes to the watch list and rules, and the system’s spend and health.
One for inside, one for outside
Your team reads the internal version; readers outside it get the external one. The briefing is internal only. The daily report and any report on demand come in both versions, built once from the same records.
Use the internal version for your own decisions. It holds everything, including account-level detail and the operations section.
Send the external version to readers outside your team. It carries only verdicts an analyst has confirmed, no account-level details beyond public official handles, and no operations section. It is written by a separate prompt and then scrubbed: handles, account names and links to accounts other than official ones are removed, and faces in key frames are pixelated.
An approver releases the external version before anyone outside sees it. If a section’s records could not be read, the section is shown empty with the reason; the report is never skipped.

Approve and download
On the Reports screen your approver finds what is waiting, and anyone with access opens or downloads a report. Each row shows its window, version, kind (briefing, daily, weekly or correction) and language.

01
See what needs an approver
Each report’s approval reads pending, approved or not required. An internal report needs no approval; an external one stays pending until an approver approves it.
02
Approve an external report
An approver or an admin can release one. The approver’s name is then printed on every page, with the version, the window and the report number.
03
Download a copy
Every download is recorded with who made it, so your team knows where each copy went.
04
Correct a released report
A correction goes out as an addendum to everyone who received the original.
Formats and delivery
Choose how each version reaches its readers. Reports are written in English or Hindi, and each channel is set for your installation.
Email and Telegram go out through your organisation’s own mail server and Telegram chat, set up in the first week, to the recipients you list. Until then, your team reads reports in the console or downloads them.
| Format or channel | Internal version | External version |
|---|---|---|
| Web page in the console | Yes, kept as the record for two years | Yes, kept as the record for two years |
| Yes, downloaded with a record of who did so | Yes, downloaded with a record of who did so | |
| A signed link valid for 72 hours, with the PDF attached by default | A signed link valid for 72 hours, without the PDF by default | |
| Telegram | A link | Not sent |
See last night’s briefing laid out for your own topics, and decide who should receive which version.
Request a demo/use-cases/briefing · The morning briefing