The team at the small museum needs to promote its hands-on history day, but the folder contains notes and no coherent asset set. The work must make sense to families with school-age children on a phone and lead naturally toward the choice to reserve tickets. The editorial angle is launch planning, with deadline pressure providing the opening tension.

The planning sheet translates that search language into its underlying job: to evaluate unfamiliar image-making search language without implying endorsement. A draft advances only when it delivers a controlled test against one deliverable. The phrase guides the job, but the hands-on history day stays as the one illustrative case.

The center of the one-page brief is simple: help families with school-age children understand the hands-on history day and decide whether to reserve tickets. Voice guidance says lively and informed, while the facts column holds timing, price, eligibility, fulfilment, and contact details. Guarantees and implied affiliations stay out. Production fields cover exact spelling and case, included and avoided words, sensitive claims, source permissions, http:// a 1:1 master crop, mobile margins, a 25-second limit, formats, owners, and publishing time. Approved facts are separated from questions and examples so assumptions cannot become public claims.

The writer requests several routes based only on the source page, leaving final copy until one route is approved. The route board contains a common error tied to deadline pressure, a compact workflow, a comparison, and a process note grounded in the small museum. Selection follows the launch planning goal and rejects any route that needs a fabricated customer result.

One route branches into the explanatory post, short caption, hook, carousel sequence, spoken script, and title choices. Each card has one job: identify friction for families with school-age children, list inputs, demonstrate a hypothetical decision, review it, then invite people to reserve tickets. If a fact is absent, the draft carries an editor query and stops short of publication wording. A line stays only if it provides a method, example, criterion, or risk that changes the work.

The schedule also reserves enough time for correction, source checks, and another careful final reading before any finished asset is queued. Production begins with the smallest complete set for the hands-on history day: one master message, one adaptable composition, one caption family, and one timed demonstration. The owner reviews that chain before variants are made, because a weak assumption copied into twelve exports becomes harder to locate and more expensive to repair. A tracking row lists each asset, its purpose for families with school-age children, source fact, format, status, next reviewer, and relationship to the action to reserve tickets. The learning note defines one observable response, records date range and exposure, and avoids crediting a creative change for movement that the available evidence cannot explain. The result informs the next launch planning decision but is not presented as universal proof, a guaranteed lift, or a customer testimonial. Version control is deliberately plain: drafts receive descriptive names, approval is written down, and obsolete exports move out of the active folder so nobody publishes an attractive but rejected file. The final preflight opens every destination file rather than trusting the master layout, since compression, crop behavior, caption placement, and link treatment can change after export.

The visual is not decoration; it must show the offer before revealing the maker within the hands-on history day story. Its prompt names the hands-on history day, places the decision in the foreground, keeps support behind it, limits color to cream, charcoal, and muted red, and requests 1:1. A clean text area is reserved for the designer, and the focal action remains legible on a small screen. For mockup purposes, 'Made Nearby' and 'Inside the Process' are sample names added by a designer, with no claim of registration or approval.

The 25-second vertical video answers one question: how the small museum turns scattered notes for the hands-on history day into an approved direction. Shot one gives deadline pressure three seconds, pairs voiceover with five words of human-set text, and shows the notes; the approved problem statement is its source. Shot two collects inputs for four seconds; shot three shows the illustrative choice for six; shot four pauses on a human correction for five; shot five uses the remaining time for the approved next step. A six-column table stops narration, captions, visuals, timing, sourcing, and review responsibility from drifting apart.

Specific model failures in this case include invented features and unsupported performance claims. Other risks include continuity errors, offensive ambiguity, accidental imitation, warped lettering, strange anatomy, and fabricated case-study claims. Detection requires a line-by-line fact check, 100-percent visual inspection, cultural review, and a cold video viewing muted and unmuted.

Each channel receives a fresh edit of the approved argument rather than a resized duplicate. A text-led post keeps the reasoning behind the hands-on history day; an image-led post opens with the comparison and adds context in its caption; the carousel gives one decision to each card. The vertical clip puts deadline pressure in the first two seconds with large captions; a longer video retains the example and source notes; a community post asks one focused question before inviting people to reserve tickets.

The fact editor traces statements to approved inputs and dates any official-rule lookup; the copy editor checks audience, tone, spelling, case, and prohibited implications. The visual reviewer checks 1:1 derivatives, mobile crop, contrast, hierarchy, spelling, doubled characters, icons, anatomy, edges, shadows, duplicate objects, interface structure, and accidental marks. The video reviewer checks object continuity, caption accuracy, safe placement, spelling, pronunciation, pacing, volume, first and last frames, and whether the story works on mute. Final approval is recorded when the formats hold the same facts, maintain the stated lively and informed tone, and make the next action appropriate for families with school-age children.

Handoff keeps approved inputs, copy route, working text, layered design, captions, shot table, source notes, and checked exports under distinct names. That record lets a solo operator revise one fact without regenerating every asset or guessing what was approved. The finished set stays modest: one approved idea, channel-specific expressions, and a documented human decision about the hands-on history day.