An example: a repairs exchange tied to the right property
A resident's letter may begin a repairs matter, followed by correspondence with a contractor and an update to the resident. Each item needs the right property and case context, but the recipients do not necessarily need access to every document in the exchange. A contractor's work instruction and a private resident letter may require different handling.
When discussing property workflows, explain whether correspondence is organised by property, tenancy, landlord, resident or a specific case. Identify the records already maintained in your property system and the references that should connect them. Routine operational correspondence also needs to be distinguished from notices with specialist requirements. The organisation remains responsible for selecting the correct wording, timing and delivery procedure where those requirements apply; a correspondence record does not decide them automatically.
Folders that reflect how real correspondence happens
People do not naturally organise their letters by file extension. They think about matters: an insurance claim, a tenancy, a client relationship or an exchange with a public authority. Dedicated correspondence folders should follow that mental model. Each folder can hold incoming letters, outgoing replies, attachments, notes and reminders, while a case record connects events that belong to the same issue.
Folders should stay simple for individuals and become more structured as organisations grow. A personal account might contain Home, Banking, Work and Insurance. A professional firm may organise by client, matter and department, with sensitive folders visible only to authorised colleagues. Moving a letter between folders must not alter its identity, final document or historical evidence.
Stay on top of replies and deadlines
A letter rarely ends the work. The recipient may need to respond, documents may need to be provided, or the sender may want to check progress after a reasonable interval. Epistles should connect reminders to the relevant correspondence record so that follow-up activity is not lost in a separate to-do list.
A personal account may only need a simple reminder date and a note. A company may need assigned tasks, approval deadlines, escalation policies and a queue of unresolved correspondence. These features should be useful without implying that Epistles has calculated a legally binding deadline; specialist statutory deadlines must be independently confirmed.
A meaningful correspondence audit trail
Audit history becomes valuable when it tells a clear story: a letter was drafted, amended, approved, finalised, queued for email, submitted for post and later updated when verified events arrived. Each significant action should have an event identifier, timestamp, actor, outcome and source. Corrections should appear as new entries rather than silently replacing older ones.
For everyday users, the history should be understandable without technical training. Business administrators may need more detailed audit exports, staff permissions and retention controls. The underlying log should be protected against unauthorised alteration, but the interface should avoid claiming that a software audit entry is, by itself, proof of receipt or legally effective service.