Link cube test results to the dispatch of each block batch

A site engineer rings about a wall that cracked, or a lintel that sounds hollow, and wants the strength result for the blocks delivered in a given week. The quality manager opens the test register and finds fifteen results for that week.

Which one covers that truck? Nobody can say. The register lists cube numbers and crushing loads, the dispatch book lists customers, vehicles and counts, and the two never meet.

So the plant answers with a guess, or with the average of the week. Neither survives a dispute. A contractor who loses trust over one unanswered query tends to test every later delivery with a hammer and a rebound gauge of his own.

Take one dispatched load from last month and walk it backward. Start with the delivery note. Find the batch it came from, then the cube set cast from that batch, then the crushing result. Count the steps where you had to ask someone.

Each step where memory, a pencil mark or a pallet position stood in for a record is a break. Most plants find two or three. The usual culprits are loading from a yard where batches mix, and cubes cast without a label that survives the curing tank.

Fix the cheapest break first. Usually that means swapping marker ink for stamped tags. Nobody needs software to start. A numbered tag and a notebook will prove the idea within a week.

Create the number when the mixer starts, not later. It goes on the cube mould tag, the pallet tag, the curing lane sheet and the stock card. A short code works, such as the date plus the machine plus a serial.

Cast cubes from the same mixer load that fed the pallets. If they come from a separate hand mix, the result describes the cubes, not the blocks.

Use a stamped tag on each cube. Curing water erases ink. Check the tags every morning. A cube without a number is wasted effort.

Strength results arrive at seven days and again at twenty-eight, so decide in advance which age releases stock for sale. A plant that sells at seven days should know how that early result relates to the later one.

Mark each pallet as held, released or failed. Software can enforce this at loading time, so a held batch cannot join a gate pass. A failed batch needs a deliberate decision: crush for aggregate, sell as a lower grade, or retest. Record who made that call, and why.

With the link in place, the site query becomes a search. Enter the customer and the delivery date. Read off the batch numbers and open each result with its crushing load and curing dates. Then reply with a batch certificate on one page.

Keep the template short, with the batch number, casting date, test ages, loads at failure and the signature of whoever ran the crusher. Customers file a plain page. They rarely open a long report. Add the site name and the delivery note numbers it covers.

Test it on yourself first. Ask a colleague to pick any delivery from last quarter and trace it, and if that takes more than a few minutes, find the missing link. Then fix whatever slowed you down.