Numbering letters and writing the reference line so a dispute can follow the thread
The glazing manager's letter says further to your recent message, but the project has several messages about anchor changes. Months later, a new manager cannot tell which one it answers. A precise reference line and consistent letter identifier would remove that avoidable ambiguity.
Give outgoing letters unique identifiers in an agreed project-and-party series, and identify the records each letter answers or relies on. Preserve incoming references and connect the replies. The aim is a thread a later reader can follow using actual documents, not a decorative number on a letter that still leaves its subject and source uncertain.
Make a letter's place in the record clear
- Choose a consistent identifier. Agree a series that distinguishes the project and issuing party, with a unique sequence or other controlled identifier. Check for duplicate numbers before issue and record any correction without silently replacing an issued letter. Preserve the actual issue date and revision or reissue history. The identifier is an index, not evidence that delivery or a required response occurred.
- Write a precise reference line. Name the relevant agreement or project reference, a specific subject and the earlier letter's identifier and date where applicable. Identify the relevant instruction, drawing issue or other source by its actual designation. Use the applicable clause reference only after checking it with the responsible team; an incorrect clause can confuse the issue rather than strengthen the letter.
- Keep the subject followable. Give a routine letter one clear purpose where practical and list the points requiring a response. If a required notice or connected issue needs several matters together, follow the applicable process rather than splitting it to obey a filing preference. Distinguish the factual record, unanswered question and requested action without implying that the reference line decides the dispute.
- Issue and preserve the connected records. Check recipients, attachments and applicable communication requirements through the project's process. File the actual issued letter under its identifier and link delivery records, replies and related documents in the register. Keep a readable record as well as required original files and metadata. Test that a new reader can follow the thread without knowing your inbox habits.
Cross-references work only when the referenced records remain available and distinguishable. If the reply discusses a different revision or an attachment was missing, record the gap and ask for clarification. Do not rewrite an earlier letter's references after the event to make the history appear cleaner. Preserve the correction and its actual date.
Common mistakes
- Writing further to your message without its identifier or date.
- Reusing a letter number or silently replacing an issued version.
- Assuming a clear reference line makes the letter a valid contractual notice.
Checklist
Check the letter before issue
- Unique project-and-party identifier.
- Actual issue date and reissue status.
- Specific subject and relevant agreement.
- Earlier letter and source-document references.
- Required recipients and actual attachments.
- Connected filing, delivery record and reply path.
Check your understanding
Can a well-numbered letter replace checking the notice clause?
