Case study: planning a fictional city-data magazine issue

What to take away

Civic Measure is a fictional monthly. Its June 10 issue runs 72 pages on how residents meet public data. The editorial promise: what common city measures mean, how records get made, and where a number cannot answer a public question by itself.

Ten weeks out: build the lineup

The lineup carries six named items and three short departments. 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 on missing neighborhood data. Each item gets its own reader job and evidence plan.

For the digital companion, the team studies Poynter's account of a multiplatform production workflow. That piece describes scripts, shared feedback, a production checklist, scheduled roles and platform distribution. Civic Measure borrows the assignment and approval fields. It does not copy the format or the subject.

The companion gets its own script, visual assets, review owner, accessibility work, release time and promotion package. It is not a smaller copy of the print feature. Print and digital share reporting where useful, but each carries a separate definition of ready.

Eight weeks out: record dependencies

The permits feature depends on a fictional May 12 city release.

The real Census Bureau economic indicators calendar shows why both latest and next releases belong on the wall, and why the specific program's methodology matters. Civic Measure applies that lesson to its invented city source. It never claims federal data supports its local findings.

Six weeks out: draft the flatplan

The team places covers, contents, masthead, section openers, ads and recurring departments. Features get provisional pages from reported scope and visual need. The budget guide takes six pages. The transit visual takes eight. Page position and editorial status stay in separate columns.

Four weeks out: make a go decision

The city pushes the fictional permits release back nine days. Background reporting is strong. The issue would still reach the printer before the claims could be verified properly.

The editor moves the permits feature to digital, to run after the release. A fully checked four-page backup on public meeting records comes in. A two-page department expands with an annotated document already cleared for use.

Two weeks out: control page changes

The swap moves two section starts and one ad adjacency. The production editor updates folios, contents, page references, the image list and the printer plan. Nobody labels the backup a late draft, because its status was tracked apart from its page assignment.

Worked example: what the hold released

The permits feature had reserved three editing days, one design day and a photo shoot. Once the hold was made, those hours went to the backup and to the budget guide's fact-check.

The review found the swap worked, but too many hours stayed reserved for the delayed feature after the go decision.

For the next issue, a hold decision releases scheduled copy and design capacity on the same day. The managing editor owns that rule and will compare unused hours after one cycle.

Common questions

Is Civic Measure real?

No. The magazine, city, schedule, stories and release are all fictional. Use the structure, not the specifics.

Why not run the permits feature with preliminary information?

Its reader value depended on the delayed records. Without them the piece could not deliver what the headline promised, and there was no time left to verify the claims.

Why was the backup usable at four weeks?

It had approved copy, verified claims, cleared media, a known length and a clear role in the issue. Those four things are what a definition of ready is for.

What did the review change?

It tied a hold decision to staff capacity. The next cycle tests whether hours reserved for a held feature actually come free.