AI Site Communications Drafter

When a delay, a breach, or a cost overrun needs to be put in writing, the mental note of "I need to email this" too often stays stuck at the WhatsApp message that already went out, and the formal notice never actually gets drafted — until it's needed and there's no time left to do it properly.

This skill takes the note exactly as you'd write it — rushed, unstructured — and figures out on its own who it's for and what kind of communication it is: a formal request to a subcontractor, a technical notice to the site architect, a delay or cost-overrun notice to the developer, or a delivery claim to a supplier. It returns the finished email, with subject line, reference, and response deadline, clearly flagging any data still missing.

What it doesn't solve — and the skill says so itself — is legal advice: it doesn't calculate contractual penalties or interpret legal clauses; that always goes through the site architect or the project's legal advisor.

Bloqbase keeps every site's communication history in one place, linked to the milestone or issue that triggered it, so every notice stays documented and easy to find. Download the skill free with your email, or write to us if you want to see it working with your actual site.

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.