Circulation Routes

A circulation route records the edition date, route name, copies dispatched and copies returned. It links to an operational content record, keeping the route evidence connected to the published work. The Circulation Manager uses this record when the edition goes out and when returns arrive. The Editor can see the route alongside the edition’s content and production history.

The capture workflow accepts a route entered in the app or through its custom page. It resolves the linked operational record and permitted actor, validates the date, route and copy values with source evidence, then saves an attributed route record. That means the record reflects a specific capture event rather than an unexplained total entered after the fact.

• Edition date. The route belongs to a specific edition date.
• Route name. A stable route name helps compare dispatch and returns for the same distribution path.
• Copy evidence. Dispatched and returned copies are stored on the route record with the linked operational content.

Decide when dispatch and return figures are ready for capture. If figures change, use an agreed correction path that preserves attribution. Keep the route names consistent across editions; a spelling variation can make two entries look like separate routes in a report. The route log is useful for day-to-day review because it shows both copy values beside the edition date.

Choose which content item represents the operational record for an edition route. Confirm that the item belongs to the relevant project and that the Circulation Manager has the right actor identity for capture. Agree how source evidence is collected for dispatch and returns. Choose a route naming convention the distribution team can apply under deadline pressure.

When testing a custom page capture, use the same values as a normal app-created route and compare the saved result. A repeated capture should not create a second route for the same business operation. A conflicting retry should be visible for resolution. These distinctions matter when a device or operator resends a submission.

After the Editor publishes content for a Saturday edition, link a route to the operational content item. When dispatch and return figures are ready, enter the edition date, route name and both copy values with the agreed evidence. Open Circulation Routes and check the date, route, copy values and linked record. Then review the circulation report to see the same dispatch and return values together.

Rehearse a wrong-route submission. The Circulation Manager should resolve it as an attributed correction, not create an untraceable replacement. The Editor can then use the route record alongside the publication history when closing the edition.

• Circulation Routes — Review dispatch and returns by edition date and route.
• Content Pipeline — Locate the operational content record linked to a route.

See publication and circulation and the implementation plan for the first operating cycle.