Case study: a fictional magazine issue through production

What to take away

This case is fictional and describes no real publication or contributor.
The issue plan gives every story a different reader job.
Reporting and visual risks are logged before drafting.
A late factual change returns through affected review gates.
The post-issue review produces assigned workflow changes.

Fictional quarterly magazine Field Desk plans a 64-page issue called "After Dark" about how a city works overnight. The editor wants reported depth, practical access, and strong documentary photography without turning night workers into scenery.

Week 1: issue architecture

The team defines four distinct features: a reported account of overnight transit maintenance, a profile of a bakery production manager, a visual essay on street-cleaning crews, and a service piece about public services available after midnight. Departments cover books, food, and reader letters without repeating the feature angles.

For research planning, the desk uses the Journalist's Resource source evaluation guide as a prompt to check author credentials, primary versus secondary material, publisher reputation, date, purpose, documentation, and corroboration. The guide does not decide which source Field Desk should use, but it supplies questions the editor adds to each reporting check.

Weeks 2 and 3: commissioning and reporting

Each brief names its reader question, length, editor, reporting expectations, visual plan, rights needs, delivery date, and possible harm. The transit writer needs agency records, worker interviews, and on-site observation. The bakery profile needs consent for overnight access and a plan that does not expose private employee schedules.

The photo essay receives a shot brief, caption fields, release guidance, and a rule against staging documentary activity. Its editor schedules a mid-reporting review before travel and access costs become fixed.

Week 4: structural edits

The transit draft opens with an atmospheric scene but delays the explanation of why the work affects riders. The features editor moves the service consequence earlier, cuts a repeated history section, and requests one missing maintenance record. The writer revises before copy editing begins.

The service article overlaps with a department page. The team keeps the feature's verified directory and changes the department page to a first-person essay. This preserves two different reader benefits.

Week 5: verification and design

Fact checkers trace names, job titles, shift times, totals, quotations, and historical claims. Designers receive locked copy, approved image selects, captions, credits, rights status, and hierarchy. The cover line is checked against the actual transit finding rather than against an early pitch.

The Columbia Publishing Course brochure describes publishing work across editorial and business functions, including planning, writing, editing, design, audience strategy, promotion, and distribution. Field Desk's schedule reflects that coordination while preserving editorial authority over reported conclusions.

Week 6: late change and proof

The transit agency amends a maintenance total after pages are composed. The editor confirms the new record, updates two body references, a chart, caption, contents teaser, and digital summary, then reruns fact and copy review for those elements. The proof log records the old and new value, source, request time, and approval.

After release

The live digital package and printer advance match the approved proofs. The review finds that photo permissions arrived on time, but the service feature's source packet was incomplete at first draft. The managing editor adds a source-packet acceptance check three days before structural editing and assigns an owner for the next issue.