Reusable frameworks

4 Writing the Date 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 well-written date is unambiguous to the intended reader, consistent within the document, and compliant with any form, style guide, contract, publication, or system requirement that controls the format. The best format is therefore contextual rather than universally correct.

  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.
Writing the Date Template 1
Prose date
US-style example: [Month] [day], [year]
Day-month example: [day] [Month] [year]
Choose according to required audience/style.
Writing the Date Template 2
Technical date
YYYY-MM-DD: [year]-[month]-[day]
Use only where the system, standard, or workflow supports it.
Writing the Date Template 3
Date range
Start: [x]
End: [x]
Shared month/year can be compressed only if the style keeps the range unambiguous.
Writing the Date Template 4
Date verification check
Source date: [x]
Required format: [x]
Region/style: [x]
Ambiguous numeric form avoided? [ ]
Deadline/time zone verified when relevant? [ ]