What is En Dash?
An en dash is a punctuation mark longer than a hyphen and shorter than an em dash, commonly used for numerical ranges and certain relationships between paired terms.
What good en dash looks like
Correct en-dash use is restrained and consistent: use it where the style calls for a span or relationship, avoid mixing it with from/to constructions, and do not substitute it for every hyphen or em dash.
- Use an en dash for inclusive ranges when appropriate.
- Use it for selected paired relationships in styles that recommend that convention.
- Apply spacing consistently according to the publication style.
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.
- Use an en dash for inclusive ranges when appropriate.
- Use it for selected paired relationships in styles that recommend that convention.
- Apply spacing consistently according to the publication style.
How to write en dash step by step
- 1Check whether the expression means from X to Y.
- 2If words such as from or between already appear, usually write to or and instead.
- 3Distinguish compound-word hyphens from relational en dashes.
- 4Follow the house style for dates, scores, and page ranges.
- 5Proofread copied text because hyphens and dashes are often substituted automatically.
8 En Dash examples
Read the examples for structure and choices rather than copying surface wording. Notice what stays consistent and what changes with audience or purpose.
The survey covers 2019–2023.
Read pages 45–62 before class.
The vote passed 7–3.
The New York–London route reopened in spring.
The teacher–student conference lasted twenty minutes.
Office hours are 10:00–12:00.
En Dash templates
Replace every bracketed field with situation-specific information. A template is a starting structure, not finished copy.
Range: [start]–[end].
Pages: pp. [start]–[end].
Score: [number]–[number].
Common mistakes to avoid
- Writing from 2019–2023 instead of from 2019 to 2023.
- Using an en dash where a hyphen belongs inside a compound modifier.
- Using an en dash as a general-purpose pause mark instead of an em dash.
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 En Dash
What is En Dash?
An en dash is a punctuation mark longer than a hyphen and shorter than an em dash, commonly used for numerical ranges and certain relationships between paired terms.
What makes En Dash effective?
Correct en-dash use is restrained and consistent: use it where the style calls for a span or relationship, avoid mixing it with from/to constructions, and do not substitute it for every hyphen or em dash.
How do I write En Dash?
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 En Dash?
Writing from 2019–2023 instead of from 2019 to 2023. Using an en dash where a hyphen belongs inside a compound modifier. Using an en dash as a general-purpose pause mark instead of an em dash.
How do I know whether a claim or source on a En Dash 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 En Dash 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 En Dash 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.