A small campaign can become messy before a single asset is published. A local tour operator preparing posts during a policy-sensitive season may have a useful topic and a deadline, yet the source facts, audience question, and approval standard live in different notes. Here, the real problem is to keep publishing decisions tied to current sources rather than remembered limits while keeping official guidance, date checked, account status, scheduled actions, access list, risk owner, and pause procedure visible. The useful work begins before generation. We will approach the assignment through visual explanation, where the operational goal is to turn an abstract growth question into a comparison people can inspect. Each output will come from the same brief, but each platform will receive its own edit.

Translate the query into an observable audience decision. A person entering why Instagram accounts get banned is likely under time pressure, but speed does not remove the need to distinguish evidence, examples, and unknowns. The campaign should help that person keep publishing decisions tied to current sources rather than remembered limits. Search language is context, not a slogan. Use the supplied phrase once in a search-intent note. Elsewhere, write naturally about promotion, publishing, account care, measurement, or support, and avoid guarantees. The reader may want one cause, but an article should not diagnose a particular case from a generic phrase. Distinguish documented notices, observable activity, content or rights questions, access history, and unverified theories. Platform decisions require case-specific evidence. Direct editors to current official material without inventing enforcement triggers.

A workable brief answers the questions that otherwise return during revision. State who needs help, what single decision should change, what content must be produced, and what evidence exists. Put official guidance, date checked, account status, scheduled actions, access list, risk owner, and pause procedure in a source table for a local tour operator preparing posts during a policy-sensitive season, with confirmed, pending, and illustrative statuses. Add a do-not-say list. Specify voice as calm, direct, and willing to state uncertainty. Record formats, ratios, clip length, publishing window, owners, and separate factual, editorial, visual, security, and final sign-offs.

Treat copy work as controlled expansion and compression. Draft a compact core explanation from the approved fields, produce three genuinely different routes, select one, and only then adapt it into headlines, a feed caption, carousel panels, and narration. Use a review marker when support is missing. An illustrative source ledger with confirmed, pending, and example-only rows is a teaching device, not observed user data. Remove repeated conclusions and make each paragraph contribute a criterion, action, example, or risk.

An image prompt should describe what the viewer learns first and what comparison follows. For current-rule verification and account safety, an illustrative source ledger with confirmed, pending, and example-only rows gives the design a concrete job. State camera distance or diagram view, layout, focal object, restrained palette, background complexity, light, ratio, mobile crop, and empty text zone. Request structural alternatives instead of color swaps. Inspect hands, objects, interface geometry, stray characters, logos, borders, shadows, repeated elements, contrast, and screen-size reading order.

Design phone-first. Test the leading line, focal object, subtitle size, contrast, and safe zones at a narrow width before adding secondary material. Small screens expose weak hierarchy quickly. Keep the first frame understandable without sound and reserve clean space for manually typeset text that survives interface overlays.

Adapt each format from the approved core message. A text-led platform can retain reasoning as a compact thread; an image-led feed needs a legible first panel and contextual caption; a carousel assigns one decision to each slide; vertical video shows the difficulty in its first two seconds with phone-safe subtitles; a longer video can preserve the full example and source note. Change structure before wording. Community posts should ask a specific feedback question. Do not publish identical titles, captions, and scripts everywhere.

Storyboard one question in five beats: real difficulty, information to collect, one illustrative example, a human check, and the next decision. Use an illustrative source ledger with confirmed, pending, and example-only rows throughout. Put voiceover, on-screen text, shot direction, duration, source or assumption, and review note in separate columns. Let motion demonstrate the method. Generate visual fragments and assemble them manually. Check spelling, continuity, changing objects, warped interfaces, subtitle accuracy and safe areas, pace, pronunciation, volume, first and last frames, and comprehension with sound muted.

Use a human checklist that separates correctness from polish. The factual pass verifies sources, dates, policy language, service claims, examples, quantities, and account-access assumptions. The editorial pass checks audience fit, restrained voice, repeated wording, ambiguity, cultural meaning, accidental imitation, and unsupported outcomes. Open the real export rather than trusting the prompt. The visual pass covers typography, characters, icons, hands, screens, edges, crop, safe areas, contrast, and reading order; the video pass covers continuity, subtitle accuracy, rhythm, pronunciation, volume, ins刷粉 sound-off comprehension, and silent playback.

The weak points of AI are specific enough to plan around. Text can fabricate policies, rely on stale advice, overstate safety, confuse correlation with cause, imitate recognizable brands, or turn a hypothetical test into a result. It may also produce repetitive structure and inconsistent terminology across formats. Images can create broken lettering, impossible hands, misleading interfaces, and duplicate objects; clips can lose continuity or caption accuracy. Confidence does not establish provenance. Human reviewers should verify sources, reconcile assets, replace raster text, and approve final exports.

The finished set should feel coordinated rather than cloned. A local tour operator preparing posts during a policy-sensitive season can move quickly by anchoring every format to one audience problem, source ledger, voice, and labeled example. Keep the source stable while presentation changes. When official guidance, date checked, account status, scheduled actions, access list, risk owner, and pause procedure remain visible and an illustrative source ledger with confirmed, pending, and example-only rows stays hypothetical, the campaign can teach a concrete process without promising a result. Publish only after copy, images, crops, continuity, captions, security boundaries, and silent playback pass human review.