The correspondence register: numbering, linking and following formal letters
A municipal project's team remembers a letter about unexpected ground conditions but cannot find the reply or the recorded acknowledgment. An incoming-and-outgoing register needs to connect the whole thread, not merely count how many letters passed through the coordinator's inbox.
Keep an index of formal incoming and outgoing correspondence that connects each letter with its subject, source, related records and response status. Define the correspondence class with the project team and check the actual communication requirements. A register helps you find and follow the record; numbering a letter does not itself establish valid notice, receipt or entitlement.
Connect each formal letter with its thread
- Agree what enters the register. Identify the project's formal letter series and other communications that need this level of tracking. Check applicable requirements for notices, delivery channels and recipients with the responsible team. An email may still carry an important obligation even if it falls outside your chosen letter class; do not use an administrative category to ignore it.
- Record identity and source. Enter a unique reference, letter date, actual received or issued date, sender, recipients and a clear subject. Link the actual document, attachments and relevant delivery or acknowledgment evidence. Preserve the sender's original identifier rather than renumbering incoming letters as if your reference were theirs. Note a missing attachment or uncertain receipt rather than filling the gap from memory.
- Connect the reply and required action. Record the letter being answered and the relevant earlier references. Identify the responsible responder, actual response requirement and due date, distinguishing a contractual deadline from an internal follow-up date. Link a reply to the thread without assuming it answers every point. Mark any unresolved questions and the next required action.
- Review open threads and protect urgent dates. Use a recurring review suited to the project, with earlier alerts for time-sensitive items. Check that the action owner has the actual letter and understands the response needed. Escalate unanswered requirements before the relevant date; a weekly register review is no reason to leave an urgent letter unread. Keep the original records and their history accessible through the agreed filing process.
Close a line only when its recorded purpose has been addressed or its remaining status has been deliberately identified. A reply saying the matter is under review is a reply, but not necessarily a final answer. Keep the distinction visible so a later project manager can see whether the thread was resolved, transferred or still open.
Common mistakes
- Registering the letter but losing its attachments or delivery evidence.
- Marking any reply as complete even when questions remain open.
- Using a weekly review date instead of the actual urgent deadline.
Checklist
Check one correspondence thread
- Original letter and unique reference.
- Sender, recipients and actual issue or receipt date.
- Attachments and delivery evidence.
- Earlier letter and linked reply.
- Response requirement, owner and date.
- Unresolved points and next action.
Check your understanding
A reply is linked in the register. Is the thread finished?
