Equipment Breakdown & Maintenance Manager for Sites

A breakdown reported over WhatsApp or mentioned in passing at the site meeting easily gets lost among everything else — meanwhile the crane, the generator, or the excavator stays down, racking up cost every hour with nobody actually adding it up.

This isn't the full fleet manager (that's covered by the Equipment Fleet Manager, which tracks usage and rental cost machine by machine); this one is for the breakdown log: the crane that stops lifting, the generator that overheats, the site cabin's panel that trips. The skill calculates accumulated downtime cost, distinguishes which breakdowns are urgent and blocking from those that can be scheduled, and flags which equipment fails most and which maintenance provider takes longest to resolve.

What it doesn't do: it doesn't replace scheduled preventive maintenance or keep a full service history for each machine — it only works with breakdowns that have already been reported. It also doesn't decide whether to buy, rent, or retire a piece of equipment; that's still a management call, though the report gives you the data to make it with confidence.

Download the skill free with your email. Copy and paste it into any conversational AI — no integration or new account required. If your site needs this tracking wired into WhatsApp, your ERP, or with automatic alerts for the site manager, at Bloqbase we build it to order — reach out at /contacto.

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.