Guides
Factory tour case study checklist: how to plan yours for 2027
Factory tour case study checklist for 2027 planning helps U.S. sites define scope, collect credible evidence, state limits, and publish useful findings.
What to take away
- Decide the question and intended decision before collecting material.
- Keep context, evidence, results, and limitations in separate fields.
- Use the checklist to make a case study reviewable, not merely attractive.
A case study is easier to trust when its boundaries are clear. Use this factory tour case study checklist before a pilot, seasonal change, access project, or interpretation update. It keeps the team focused on what can be documented and what still needs testing.
What 2027 changes
A 2027 factory tour season is planned before the year starts. Dates, budget rounds, and briefing versions are often set months before opening, so the evidence window closes earlier than the publication date. A typical sequence:
- Set the question, baseline period, and evidence cut-off before the season.
- Run the pilot and collect the sources during it.
- Draft the findings, sign the boundary, and name the review date before opening.
Adjust these weeks to your own booking cycle.
Begin with a defined purpose
Write one sentence that names the decision this work should inform. For example: "Should the site keep the new timed-entry briefing for summer weekends?" That is much more useful than a general goal to improve visitor experience.
The CDC's guidance on evaluation questions explains that questions should fit the purpose, intended use, available resources, and the program's stage. Apply that discipline here. A question about visitor flow needs a different record than a question about guide training.
Before collecting evidence, write down who will use the finding and what decision they can make. The Administration for Children and Families case-study evaluation guide describes defining a case and its purpose as part of evaluation work. A small heritage site can apply that practice by limiting the record to facts that help answer the stated decision.
The factory tour checklist, field by field
Factory tour case study checklist
- Purposedecision, audience, time frame
- Scoperoute, dates, version, exclusions
- Evidencetickets, notes, feedback, photos, interviews
- Findingswhat changed and what is supported
- Limitsmissing data, small samples, concurrent changes
| Checkpoint | What to record | Done when |
|---|---|---|
| Purpose | The decision, audience, and time frame | A manager can explain why the case exists |
| Scope | Route, dates, program version, and exclusions | Readers know what was and was not observed |
| Evidence | Ticket data, notes, feedback, photos, or interviews | Each source has an owner and collection date |
| Findings | What changed and what the record supports | Claims match the evidence available |
| Limits | Missing data, small samples, concurrent changes | Gaps are listed |
Print the table on one page so a reviewer can sign the same sheet.
A completed example makes the fields concrete. The case below covers a 15-minute timed-entry briefing on a Saturday factory tour, and the entries are illustrative.
| Checkpoint | Completed entry: timed-entry briefing |
|---|---|
| Purpose | Decide whether the briefing stays on Saturday tours |
| Scope | Assembly route, June to August, briefing version 3, no school groups |
| Evidence | Timed-entry scans, two guide logbooks, 10 to 15 visitor interviews |
| Findings | Late arrivals fell across the observed Saturdays, with no comparison group |
| Limits | One site, one season, one guide change mid-summer |
A guide-training version of the same case would swap the scans for session attendance and a trainer's sign-off sheet.
Gather only what answers the question
It is tempting to save every document. Start smaller. If the question concerns a revised welcome talk, retain the script version, dates used, attendance, staff notes, visitor comments, and any access or weather events that affected the tour. Do not present a general attendance increase as proof that the talk caused it unless the comparison supports that conclusion.
Use this short sequence:
- Identify the baseline period.
- Name the change being examined.
- Choose two or three evidence types.
- Assign one person to maintain the record.
- Schedule a review before publication.
If conversations are included, prepare brief open prompts and record the context of each response. The Smithsonian oral-history guidance recommends simple questions and prepared topics rather than leading people toward a preferred answer. Do not treat one quotation as a result for all visitors.
Check the draft for honest language
Read the completed draft aloud and circle words such as "proved," "always," and "every." Replace them with the specific result. A sentence such as "the pilot received fewer late-arrival questions on four observed Saturdays" tells readers more than a broad success claim.
Final factory tour publication check
Before posting, confirm that a photo has a credit, permissions cover quotations, numbers have a source note, and the conclusion distinguishes observation from interpretation. A useful factory-tour case study leaves the next site with a method to test, not an unsupported promise.
Keep the evidence log with the final draft. The National Archives records-management FAQ index provides general information about records that can be found and understood later. It is not a project retention schedule, but it supports labeling the source, date, version, and owner behind each claim.
Sign off on the study boundary
Before publishing, name the review date and the person who checked the final evidence. A credible checklist records both the available material and what the case cannot show.
Save the signed checklist with the project file.
Common questions
How many evidence sources should a short case study use?
Use enough to answer the stated question. Two or three complementary sources are often more useful than a large unsorted file collection.
For a seasonal change at one site, choose sources that cover the same weeks: one count, one staff record, one visitor view. For interviews, a typical target is ten to fifteen responses, or fewer once the answers repeat.
Should a checklist include visitor names?
No. Use aggregated notes or consented quotations, and remove personal details that do not serve the case.
Can this checklist be used after a program ends?
Yes. It is especially useful for reconstructing what records exist and what future projects should capture from day one.
