An incoming and outgoing letter SOP for companies: outline and sample content

A letter-handling SOP is a short document that answers three questions: who does what, in what order, and within what time. Without one, each department handles letters its own way, numbers can collide, and dispositions get stuck on an empty desk. This guide gives an outline for a correspondence SOP in a private company, with sample content for each section that you can adapt. The rules in it are your company's internal policy and not a standard that applies to every organisation.

What this SOP covers

A correspondence SOP governs a letter's path from the moment it arrives or is drafted to the moment it is filed. Three things make it worth having.

• Consistency. A letter from a client is treated the same way whether it comes through reception, email or courier.
• Accountability. Every step belongs to a position, so when someone is on leave the work does not stop with them.
• Evidence. Who approved a letter, when it was sent, and when it was answered can be traced without asking around.

This guide does not cover the formal letter conventions used by government agencies. A company is free to choose its own formats, unit codes and terms, as long as they are consistent and written down.

The outline

A good SOP rarely runs longer than three or four pages. This structure is enough for most companies.

1. Purpose
2. Scope
3. Roles and responsibilities
4. Incoming letter procedure
5. Outgoing letter procedure
6. Numbering
7. Disposition
8. Deadlines and follow-up
9. Archiving
10. SOP review

SOP outline example

The example below uses placeholders in square brackets. The numbers and terms are only examples, so adapt them to your company's size and habits.

SOP: HANDLING INCOMING AND OUTGOING LETTERS
[Company name]
SOP no.: [SOP/[UNIT-CODE]/[NUMBER]]   Version: [1.0]   Effective: [date]
SOP owner: [Position]                 Approved by: [Position]

1. PURPOSE
   To make sure every incoming and outgoing letter is recorded, handled by
   the right position, and filed completely.

2. SCOPE
   Applies to official and internal letters in [all units / named units],
   on paper or in digital form. Does not apply to [daily operational email /
   invoices / other excluded documents].

3. ROLES AND RESPONSIBILITIES
   Correspondence officer : receives, records, numbers, sends, files
   Executive secretary    : passes letters to the disposition giver, tracks deadlines
   Disposition giver      : [Director / Head of Division], decides the handling
   Disposition recipient  : carries out the instruction and reports back
   Drafter                : writes outgoing letters
   Reviewer and approver  : [positions], depending on letter type
   SOP owner              : keeps the SOP current

4. INCOMING LETTER PROCEDURE
   4.1 The officer receives the letter and checks the address and attachments.
   4.2 A [confidential] letter goes to its addressee sealed.
   4.3 The officer logs it in the register and assigns an agenda number.
   4.4 The officer scans it and names the file after the agenda number.
   4.5 The letter reaches the disposition giver within [1] working day.
   4.6 After disposition, the recipient acts on the instruction.
   4.7 The register status is updated until the letter is closed.

5. OUTGOING LETTER PROCEDURE
   5.1 The drafter writes the letter on the company template.
   5.2 The direct supervisor reviews the content.
   5.3 The approver for that letter type gives approval.
   5.4 The officer assigns the letter number after approval.
   5.5 [Authorised position] signs the letter.
   5.6 The officer sends it and records the date and the channel.
   5.7 The final letter and proof of sending are filed.

6. NUMBERING
   Outgoing format: [sequence]/[UNIT-CODE]/[roman month]/[year].
   Incoming agenda uses a separate series: AGD/[sequence]/[year].
   Numbers are never reused. A voided number is logged with the reason.

7. DISPOSITION
   A disposition states the target position, instruction code, notes,
   deadline, and the initials and date of the giver. The instruction
   codes are in Appendix [A].

8. DEADLINES AND FOLLOW-UP
   Very urgent: [1] working day   Urgent: [3] working days   Normal: [7] working days
   The executive secretary reviews open dispositions every [week].
   Dispositions past their deadline are reported to the giver.

9. ARCHIVING
   The incoming letter, its disposition and the reply are filed together
   once the status is closed. Folder structure: [Year]/[Letter type]/[Unit].
   Retention follows the company retention schedule, Appendix [B].

10. SOP REVIEW
    The SOP is reviewed every [12] months or when the workflow changes.
    The revision history is kept at the end of the document.

APPENDICES: [A] Disposition instruction codes  [B] Retention schedule  [C] Forms

Running the SOP on one letter

Suppose a client sends a letter objecting to an invoice. The correspondence officer receives it on Monday, logs it in the register, scans it, and passes it to the executive secretary the same day. The director gives a disposition to the Head of Finance with a three-working-day deadline because the letter is urgent. The Head of Finance drafts a reply, a supervisor reviews it, and the director approves it. The officer then assigns the outgoing number, sends the reply, and records that number in the status column of the register. After that the status is closed, and the incoming letter, the disposition and the reply are filed together. When every step has an owner and a deadline in the SOP, you can answer the question "has this been replied to?" without calling anyone.

Adapting each section

Purpose and scope. Write one or two sentences. The scope section is most useful when it names what is excluded, for example invoices that already have their own flow in finance. Without exclusions, people tend to ignore an SOP because it does not seem to fit every case.

Roles. Write positions, not names, and decide who stands in when a position is vacant. Small companies sometimes combine the correspondence officer and the secretary, and that is fine as long as every step still has an owner.

Numbering. Decide who may issue a number and at what point. Numbering after approval avoids wasting numbers on drafts that end up rejected. Number patterns, unit codes and reset rules are covered in the guide to company letter numbering formats.

Disposition. Use a short list of instruction codes and write the target position, not just a name. The register columns, the disposition sheet and the code list are in the guide to the incoming letter register and disposition sheet. Your SOP can point to an appendix instead of repeating them.

Deadlines. Tie the deadline to the urgency of the letter. A deadline only means something when someone checks it, so the SOP should say who reviews and how often.

Archiving. State when a letter counts as closed and who files it. Retention should follow your company's retention schedule, and the guide to how long to keep company documents explains how to build one.

Review. An SOP that is never reviewed drifts away from what people actually do. Name an owner, set a review date, and add one trigger for an earlier review, such as switching applications or reorganising the company.

Common mistakes when writing the SOP

• Making it too long. A ten-page document rarely gets read. Put forms and code lists in appendices.
• Copying another company's SOP. Formats and positions that do not exist in your company make the SOP impossible to follow.
• Having no owner. An SOP without an owner is never revised.
• Ignoring real practice. If letters actually travel by email and chat, write the flow as it is and improve it step by step.
• Setting deadlines without monitoring. The numbers in the SOP mean nothing without a regular review.
• Skipping the rollout. Give each unit a short briefing and keep the current version in one place that is easy to open.

If you still use a spreadsheet and plan to move to an application, write the SOP first. The guide to incoming and outgoing letter applications explains how to choose one and how to switch in stages, and an application will only speed up rules that are already clear.

How Obscura helps

The Obscura Correspondence module runs a flow close to the outline above. An outgoing letter follows one path from template through approval and numbering to the archive, and approval tasks go to positions so that responsibility holds when people change jobs. Obscura issues the next number under the scheme you configure, and an issued number cannot be changed. Incoming letters are registered with an agenda number and routed to the responsible position with instructions and a deadline. Tasks and read access travel together, and both are withdrawn if the routing changes.

An issued letter files itself into the archive with its Document ID and starts its retention period, and you record the dispatch to close the letter. Incoming and outgoing letters share one register that you can search by subject, number, agenda, sender or scanned text. The Correspondence module is licensed separately from the core document management system, and the details are on the Correspondence page.