Publication day is close, and the local theater has only scattered notes for its rehearsal-room preview. Because it must reach occasional theatergoers, every asset has to explain the offer before asking people to book the preview. The producer organizes the assignment around short-video scripting and uses a mobile readability problem as the first point of recognition.

The planning sheet translates that search language into its underlying job: to repair or adapt an existing campaign photograph. A draft advances only when it delivers consistent light, geometry, identity, and editable finishing. That reading keeps the story tied to the rehearsal-room preview rather than turning it into a tool list.

Drafting begins with editorial routes so the team can choose an argument before polishing sentences. The route board contains a common error tied to a mobile readability problem, a compact workflow, a comparison, and a process note grounded in the local theater. The short-video scripting objective favors the route with a visible action, a defensible claim, and an honest path to book the preview.

The working brief fits on one page: the local theater is promoting the rehearsal-room preview to occasional theatergoers, and the single communication goal is to book the preview. Voice guidance says playful and candid, while the facts column holds timing, price, eligibility, fulfilment, and contact details. Guarantees and implied affiliations stay out. The sheet records capitalization, prohibited language, claim sensitivity, reference rights, a 1:1 frame, phone-safe areas, a 32-second runtime, delivery formats, deadline, and reviewers. Confirmed facts, open questions, and illustrative examples occupy separate columns.

The approved route expands into one explanation, a caption, a two-line hook, a five-card carousel, a voiceover, and three headline options. The five cards move from audience problem to required facts, illustrative choice, human check, and the action to book the preview. Unknown details are returned as questions rather than filled with plausible specifics. Sentences without a method, example, decision rule, or warning are removed.

A vertical script capped at 32 seconds shows one decision, from loose notes about the rehearsal-room preview to a reviewed asset. The opener uses three seconds: spoken context about a mobile readability problem, a short caption, and a tight shot of source notes. The middle assigns four seconds to inputs, six to the example, and five to a visible check; closing seconds carry the confirmed next step. Each shot row keeps narration, screen copy, camera instruction, timing, evidence status, and reviewer distinct.

For the image route, the single job is to make the deadline legible without generated type. Prompt fields cover the rehearsal-room preview, spatial relationship, dominant focus, plain setting, the palette terracotta, sand, and dark brown, believable side light, and 1:1 output. A clean text area is reserved for the designer, and the focal action remains legible on a small screen. For mockup purposes, 'Quiet Start' and 'Inside the Process' are sample names added by a designer, with no claim of registration or approval.

Generated material can fail through warped objects, changed faces, and mismatched shadows. Other risks include continuity errors, offensive ambiguity, accidental imitation, warped lettering, strange anatomy, and fabricated case-study claims. An ai photo editor catches them by tracing claims to the source sheet, enlarging every image, and watching the final cut cold with sound off and then on.

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 rehearsal-room preview: one master message, one adaptable composition, one caption family, and one timed demonstration. Variants wait until the owner approves the chain; otherwise one unsupported assumption can spread through many exports and consume the review budget. A tracking row lists each asset, its purpose for occasional theatergoers, source fact, format, status, next reviewer, and relationship to the action to book the preview. 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 short-video scripting 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. Each exported derivative is opened in context before release, catching platform compression, unexpected cropping, unsafe captions, broken links, or a reordered message that the working file did not reveal.

Platform adaptation begins from the approved message, not from pasting one caption into different boxes. On a text feed, the producer explains the choice behind the rehearsal-room preview. An image feed foregrounds the visual task, while the carousel distributes the reasoning. A phone-first clip names a mobile readability problem within two seconds, a longer cut includes the review, and the community version asks for focused feedback tied to the choice to book the preview.

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. 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. A cold reviewer watches for changing objects, warped text, caption errors, unsafe margins, mispronunciation, uneven pace or audio, weak boundary frames, and lost meaning without sound. Sign-off follows when post, image, and clip agree on evidence, keep the playful and candid manner, and direct occasional theatergoers honestly toward the choice to book the preview.

The delivery record shows the path from confirmed material through approved message, editable design, timed script, and final files. That record lets a solo operator revise one fact without regenerating every asset or guessing what was approved. The local theater finishes with connected assets that can be checked and changed without pretending automation supplied judgment.