Develop a Microdrama Story Bible and Episode Arc

What a story bible needs to answer

A story bible is the compact agreement behind a serial: who the audience follows, what they want, what blocks them, what rules govern the world, and what question can sustain the planned arc. It should contain the premise, audience, tone, character wants and tactics, relationship map, season movement, episode summaries, recurring locations and visual anchors. Add a production note for any fact, product claim or reference that needs approval.

For The Last Table, Lina wants to sell the family restaurant before it becomes a larger burden; Wei keeps reserving one last table because he believes someone important will return. The season question is whether they can decide what the restaurant means to them before it closes. The story bible must explain why both wants matter, not decide that one person is right. The getting-started guide helps sharpen the premise; the character-consistency guide carries the bible into visual references.

The film story and script structure guide explains how to connect that dramatic question to a scene sequence.

Map an arc as actions, not personality labels

Give each main character an outward want, a tactic, a mistaken belief and a decision that can change. Lina is brisk and practical because she believes clear numbers will protect her from loss. Wei uses ritual because he believes the familiar table can keep family connected. Their arcs move through choices: Lina signs nothing in the opening; Wei delays the conversation; later, each gives the other new information; finally, they consider the future together.

For every episode, note what each character knows, what they conceal, what they ask for and what they do when refused. The visual side should be observable: Lina stops sorting receipts when she hears a name; Wei closes the reservation book rather than answering. The costume anchors stay the same unless the passage of time justifies a change. For a contrast in physical storytelling, see how Last Ferry turns rivalry into a decision; for continuous character identity across shots, use the scene-state record.

Build a season arc with different kinds of change

Do not repeat the same episode beat with a new secret each time. Escalate the cost, change the alliance, reveal a fact that recasts an earlier choice, or let a character reach a point where the old tactic fails. A practical grid has one line per episode and columns for A-plot change, character knowledge, relationship shift, visual anchor and end question. Each episode should have its own movement and contribute to the season’s answer.

Give the season a middle as well as an opening and finale. A midpoint can reveal the cost of the original plan, expose a character’s mistaken belief or force the pair to work together. Later episodes should follow from that consequence; they should not reset the relationship to its initial state. A concise grid makes that progression easier to review than a long prose synopsis alone.

Use the first-episode walkthrough to test the opening. Here, track the consequences across the season: what a discovery costs, which tactic stops working and what the next episode must change.

Translate the arc into a shootable scene

Turn episode summaries into scenes that can be seen and heard. For each scene, identify the goal, obstacle, new information and exit condition. Then write what changes in the room: who arrives, which object moves, what question goes unanswered, where a character looks and what choice ends the beat. This keeps a short episode from becoming dialogue-heavy explanation.

1. Opening state: Lina lays the sale form beside the reservation book and asks Wei to sign.
2. Pressure: Wei says a final booking is expected, but Lina cannot read the name.
3. New information: the caller recognises a family detail Wei has not shared.
4. Exit choice: Lina folds the form and asks Wei to answer on speaker.

Storyboard the positions, handwriting, phone and reaction targets before writing extra explanatory lines. For close-up and wide-frame choices, consult the aspect-ratio planning guide.

Before dialogue polish, check that each scene either changes knowledge, creates a decision or alters the relationship. If two scenes do the same work, combine them or give the second a new consequence. Note the opening image and exit action for each episode so storyboard panels can support the arc rather than become a sequence of attractive but disconnected frames.

Track clues, knowledge and visual evidence

For a mystery or family secret, keep a clue ledger: what the audience sees, what each character knows, when the fact is introduced, and what later scene pays it off. Separate known truth from a character’s interpretation. If the reservation name appears in two shots, preserve its spelling and legibility. If Wei knows the caller, his reaction should begin before he explains why.

Continuity notes should include dialogue, props and body state. Track the reservation book, sale form, phone, chair positions, hand occupancy, gaze and emotional state across cuts. A later episode should not make an earlier prop appear in a different place without an action or time change. For a formal continuity sheet, see the character shot-review method; the period mystery in The Jade Ledger shows how a visible clue drives a reversal.

Give the buyer a clear story and approval brief

Bring the central story question, the two leads’ incompatible wants and the change the ending must earn. If a product affects a decision, identify the fact the writer can rely on before dialogue is drafted.

Our AI microdrama production in Singapore service sets out approvals from treatment to representative scene. Keep feedback tied to the current decision: whether the premise is clear, whether the character turn is earned, or whether the scene makes it visible.