How small container yards track containers

Small yards need one operational record from gate to billing.

A container yard does not have to be large to lose track of a container. It only has to have more than one person touching the record. One employee updates the spreadsheet in the morning. Another writes the spot on a paper ticket in the afternoon. A third moves a container to make room for a delivery and tells the yard manager by text message, if they remember to at all. By the end of the week, the spreadsheet says one thing, the yard says another, and nobody is fully sure which one is right.

This is not a technology problem in the way people usually mean it. It is a records problem. A container yard runs on a chain of small facts — who owns the container, when it arrived, where it sits, what condition it was in, and what should be billed for the time it has been on site. When that chain lives in different places, in different formats, updated by different people, the yard is guessing more than it realizes.

Why container tracking breaks down in a small yard

A spreadsheet or a notebook can hold container numbers just fine. The problem is not storage. The problem is that a container's status changes constantly, and each change needs to reach everyone who depends on it.

• A container is gated in, but the ticket is handwritten and filed later, if at all.
• A yard worker moves a container to a different row to make space, but does not update the sheet.
• A customer calls asking whether their container is ready for pickup, and the answer depends on who picks up the phone.
• A container sits past its free days, but nobody flags it until the customer disputes the invoice.
• Two spreadsheet versions exist — one on a shared drive, one downloaded and edited locally — and they disagree.
• A container leaves the yard, but the "departed" status is never recorded, so it still shows as on site weeks later.

None of these failures require a large yard. A yard with a few hundred container moves a month can lose the thread just as easily as one with a few thousand, because the underlying cause is the same: the record of where a container is and what has happened to it is not connected to a single, current source.

What "knowing where a container is" actually requires

Knowing a container's location sounds simple, but for a small yard it usually depends on several things being true at once:

1. The container was recorded when it entered the yard.
2. It was assigned to a specific location — a row, bay, slot, or named zone.
3. Any moves since arrival were logged, not just remembered.
4. The customer account it belongs to is current and correctly linked.
5. Its condition and any damage notes were captured at gate-in, not reconstructed later.
6. The free-day clock and any storage charges are tied to the correct arrival date.
7. Nothing marks it as departed unless a gate-out event actually happened.

A yard location, in other words, is not just a physical spot. It is a record — the recorded place where a container is parked or stored, whether that is a row, bay, slot, space, or named zone — and it is only as reliable as the last update that touched it.

The old way: paper walks, spreadsheets, and tribal memory

Most small container yards start with some version of the same manual process:

• A gate clerk writes the container number, and sometimes the spot, on a paper ticket.
• The yard team moves containers around during the day based on space, access, and priority — often without writing anything down.
• Someone periodically walks the yard to check what is actually there against what the spreadsheet says.
• Photos of container condition, if taken at all, live on someone's phone.
• Billing is handled separately, often at the end of the month, by someone reconstructing arrival and departure dates from the paper tickets and whatever the spreadsheet still agrees with.

This can work while the yard is small, quiet, and staffed by one or two people who know the lot by memory. It stops working the moment the yard grows, staff turns over, or a customer asks a pointed question: "Where exactly is my container, and why does this invoice show twenty storage days?"

At that point, the team is often asking questions the current process cannot answer quickly:

• Is this container still on site, or did it leave last week without anyone updating the sheet?
• Which row is it actually in right now, versus where it was first parked?
• Who logged the last move, and when?
• Has it passed its free days, and by how many?
• Do we have any proof of its condition when it arrived?

Every one of these questions is answerable — but only if the yard has been keeping a connected record instead of a set of disconnected notes.

The better way: one connected record from customer to billing

A small container yard does not need enterprise terminal software to fix this. It needs one record that follows a container through its entire stay, in this order: customer, order, ticket, in/out, location, rate plan, invoice, statement.

1. Start with the customer account

Every container belongs to a customer, and that account should carry the billing rules that apply to it — free days, per-TEU or per-container storage rates, and payment status — so nobody has to look them up separately when it is time to bill.

2. Capture the ticket at the gate

When a container is gated in, the ticket should record the container number, the customer, the driver, arrival time, condition notes, and photos or other proof — in one digital record, not a paper form that gets filed away and forgotten.

3. Track in/out records and location together

The container's status and its yard location need to be the same record, not two separate ones that someone has to reconcile. When a container is moved, the location updates. When it is gated out, the status updates. There is no separate spreadsheet to remember to touch.

4. Apply the rate plan automatically

Once the container is on the record with an arrival date and a customer account, free days and per-diem storage rates can be applied without anyone manually counting days on a calendar.

5. Let billing follow the record, not chase it

When a container is finally gated out, the yard already has everything it needs to invoice correctly: the arrival date, the departure date, the applicable rate, and the condition notes and photos that prove what happened in between.

A practical checklist for small container yard tracking

At minimum, a small container yard's record should capture:

• Container number and type.
• Customer account.
• Arrival date and time.
• Assigned yard location (row, bay, slot, or zone).
• Condition notes and photos at gate-in.
• Any moves since arrival, with timestamps.
• Free days and applicable storage rate.
• Departure date and time, when it occurs.
• Proof notes for gate-in and gate-out.
• Invoice and payment status.

If these fields are updated as events happen — not reconstructed later from memory — a small yard can answer "where is this container, and what do we owe or bill for it" without a yard walk or a phone call.

Why this matters for billing, not just operations

Losing track of a container is not only an inconvenience. It is a direct hit to revenue and to customer trust. A container that sits in the yard without a clear arrival date cannot be billed accurately for storage. A container that has moved rows three times without a logged update makes it harder to prove where it was and when, if a customer disputes a charge. And a container that departed without a recorded gate-out event can keep accruing storage charges on paper long after it is gone — an error that looks like overbilling to the customer and looks like a lost audit trail to the yard.

A connected record — customer, order, ticket, in/out, location, rate plan, invoice, statement — closes that gap. It does not require the yard to give up its current pace of work. It requires that each event, from gate-in to gate-out, gets recorded once, in the place everyone else already looks.

What Yarduno does for container yards

Yarduno is built for small and mid-sized container yards, depots, and short-term container parking operations that need in/out tickets, TEU or per-container storage rates, and a full chain-of-custody audit trail on one record — customer, order, ticket, in/out, location, recurring rate plan, invoice, payment, statement, and notifications. It is not a terminal operating system or an enterprise WMS; it is built for yards that mainly need to know what is on site, where it sits, and what should be billed.

CTA

Still tracking containers with a spreadsheet, a paper ticket book, and a yard walk to double-check? See how a connected record — customer, ticket, in/out, location, rate plan, invoice, and statement — keeps a small container yard from losing the thread.