9592 Solutions
All work

Demonstrator / work sample

A two-stage editorial workflow that keeps a public dataset current without growing the team's workload

A deployed prototype you can test in the browser. It is a work sample, not a customer project and not a product.

The problem

The same network needed contributors to maintain their own entries without the editorial team becoming the bottleneck. At the same time, every change had to stay reviewable and auditable.

The approach

  • A self-service account for contributors with passwordless magic-link login: low friction for volunteer and part-time submitters, and no elevated data-protection risk because only publicly-intended offer data is edited.
  • A five-state lifecycle for every entry (draft, submitted, published, change-requested, archived) implementing a two-stage review: contributors submit, the editorial team reviews and publishes. Published entries can only change via a reviewed change-request with a before-and-after comparison.
  • An editorial back-office with an intake queue, a change queue with diff view, full-text search and bulk actions over published entries, and master-data management.
  • An automated reminder pipeline: a periodic check flags entries not confirmed in six months and runs a three-step escalation with token-signed one-click links (still current, submit a change, withdraw), no login required. Currency is maintained without editorial initiative.
  • A complete audit log: every action timestamped with account and operation.
  • Editorial CMS header with a demo persona selector for the public view, a contributor, and an editor, above the public list of published offers.
    A demo persona switch between the public view, a contributor, and an editor.
  • A contributor's five-step "new offer" form, on the first step, with title, description, category and target-group selectors.
    Contributor submission: a five-step offer form with conditional fields.
  • The editor's intake queue showing a submitted offer expanded into a preview, with publish, return-with-note and edit actions.
    Editor intake queue: a submitted offer expanded for review.
  • A change request to a published offer, shown as a before-and-after comparison of the title and description fields.
    A change request shown as a before-and-after field comparison.
  • The reminder pipeline's preview outbox: generated reminder emails for an offer across the day-0 / 30 / 60 / 90 escalation stages.
    The reminder pipeline: generated reminder emails in the preview outbox.
  • The audit log for a single offer: a chronological timeline of state transitions (created, submitted, published) with actor and timestamp.
    The audit log: a chronological timeline of state transitions for one entry.

What the demonstrator shows

The demonstrator is fully interactive: a clearly-labelled demo persona switch moves between the public view, a contributor, and an editor. You can submit an offer, watch it appear in the editor's intake queue, publish it, submit a change request, and resolve it via the diff view.

A control to fast-forward six months triggers the full reminder escalation, and the generated reminder emails appear in a preview outbox. Every action is written to the audit log.