Spell out the month and retain a four-digit year in English-language prose—but establish the intended date before reformatting it. Changing “03/04/2027” into polished words does not resolve its meaning. It can simply hide an unconfirmed choice inside a confident-looking workshop message.
For an operations coordinator writing to colleagues in more than one country, the useful deliverable is a small date-clarification card. Keep the original wording, identify who can confirm it, and separate that confirmation from the proposed display. Maya, the human workshop coordinator in the illustrative example below, approves the final workshop message before anyone sends it.
Make the display clear, not the uncertainty invisible
Microsoft’s English-language Writing Style Guide says, “To avoid confusion, always spell out the name of the month.” Its Numbers page explains that month and day positions vary by country. This is Microsoft’s style recommendation, not a universal rule governing every document or system. [1]
Google’s English-language developer documentation style guide similarly recommends spelling out month names and giving the full four-digit year. Its exact guidance includes: “Give the full four-digit year, not a two-digit abbreviation.” [2] For a confirmed date, “April 3, 2027” is a useful reader-facing form for this workshop message.
Neither recommendation tells you which date an ambiguous source intended. A colleague’s location, the language of a brief, or your computer’s display settings is not confirmation of that particular string. Ask the source owner a direct question: “Does 03/04/2027 mean March 4, 2027, or April 3, 2027?” Keep the message on hold until the answer is established.
Use a proposed date-clarification card
The MAJLS proposed review card has five fields. It is a working handoff, not a replacement source record.
- Original literal wording: copy exactly what the source says, including separators and any missing information.
- Source/owner: identify the brief, note or export, and the person responsible for resolving uncertainty.
- Confirmed intended day: record the supported date, or explicitly say that it is unconfirmed or that no day was supplied.
- Proposed display: write the reader-facing wording only when the evidence supports it; otherwise leave it unset.
- Disposition: state HOLD, ready for message review, or retain partial date, with the responsible person and next action.
Separate the source from the display even when both happen to contain identical text. The distinction lets Maya see why a proposed sentence is supported rather than merely well formatted. If a clarification arrives, add it as evidence instead of silently editing the original brief to make it appear unambiguous all along.
Filled example
This is a constructed, static workshop example. Maya and the records below are illustrative, not MAJLS customer evidence or a claim that a real confirmation took place. Row B represents an explicit clarification within the example; it does not remove the original uncertainty recorded in A.
| Row | Original literal wording | Source/owner | Confirmed intended day | Proposed display | Disposition |
|---|---|---|---|---|---|
| A | 03/04/2027 | Unconfirmed draft brief; Maya to confirm | Unconfirmed: March 4, 2027, or April 3, 2027 | None—no proposed final date | HOLD; ask Maya which date was intended |
| B | April 3, 2027 | Maya’s explicit clarification for A | April 3, 2027, within this illustrative record | April 3, 2027 | Ready for Maya’s message review, not sending |
| C | 2027-04-15 | Hypothetical export; documented field format is YYYY-MM-DD; Maya reviews reuse | April 15, 2027, under that documented contract | April 15, 2027 | Preserve original in evidence; include proposed wording for Maya’s review |
| D | April 2027 | Month-only planning note; Maya owns workshop wording | No day supplied; month and year only | April 2027 | Retain month-only precision; do not invent a day |
For B, the assistant could propose: “The workshop is on April 3, 2027.” Maya still reviews that sentence in the complete message. For D, “Workshop planning: April 2027” preserves the information available without pretending that a workshop day has been chosen.
Treat machine fields as a separate contract
Google specifies YYYY-MM-DD, with hyphens, when a numeric-only date is necessary. [2] That recommendation is useful, but it does not authorize rewriting a machine field whose documented contract requires something else. Check the actual export or receiving field documentation before interpreting or changing its value.
In row C, the hypothetical field’s documented format supplies the interpretation. The display changes; the preserved evidence does not. Without that contract, a string’s appearance alone should not be treated as proof of what an unfamiliar field means.
A date-only value is not an instant. Writing “April 15, 2027” from a documented date-only field is a display choice, not a time-zone conversion. Do not attach an invented time, offset or weekday to make the message seem more complete. Likewise, a month-only note remains month-only. Google’s guide explicitly shows month-and-year wording without a comma. [2]
Checklist
- Preserve each original date string and its source before proposing changes.
- Hold ambiguous dates for an explicit answer from the responsible owner; do not infer intent from locale.
- Check the documented contract for numeric machine fields, separately from the prose style choice.
- Keep partial dates partial unless the owner supplies the missing information.
- Compare the proposed message with the clarification card, then obtain Maya’s approval before anyone sends it.
An assistant can flag ambiguous strings, assemble questions and draft supported wording. It cannot turn a likely interpretation into a confirmed fact or overwrite source records. The finish is a message Maya can approve with its date meaning visible—not a calendar calculation, a file-naming convention or a new scheduling workflow.
