The team at the repair cafe needs to promote its volunteer repair day, but the folder contains notes and no coherent asset set. Because it must reach owners of broken household items, every asset has to explain the offer before asking people to register an item. The editorial angle is brand voice control, with an overlooked preparation step providing the opening tension.

In the source brief, the assigned search phrase represents a need to prepare a small or soft source image for several placements. A draft advances only when it delivers natural edges at the required size. The phrase guides the job, but the volunteer repair day stays as the one illustrative case.

The working brief fits on one page: the repair cafe is promoting the volunteer repair day to owners of broken household items, and the single communication goal is to register an item. Tone is resourceful and calm. Required inputs are approved wording, timing, cost, eligibility, delivery method, and contact path; unsupported results and false urgency are prohibited. Constraints specify spelling, mandatory and avoided terms, source permissions, the 9:16 ratio, safe zones, 30 seconds, file formats, responsible people, and release time. Three labels matter: confirmed, verify before use, and illustrative only.

The visual is not decoration; it must explain a before-and-after choice without exaggeration within the volunteer repair day story. Prompt fields cover the volunteer repair day, spatial relationship, dominant focus, plain setting, the palette navy, pale blue, and restrained yellow, believable side light, and 9:16 output. No essential detail enters the mobile crop or caption-safe margins; real copy is added later as an editable layer. 'Small Steps' and 'Inside the Process' are hypothetical options for internal layout testing, not claims of availability or proof.

The assignment's failure watchlist includes invented texture, doubled lines, and oversharpening. Other risks include continuity errors, offensive ambiguity, accidental imitation, warped lettering, strange anatomy, and fabricated case-study claims. A second reviewer compares each output with the source, inspects artwork at full size, and reads the script without prompt history.

A vertical script capped at 30 seconds shows one decision, from loose notes about the volunteer repair day to a reviewed asset. Shot one gives an overlooked preparation step three seconds, pairs voiceover with five words of human-set text, and shows the notes; the approved problem statement is its source. The next four seconds gather inputs, six compare hypothetical options, five show a reviewer correcting one flaw, and the final beat states the action. Each shot row keeps narration, screen copy, camera instruction, timing, evidence status, and reviewer distinct.

The schedule also reserves enough time for correction, source checks, and another careful final reading before any finished asset is queued. The minimum viable set for the volunteer repair day contains a master argument, a flexible visual frame, related caption copy, and a timed demonstration of the same decision. Variants wait until the owner approves the chain; otherwise one unsupported assumption can spread through many exports and consume the review budget. For every item, the tracker names its job, evidence, format, current state, responsible reviewer, and place in the route from owners of broken household items to the choice to register an item. After a small release, the owner compares observable signals chosen in advance, such as completed inquiries or saves, while keeping exposure and time period visible. What the team learns is limited to this brand voice control test; it does not become a guarantee, invented success story, or broad claim about every audience. 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.

Drafting begins with editorial routes so the team can choose an argument before polishing sentences. The route board contains a common error tied to an overlooked preparation step, a compact workflow, a comparison, and a process note grounded in the repair cafe. Routes are scored for fit with brand voice control, evidence, visual clarity, and whether they lead naturally to register an item.

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 owners of broken household items, list inputs, demonstrate a hypothetical decision, review it, then invite people to register an item. Unknown details are returned as questions rather than filled with plausible specifics. The copy earns space by helping the reader act, judge, compare, or avoid a known failure.

Each channel receives a fresh edit of the approved argument rather than a resized duplicate. A text-led post keeps the reasoning behind the volunteer repair day; an ai image enhancer-led post opens with the comparison and adds context in its caption; the carousel gives one decision to each card. A phone-first clip names an overlooked preparation step within two seconds, a longer cut includes the review, and the community version asks for focused feedback tied to the choice to register an item.

First, a person verifies claims and changing rules with current primary sources, notes the date, and confirms that wording fits the audience and stated voice. At full size and on a phone, visual review covers spelling, repeated letters, icons, hands, object count, edges, shadows, interface logic, stray marks, contrast, reading order, safe zones, and every crop from 9:16. Motion review compares shots for continuity, verifies captions and spelling, checks pronunciation and levels, tests pace and safe areas, inspects opening and closing frames, and repeats the viewing muted. The owner approves only when every format preserves the facts, keeps the voice resourceful and calm, and gives owners of broken household items a credible path to register an item.

Handoff keeps approved inputs, copy route, working text, layered design, captions, shot table, source notes, and checked exports under distinct names. A late correction can flow through the set without forcing the owner to reconstruct which draft supplied a claim. The repair cafe finishes with connected assets that can be checked and changed without pretending automation supplied judgment.