Published Updated

A facilities team coordinates a service change by email. A later message asks the organisation to explain the change in writing and address a specific concern. The shared mailbox now holds a request that needs service-team input, a named owner and a reviewed reply.
Register email as formal correspondence when your organisation's rules require accountable action, a tracked response or an official decision record. Define those capture triggers in the correspondence and records policies, then apply them during triage. The same rule can cover a letter, portal submission or scanned enquiry. Record why the item was captured and what must happen next.
Start with practical questions. Does the message request an official answer, raise a complaint, communicate an authorised decision or supply evidence for an open matter? Does another team need to act, and will someone need to explain the response later? These are useful workflow triggers to agree with the people responsible for correspondence and records management.
| Communication | Workflow action | Reason to capture or link |
|---|---|---|
| Service enquiry needing a written answer | Register the request, assign an owner and confirm the response target. | Staff need to track the incoming concern, supporting work and official response. |
| Approved decision sent to a correspondent | Connect the sent version, approval and available dispatch evidence to the file. | The organisation needs to explain what it authorised and what was actually sent. |
| Supporting evidence for an existing enquiry | Confirm the correspondent and related file, then link the message and attachments. | The new material may change the review or the next response without creating a separate matter. |
| Routine meeting coordination | Apply routine communication rules; link it where it explains a material action in an existing file. | Context determines whether the exchange contributes to the business record. |
Make uncertain items easy to refer to a responsible reviewer. Record the capture decision and category so staff can apply the rule consistently across personal inboxes, shared mailboxes and other intake channels. The policy should also identify who owns uncategorised messages and who checks for missed requests.
Preserve the source communication and identify its correspondent, subject and related work.
Name the accountable owner, contributors, response target and basis for that target.
Review the exact reply, record dispatch outcomes and resolve further questions before closure.
Preserve the original message and attachments with their source references, sender and recipient details, subject, and available sent/received times. Keep the intake's recorded receipt and the selected response target distinguishable. The Outlook MSG preservation guide explains how native email objects and their derived views stay connected.
Confirm the correspondent and the intended business file during intake. A forwarded excerpt can help explain the matter, but retain its relationship to the original communication. Later messages, supporting documents and replies need their own identities within the connected correspondence file. The correspondence and CRM guide covers the relationship with an existing contact or service record.
Record the due date and its basis after triage, including the agreed calendar and any approved extension. A target taken from internal service policy and one arising from another obligation need their source identified. The application tracks the configured work; responsible staff confirm which requirement applies and who may change it. Keep handover reasons and the next action visible when ownership moves between departments.
This fictional workflow uses COR-1042 from the Correspondence Management example. A message received through the organisation's chosen email intake asks for a written explanation of a service change.
The records officer captures the message and attachments, selects the correspondent and records the received time and source reference. The capture rule identifies the requested written answer, so the enquiry enters the correspondence workflow.
The coordinator confirms the category, accountable officer and response target under the organisation's service policy. Other teams contribute information while Facilities Operations retains responsibility for the answer and any handover.
The officer gathers service-team input and the relevant notice, prepares a reply and submits that version for Operations Response Review. Requested corrections return to the draft. The application identifies the version approved for dispatch.
The officer sends the approved response through the selected channel. The file records the recipient, exact version, attempt time and available channel reference or delivery result. A failed attempt remains assigned for correction or another delivery action.
A further question joins COR-1042 with its next action and owner. Staff confirm that the response obligations are addressed before recording closure. The file retains the received message, reviews, sent reply and later exchanges under the applicable access and retention controls.
An approved reply, a sending attempt, a delivery result and completion of the enquiry are separate events. Record the evidence the chosen channel actually provides; sending does not establish that the correspondent read the message. Keep returned mail, delivery failures and promised follow-ups connected to the responsible owner.
Likewise, registering an enquiry does not itself confirm its final outcome. The submission-acknowledgement guide explains how receipt and later processing messages can make their scope clear. A correspondence file can remain open for a further answer after the first reply has been sent.
A bounce or returned envelope creates follow-up work; it does not authorise an address change. Confirm corrected contact details through the organisation's approved source and record who accepted them. Keep the recipient details, exact reply version and channel result for the failed attempt.
Give a resend its own linked attempt. Check whether the changed recipient, wording or channel requires further approval, and retain the result. The responsible owner should assess any effect on the response target or applicable deadline; a retry must not silently restart the clock or mark the enquiry complete.
Use the organisation's capture rules to identify messages that need accountable work and a retained response history. A shared mailbox can remain the entry channel while Correspondence Management connects the request, owner, reviewed reply, dispatch outcome and follow-up. Staff can then explain what arrived, who acted and what remains outstanding.
The open-source foundation — API-first, deployable into your own AWS account, and free to use. Right for architecture validation and early implementation.
Production-ready editions for departments and complex workflows. Start with a Proof-of-Value deployment or go straight to production.
For governance-heavy environments with residency, sovereignty, assurance, and multi-jurisdiction requirements. Talk to us about the right deployment model.