Guides
Manufacturing museum case study checklist: how editors scope the work
A manufacturing museum case study checklist for editors: define the question, map each claim to a dated source, and state what the record cannot prove.
A case study of a preserved plant earns trust the way a maintenance log does: every entry has a date, a name, and a reason. This checklist covers the fields to fill before drafting and the claim map that keeps the finished article inside its evidence.
What to take away
- Fill the eight checklist fields before writing; a blank field is a missing source, not a writing problem.
- Give every consequential sentence an identifier, a supporting record, the date it was checked, and the limit on what it proves.
- Keep source-backed facts, dated observations, and interpretation in separate sentences so a reader can tell which is which.
- Sample the claim map backward from the conclusion before approval, then correct the headline and caption to match.
- Record gaps in the article rather than smoothing them with confident language.
The eight fields
| Field | What to record | Worked entry |
|---|---|---|
| Question | One narrow decision, condition, or visitor experience | How was the 1928 blowing engine house returned to demonstration running? |
| Scope | Resource, period, and material in or out | Engine house only; 1928 to 1974; no furnace line |
| Evidence | Institutional pages, project records, image credits, dated visits | Condition survey dated 2019-04-11; docent walk-through 2026-06-02 |
| Claim map | Which source supports each factual sentence | See identifier table below |
| Decision path | Options considered, choice made, changes logged | Rebuild versus static display; rebuild approved 2020-01-15 |
| Outcome | What the record verifies, stated no wider | Engine turns under power on scheduled days |
| Limitation | What the case does not establish | Says nothing about furnace line access or other sites |
| Update trigger | Changed record, condition, program, or source | New condition survey, or a change to demonstration hours |
The NPS Preservation Tech Notes index frames its notes as preservation case studies: one problem, one approach, practical detail. Copy that shape. A single engine house does not settle how any other plant should be treated.
Eight Case Study Fields
- Questionone narrow decision or experience
- Scoperesource, period, material in or out
- Evidencedated sources and image credits
- Claim mapsource behind each sentence
- Decision pathoptions, choice, logged changes
- Outcomewhat the record verifies
- Limitationwhat the case cannot establish
- Update triggerchanged record or program
Build the claim map
Give each significant sentence an identifier, then list what backs it, when you checked, and what it cannot prove.
| ID | Sentence claim | Source | Checked | Limit |
|---|---|---|---|---|
| C1 | Engine house built 1928 | Accession record, site archive | 2026-08-14 | Date only; no builder attribution |
| C2 | Rebuild approved 2020 | Board minutes, project file | 2026-08-14 | Approval, not completion |
| C3 | Engine runs on scheduled days | Site program page | 2026-09-01 | Schedule changes; verify before travel |
Three kinds of statement sit in that table, and they must not merge. A source-backed fact says what a record documents. An observation says what a writer saw on a stated date. An interpretation explains why the detail matters.
A photograph of a corroded valve proves nothing about its condition today. The Smithsonian's guidance on collections care makes the point for objects: understand material and condition before deciding anything. For an editor the rule is simpler. Find the record, the accountable institution, or a named expert.
Keep the working file
The National Archives explains that records-management fundamentals preserve information documenting an organization's actions. A museum article is not a federal records program. Retain the source list, research notes, interview permissions, draft date, and correction log in one folder anyway. A later editor can then separate a documented fact from an interpretation.
The National Park Service's museum documentation guidance ties documentation to accountability. That imposes no policy on an independent publication. It supports one habit: name the source, the date, and the limit on every important claim.
Before publication
Sample the map backward from the conclusion. Take the most consequential claim and confirm the cited source actually says what the article attributes to it. Then check the limitation survived into the summary, the image caption, and any list entry.
Drift usually appears in the public-facing language first. A careful body sentence becomes an overbroad headline. Fix the headline, then log the edit.
Budget fields for guides, transport, and insurance belong in the working file too; the cost notes for a case study show how to keep them dated. If the case covers several sites, compare the site options before committing to one question.
Common questions
What is the first case-study decision?
Define one question that the records you can actually reach will answer. If no source speaks to it, the question is not ready.
Why make a claim map?
It stops a broad source from being stretched over a narrow sentence. The map shows, sentence by sentence, what the evidence supports and where it stops.
When should a case study be updated?
Update it when a project record, visitor condition, program, or reliable source changes. The update trigger field names what to watch.
