Fictional plumber reviewing a job beside a separate tap and sink trap on a kitchen counter
AI-generated image; illustrative scene.

A supervised AI proposal for extra plumbing work

How a reviewed register could compare accepted scope, new work and versions awaiting review.

Adaris Tech team8 min

The tap is included; the trap is still a request

You arrive to replace a kitchen tap and the customer adds: “While you are here, look at the trap too.” The tap quote is accepted; the new work still needs defining. A supervised register could help compare what remained included, what is requested now and what is missing before pricing the change, without turning the remark into an instruction to proceed. For a related guide, see “The part is ordered: can you confirm the return visit yet?”.

We build that comparison using an original fictional case. All documents, messages and responses below were written for this guide; they are neither a real conversation nor tested assistant output. Professional judgement, pricing, safety and execution remain with the plumber. This is about organising a job, with no repair instructions or legal advice.

Bring together the accepted version and complete messages

Use three separate inputs. P-18 v1 is our fictional accepted quote: “Replace the kitchen tap supplied by the customer. Replacement of sink traps is excluded.” To focus on scope, the exercise does not reproduce prices or commercial terms. It cannot reconstruct a complete quote or determine tap compatibility.

M-1 is a later request: “While you are coming, replace the kitchen trap too, but tell me the price first. Do not touch the bathroom trap.” N-1 is the plumber’s internal note: “Kitchen trap assessment and required material pending. No price for the extra has been sent and no acceptance is recorded.” Add no fault, part reference or urgency that these inputs do not describe.

For professional context, Planhopper’s plumbing page distinguishes who supplies materials and how to reference work changes. Tabiquo’s tutorial addresses extras against an accepted quote. These are descriptions of their own services, not tests of this AI exercise or guidance on the legal validity of an acceptance.

The comparison must preserve the exclusion too

This manual reference output is for checking any draft. Every conclusion has a source. Kitchen and bathroom are not grouped as “two traps”, and a request for a price is not recorded as an accepted extra.

Fictional reference for reviewing the classification
ItemWhat to preserveStatus in this example
Kitchen tapP-18 v1: replacement; customer supplies the tap.Scope of the accepted quote; does not imply completed work.
Kitchen trapM-1 requests replacement subject to a price first; N-1 leaves assessment and material pending.Extra-work request awaiting assessment and proposal.
Bathroom trapM-1 excludes work on it.Outside the requested change.
Extra price and timingN-1 contains no price sent or acceptance.No confirmed price or execution date for the extra.

A register linking versions and requests

Adaris could assess a custom register linking the accepted quote, authorised messages, extras and versions. An AI function could propose a source-linked comparison and flag open questions; the professional would check it before preparing a reply.

In the example, P-18 v1 covers the tap, M-1 requests a price for the kitchen trap and excludes the bathroom, and N-1 records neither a sent price nor acceptance. Only in a second hypothetical phase, after E-18 v1 is prepared and sent, does M-2 declare acceptance; it establishes neither execution, payment nor approval of another version.

Before connecting tools, the team would agree permissions, formats, retention and review. The workflow does not diagnose faults, choose materials, send messages, buy or invoice automatically. Technical and commercial decisions remain with the plumber.

Turn the draft into a reply you can review

Example draft: “Quote P-18 v1 covers replacing the kitchen tap you supply. You have also requested a price for replacing the kitchen trap; the bathroom trap remains excluded. Material, price and conditions for that extra are still to be defined before I present it to you. Replacement of the kitchen trap is not yet recorded as accepted.” This is text for review; it has not been sent to anyone.

Before using it, the plumber checks the complete quote, technical scope, appropriate material and commercial terms. If presenting the extra, prepare an identified proposal, such as E-18 v1 linked to P-18 v1, specifying the description, included material and work, price and conditions confirmed by the professional. Keep the original version and proposed change separate; do not fill gaps with AI estimates.

To continue the case, suppose the professional has prepared and sent that complete proposal E-18 v1. A new message M-2 says: “I accept extra E-18 v1 for the kitchen trap; the bathroom trap remains excluded.” The record can retain that declaration with its message and version for human review. It proves neither execution nor payment, approves no future E-18 v2 and extends no work to the bathroom. If M-2 simply said “OK”, do not guess its scope: prepare a clarification question. We are not assessing the legal effects of these messages.

Four failures to look for before accepting the draft

“Replace the kitchen and bathroom traps.” This contradicts M-1. Correct the bathroom item to an exclusion and check all locations again; editing the final message is insufficient if the internal comparison remains wrong.

“Extra approved: replace kitchen trap.” With P-18 v1, M-1 and N-1 there is still no extra proposal sent or acceptance recorded. Keep the request pending and identify what is missing. M-2 belongs only to the second hypothetical phase, after E-18 v1.

“The trap is broken and a universal replacement must be purchased.” That invents a diagnosis and material selection. Remove both claims and return assessment to the plumber. This guide cannot decide repairs, dimensions, watertightness or compatibility.

“The new version automatically replaces everything before it.” No such rule has been defined. Preserve the original quote, extra, messages and applicable revision. Confirmation of one version does not transfer to another because they look similar. Discard the output if the assistant continues to ignore these distinctions after correction.

Test the judgement first; connect the workflow later

We propose a pilot that has not yet taken place: prepare fictional cases involving a price-conditional request, a room-specific exclusion, an ambiguous reply and an extra accepted by version reference. Write your manual classification first. If a prototype exists, compare its output and record preparation and correction minutes, misclassified items, invented approvals and necessary clarifications. These are test criteria, not results or promises of savings.

Keep an output only after checking every item against its document. Pay particular attention to preserving the bathroom exclusion and not treating the initial request as accepted. Also decide whether the draft helps explain the change to the customer; an accurate table nobody can use does not resolve the job.

Automation is a separate project: agree where the valid version is kept, who prepares and reviews extras, how messages are linked, and what happens with duplicate changes or failed connections. A first delivery to assess with Adaris could simply show the original scope alongside a proposed change for review, without sending messages, buying material or invoicing. Formats, access and integrations for your existing software must be checked before offering it. Adaris provides custom software and integration according to each case; the proposal would require evaluation and development. Commercial contact is in Spanish.

Related services

Sources

Do changes get lost between the quote and the visit?

At Adaris, we specialise in integrating AI to compare accepted scope, plumbing extras and estimate versions while retaining declined work for the responsible person’s review. Tell us which system holds the quote and who reviews extras. Start with a fictional scope-and-change example; we can assess whether organising the workflow is enough or a scoped integration is needed. Commercial contact is in Spanish.

Discuss my workflow in Spanish

Back to all insights