Freight Pallet Board

The Freight Pallet Board answers one question: how many physical freight pallets are booked, awaiting pickup, collected, at each depot, loaded, moving, out for delivery and delivered — and which connotes make up every number?

It is a freight view measured in pallets. It is not the hire-equipment ledger the other Pallets pages show (CHEP/Loscam accounts, dockets, declarations), and it never reads a pallet docket.

Open it from Pallets → Freight Pallet Board in the sidebar, or the Freight Pallet Board tab on any Pallets page.

What counts as a pallet

Only booked freight lines whose packaging type is configured as a pallet count. One unit on such a line is one physical pallet. Deck spaces and chargeable pallets are different measures and are never shown here: two oversize pallets that take four deck spaces and are charged as four are two pallets on this board.

Not confirmed is not zero

A quantity nobody has counted shows Not confirmed, never 0. A pickup stop can be completed, or a connote can say delivered, and the collected or delivered quantity is still Not confirmed until someone records a count.

A count of 0 is a real, confirmed zero — for example a pickup where the freight was not ready.

Nothing ever copies a booked quantity into an actual one, and connotes moved before the board existed have no counts.

The three views

Lane board

The top of the page shows two groups of numbers. Read them differently.

Progress totals are milestones: booked, confirmed collected, picked up but count not confirmed, confirmed delivered, outstanding pickup, outstanding delivery and with a variance. They overlap — a delivered pallet was also collected and booked — so never add them together.

Current position shows where every pallet is right now. These buckets do not overlap: each pallet is in exactly one of them.

Bucket	Meaning
Awaiting pickup	Still at the sender.
On pickup vehicle	Collected and on the pickup truck, not yet at a depot.
At depot	Received at an origin or hub depot.
Loaded, not departed	Loaded onto a truck whose run has not started.
In linehaul transit	On a linehaul run that is moving.
At destination depot	Received at the destination depot.
Out for delivery	On a delivery run that is moving, with the drop still pending.
Delivered	Counted as delivered to the receiver.
Not confirmed	Picked up (or past pickup) with no collected count, or still on a truck whose run has finished — arrival is not receipt.
Unresolved discrepancy	More pallets left a place than were confirmed there (for example 10 loaded out of a depot that confirmed 8). Open the connotes behind it and correct the wrong count.

Every number shows its connote count beside the pallet count.

Below that, each lane has its own row. Lane level, above the lane table, chooses how lanes are grouped:

• Region - the default. A lane runs from its origin region to its destination region. Click a region row to show the zone pairs inside it; click again to hide them. Every number on a region row and on each zone pair opens the connotes behind it.
• Zone - one row per origin zone to destination zone.

The board remembers the lane level for each signed-in viewer in this browser, and nothing else: filters still start empty. Changing the level only regroups the lane rows. The progress and position totals at the top stay the same. If browser storage is unavailable, the board starts at Region.

A lane’s origin and destination regions come first from its approved zone groupings. Where no grouping is available, the board uses the first pickup address and final delivery address, matching their Australian state and postcode against the company’s approved operational reference.

Unassigned region means the available address information is missing, uncovered or conflicting. It does not mean zero pallets. The reference covers configured operational postcodes; it does not claim to cover every Australian postcode or define official postal boundaries. Unassigned is a working row: open its numbers and zone pairs to inspect the connotes and resolve their region or address details. Inside a region, Missing origin or destination zone groups connotes that lack a zone at either end.

The lane remains the end-to-end origin and destination, whichever depot currently holds the freight. Only pallet freight is on the board: a connote whose expected pallets are above zero or not yet known, or that has a confirmed count above zero or pallets somewhere. A connote confirmed to have no pallets, such as carton-only freight, is left out of every number, lane row, list and export; a voided count, or one corrected to zero, does not bring it back. Unknown pallet quantities remain visible for review. Cancelled connotes that were never collected are not active freight and are left out of every number, lane row and list too. A region with no pallet freight has no lane row.

Network totals count each connote once. A lane is marked Local when both ends are the same zone, or at Region level the same configured region.

Depot position

Choose a depot to see three separate numbers:

• Confirmed here — pallets someone has counted into this depot and that have not been loaded out.
• Expected inbound — pallets on trucks heading to this depot (the truck’s run ends here, or it has a depot stop here).
• Planned outbound — pallets here that already have their next leg allocated but have not been loaded.

They are kept apart on purpose: pallets on the way are not pallets in the yard.

Connote journey

Click any connote number, or use Find (below). The journey shows:

Ref	Quantity
A	Originally declared
B	Current approved expected
C	Actual collected
D	Actual received at each depot
E	Actual loaded, per run
F	Current confirmed custody at destination depots
G	Actual delivered
H	Outstanding and variances, with the reason and what happens to the remainder

Under that is the expected-quantity history and every count, including corrected and voided ones: who recorded it, their role, the evidence it rests on, when it happened and when it was entered, the stop, run and depot, and the depot role (origin, hub or destination) with how it was decided. Allocations, stops, runs and exceptions are listed too.

Find opens one connote’s journey by its connote number. Type the whole number; letter case and spaces before or after it are ignored. Find ignores the date basis, the filters and whether the board counts the connote, so it also opens a connote outside the current date basis or one with no pallets. It does not match part of a number, a reference or a customer name: use Search in the filters for those, which stays within the date basis. Finding a connote changes nothing else: the board’s numbers, lists and export keep their filters.

Drilling down

Every number is a link. Clicking it opens the list of connotes behind that number, with the same filters. The totals at the top of that list are for the whole filtered set; moving between pages never changes them.

The Lane column of that list follows the lane level. A list opened from a lane row keeps that row’s level, even if you switch the lane level while the list is open.

Filters and date basis

Filter	What it does
Date basis	Live (default): position now, including older freight that is still open, closed freight with residual custody or discrepancies, plus anything counted or corrected today. Pickup date: the booking cohort picked up in a date range. Count date: connotes with a count in the date range, plus activity in period totals per count type.
Depot	Connotes confirmed at, expected into or planned out of that depot.
Origin / destination region	Connotes whose origin or destination resolves to that region through its approved grouping or address reference. It combines with the zone filters, so a region and a zone outside it show nothing. The list holds every configured region, including regions with no pallet freight on the board right now. Unassigned is not in this list; open the Unassigned lane row instead.
Origin / destination zone	The end-to-end lane.
Leg	The leg the pallets are on or go to next (first mile, linehaul, last mile, full).
Stage	The derived lifecycle stage.
Exceptions	Only connotes with (or without) an exception flag — on hold, failed delivery, shortage, refused, damage.
Customer, LTL/FTL, pallet type, run, unit	As named.
Search	Connote number, customer reference, booking reference or customer name, within the date basis. To open one connote outside it, use Find on the Connote journey view.

The basis in use and the as of time (in the business timezone) are shown above the numbers. Positions are always worked out from every count a connote has ever had, so a count-date filter changes which connotes are shown, not where their pallets are.

Unmapped lanes

A connote with no origin or destination zone cannot go in a zone lane. It is listed in the Unmapped lane queue with a link to the connote, at either lane level. At Region level it also appears under Missing origin or destination zone inside its region row. Fix the zone on the connote and it moves into its lane. Its pallets still count in the network totals.

Unmapped is about a missing zone. Unassigned means no region could be resolved from the available grouping or address reference. A connote can have both zones and still be Unassigned; it is not then in the Unmapped queue. A connote missing a zone may still resolve to a region from its address.

Recording counts

Operations and Admin users see Record count buttons; everyone else sees the board read-only. The server refuses a count from any other role regardless of what the screen shows.

Every count needs:

• the actual quantity (the expected quantity is shown beside it);
• an evidence note — what the count rests on, for example “Driver phoned, 10 on the docket” or “Counted on the dock”;
• when it happened (defaults to now).

When the actual quantity differs from the expected, choose a variance reason; a short pickup also needs what happens to the remainder (awaiting pickup, rebooked, split, short shipped, held, and so on).

You may also enter the pallet types (for example 6 CHEP and 4 Plain). They must add up to the quantity.

Count	Where	Notes
Pickup (collected)	A pickup stop on the connote’s run	One per pickup stop.
Depot receipt	A depot	Choose the inbound run, or none if the sender dropped the freight at the depot (that counts as collected). If the system cannot tell whether this depot is the origin, a hub or the destination for the connote, it asks you.
Load	Onto a run	Choose the depot the pallets left, or the source run allocation for a confirmed vehicle transfer. A source run and depot cannot both be selected.
Delivery	A delivery stop	One per delivery attempt. A failed attempt delivers nothing.

Recording a count never completes a stop, starts a run or changes the connote’s status by itself. Delivery still needs the drop completed and POD. When a connote has delivery counts, it is only marked delivered once the delivered pallets reach the expected quantity; a short delivery leaves it in transit with an exception.

If the connection drops while saving, press Save again: the same submission is recognised and not recorded twice.

Corrections

Counts are never edited or deleted. To fix one, open the connote journey and choose Correct on the count. Enter the right quantity, or void it if it should never have been recorded, and a reason. The original stays visible, marked as corrected.

If you try to record a second count for the same stop, the board tells you one already exists and offers to correct it instead.

Changing the expected quantity

If the sender changes how many pallets are coming, use Change expected on the journey. A reason is required. The original declaration (A) never changes; the new expected quantity (B) is added to the history.

Freshness

The time of the last refresh is shown as as of hh:mm. After five minutes without a refresh the board is marked stale; press Refresh. It refreshes itself after every count you record.

Export

Export CSV downloads the connote list for the current filters, with the same definitions as the screen. Not-confirmed quantities are written as Not confirmed, not 0. It is available to Operations and Admin only.

Its Lane column follows the lane level, like the screen. Export these on an opened list exports exactly that list, at that list’s level.

Transfers, corrections and unresolved evidence

A confirmed transfer between runs names the source allocation and the receiving allocation. The source must hold the physical quantity; planning a new run never moves freight. Transfer corrections remain on the same source and target.

Destination quantity F measures current custody, so loading pallets out reduces it and returning them restores it once. Repeat receipt activity stays in history.

If an operator confirmed a count before an offline driver’s POD arrives, the POD still records. Matching evidence reuses the existing count. Conflicting evidence creates an unresolved exception and keeps both accounts in the journey; review that evidence and correct the current count with a reason.

Unclassified booking lines show an unknown expected quantity. Resolve the packaging classification or approve a measured expectation; unknown is never zero. Depots with activity appear first; use the search field or Show all depots to find another site. Each view displays its own freshness time.