CWICR Waste & Disposal Cost Estimator

A demo or renovation scope generates waste nobody prices until the hauler invoice arrives — the take-off gets coded and quantified for materials and labor, but the debris it leaves behind rarely gets the same discipline, so disposal cost shows up as a surprise line item instead of a planned one.

The skill takes your CWICR-coded scope with quantities, multiplies by the waste generation factor you supply per material, prices the resulting waste against the disposal or tipping rate you supply, rolls the totals up by division, flags any material where disposal cost is disproportionate to its material cost, and — where you tag a material's stream — splits the estimate into recyclable versus landfill-bound waste and cost.

It does not know actual local waste generation factors or tipping fees for any material or market — those numbers have to come from your own job history, a demolition subcontractor, or your hauler's current rate sheet, and the skill flags rather than guesses when either is missing. It also doesn't price the material or installation cost itself, classify raw scope into CWICR codes, or replace a hauler's own quote.

Bloqbase itself is built for the Spanish market, but if you manage projects across markets and CWICR is part of how your US jobs get estimated, this skill slots into that workflow directly. Download it free with your email, or write to us if you want to see it working with your actual project's waste factors and disposal rates.

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.