A return due next week
Your site has to submit a periodic return of what came in and what went out, broken down by the categories your obligations require. The office manager starts by exporting the weighbridge data for the period. Then she spends days fixing it.
Some tickets have the wrong material code because the operator picked the nearest one. Some have no source recorded. Outbound loads need their destinations, which are in a separate spreadsheet. Categories on the weighbridge do not line up with the categories the return needs. She builds a pivot table, checks the totals against last quarter, finds a gap, and goes looking for missing tickets.
The gap turns out to be a week when the weighbridge PC was replaced and tickets were written by hand. They are in a folder, not in the export. She types them in, rebuilds the pivot table and starts checking again.
Why returns start from a messy export
The data for a return is captured at the weighbridge, but not in the form the return needs.
- Weighbridge material codes do not map neatly to return categories.
- Operators pick codes quickly, and some are wrong.
- Source and destination details are incomplete on tickets.
- Corrections are made in the spreadsheet, not in the source data, so they are repeated every period.
- Only one person knows how the figures are built.
What your returns must contain and how they are submitted is for your business and its advisers. We deal with getting the underlying data right.
What rebuilding returns costs
Days of skilled office time every period go into cleaning and categorising data. Errors caught late mean resubmissions. Errors not caught are a risk your business does not want.
Dependence on one person is the bigger risk. If the person who builds the return leaves, the method leaves with them, and the next return is built from scratch by someone who does not know the history.
How we keep the data return-ready
What we build makes the weighbridge data right at the point of capture and keeps it in reporting shape.
- Weighbridge material codes are mapped to your reporting categories once, with your adviser's input where needed.
- At the weighbridge, operators pick from a short list suited to your site, and required fields, such as source or destination, cannot be skipped.
- Tickets with missing or doubtful data go into a fix list daily, so corrections happen while the details are fresh.
- In and out records are kept by category, source and destination through the period, with stock movements alongside.
- At period end, a draft of the figures your return needs is produced, with totals checked against the previous period and anything unusual flagged.
- A responsible person checks the draft and submits it through whatever route your obligations require.
| Problem today | What changes |
|---|---|
| Wrong codes chosen | Short site-specific list, fix list daily |
| Missing source or destination | Required at the weighbridge |
| Categories do not match | Mapped once, applied to every ticket |
| Corrections repeated each period | Corrected at source |
The next return
Throughout the quarter, the office manager clears a short fix list each morning: a ticket with no destination, a code that looks wrong for the supplier. At quarter end, the draft figures are ready. She compares them with last quarter; one category is up noticeably, and she can see why, a new supplier's loads.
The draft goes to the site manager, who checks and submits it. It took an hour, not a week.
Do returns start with a messy export?
- Every return is built in a spreadsheet from a weighbridge export.
- Tickets have wrong codes or missing details.
- Corrections are made in the spreadsheet every period.
- Only one person knows how the figures are built.
- Returns take days of office time.