Real Material Consumption Manager

Material waste usually shows up when it's too late to act on it: at closeout, someone compares what was purchased against what was certified, and an unexplained overspend appears, because nobody had compared what was actually installed against what was actually bought and received while the work was happening.

This skill doesn't track purchase orders or supplier delivery schedules, and it doesn't plan future material needs — it starts from material already on site and compares its real, logged consumption against what was purchased and against the expected waste range for its material family (ceramic, concrete, steel, timber...). It flags materials that fall outside that range, calculates the cost of the excess waste, and ranks which materials to check first.

What it doesn't solve — and the skill says so itself — is the exact cause of the deviation: it flags "waste to investigate" with neutral hypotheses (unlogged breakage, a miscounted stockpile, a measurement error, material used on another job), never an accusation, because the numbers alone can't tell an error in the records apart from a real loss.

Bloqbase connects purchasing, take-offs and real consumption for every project automatically, so this comparison doesn't depend on pulling together three separate files before closeout. Download the skill free with your email, or get in touch if you want to see it running on your own site's real numbers.

How to use it with judgment: start with one real, well-defined case, enter only data you can verify, and keep the reviewed version. The goal is not to fill in another document for its own sake, but to turn a project decision into a record that someone else can understand and review later.

Before making it part of your process, check three things: the inputs come from an identifiable source, the calculations or wording match the actual project, and it is clear who must approve the result. If one is missing, treat it as working material rather than final project documentation.

How to prepare the input: start with a real case and define which question the skill must answer, which period the data covers, and which fields cannot be missing. Mark estimates or incomplete sources before requesting the analysis.

How to review the output: check that conclusions can be traced back to your data, inspect the rows or documents behind each alert, and discuss priority cases with the person responsible for the project. A skill helps organize judgment; it does not replace technical, contractual, or financial approval.

How to make it part of the workflow: keep the prompt, the source data, and the reviewed result with the project. This lets you repeat the analysis when progress changes, compare periods, and explain why a recommendation was accepted, rejected, or sent for review.

How to put it to work on a real project

The idea isn't to download another file and forget it in a folder. Use it with a specific case: a pending certificate, a coordination meeting, a cost overrun or a handover to the developer. Fill in the resource with real data from your project, validate the result with your own technical judgment, and keep it as an internal reference to repeat the process next time.