A document has two lives, and your organisation has to control both.
Its first life is movement. It arrives, gets logged, travels between departments, collects signatures and comments, and demands a reply before a deadline. Its second life is memory. The case closes, the document becomes part of the institutional record, and it waits to be recalled for an audit, a dispute, a handover, or a decision years later.
Most organisations manage the first life with effort and the second with luck. Correspondence is tracked while people are watching, then it disappears into folders nobody searches. The result shows up at the worst moment. An auditor asks for an approval from five years ago, and the answer takes three weeks.
Closing that gap is not one large project. It is five specific decisions. This is how we frame them with the organisations we work with, and how our platforms, CMS for correspondence and ELArchive with the Backfile Scanning service for archiving, answer each one.
Do not wait for the audit to reveal the gap. Bring us one live correspondence type and we will map where its identity, ownership, closure, permissions, and retrieval should sit.
Map the handoffDecision 1: Where does a document get its identity?
A document without a single permanent identity cannot be tracked or retrieved. Organisations that skip this decision end up with the same letter carrying three reference numbers in three departments.
The answer is to assign identity at the point of entry. CMS creates a unified correspondence number the moment a document is logged, and that number can be printed as a barcode. From that point, every action, attachment, and routing step links to that one number. On the archive side, ELArchive can generate a barcode automatically for each document, and files carry their own barcodes too. One document, one identity, from the mailroom to the archive shelf.
Decision 2: Who is accountable for a document while it moves?
Movement without accountability is how correspondence gets lost. If a letter can pass through four hands with no record of who held it and for how long, responsibility evaporates.
CMS makes the path itself the record. The sender and recipient can follow the status of each piece of correspondence, the actions taken on it, and the time it spent with each recipient, and can print the full correspondence path for a manager's review. Referring a document requires selecting the action required from each department or employee, so routing is never merely "for information" unless the organisation wants it that way. Reply dates with colour-coded alerts keep deadlines visible, and follow-up periods can be set so the sender knows what happened without chasing anyone.
If your team still asks "who has this letter?", you do not have a correspondence process. You have a search party. See how CMS turns every handoff into a record.
Explore CMSDecision 3: When does a document stop being correspondence and become a record?
This is the decision most organisations never make consciously, and it is where the document's two lives meet.
The transition should be deliberate. In CMS, departments create classified archive files and link closed correspondence to them, with classifications each department defines for its own work. Correspondence links to a single file, so the record stays unambiguous. For enterprise-scale archiving, including decades of paper backlog, ELArchive and the Backfile Scanning service organise intake. Documents are scanned, indexed against fields defined for each document type with validation rules on every field, and reviewed in a quality-control stage where rejected items are returned for correction with recorded reasons.
A record that enters the archive through this gate is complete, checked, and retrievable. A record that drifts into a shared folder is none of those things.
Your paper backlog is not a storage problem. It is an intake problem. Backfile Scanning gives old paper the same classified, indexed, quality-checked entry path as new records.
See Backfile ScanningDecision 4: Who is allowed to reach the record, and how deep?
An archive everyone can open is a liability. An archive nobody can open is a filing cabinet with a power cable.
The practical answer is tiered permissions. Users see documents from their own departments. Groups define which features, such as download, print, or share, are available to which staff. The Backfile Scanning service adds confidentiality levels that can hide entire sections of the archive from users without the required clearance, and allows annotations on electronic documents that can be printed with or without the notes. Both platforms authenticate users through Active Directory, so access follows your existing identity management rather than a parallel account list.
Decision 5: How fast should retrieval be, and can you prove performance?
Retrieval speed is the entire return on an archiving investment. It is also measurable, so measure it.
ELArchive offers four search paths: document indexes, file indexes, document barcodes, and file barcodes. The Backfile Scanning service supports exact and approximate search across any field or combination of fields, with more than one search format at once, and lets several users view the same document at the same time. Behind search sit the reports: daily and periodic entry reports, incomplete-file reports, and per-user and per-department statistics in ELArchive, archiving-rate measurement in the Backfile Scanning service, while CMS dashboards track correspondence status and task completion rates by month, week, department, and user.
Leadership does not have to take archive health on trust. The numbers are in the reports.
Ask for the number that matters: how many seconds from request to record? ELArchive was built so retrieval performance can be searched, reported, and defended.
Explore ELArchiveOrganisations that decide, and organisations that drift
None of these five decisions requires a technical miracle. They require an organisation to treat its documents as assets with a full lifecycle, not as traffic to survive. That is the difference between organisations where a record surfaces in seconds and organisations where a missing page holds up a committee for a month.
IT-Blocks has been building for the first kind of organisation since 2001. CMS, ELArchive, and the Backfile Scanning service run today inside government bodies and private-sector institutions across Egypt and Saudi Arabia. The Backfile Scanning service is a ready system that deploys without development work, supports unlimited users, and runs entirely in the browser.
Pick the one decision your organisation has left unresolved, the one costing you the most time today, and bring it to us. We will walk you through what it looks like when the whole lifecycle runs on one connected foundation.
Frequently Asked Questions
What connects correspondence management to electronic archiving?
A controlled handoff connects the two: unified document identity, accountable movement, deliberate closure, tiered permissions, and retrieval performance that can be measured.
Where should a document get its identity?
At the point of entry. CMS assigns the unified correspondence number, while ELArchive and archive files carry barcodes for long-term retrieval.
When does correspondence become an archive record?
When the case closes and the correspondence is linked to a classified archive file, indexed, quality checked, and accepted as a complete record.
How do the three IT-Blocks components work together?
CMS governs active correspondence, ELArchive stores the governed record, and Backfile Scanning converts legacy paper into indexed, quality-controlled archive content.