Several clients, each kept apart

In Media Verdict a client is one organisation, with its own watch lists and its own users. Each client’s users see only that client’s work, and what one client does never reaches another.

A user belongs to one client. Only a few named people on our side can switch between clients, and every switch is in the audit log.

The shared system holds several clients side by side and keeps them apart. A client that needs its data in a database no other client touches has its own installation instead.

Separation

Separate means six things, with no exceptions.

1. Nobody sees another client’s work: not its watch list, topics, forecasts, cases, reports, drafts, labels, verdicts, audit trail or spend, on any screen, or in any export, search or error message.

2. One client’s choices never change another’s results. Its keywords, labels, corrections, rules and thresholds do not move another client’s topics, alerts, forecasts or calibration.

3. Money is per client. Each client has its own daily budget, so one client’s busy day cannot pause another’s collection.

4. Logins are per client. A user belongs to one client; a few named people on our side can switch between clients, and every switch is in the audit log.

5. It can be shown. For any stored row we can say which client it belongs to, and a test fails the build if a table or query does not say.

6. Leaving is clean. A client’s data is exported as CSV files and a PDF summary, and the rest is deleted within 30 days without touching anyone else’s.

Detection models are shared, and each client’s labels and calibration are its own.

Media Verdict console
Illustration

An account team’s day

One day of a public affairs team, working in its own organisation’s account, from the morning briefing to the evening report.

Media Verdict console

A report for inside, a report for the client

Each report is built once from the records and comes in two tiers: an internal one for the team, and an external one for readers outside it, such as the organisation you act for.

Media Verdict console
1 2 3 4 5
IllustrationEach row is one report: the solid square is its internal version, the outlined square its external version, which goes out only once an approver releases it (the red line). Approval states are left blank.
  1. 01

    Internal

    Everything: top trends with stance and summaries, forecasts and how they turned out, coordination findings, rule firings, media verdicts, actions taken and operations.

  2. 02

    External

    Only verdicts an analyst has confirmed, no account-level details beyond public official handles, and no operations section. Other handles, names and links are removed, and faces in key frames are pixelated.

  3. 03

    Released by an approver

    An external report goes out only once an approver has released it.

  4. 04

    Formats and delivery

    A web page and a PDF, in English or Hindi, with the tier, window, report number and approver on every page; kept in the console, downloaded with a record of who did so, or sent by email with a link valid for 72 hours.

  5. 05

    Every claim cited

    Each claim in a report points to the record it came from.

What it uses

CapabilityWhat it gives the team
Social listeningThe keywords, hashtags and accounts the team watches, and the keyword report: how much is said and where, who drives it, and what search results and AI assistants show, for any date range, as one CSV download and one printable page.
Trend detectionWhich of the watched issues are rising now, each measured against its own usual level.
ForecastsWhich way a busy topic, or a watched keyword, is likely to go in the next hour, and why.
StanceWhether posts are for, against or neutral toward the government and the other bodies an installation names.
Coordinated activityBefore the team escalates a campaign around an issue, whether it is ordinary interest or accounts acting together, shown with the accounts and the evidence.
AI answersWhich websites AI assistants cite when asked about the issues the team watches, and whether their answers name them, so the team knows which sources shape those answers.

Questions

Does each client hold its own copy of a post?

No. Posts are public, so one collected copy can serve two clients. What each did with it, such as its topics, labels and cases, is never shared.

Can a client see what it costs?

Yes. Each client has its own daily budget, set by us, and sees its own spend and no one else’s.

Does one client’s work change another’s results?

No. Labels and calibration are kept per client. A client without enough labels of its own uses the shared starting calibration, never another client’s.

Can a client have its own servers?

Yes. A client that needs its data in a database no other client touches gets its own installation: the same build, on its own servers.

Walk through how two clients of the shared system are kept apart, screen by screen.

Request a demo