Guide8+ examplesTemplates

External Conflict: Definition, Examples & How to Write It

Effective external conflict has understandable rules and consequences, responds to the character’s actions, and becomes more difficult in ways connected to the story rather than through unrelated bad luck.

Quick answer

What is External Conflict?

External conflict is opposition between a character and another person, institution, environment, technology, social system, or concrete circumstance that blocks an important goal.

What good external conflict looks like

Effective external conflict has understandable rules and consequences, responds to the character’s actions, and becomes more difficult in ways connected to the story rather than through unrelated bad luck.

  • Define the external force and what it does to block the goal.
  • Give institutions and antagonists motives, constraints, or rules rather than making them abstract evil.
  • Let the protagonist’s attempts change the opposition.
  • Escalate by narrowing time, resources, trust, access, or options.

A practical structure to follow

Use these elements as a decision checklist, not as a rigid formula. The exact wording should still fit the reader, context, and purpose.

  • Define the external force and what it does to block the goal.
  • Give institutions and antagonists motives, constraints, or rules rather than making them abstract evil.
  • Let the protagonist’s attempts change the opposition.
  • Escalate by narrowing time, resources, trust, access, or options.

How to write external conflict step by step

  1. 1
    State the concrete external objective.
  2. 2
    Identify who or what can prevent success.
  3. 3
    Define the rules of that opposition.
  4. 4
    Plan three escalating interactions in which the protagonist’s action changes the next obstacle.
  5. 5
    Tie the climax to mastery, sacrifice, cooperation, or a strategic choice rather than coincidence.
Pattern library

8 External Conflict examples

See all examples →

Read the examples for structure and choices rather than copying surface wording. Notice what stays consistent and what changes with audience or purpose.

Example 1

A courier must cross a flooded district before medicine expires.

Example 2

An employee challenges a policy while the compliance system automatically locks accounts that miss a verification deadline.

Example 3

A climber must descend before a second storm closes the only safe ridge.

Example 4

A community organizer needs council approval while a developer controls the only available access road.

Example 5

A reporter must verify a leak before the source’s temporary credentials expire.

Example 6

A student must complete fieldwork while the archive holding the primary records closes for renovation.

Reusable structure

External Conflict templates

Open template library →

Replace every bracketed field with situation-specific information. A template is a starting structure, not finished copy.

Template 1
Person conflict: [Character] wants [goal]; [opponent] wants [incompatible goal] because [reason].
Template 2
Institution conflict: To obtain [goal], [character] must satisfy/challenge [rule], which creates [cost].
Template 3
Environment conflict: [Hazard] changes [resource/time/access], forcing [new strategy].

Common mistakes to avoid

  • Using weather, villains, or bureaucracy as generic obstacles with no specific mechanics.
  • Letting the opposition remain static while the protagonist keeps trying the same tactic.
  • Adding new antagonists only because the existing conflict has stalled.
  • Making success depend on a last-minute rescue from an uninvolved character.

Final revision checklist

  • Does the opening make the purpose clear quickly?
  • Is every important claim, detail, or example doing a distinct job?
  • Could a reader misunderstand any pronoun, transition, time reference, or instruction?
  • Is the tone appropriate for the relationship and situation?
  • Can you remove repetition without removing necessary context?
  • If the writing contains factual claims, names, dates, quotations, or citations, have you verified them independently?
Frequently asked

Questions about External Conflict

What is External Conflict?

External conflict is opposition between a character and another person, institution, environment, technology, social system, or concrete circumstance that blocks an important goal.

What makes External Conflict effective?

Effective external conflict has understandable rules and consequences, responds to the character’s actions, and becomes more difficult in ways connected to the story rather than through unrelated bad luck.

How do I write External Conflict?

Start with the purpose and reader, then work through the structure in order. Draft for meaning first, check the examples for pattern, and do a final revision for clarity, accuracy, tone, and unnecessary repetition.

What should I avoid when writing External Conflict?

Using weather, villains, or bureaucracy as generic obstacles with no specific mechanics. Letting the opposition remain static while the protagonist keeps trying the same tactic. Adding new antagonists only because the existing conflict has stalled.

If a source behind External Conflict changes, how do I know which other claims or guides need review?

Use the dependency map rather than reviewing the entire site blindly. Identify the exact claim or example that depends on the source, classify the dependency as direct, shared, advisory, or independent, and record why the source changed. Direct dependents should be reviewed immediately when a controlling source is corrected, retracted, superseded, or no longer supports the claim. Shared dependents can be queued by source/claim ID and scope. Replace the source only when the replacement performs the same evidentiary job—or change the claim. Keep the old source/status in the ledger, then propagate the review to templates, examples, and related guides only where that dependency actually exists.

How can editors track a source change for External Conflict without reviewing the entire site?

Use persistent claim, source, and dependency records. Link only the claims that truly depend on a source, then change that source record’s status in the Writing Authority admin when it is corrected, superseded, stale, withdrawn, or retracted. The registry queues the linked claims with a reason code and priority. Reviewers can see the affected guide, inspect the source/dependency IDs, revise or replace the evidence where necessary, and close the queue item after verification. Original site-created examples and templates remain independent unless they contain a real external factual dependency.