How a story moves

A walkthrough of the planned flow. Every step below is specified, not built yet.

  1. Field

    • Reporter appOffline filing with a signed receiptGoes to: Newsroom queue
    • WhatsApp intakeStringer copy and photos with a receipt, through a messaging providerGoes to: Newsroom queue
    • Wire deskAgency takes, kills and embargoesGoes to: Newsroom queue

    Then to: Desk

  2. Desk

    • Newsroom queueState, owner and deadline for every story in the queueGoes to: Story workspace
    • Story workspaceCo-editing, immutable versions, provenanceGoes to: Gates
    • GatesNamed approval, legal, embargo, correctionsGoes to: FactSheet
    • AI under policySuggestions and drafts; a person approvesAssists: Gates

    Then to: One story

  3. One story

    • FactSheetThe facts every channel variant must respectGoes to: Channel variants
    • Channel variantsOwn style, copy and approver; never more factsGoes to: Web, Print, Social, Push alert, Newsletter

    Then to: Channels

  4. Channels

    • WebLoom, or a WordPress fallback channel
    • PrintTo NewsForge Pages (print layout), then e-paper
    • SocialCopy for Facebook, Instagram and LinkedIn, posted by a person
    • Push alertSent by a named person
    • NewsletterEmail newsletter copy
Design illustrationDesign illustration of the planned flow. Arrows show where a story will go next; a dashed box is AI assistance that the newsroom's policy will limit.

Step by step

  1. A reporter files from the field

    Filing will work from a phone, online or not. The app is designed to keep every word and to return a signed receipt once the filing reaches the newsroom. Stringers will also be able to file through WhatsApp, subject to a messaging provider.

  2. The desk sees it in the queue

    Wire copy and filings are to arrive in one queue with state, owner and deadline. The desk will assign, route to a bureau or take it on.

  3. Editors work on it together

    Sub-editors will edit alongside the reporter. Every saved version is specified to be kept unchanged, and every sentence will show who wrote it.

  4. AI helps only as far as the policy allows

    Suggestions, headline options or a draft from cited sources will be offered, depending on the newsroom's settings. Each AI step will be logged and a person will decide.

  5. The story passes its gates

    A named approver will sign off. Legal flags, embargoes and other holds are designed to block release until they are cleared.

  6. One story becomes many channel variants

    Channel variants for web, print, social, push and the newsletter are to be shaped from the same FactSheet, each with its own style and approver, and released to their channels.

When something goes wrong

  • A correction is designed to be approved once and to reach every channel where the story lives.
  • A kill or a legal hold after a page is sent to layout will withdraw the story from the page and the e-paper.
  • Any action is specified to be traceable in the audit chain to a named person or a logged policy decision.