Skip to content
Corporate mailroom management

Every document accounted for — from the gate to the desk.

SmartMailroom gives your centralised mailroom one auditable record for every inbound and outbound shipment: courier handover, LIN barcode, pigeon-hole sorting, runsheet or mobile proof of delivery, reminders, archival and shredding. Nothing arrives without a record. Nothing leaves without an approval.

< 3 min
Counter handover, from LIN to signature
100%
Shipments traceable by LIN
R1–R3
Automated collection reminders
2-level
Outbound approval before despatch
The problem

A register book cannot answer “where is my courier?”

In most corporate mailrooms the courier drops a bundle, someone signs a paper sheet, and the documents disappear into a rack. When a legal notice, a cheque or a board pack goes missing, there is no trail — only memory. SmartMailroom replaces that register with a timestamped, signed, searchable record at every hop.

No proof of handover

Courier staff leave without an acknowledgement, so a disputed delivery cannot be settled.

Documents sit uncollected

Shipments age in the pigeon hole with nobody chasing the employee to collect them.

Despatch without control

Employees send shipments through any courier at any rate, with no manager sign-off.

Manual courier follow-up

Somebody spends the morning on courier websites, pasting AWB numbers one by one.

Inbound · 01–07

Inbound: from the courier's hand to the employee's desk

Everything arriving for the company — letters, parcels, big boxes, legal envelopes — is handed over at the centralised mailroom and captured before it moves anywhere else.

The core of the product: an employee states their LIN at the counter and walks away with the document in under three minutes, signature captured.
01 LOG ENTRY

Single log entry at handover

When the courier representative arrives, the mailroom makes one log entry — courier name, date, time and number of shipments — and captures the delivery person's digital signature on screen as confirmation of handover. One entry covers the whole bundle, so the counter keeps moving.

Courier master Digital signature Shipment count
02 INBOUND ENTRY

In-depth entry against the log

Each shipment in the bundle is then opened up into a detailed inbound entry, linked back to its log: AWB number, sender details, receiver employee, number of pieces and document type — normal, parcel, big box, and any other type you define in the master.

AWB no. Sender & receiver Pieces Document type
03 LIN

A unique LIN is generated

The application issues a Letter Identification Number — the shipment's identity for the rest of its life. Every later action, query and report hangs off the LIN, which is what makes a three-minute counter handover possible.

The leading letter carries the shipment's category, so an operator reads the priority off the number itself before opening a single screen:

N0112/1 Normal — routine correspondence on the standard delivery round
P2510/10 Priority — moved ahead of the normal queue
H1125/2 High priority — intimated and delivered immediately
C123 Company — addressed to the organisation rather than a named employee
X2512/2 Resigned employee — routed to HR or the reporting manager instead of the desk
Unique per shipment Category in the prefix Barcode-ready
04 SORTING

Sorted into the pigeon hole

Shipments are sorted by department, floor or employee and placed in the assigned pigeon hole (PH). The PH location is held against the LIN, so any mailroom operator — not just the one who sorted it — can retrieve the document.

PH master
05 INTIMATION

Intimation email to the employee

An automatic intimation goes out to the recipient with the LIN and shipment details, either inviting them to collect from the counter or telling them it will arrive on the next scheduled desk delivery — morning or evening.

Email template master Delivery schedule
06 DELIVERY

Counter, desk or mobile delivery

The shipment is handed over by whichever mode suits the recipient — over the counter against a LIN, on a printed runsheet, or through the Android delivery app. All three modes are covered in detail below.

Counter Runsheet Mobile POD
07 PROOF

Proof of delivery and confirmation mail

A digital signature is captured at the point of handover and stored against the LIN as the proof of delivery. A delivery confirmation email is then sent to the employee, closing the inbound cycle with an auditable record from courier to desk.

POD storedAudit trail closed
Three delivery modes

Hand it over the counter, on a runsheet, or on a tab

Different floors work differently. SmartMailroom supports all three ways of getting a document to its owner, and closes the same record whichever one you use.

Mode 01 · Counter

Counter delivery against LIN

The employee comes to the mailroom and states the LIN from their intimation email. The operator keys it in, the screen shows the pigeon-hole location, the document is pulled and signed for on the spot.

  • LIN lookup returns the PH location instantly
  • Digital signature captured as POD
  • Whole transaction inside three minutes
Mode 02 · Desk · Paper

Runsheet desk delivery

The mailroom generates a runsheet (delivery sheet) for the round. The delivery staff carry the physical shipments and the printed sheet, visit each desk, and take the recipient's signature on the sheet as POD.

  • Runsheet grouped by floor, department or route
  • Signature taken against each line on the sheet
  • Status entry on return marks each LIN delivered or undelivered
Mode 03 · Desk · Mobile

Mobile POD on Android

Instead of printing, the runsheet is pushed to the delivery person's mobile or tablet. The recipient signs on the device, and the status entry closes itself — no paper, no second round of data entry back at the mailroom.

  • Runsheet delivered to the enabled device
  • On-screen signature at the desk
  • Status entry closed automatically, confirmation email fired

Undelivered is a status, not a gap. Anything that comes back from a round is recorded as undelivered against its LIN and stays in the pigeon hole, where the reminder cycle picks it up.

Retention & closure

What happens to what nobody collects

A shipment that stays in the pigeon hole moves through a defined retention path — reminders, archival, retrieval, and finally disposal — with every interval configurable in the master screen.

R1 DAY n

First reminder

The mailroom sends the first reminder to the employee to collect the pending shipment from the pigeon hole.

R2 DAY n

Second reminder

A second reminder follows after the gap set in the master, usually copied to the reporting manager.

R3 DAY n

Final reminder

The last reminder before the shipment leaves the mailroom floor. The days between R1, R2 and R3 are all master-driven.

A1 ARCHIVE

Compacting to the archive room

Still uncollected, the shipment is moved out of the pigeon hole into the archive room — compacting — and its new location is recorded against the LIN. The compacting period itself is set in the master screen.

Location updated
A2 FETCH

Fetch from archive on request

Within the compacting period the employee can still walk in and request the shipment. It is fetched from the archive room, handed over, and a fetch confirmation email is fired automatically.

Still traceable by LIN
A3 DISPOSE

Shredding on approval

At the end of the compacting period, shipments still uncollected are shredded — only against a recorded approval. The disposal is logged, so the audit trail survives the document.

Approval-gated
MS EXCEPTION

Missing status entry

If a shipment cannot be found at any stage, it is marked through the missing status screen rather than quietly disappearing — giving you a real, reportable exception instead of a silent loss.

Reportable exception
Outbound · 01–06

Outbound: controlled despatch through your contracted couriers

Everything leaving the building — to customers, vendors, branches or regulators — goes out through the couriers you have agreed rates with, at the product you chose, with the approvals you require.

01 LOG ENTRY

Log entry on receipt from the employee

The employee brings the document to the mailroom to be sent outside or to a branch, and may request a specific courier. The mailroom makes a log entry at the moment it takes custody.

02 OUTBOUND ENTRY

Detailed outbound entry

Sender employee, recipient name and address, destination pincode, courier and courier product, number of shipments, weight and document type are captured against the log.

Sender · Recipient Courier product Pieces & weight
03 ROUTING

Pincode-mapped courier suggestion

Based on the pincode-to-courier mapping held in the masters, the application proposes the couriers that actually service that location. The operator picks one and enters the AWB number against the shipment.

Location masterAWB capture
04 HANDOVER

Evening handover with digital signature

At the end of the day all outbound shipments are handed to the respective courier representatives, who sign for the bundle inside the application — the mirror image of the inbound log entry.

Courier-wise manifest
05 STATUS

Delivery status update

Two to three days later the delivery status is updated against each AWB — manually, or automatically for couriers connected through the API integrations below.

06 RATE

Rate module and cost allocation

Contracted rates per courier, product and zone let you cost each shipment and attribute it to the sending department — turning courier spend from a monthly surprise into a line you can query.

Rate masterDepartment-wise cost
Employee self-service

Employees prepare their own despatch. Two approvals release it.

An employee can complete the data entry for their own shipment in advance and keep it ready for the mailroom's collection round. Nothing is connected to a courier, though, until both approvals are in.

  • Employee entry. Recipient, address, pincode, pieces and preferred courier, entered from the desk.
  • Level 1 — department manager. Approves shipments raised by their own team.
  • Level 2 — admin. Releases the shipment for connectivity with the courier.
  • Rejection at either level. Both approvers can reject with a reason, which goes back to the employee.
Outbound approval queue showing request reference, department, destination, manager approval and admin approval status
RequestDepartmentDestinationMgrAdmin
OB‑4412FinanceMumbai · 400051 Approved Approved
OB‑4413LegalNew Delhi · 110001 Approved Pending
OB‑4414HRCoimbatore · 641014 Pending Waiting
OB‑4415MarketingBengaluru · 560001 Rejected —

ILLUSTRATIVE SCREEN — SAMPLE DATA, NOT LIVE RECORDS

Courier integrations

Delivery status that updates itself

SmartMailroom connects directly to Blue Dart and India Post for outbound delivery activity, so nobody in your team spends the morning pasting AWB numbers into courier websites.

Blue Dart API

Outbound shipment status pulled back into the LIN record automatically.

India Post API

Booking and status updates for Speed Post and registered articles, inside the application.

HR / AD employee sync

Employee, department and location masters kept current from your HR system or directory.

Barcode & label printing

LIN barcode labels and courier labels printed at the counter for scan-based retrieval.

Configuration

Your rules live in the masters, not in a change request

Reminder gaps, compacting periods, document types, pigeon-hole layout, courier products and pincode service maps are all configured by your administrator — so the process bends to your policy.

Reminder & retention

Days between R1, R2 and R3; compacting period; shredding approval rules.

Pigeon hole & archive

Rack, row and hole layout, department mapping and archive-room locations.

Courier, product & pincode

Contracted couriers, their products, serviceable pincodes and delivery locations.

Document type & rates

Normal, parcel, big box and your own types; courier rate cards by product and zone.

Query · Reports · MIS

Answer the question before it becomes an escalation

Beyond the process, SmartMailroom ships with a query screen, an operational report set, MIS for management and a dashboard for the mailroom floor.

Search a single LIN or AWB and see its whole life — courier, log, entry, pigeon hole, reminders, runsheet, signature, archive movement — on one screen.

Query screen

Search by LIN, AWB, employee, department, courier, date range or status.

Operational reports

Daily inbound and outbound volume, pending collection, runsheet status, ageing in PH.

MIS pack

Courier-wise volume and spend, department-wise usage, SLA and turnaround analysis.

Live dashboard

Today's receipts, pending POD, overdue reminders and exceptions at a glance.

Who it is built for

Built for centralised corporate mailrooms

MNC head offices, shared service centres, banks and insurers, IT campuses, manufacturing corporate offices, hospitals and facility-management providers running a mailroom on behalf of a client.

Facility & admin heads

A defensible record for every document and a courier spend you can explain.

Compliance & legal

Signed proof of delivery, retention periods and approval-gated disposal.

Mailroom operators

One screen per task, LIN-driven retrieval, and no evening of catch-up data entry.

Questions

Frequently asked

Still unsure how a step would work in your building? Ask us — we will walk your actual process on a demo instance.

Talk to us

LIN stands for Letter Identification Number. SmartMailroom generates one automatically for every inbound shipment at the point of detailed entry. It is the shipment's identity for the whole of its life — sorting, pigeon-hole location, intimation email, counter handover, runsheet, proof of delivery, reminders and archival all refer back to it. Because the employee quotes the LIN at the counter, the operator can locate and release a document in under three minutes. The first letter encodes the category: N normal (N0112/1), P priority (P2510/10), H high priority (H1125/2), C company (C123) and X resigned employee (X2512/2).

They serve different purposes. The log entry is fast and happens while the courier representative is still standing at the counter: courier name, number of shipments, and their digital signature. That closes the handover and releases the courier. The detailed inbound entry — AWB, sender, receiver, pieces, document type — is then done shipment by shipment against that log, without holding anyone up.

With runsheet delivery the mailroom prints a delivery sheet, the delivery person collects signatures on paper at each desk, returns to the mailroom, and does a status entry to mark each LIN delivered or undelivered. With mobile delivery the same runsheet is pushed to an enabled mobile or tablet, the recipient signs on the device, and the status entry closes automatically — removing the second round of data entry and firing the delivery confirmation email immediately.

They go through three levels of reminder — R1, R2 and R3 — with the gap between each set in the master screen. If still uncollected, they are compacted into the archive room for a master-defined period, during which an employee can still request the shipment and have it fetched and handed over, with a confirmation email. At the end of that period, uncollected shipments are shredded against recorded client approval.

Yes. An employee can complete the outbound data entry from their desk and keep the shipment ready for the mailroom's collection round. Two approvals are required before the shipment can be connected to a courier: the department manager for their own team, and the admin for despatch. Either approver can also reject the request.

Each contracted courier's serviceable pincodes and products are held in the master screens. When the outbound entry captures the destination pincode, SmartMailroom proposes the couriers that service that location, and the operator selects one and records the AWB number against the shipment.

SmartMailroom integrates with Blue Dart and India Post through their APIs for outbound delivery activity, so status updates flow back into the shipment record instead of being looked up manually. Other couriers are handled through AWB capture and status entry, and further integrations can be taken up as part of implementation.

There is a dedicated missing status entry screen. Marking a shipment missing records it as a formal exception against its LIN, with the last known status, location and handler — so it appears in reports and can be investigated, rather than simply vanishing from the register.
Get started

See your own mailroom process, running.

Tell us how documents move through your building today. We will configure a demo instance with your departments, couriers and retention rules, and walk you through a full inbound and outbound cycle.

Office
MRK Infotech, 11/6 Thiruvalluvar Nagar Main Road,
Alandur, Chennai 600016, Tamil Nadu, India

Request a demo

WE REPLY WITHIN ONE WORKING DAY