In-depth practical guides

Organise verifiable documentary monitoring

Choose sources, recognise real novelty and retain history: build monitoring that produces useful information rather than a pile of notifications.

Updated :

Document monitoring desk with a notebook, clock and resources to consult.

AI-generated illustration

Which change deserves verification and reporting?

Monitoring starts with a decision need, not a feed count. Define topics, actors, territories and expected documents to distinguish a relevant signal from republication. Preserve provenance and dates for each observation. An absence of updates is meaningful only when consulted sources and unavailable sources are known.

  1. Define scope and outputs

    Write the questions, exclusions and intended recipient. Define what triggers a note: new document, material change, correction or disappearance. Use a short output containing the change, supporting evidence and relevance to the decision.

  2. Build a source register

    List accessible official pages, publications, registers and feeds. Record issuer, coverage, language, access method and chosen checking frequency. Fill coverage gaps rather than multiplying interfaces that repeat the same publication.

  3. Separate dates and states

    Record event, publication, announced modification and observation in separate fields. Atom feeds distinguish identifiers and update dates; an update date should not automatically be interpreted as the date of the described event.

  4. Recognise republications and revisions

    Compare document reference, stable identifier where available, final URL and useful content. A changed title alone does not create a new document. Link a revision to its predecessor and describe the actual change.

  5. Qualify signals before reporting

    Open the complete document, read qualifications and verify scope. Attribute statements clearly. Media coverage can help discover a publication, but keep the document link that actually supports the conclusion.

  6. Maintain usable history

    Retain findings, access failures and classification decisions. Schedule checks according to actual change frequency and the cost of missing information. Reassess inactive sources and alerts that never yield useful signals.

Reading workshop

An interruption is not an absence of news

File DEMO-W08 separates coverage, observation and material change at an unchanged URL.

Fictional data and records for learning: none of these results comes from a live service query.

Interrupted feed window and a correction at the same URL

Document v1 was retained before the outage. On resumption the feed window starts at 06:00, and v2 changes the case count without changing the event date.

  1. Scheduled check on 2 May

    Scenario data
    HTTP 503; no document read
    Diagnosis
    The interval is not covered.
    Decision
    Retain failure rather than recording zero changes.
  2. Resume on 3 May at 08:00

    Scenario data
    Received window starts at 06:00
    Diagnosis
    Earlier entries are not retained here.
    Decision
    Seek archives or another source; keep the gap visible.
  3. Same URL, different version

    Scenario data
    v1: 50 cases; v2: 47; event 30 April
    Diagnosis
    Content changes without a new URL or event.
    Decision
    Compare documents and revisit the affected conclusion.
  4. A mirror repost

    Scenario data
    Mirror reproduces v1
    Diagnosis
    Neither v2 nor independent confirmation.
    Decision
    Link its provenance to the original document.

What summary can be communicated?

Open each proposition to compare its diagnosis. More checks may still be needed.

No change between checks.

No: the outage leaves an uncovered interval and v2 contains a correction.

A new event of 47 cases on 3 May.

No: 3 May is the observation date; the event remains dated 30 April.

A verified revision from 50 to 47, with a coverage gap.

Appropriate here. The gap stays open until other evidence resolves it.

Filled fictional record

File: DEMO-W08
2 May: 503; uncovered period
3 May 08:00: resumed; window since 06:00
URL: unchanged between v1 and v2
Event: 30 April; value 50 → 47
Mirror: v1 repost; linked provenance
Outcome: correction to follow; gap retained

Cite the version actually reviewed and separate event, publication and observation dates. Keep the uncovered period and the mirror’s provenance link in the log.

Documentation of the rules, separate from fictional examples

Compare other situations and exercises

A feed announces an old publication

Check first-publication date and content. Separate renewed promotion from documentary novelty. If a real revision exists, describe the difference rather than repeat the title as a new fact.

Several alerts concern one document

Link notifications to the initial publication. Keep republications adding an identifiable contribution; group others so notification volume is not presented as independent confirmation.

A monitored page becomes unavailable

Record last successful access and current failure. Look for a new official address or equivalent channel. Do not translate access failure into no change; mark coverage as incomplete.

Worked exercise

Eight alerts, three documents, two actions

Fictional example: the values and documents teach the method and do not describe a real organisation.

Eight alerts concern these three records. Repeated notifications do not change their content.

If the table exceeds the screen, scroll horizontally; arrow keys work when the region is focused.

Starting information
RecordAlerts receivedRecord status
A4Already known
B2Correction identified
C2New record

Your checks

  1. Group alerts by document and version.
  2. Compare B with the retained version.
  3. Assign an action to each actual change.
Read the answer

Answer and decision

There are three distinct documents. File A, check affected conclusions for B and read C. The useful outcome is one new item and one correction, not eight confirmations. Deduplicating notifications does not replace comparing versions.

If the case changes

If B's alerts concern different versions, separate them before grouping.

Record to retain

Keep identifier, previous version, observed change, action and follow-up status.

Record to retain

  • Source register, scope, access methods and planned checks.
  • Document identity, separate dates, version and signal-supporting excerpt.
  • Links between republications, revisions and initial publication.
  • Check status, classification decision and outstanding verification.

Official references

Related protocols

Checks before reaching a conclusion

  • Does each retained alert identify what changed in the source rather than just its collection date?
  • Are repeats of the same release or dataset linked to a common origin before confirmations are counted?
  • Does the record explain why a signal triggers action, needs verification or requires no intervention?

Frequently asked questions

How often should checks run?

Match frequency to the source, need and acceptable delay. Annual publications and frequently edited pages need different schedules. Reassess based on changes actually observed.

Is a notification sufficient evidence?

It identifies a lead. Open the document, confirm version and context and retain its reference. If inaccessible, mark the signal unverified instead of treating the notification as complete evidence.

Should all republications be deleted?

No. They may add translation, context or independent verification. Link them to the original and describe their contribution; copies adding nothing can be grouped.

How can monitoring usefulness be measured?

Track qualified signals, decisions supported, coverage gaps and processing time. Raw alert count measures activity, not by itself the documentary value produced.

How can one distinguish between form and background change?

Compare the information used in the folder: values, definitions, conditions and conclusions. A visual change may be minor, but it must be examined if it affects the readability or location of evidence.

DEEPER READING / PRACTICE

Monitor changes as well as publications

A documentary watch collects new links but does not notice changes to a already known document. Tracking must include versions, replacement and context changes.

Updated on .

Priority checks

Defining followed documents, identificators, frequency and change criteria. Compare versions and distinguish form modification, new data and background correction.

Interpretation pitfalls

An unchanged URL can be used as a modified document. A new publication can also be a copy without additional information.

Working record to retain

The watch journal retains the previous version, the observed version, the change and the consequence for the conclusions. The warnings correspond to a concrete effect on the case.