
Written by OpenKM on 7 august 2026
You can centralize incoming and outgoing correspondence, assign responsibilities, manage deadlines and approvals, and maintain complete traceability with OpenKM.
Organizations receive important correspondence through email, postal mail, scanned documents, web forms, and other channels. Some communications are simple to respond to. Others lead to deadlines, reviews, approvals, or even work involving multiple departments.
The problem arises when correspondence remains in personal inboxes, shared folders, or paper files. The communication exists, but the organization may not know who is responsible, what needs to happen next, or how to demonstrate what response was provided.
A correspondence management system allows you to track, categorize, assign, control, and retain incoming and outgoing communications as part of a structured process.
OpenKM provides document management, metadata, workflows, search, document relationships, permissions, and activity history capabilities that can be used to configure these types of processes.
A good correspondence management process is about more than simply storing documents. It needs to maintain a continuous flow from receipt through to response.
OpenKM can help at every stage of the process:
The result is a process in which each communication can be recorded with an identifier, responsible person, status, deadline, and outcome.
This allows different levels of control depending on the type of correspondence. A sales inquiry may require a simple assignment. A complaint, legal notice, or regulatory communication may require several reviews and formal approval.
Customers, suppliers, citizens, regulators, employees, and other parties may send correspondence. Outgoing correspondence may consist of responses, whether by letter or notification, confirmations, or other company communications.
OpenKM can be configured to maintain both types as separate but related records.
For example:
IN-2026-00417 – Incoming communication
OUT-2026-00188 – Outgoing response
When both records are linked, you can review the entire exchange without having to reconstruct it from inboxes and folders.
For this example, we are using a public administration case, but the same model can be applied to customer complaints, supplier messages, internal requests, legal notifications, and other types of correspondence.
A citizen sends an email to the city council to report a broken streetlight and attaches a photograph.
The communication needs to be registered, assigned to Public Works, and answered within the response deadline established by the organization.
A configured email account can import the message into OpenKM.
The email and photograph are stored, and the communication is associated with the following identifier:
IN-2026-00417
It may contain information such as:
In this case, the request is assigned to the Public Lighting team.
A workflow or rule can be used to assign the request to the responsible person.
The task will indicate the status, priority, deadline, and next steps.
Responsibility no longer depends on the latest email sitting in someone's inbox.
The process can also include an acknowledgment of receipt informing the citizen that the request has been registered.
The technician can view the email, photograph, metadata, and other related documents within the same context.
If an inspection is carried out regarding the same issue, the report can be associated with the same case.
This makes the process easier to manage when a request changes in scope or needs to be reviewed by another department.
Once the case has been reviewed, the technician prepares the response.
If the procedure requires approval, a supervisor can review the draft through a workflow before it is sent.
The final response can be registered as outgoing correspondence:
OUT-2026-00188
and linked to:
IN-2026-00417
This allows the organization to follow a clear chain:
request → assignment → review → approval → response.
A correspondence management system can also use structured information to provide visibility into ongoing work and processes.
Depending on the configuration, users can monitor:
The value goes beyond simply displaying indicators. Users should also be able to access the underlying records that explain what is happening.
OpenKM provides the platform technology, but each organization needs to adapt the process to its own requirements.
Metadata
A basic configuration may include:
Numbering
For example:
IN-YYYY-NNNNN
OUT-YYYY-NNNNN
Assignment Rules
Examples:
Customer complaint → Customer Service
Legal notice → Legal Department
Public Lighting → Public Works
Workflow
A simple process could be:
The level of complexity will depend on each organization.
The same model can be used across different areas:
Fields, permissions, deadlines, and workflows may vary, but the objective remains the same: accountability, context, and traceability from receipt through to closure.
Can OpenKM manage incoming and outgoing correspondence?
Yes. OpenKM can manage both types of correspondence and link them through metadata, workflows, and document relationships.
Can OpenKM manage reviews and approvals?
Yes. Its workflow capabilities can be customized for assignment, review, approval, and other processes.
Does every project require custom development?
No. Many requirements can be addressed through configuration, metadata, and workflows. Integrations with portals, CRM systems, ERP systems, external services, or specialized systems may require additional development.
From Storing Correspondence to Working with It
Managing documents is useful, but effective correspondence management requires more.
Every important communication needs to be linked to a responsible person, status, deadline, context, and response.
OpenKM allows us to structure this process using documents, metadata, workflows, and traceability.
In the example above, a simple email becomes part of a controlled process: it is registered, assigned, reviewed, answered, and linked to all the activity generated around it.
The same principle can be applied to many other correspondence processes within an organization.
How Can We Manage Our Correspondence with OpenKM?
Every organization has different processes, responsibilities, and deadlines.
OpenKM can be used to centralize correspondence, assign tasks, ensure that staff members are responsible for those tasks, obtain approvals for correspondence, and maintain links between incoming communications, internal work, and responses to incoming messages and emails.