Method

SSE connects an incoming records request to the search, review decisions, and response prepared for it. The Bellwether demo shows this method with fictional records in a temporary workspace.

Keep the source

An imported request or collected record retains its original file. Extracted text, numbered copies, and copies approved for release are separate outputs. Staff can compare the information used in the workflow with the original before completing review.

For the demo, use invented PDF or plain-text records within the documented format and size limits. Incoming PDF extraction does not approve the request’s details.

Record human decisions

The reviewer decides whether a record is released in full, released with redactions, withheld, or not responsive. The saved decision includes a reason; redaction and withholding require an authority supplied by the reviewer. Requested items also receive an outcome and explanation.

Software checks can identify missing steps. They do not determine every applicable exemption, find all sensitive information, or establish legal compliance. Staff must check the source, circumstances, and proposed output.

Inspect the approved copy

The release package contains the copies explicitly approved for release, the response, and a manifest. Inspect those copies before approving the package. PDF release copies are rebuilt from page images; they do not retain the original searchable text.

Package creation does not deliver a response. Delivery entries record evidence supplied by staff after using a separate delivery process. The public demo sends nothing. Follow the review and release guide for the complete sequence.

Keep decisions with the case

Request history records intake, routing, deadline changes, and review activity. Fingerprints and retained snapshots support checks for inconsistencies. They do not prove that every real-world action was recorded or authenticate the person who performed it.

The internal audit file may include unredacted originals and must stay separate from the requester’s release package. The history and exports guide explains the distinction. Demo history is temporary and disappears on reset, expiry, or server restart.

Describe what is available

The documentation distinguishes public-demo features, reference-application capabilities, and planned work. A format listed in a picker or supported by an extraction component is not enough to establish a complete review and release workflow.

Check current availability and deployment limits before evaluating SSE for agency use. The public demo does not establish that municipal authentication, supported connectors, backups, or retention controls are complete.