An investigation correspondence log creates a searchable index of case communications so requests, responses, deadlines and follow-up do not remain scattered across inboxes, files and individual notes. The log should point back to the original communication rather than become a replacement for it.
Quick-start correspondence log checklist
For each request or response, record the date, direction, contact, reason, status, next review date and original document reference. When the request becomes an investigative action, give the follow-up an owner; don't just leave it in an inbox.
Want the underlying contact workflow? See the actual previews of the CaseWorks Interview Notes & Contact Log ($19). It helps track outreach and follow-up but is not a dedicated standalone correspondence-log download. For broader linked case documentation, compare the $79 Case File System.
For a free, general starting point, use the case-file documentation checklist.
What should an investigation correspondence log include?
A practical log can include the date sent or received, correspondent, organization or role, communication type, subject or purpose, assigned owner, response due date, response date, status, related case item and a stable reference to the original record.
- Date: when the communication was sent or received.
- Direction: incoming or outgoing.
- Correspondent: person, organization or relevant role.
- Purpose: what was requested, provided or discussed.
- Status: sent, received, awaiting response, completed or other workflow-specific status.
- Due/review date: when unanswered correspondence should be checked again.
- Record reference: where the original email, letter or other communication can be found.
Track incoming and outgoing correspondence
Recording both directions makes it easier to understand what was requested, what was provided, whether a response is still expected and which communication triggered later work.
Correspondence log vs. contact log
A correspondence log is useful for formal or substantive communications and their response status. A contact log is typically broader and may include calls, outreach attempts, scheduling and interview contacts. The exact distinction should match the workflow, but keeping the purpose of each record clear reduces duplication.
Reference the original record
Use a stable file name, document ID, folder location or other authorized reference rather than copying the full communication into the log. This keeps the index concise while preserving a path back to the source record.
Turn unanswered correspondence into follow-up
An unanswered request should not disappear because the original email is buried in an inbox. Use a due date or next-review date and, where appropriate, assign an owner and next action. Once a response arrives, record the outcome and link it to any resulting lead, source, interview or task.
If the correspondence is requesting records or information, track the unresolved request in the Information Request Tracker. If it asks another team or authorized resource to perform or support work, use the Request for Assistance Log.
Connect correspondence to the investigation
If a communication provides a material fact, document, new contact or unresolved question, reference the corresponding timeline, source, interview or lead record. The correspondence log preserves the communication history; the other case records preserve the substantive investigative work.
Correspondence log example: request, reminder and response
The following fictional entries show how one request can be tracked without losing its history. Use a separate row for each communication, and keep the original records in your authorized case file.
| Reference | Date | Direction | Purpose | Status / next action |
|---|---|---|---|---|
| COM-001 | Oct 2 | Outgoing | Request delivery record | Awaiting response; review Oct 7 |
| COM-002 | Oct 7 | Outgoing | Follow-up on COM-001 | Reminder sent; review Oct 10 |
| COM-003 | Oct 9 | Incoming | Delivery record received | Response received; assign record review |
Link COM-003 to the resulting source or document-log entry, then close the outstanding request only after the response has been assessed. Dates and details above are illustrative, not real case records.
Common correspondence-log mistakes
- Recording only outgoing requests and not the responses.
- Using vague subjects that do not explain the purpose.
- Leaving unanswered requests without a review date.
- Copying entire emails into the log instead of referencing the original.
- Failing to connect a response to the case action it created.
Need contact and interview tracking?
The $19 Interview Notes Template & Investigation Contact Log organizes interview preparation, contact attempts, outcomes, unresolved questions and follow-up.
Need correspondence connected to the full case?
The $79 Investigation & Case Management System connects timelines, leads, sources, interviews, actions and case review. You can also start with the Free Investigation Case File Checklist to review the broader file structure.
Frequently asked questions
Should the correspondence log contain the full email or letter?
Usually the log works better as an index that references the original record, subject to applicable procedures.
Should phone calls go in a correspondence log?
That depends on the workflow. Calls and outreach attempts may fit better in a contact log, while formal written communications remain in the correspondence log.
What happens when correspondence creates a new lead?
Reference the communication and move the unresolved investigative work into the appropriate lead or action tracker so it remains visible.
General organizational tools only; not official forms or legal advice. Follow applicable privacy, disclosure, retention and organizational requirements.