What is Description?
Description is the selective use of concrete detail to make a person, place, object, action, or condition perceptible and meaningful to a reader rather than merely naming its category or listing visible features.
What good description looks like
Effective description chooses details that matter to viewpoint and purpose, favors specific evidence over generic adjectives, integrates detail with action or thought, and creates a clear impression without stopping the writing for an inventory.
- Subject: what the reader needs to perceive.
- Viewpoint: who notices the details and why.
- Dominant impression: the mood, condition, or meaning the selected details should create.
- Specific evidence drawn from appearance, sound, texture, movement, behavior, or context.
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.
- Subject: what the reader needs to perceive.
- Viewpoint: who notices the details and why.
- Dominant impression: the mood, condition, or meaning the selected details should create.
- Specific evidence drawn from appearance, sound, texture, movement, behavior, or context.
How to write description step by step
- 1Write the impression you want the reader to receive in abstract terms.
- 2Replace that abstraction with three observable details.
- 3Choose which details the viewpoint character or intended reader would actually notice.
- 4Arrange details by movement, importance, contrast, or spatial path.
- 5Connect at least one detail to action, memory, judgment, or consequence.
- 6Cut details that repeat the same effect.
8 Description examples
Read the examples for structure and choices rather than copying surface wording. Notice what stays consistent and what changes with audience or purpose.
Instead of 'the office was neglected,' one ceiling tile sags beneath an old leak and every desk has a different model of monitor.
Instead of 'he looked nervous,' he folds the parking receipt into smaller and smaller squares while waiting for his name to be called.
The market is loudest under the sheet-metal roof, where vendors raise prices and jokes above the rain hammering overhead.
The coat looks expensive from across the room, but the cuffs are shiny from wear and one button has been replaced with a darker one.
Her handwriting begins upright and evenly spaced, then leans hard to the right in the final lines where the ink also grows darker.
The trail narrows between wet stone and thorn scrub, forcing hikers to turn their shoulders sideways for several meters.
Description templates
Replace every bracketed field with situation-specific information. A template is a starting structure, not finished copy.
Dominant impression: I want the reader to feel [impression], so I will show [detail 1], [detail 2], and [detail 3].
Viewpoint filter: [Character] notices [detail] because [goal/fear/history], while ignoring [less relevant detail].
Spatial description: Start at [anchor], move through [path], and end on [detail that changes the meaning].
Common mistakes to avoid
- Listing colors, sizes, and shapes without a point of view.
- Using many adjectives where one concrete noun or verb would be stronger.
- Describing everything in a scene with equal emphasis.
- Choosing stock details that could belong to any person or place.
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?
Questions about Description
What is Description?
Description is the selective use of concrete detail to make a person, place, object, action, or condition perceptible and meaningful to a reader rather than merely naming its category or listing visible features.
What makes Description effective?
Effective description chooses details that matter to viewpoint and purpose, favors specific evidence over generic adjectives, integrates detail with action or thought, and creates a clear impression without stopping the writing for an inventory.
How do I write Description?
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 Description?
Listing colors, sizes, and shapes without a point of view. Using many adjectives where one concrete noun or verb would be stronger. Describing everything in a scene with equal emphasis.
Should Description show one “last updated” date or track verification at the claim level?
Use a page-level revision date for editorial history, but do not let it imply that every statement was reverified on that date. Changeable facts, quotations, policies, project facts, market data, provider capabilities, and other consequential claims should carry a source record with their own last-verified date or version and a specific recheck trigger. Stable editorial synthesis and original instructional examples can use the page revision/version record instead. When a material correction, retraction, or recommendation change affects what the reader should believe or do, retain the prior record and disclose what changed and why.
How do I know whether a claim or source on a Description guide is stale, corrected, or still active?
Do not infer status from the page-wide update date. Check the controlling source or project record, the exact version/date last verified, and the trigger that could make the item changeable. Keep it active when the source still controls the exact claim; mark review due when a trigger has fired but the conclusion is not yet disproved; mark stale when the old version no longer controls; and use corrected, retracted, withdrawn, or superseded when the editorial history requires it. The correction level should match reader impact: cosmetic edits are not the same as a material factual correction or a critical source failure.
If a source behind Description 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 Description 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.