Skip to main content
Early accessBeta, invite only since 1 Nov 2026. A person reads every application.Apply for an invite
Demystify OS

How do I track dispatch and delivery without software?

Keep one dispatch register with a line per consignment: party, items, transporter, receipt number and promised date. Review undelivered lines every morning, call the transporter for late ones, and get a signed proof of delivery. Record any shortage the day it is reported.

Who asks this: A dispatcher, owner or accounts person at a small trading or manufacturing business in India who sends goods through transporters, hears about delays from angry customers, and does not want to buy software for it.

The steps

  1. 1. Open a register with fixed columns

    Use one sheet or a bound book with these columns: date, party, town, items and quantity, challan number, transporter, lorry receipt number, promised delivery date, status. One person fills it at the gate. If a line is missing, the consignment did not officially go.

  2. 2. Log at the moment the vehicle leaves

    Enter the line before the truck leaves the gate, while the paper is in hand. Take a photograph of the lorry receipt and keep it in a folder named by date. Later entry leads to missing receipts and arguments.

  3. 3. Tell the customer the same day

    Send the party a short message with the transporter's name, the receipt number and the expected date. A customer who has the number can ask the transporter directly, and your phone rings less.

  4. 4. Review undelivered lines every morning

    Filter the register for lines past their promised date or without a delivered mark. Call the transporter's branch for each, note the answer and a new date. Two firm calls usually move a stuck consignment.

  5. 5. Collect proof of delivery

    Ask for the signed copy of the receipt or a photograph of the signed challan. File it against the line and mark it delivered only then. This one habit settles most disputes about whether goods arrived.

  6. 6. Record shortages and damage immediately

    If the customer reports a shortage or damage, write it on the line with the date, the quantity and a photograph. Raise the claim with the transporter within the time the transporter allows, and agree with the customer how the gap will be made up.

A worked example

illustrative

A tile dealer in Morbi logs every consignment before the truck leaves and photographs the receipt. On Wednesday the dispatcher filters the register, finds two consignments past their date, calls both transporter branches and gives the customers new dates. Later a Pune customer reports two broken cartons. Two cartons at eighteen hundred rupees apiece come to thirty-six hundred rupees of exposure. The register holds the photograph and signed copy, so the claim is raised that day. It is marked raised, and recovered only when the transporter pays or credits it.

What goes wrong

  • Entries are made in the evening from memory, so receipt numbers go missing.
  • The customer is told a date by one person and a different date by another.
  • Nobody asks for a signed copy, and the customer later says goods never arrived.
  • A shortage is reported after a week and the transporter refuses to look at it.
  • Late consignments are noticed only when the customer calls.
  • The register is on one person's phone, and nobody else can answer when that person is away.

How Demystify OS helps

  • Close the van dayEarly access

    For distributors selling from vans, you load the van against a challan, bring unsold stock back and close the day, with a short van shown at day end. It covers van sales rather than a transporter register.

  • Owner brief, morningEarly access

    The Owner brief, morning routine can list what needs a decision from the sources connected to your workspace, so a list of late consignments can reach you if the dispatch register is one of those sources.

  • Mysty WorkersEarly access

    Mysty Workers are set up with you. A dispatch follow-up worker would read the register you give it and draft a customer update for your approval. It is not yet a standard catalogue entry.

What it does not do. Demystify OS does not connect to transporter systems, does not track a vehicle on the road, and does not know a delivery status that nobody has written into your register.

Questions people ask

What should a basic dispatch register include?

The date, the party, the items and quantity, the challan or invoice number, the transporter, the lorry receipt number, the promised date and the status. Add a column for proof of delivery. Anything more makes the register slow to fill and likely to be skipped.

How do I know a consignment was really delivered?

Ask for a signed copy of the receipt or a photograph of the signed challan, and file it against the line. Until you hold that, mark the line as sent, not delivered. This single rule removes most arguments.

How long should I wait before chasing a transporter?

Chase on the promised date, not after. Call the branch in the morning, note the answer and a new date, and call again if it slips. Keep a firm tone but stay friendly, because you will need the same transporter next week.

What if the customer says goods were short?

Ask for a photograph and the quantity received the same day, write it on the register line, and raise it with the transporter at once. Agree with the customer how the gap will be made up, either a resend or a credit.

Can one sheet manage a few dozen consignments?

Yes. A well-kept sheet with filters is enough for a small dispatcher. Move to a tool only when two people must edit at once or when the sheet becomes slow. The habit of logging before the truck leaves matters most.

Apply for the beta.

Demystify OS is invite only, and a person reads every application.

Apply for the beta