Keeping a timeline of HMRC correspondence

A timeline of HMRC correspondence should record dates sent and received, references, deadlines and the action taken. Link each entry to the original document so the sequence can be checked without relying on memory or an email search.

Distinguish the date printed on a notice from the date it arrived. Record delivery evidence and any agreed extension, including its exact scope.

Record issue, receipt and action dates separately

Create a correspondence register with distinct columns for the date printed on the document, the date received and the date action was taken. Include the sender, recipient, tax reference and period concerned. A letter's issue date and arrival date can differ, and both may be relevant when an adviser checks the procedural position. Preserve the envelope or electronic delivery information where it helps establish the sequence.

Do not combine all documents under one broad tax enquiry entry. A case may include information requests, assessments, penalty notices and routine account statements, each requiring a different response. HMRC's compliance-check guidance explains that checks can lead to written findings and further tax or penalty matters. ^[1] Keeping document types separate helps ensure that a response to one issue is not mistaken for action on another.

Link every entry to the original document

Give each item a stable reference and store a complete copy with its attachments. For an email, preserve the relevant message details and enclosures rather than copying only the body into a spreadsheet. For a letter, check that reverse pages and enclosed factsheets have been scanned. The register should point to the source, allowing someone to verify the wording without relying on the summary alone.

Use short neutral descriptions such as request for invoices for a named period or decision on a specified claim. Avoid summaries that add a conclusion not present in the document. If the meaning is uncertain, put that in a separate question column. A chronology remains more useful when it distinguishes what HMRC actually wrote from the taxpayer's interpretation or the adviser's later assessment of its effect.

Maintain a separate deadline and responsibility view

For each required action, record the date stated in the document and ask the adviser to confirm any statutory calculation or procedural requirement. Identify the person responsible, the planned response date and the current status. Do not treat a diary reminder as proof that an action was completed. Link the register to the actual submission and acknowledgement before marking an item closed.

If an extension is requested, record the request and the reply separately. Specify what the agreement covers: a particular document pack, meeting or response, for example. An extension concerning one task should not be assumed to change an appeal or payment deadline elsewhere in the case. Keep unresolved timing questions visible and obtain clarification promptly instead of relying on an informal assumption shared between colleagues.

Add calls and meetings without overstating agreement

Enter telephone calls and meetings with the date, participants, topics discussed and any actions stated. Distinguish a recollection from a confirmed agreement, and identify follow-up correspondence that clarifies the position. If an officer says they will consider a request, do not record it as approved. The difference can matter when later reviewing why a response or payment was made on a particular date.

Use What to record after a call with HMRC to structure a call note. Where several people attended, reconcile significant differences in recollection while the conversation is still recent. Preserve the original notes and label any later clarification. If a material point needs written confirmation, send or request it through the appropriate channel and attach the reply to the same register entry so the sequence remains complete.

Use the timeline to prepare focused follow-ups

Before chasing progress, review the latest outstanding action and the evidence that the previous response was delivered. State the relevant date, reference and document supplied rather than sending a general request for an update. If HMRC asks for something already provided, the register should identify the exact submission and attachment. This supports a precise reply without assuming that the recipient has access to every earlier communication.

For help organising a correspondence history and assessing the next response, see HMRC enquiry response support. Supply the register together with the original notices, especially anything carrying an imminent deadline. The register is a navigation aid, not a substitute for reading the documents. An adviser should be able to move from the summary to the source and identify the current procedural position without reconstructing the entire inbox.

At regular intervals, check for missing references, unfiled attachments and entries marked awaiting action without an owner. Keep a dated snapshot before a handover or major submission. That snapshot shows the state of the case at the time and prevents later edits to a live spreadsheet from obscuring what was known when an important decision was made.

Illustrative scenario

A taxpayer receives several letters about the same return. A single timeline reveals that one response deadline concerns a different decision, allowing the adviser to address both matters correctly.

Preparation checklist

• Record issue and receipt dates
• Link original documents
• Track response deadlines
• Preserve extension evidence