Plot diagram template: explain what changes at the turning point

The wind scatters the sign, but the story's problem is still unsolved. Ada's decision to move the reading booth to a sheltered porch changes what she can do next.

A plot diagram becomes useful when the learner explains that change, rather than putting the most dramatic sentence at the top of a triangle.

Pair each plot stage with an event and a reason. The worked example keeps a short story beside its diagram and lets you compare two turning-point explanations.

A six-event story mapped to five stages, with a turning-point explanation
A six-event story mapped to five stages, with a turning-point explanation
Open the full example ↗

Read the complete short story first

This original story is fictional:

Event What happens
E1 Ada sets up an outdoor reading booth for the neighborhood fair.
E2 A gust scatters the paper sign before the booth opens.
E3 Ada tapes the sign back up, but the next gust pulls it loose.
E4 With the host's permission, Ada moves the booth onto a sheltered porch.
E5 Ada fixes the sign inside the porch, where it stays in place.
E6 The booth opens, and visitors stop to read.

E4 includes permission because the story supplies it. Learners should not have to invent that approval to explain the move.

NCTE's Plot Diagram resource describes mapping events with a triangular plot structure, including rising and falling action. Use the structure as a way to discuss how this story works; a different narrative may need a different account of its turning point.

Map events to their jobs in this story

One supported model is:

Stage Event Reason
Exposition E1 Establishes Ada, the fair and her goal.
Rising action E2–E3 Introduces the wind problem and an attempt that fails.
Climax or turning point E4 Ada changes location with permission, giving the booth shelter.
Falling action E5 The new location allows the sign to stay up.
Resolution E6 The booth opens and the goal is reached.

This mapping groups two events in rising action. There is no need to invent a sixth stage just because the story has six event IDs. Conversely, a longer story may need several events under one stage.

Compare two turning-point explanations

Select E2: the sign scatters in the example, then press Read this interpretation. The discussion note explains why the event matters: it introduces the obstacle. It does not yet provide a new way to keep the booth open.

Select E4: Ada moves to the porch and press Read this interpretation again. That note connects the decision to E5: the sign remains in place after the move. The model therefore treats E4 as the turn from repeated failure toward a workable setup.

The page presents these two authored explanations for discussion. It does not assign a universal literary score to a learner's answer. A learner proposing another turning point should cite the event, explain what changes, and account for the events that follow. Ask those questions before deciding whether the interpretation fits.

Keep the story's wording beside the diagram. If a learner calls E3 a successful repair, the phrase “pulls it loose” gives you a precise sentence to revisit.

Copy this prompt with your own story

Create one complete HTML plot diagram for this original or
permitted story: [paste full story with stable event IDs].
Audience and plot-stage terms taught in class: [enter].

Show the full story beside a plot diagram and a text table.
Give each stage an event reference and an explanation of its
role. Use the supplied story only. Do not invent permission,
motives, outcomes or missing events to make the diagram fit.
Allow more than one event under a stage. Mark any proposed
interpretation as a worked model for discussion.

Provide two clearly labeled turning-point choices drawn from
the text. Show a separate authored explanation for each choice,
including what changes and what later event supports the
interpretation. Give a blank learner explanation for human
review. Do not automatically grade free prose or insist that
every story has the same structure.

Keep event IDs stable. Use visible keyboard focus, readable
type and a stacked layout at 360px. All CSS and JavaScript
must stay in the file, with no external assets or submission.
Keep typed work in the current page only and ask before reset.
Return the complete HTML and any unresolved story questions.

Read the model against the ending before using it. Each reason should explain the supplied event's role, without rewriting the story to support the chosen label.

Revise the explanation after discussion

If “the important event” leaves the class unsure what to look for, open the prepared HTML in NOS and change the instruction to “Name the event that changes how Ada can solve the wind problem, then cite what happens afterward.” Use visual editing mode for that wording change and keep the six-event story available for comparison.

Try the revised question with E2 and E4 again. Ask learners to explain the difference between the obstacle appearing and Ada finding a workable response.

Keep reading