Train Description Template 1
Train-motion map\nTrain type: [x]\nMotion state: [x]\nInterior anchor: [x]\nSound/vibration: [x]\nNext transition: [x]
12 Train 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 train description keeps movement and geography coherent: readers can tell whether the train is stopped, accelerating, cruising, braking, entering a curve, passing a platform, or moving through open country, and the sensory details match that state.
- 1Choose the template closest to your actual purpose.
- 2Replace every bracketed field with specific information.
- 3Delete any sentence that does not belong in your situation.
- 4Read the result aloud for unnatural transitions or repeated phrasing.
- 5Verify names, dates, links, facts, and promises before sending or publishing.
Train Description Template 2
Station sequence\nApproach: [x]\nBraking: [x]\nPlatform cue: [x]\nDoors/passengers: [x]
Train Description Template 3
Generic → rail-specific\nGeneric: The train sped along.\nMotion cue: [x]\nLandscape cue: [x]\nRevision: [x]
Train Description Template 4
Research check\nRoute/era: [x]\nTechnical detail: [x]\nSource: [x]\nVerified/generalized wording: [x]
Train Description Template 5
Purpose-and-verification decision audit for Train Description: real writing job → [ ]; plausible choice A → [ ]; plausible choice B → [ ]; downstream consequence of each → [ ]; facts/evidence/canon to verify → [ ]; reader or genre boundary → [ ]; final purpose-fit reason → [ ].
Train Description Template 6
Publication-readiness audit for Train 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 → [ ].
Train Description Template 7
Provenance and classification audit for Train 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 → [ ].
Train Description Template 8
Source-record and update audit for Train 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 → [ ].
Train Description Template 9
Source-ledger and revision-history audit for Train 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 → [ ].
Train Description Template 10
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].
Train Description Template 11
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].
Train Description Template 12
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 → [ ].