Reusable frameworks

11 Portal Description Templates

Start with structure, then replace every placeholder with information that is true, relevant, and natural for your context. These templates are intentionally skeletal so your final writing does not sound mass-produced.

Use the framework

How to personalize a template

A strong portal description gives the reader usable rules without explaining every mystery at once. Appearance, sound, motion, light, temperature, pressure, surroundings, activation, destination clues, and character response should stay consistent with the story’s worldbuilding. The portal should change action or expectation rather than functioning as decorative spectacle alone.

  1. 1
    Choose the template closest to your actual purpose.
  2. 2
    Replace every bracketed field with specific information.
  3. 3
    Delete any sentence that does not belong in your situation.
  4. 4
    Read the result aloud for unnatural transitions or repeated phrasing.
  5. 5
    Verify names, dates, links, facts, and promises before sending or publishing.
Portal Description Template 1
Portal rule card\nOrigin location: [x]\nBoundary/form: [x]\nActivation cue: [x]\nCrossing effect: [x]\nDestination clue: [x]\nReturn rule: [x]
Portal Description Template 2
Crossing sequence\nApproach: [x]\nThreshold contact: [x]\nTransition: [x]\nArrival orientation: [x]\nImmediate consequence: [x]
Portal Description Template 3
Spectacle → function\nGeneric: A glowing portal swirled before them.\nObservable rule: [x]\nEnvironmental effect: [x]\nDecision it forces: [x]\nRevision: [x]
Portal Description Template 4
Continuity audit\nSize/shape: [x]\nWho can perceive/use it?: [x]\nTiming/stability: [x]\nTwo-way or one-way?: [x]\nRule changed later?: [explain]
Portal Description Template 5
Publication-readiness audit for Portal Description: claim/advice/example → [ ]; strongest available source tier → [ ]; important disagreement or uncertainty → [ ]; what would change the conclusion → [ ]; publish now / qualify / revise / hold → [ ]; final verifier or source of truth → [ ].
Portal Description Template 6
Provenance and classification audit for Portal Description: draft statement/example → [ ]; classify as fact / interpretation / recommendation / convention / original example → [ ]; source or internal provenance → [ ]; source date / version / checked date → [ ]; attribution needed → [ ]; recency risk → [ ]; final publishable wording → [ ].
Portal Description Template 7
Source-record and update audit for Portal Description: statement / example → [ ]; external fact, project fact, interpretation, recommendation, convention, or original example → [ ]; controlling first-party / primary source → [ ]; secondary source if used → [ ]; source record / locator → [ ]; date or version checked → [ ]; update trigger → [ ]; publish / qualify / revise / hold → [ ].
Portal Description Template 8
Source-ledger and revision-history audit for Portal Description: claim / recommendation / example → [ ]; source or project record ID → [ ]; source status active / superseded / corrected / retracted / retired → [ ]; claim-level last verified date/version → [ ]; event that triggered recheck → [ ]; correction / withdrawal action → [ ]; reader-facing disclosure needed? → [ ]; what changed and why → [ ]; prior wording/version retained at → [ ].
Portal Description Template 9
Claim/source status audit: Item [claim/source/example] | Status [active / review due / stale / corrected / retracted / superseded] | Controlling source/version [x] | Last verified [date/version] | Stale trigger [x] | Correction severity [0–3] | Reader disclosure [none / note / correction / withdrawal] | Changelog entry [what changed + why].
Portal Description Template 10
Dependency and propagation audit: Claim / example / recommendation [x] | Controlling source / project record [x] | Dependency strength [direct / shared / advisory / independent] | Review trigger / reason code [x] | Needs-review scope [local / direct dependents / cluster] | Replacement source requirements [x] | Carry-forward decision [x] | Propagation targets [x] | Reader disclosure / changelog action [x].
Portal Description Template 11
Persistent editorial registry audit: Topic slug → [ ]; claim UID/key → [ ]; source UID/key → [ ]; dependency UID + strength → [ ]; source status/version → [ ]; open review UID/reason/priority → [ ]; replacement source if any → [ ]; reviewer + resolution → [ ].