Case study: planning a fictional city-data magazine issue

What to take away

This case is fictional and describes no real magazine or data release.
The issue uses several forms to answer different reader questions.
External release dates are treated as dependencies, not certainties.
The flatplan separates page position from production status.
The final review changes one planning rule for the next issue.

Fictional monthly magazine Civic Measure plans a 72-page issue about how residents encounter public data. The publication date is June 10. The editorial promise is to show what common city measures mean, how records are produced, and where numbers cannot answer a public question alone.

Ten weeks out: build the lineup

The lineup includes a reported feature on building permits, a profile of a city statistician, a visual explanation of transit reliability, a guide to reading an annual budget, an essay about missing neighborhood data, and three short departments. Each item has a different reader job and evidence plan.

For one digital companion, the team studies Poynter's account of a multiplatform production workflow, which describes scripts, shared feedback, a production checklist, scheduled roles, and platform distribution. Civic Measure uses that operational example to create its own assignment and approval fields; it does not copy the format or subject.

The calendar gives the digital companion its own script, visual assets, review owner, accessibility work, release time, and promotion package. It does not treat the piece as a smaller copy of the print feature. The print and digital items share reporting where appropriate, but each has a separate definition of ready and a separate final check.

Eight weeks out: record dependencies

The permits feature depends on a fictional May 12 city release. The calendar records the issuer, expected time, data period, method page, backup source, go decision, and latest useful date. The editor assigns a background version that can proceed if the release slips.

The real Census Bureau economic indicators calendar demonstrates why planners should record both latest and next releases and follow the specific program's methodology. The fictional magazine applies that lesson to its invented city source without claiming federal data support its local findings.

Six weeks out: draft the flatplan

The team places covers, contents, masthead, section openers, ads, and recurring departments. Features receive provisional pages based on reported scope and visual needs. The budget feature gets six pages, while the transit visual receives eight. Page position and editorial status remain separate fields.

Four weeks out: make a go decision

The city delays the fictional permits release by nine days. The background reporting is strong, but the issue would reach the printer before adequate verification. The editor moves the permits feature to digital publication after the release and brings in a fully checked four-page backup about public meeting records. A two-page department expands with an annotated document already cleared for use.

Two weeks out: control page changes

The replacement alters two section starts and one ad adjacency. The production editor updates folios, contents, page references, image list, and printer plan. No one labels the backup as a late draft because its status was tracked independently from its page assignment.

After publication

The review finds that the replacement worked, but too many editing hours were reserved for the delayed feature after the go decision. For the next issue, a hold decision automatically releases scheduled copy and design capacity. The managing editor owns the rule and will compare unused hours after one cycle.