Incoming and outgoing letter apps: a good flow and how to choose one

Many companies still run their correspondence with an agenda book, a spreadsheet and paper disposition sheets. That can work for a handful of letters a day, but it breaks down once the volume grows, several divisions are involved, or someone has to prove the process to an auditor. This guide describes a good flow for incoming and outgoing letters, what to check in a company correspondence app, and how to move off Excel without disrupting daily work.

How letters are handled in many companies today

The most common pattern combines three habits.

• An agenda book or Excel. A receptionist or admin records incoming letters in a ledger or spreadsheet. The next number comes from the last row, and when two people edit at once the numbers can collide.
• Makeshift scanning. Letters are photographed or scanned into PDFs and sent around by email or chat. File names are inconsistent, so finding one is only easy when you already know its number.
• Paper disposition. The disposition sheet travels from desk to desk. Who has read the letter, what the instruction was and when it is due often lives only in someone's head or in handwriting.

As a result, a simple question such as "did anyone reply to that vendor's letter?" takes phone calls to several people.

A good flow, step by step

Whatever the app, a healthy incoming-letter flow follows the same order.

1. Register. The letter is received, and its sender, letter date, the sender's own letter number and subject are recorded, with a scan attached.
2. Agenda number. Every incoming letter gets a unique internal agenda number, separate from the sender's number.
3. Disposition. A director or secretary routes the letter to the responsible position, with an instruction and a deadline.
4. Follow-up. The recipient carries out the instruction, and whoever assigned it can see the status.
5. Reply. If the letter needs an answer, an outgoing letter is drafted, approved, numbered and sent. Ideally the reply stays linked to the letter it answers.
6. Archive. The incoming letter, its disposition and the reply are filed together with a clear retention period.

Outgoing letters have a shorter path of their own: draft, review, approval, numbering, dispatch and archive. The numbering rules are covered in the guide to company letter numbering formats.

Checklist: what to look for in an app

Use this list when you compare incoming and outgoing letter apps.

• Numbering schemes. You can configure your own number format, separate series by letter type or unit, and reset the sequence each period. The system issues the number, so nobody types it by hand.
• OCR and scanning. Scanned letters are searchable by their content, not only by number or subject.
• Disposition with deadlines. Instructions, recipients and deadlines are recorded in the system, with reminders or a clear status when something is late.
• Linked reply letters. A reply can be connected to the letter it answers, so one thread of correspondence reads as a whole.
• Access control. Confidential letters are visible only to the people entitled to see them, and access follows when the disposition changes.
• Audit trail. Changes, decisions and activity on each letter are recorded, and the record cannot be edited quietly.
• Search. You can search by number, subject, sender, date, agenda number and the text of the letter.
• Retention. There are retention rules, and deletion can be held when there is a dispute.
• On-premise option. If company policy requires documents to stay on your own servers, check that the app can be installed on your infrastructure and is not offered only as a cloud service.

Moving off Excel or the agenda book in stages

You do not have to switch everything in one day. This order is usually the safest.

1. Fix the rules first. Write the number format, letter-type codes and series rules into an SOP. A new app only speeds up rules that are already clear.
2. Start with one type of outgoing letter. Pick a letter your team sends every week, such as a meeting invitation or a quotation, and run it through the app with one or two divisions.
3. Add incoming letters. Register new incoming letters with an agenda number and disposition in the app, while the old archive stays where it is.
4. Run in parallel briefly. For a month or two, compare the old register with the new one to catch gaps.
5. Import or archive the old data. Decide whether old records are imported or kept as a read-only archive with a recorded cut-off date.
6. Retire the old spreadsheet. Once every division has moved, make the old file read-only so that no number is issued in two places.

When Excel is still enough

Excel or an agenda book still makes sense when you receive only a few letters a day, one person does the numbering, and nobody needs proof of an approval trail. The signs that you have outgrown it are easy to spot.

• The same number has been issued twice, or a number has gone missing with no explanation.
• Finding an old letter means asking several people.
• Dispositions are scattered across paper, email and chat, so it is hard to confirm who followed up.
• An auditor or manager asks who approved something and when, and the answer has to be assembled from many places.
• Confidential letters travel through the same channels as ordinary ones.

One or two of these signs is reason enough to tidy up, whether with an app or at least with a firm SOP.

Common mistakes when choosing an app

• Judging by the demo screens alone, when what matters is your own letter flow. Ask the vendor to run one real letter from start to archive.
• Ignoring incoming letters, which is where dispositions and follow-ups get lost most often.
• Moving the whole company at once without a pilot in one division.
• Not checking whether a feature needs an extra module or licence.
• Postponing access rules until after go-live, so confidential letters are open to every user.

Questions to ask vendors

These questions help separate a good demo from an app that actually fits.

• How do you prevent number collisions when several people number at once, and what happens to a voided number?
• Can we configure our own number format, and how much can an administrator change without the vendor's help?
• What happens to read access and tasks when a disposition is changed or withdrawn?
• How are scanned letters made searchable, and how accurate is that on our real letters rather than demo samples?
• What does the audit trail look like, and can it be exported for auditors?
• Where is our data stored, and is there an on-premise or closed-network option?
• How is our existing data migrated, and who does the work?
• Which modules are licensed separately, and what exactly is in the quoted price?
• What happens to our data when the contract ends?

How Obscura helps

The Correspondence module in Obscura registers incoming letters with an agenda number and routes them to the responsible position, with an instruction and a deadline. Tasks and read access travel together, and both are withdrawn if the routing changes. Scanned letters are made searchable with OCR when they are registered. Incoming and outgoing letters share one register that you can search by subject, number, agenda, sender or scanned text, and outgoing numbers are issued under a configured scheme and cannot be changed once issued. Details are on the Correspondence page.

On the document control side, you decide who can view and change each record. The audit log records changes, decisions and activity on each document, and retention rules and legal holds support your records policy. Letters marked confidential follow the document's access rules. See Document control for more.

For hosting, Obscura can run on your own servers, including a closed network, or Valid can run it for you as a service. The Correspondence module is licensed separately from the core document management system, so modules and hosting are agreed with your team before configuration. The full options are on the Deployment page.