“At ten” is not yet a shared plan
The site asks to delay the pumping job and someone moves the calendar entry. Before communicating the new plan, clarify what happens at ten: pump arrival, first truck arrival or the requested start of concreting. You also need to know what each party has confirmed. A time in the calendar does not answer those questions.
Adaris could assess a change record linking site, pumping service and plant order, retaining the previous agreement and showing outstanding responses. AI would help interpret messages; confirmations would retain their sources and human review. The first engagement can cover this administrative coordination without replacing technical planning or presenting an existing proprietary Adaris pumping application.
Three moments worth recording separately
For the proposed record, distinguish planned pump arrival, planned first truck arrival and requested work start. Do not calculate one from another using a universal buffer. Responsible professionals agree preparation, access and service arrangements for each site.
BASE states that it can coordinate pumping and supply or assess pumping alone when the customer has already arranged the concrete. It also asks customers to prepare vehicle access. This is a specific supplier reference, consulted on 12 November 2026, that helps frame the management question: who needs to respond about each part of the job?
If the contractor orders the concrete, identify who can confirm that order and who communicates changes. The person who requested the pump does not automatically speak for the plant. Assigning a driver does not establish that everyone has accepted the new schedule either.
Fictional case: the pump company replies, but the plant has not
Invented example: pumping job B-26 for Olmo site has version V1 for 17 November, recording pump arrival at 08:00, first truck at 08:30 and requested work start at 08:45. These are example times, not preparation guidance. The previous day, “move it to ten” arrives. The office leaves the meaning unresolved and asks for clarification.
The site clarifies that it wants the first truck at 10:00. Request V2 retains that clarification. The pumping company proposes arriving at 09:30, while the site reports access from 09:45. The plant has not responded to changing its earlier 08:30 delivery. No single box should summarise this as “confirmed for ten”.
The coordinator sees two separate issues: clarify the proposed arrival before the reported access time, and obtain the plant’s response about the requested delivery. A responsible person decides what enquiries and adjustments are needed. V1 remains historical evidence without triggering automatic dispatch; V2 stays pending until the specific agreements are reviewed. A later change must not inherit responses to V2 without review.
| Party or milestone | Recorded information | Outstanding decision |
|---|---|---|
| First truck | Site requests 10:00 in V2 | Plant response to the change |
| Pump arrival | Pump company proposes 09:30 for V2 | Check against access from 09:45 |
| Work start | V1 recorded 08:45 | New professional coordination; do not infer 10:00 |
| Previous version | V1 and its sources retained | Decide the new plan; retaining V1 does not dispatch a vehicle |
A job record with a clear scope for each response
The proposed record would bring together site reference, validated address, pumping job and concrete order reference when known. It would add local date and time, the meaning of each time, plan version and responsible person. A missing reference stays unidentified; do not link an email to a job merely because the street name matches.
Each response would retain sender, receipt time, source document or note and its scope: which job, version and time it confirms. “Received” records receipt of a message, not acceptance of the schedule. Calls could be captured in an authorised note reviewed by the responsible person, without inventing written confirmation.
Departures and arrivals reported during the job would be separate from schedule agreements. Managing site exchanges and collections illustrates why planning a movement and confirming it happened are different facts. For pumping jobs, that distinction preserves what actually occurred even if the plan is later corrected.
What AI would do and what software rules must control
In the proposed workflow, generative AI would read authorised messages and prepare a comparison: previous time, requested change and supporting passage. Phrases such as “at ten” would remain ambiguous until clarified. A person would check the extraction before it entered the record; confidently written output can still contain errors.
References, versions, permissions and states would be controlled by software rules. If the order changes after a summary is prepared, the proposal would require review against the new information. A bounded agent could be useful when it needs to consult several authorised sources, such as calendar and order records, to prepare the same case. It would start with read access and internal drafts, without placing orders, dispatching vehicles or sending confirmations independently.
n8n documents human approval before an agent executes specific tools. This is a design option, not an installed connection to a plant or pumping system. Before enabling changes, interfaces or exports, permissions, licences and maintenance would need verification. An interrupted connection would show what could not be checked rather than presenting an old copy as a current confirmation.
Before commissioning software, ask to see this schedule change
Linkoper describes pumping services alongside truck loads for the same order in its dispatch panel, as well as confirmation by pumping partners. Its page also describes requesting fresh partner confirmation when moving an order. These are supplier statements, not proof of fit for your business or an endorsement of its calculations or technical decisions.
Request a demonstration using B-26: does it distinguish first truck and pump arrival, retain the outstanding plant response and bind each confirmation to its version? Check data access, conditions and actual operation before deciding. If your current system handles the workflow, configuration and clear responsibilities may be enough.
An integration could be assessed when calendar, order and confirmations are separate and there is an authorised way to connect them. Custom development could make sense when the case record or exception workflow is missing. Date changes involving suppliers show another external confirmation problem: updating your own record does not itself change the other company’s agreement.
A pilot for coordination, not for directing the pour
The first delivery could cover one office, one request channel and schedule changes for already identified jobs. It would provide a list of discrepancies, responsible people and outstanding responses. Together with staff, prepare B-26, a reply referring to V1, a duplicate message and a change without a site reference. Samples would be fictional or anonymised and authorised.
Agree a baseline and observation period to count omitted changes, confirmations linked to the wrong version and human corrections, as well as total time to reach a decision. Review unnecessary holds and outdated copies too. This is a proposed evaluation, not evidence of savings, punctuality or customer results.
The record does not select the pump, calculate reach or delivery rates, accept concrete or authorise setup or concreting. Safe access, preparation, material and execution remain with responsible professionals. An administratively confirmed plan does not certify technical site readiness.
Tell us where the change gets lost
To contact Adaris, explain who receives requests, which software you use and who checks with the plant and site. We can assess an initial software or integration scope, its data, permissions and checks together. You do not need to build a pilot before enquiring or send real third-party conversations, phone numbers or documents without permission and suitable processing conditions. Commercial communication is in Spanish.
Related services
Sources
Does the calendar change before the plant and site reply?
At Adaris, we specialise in integrating AI to coordinate schedule changes across the site, pump and batching plant, showing arrival, first truck and confirmations separately before updating a job. Tell us how you coordinate pumping schedule changes. We can assess a shared record or a scoped integration with your team. Commercial communication is in Spanish.

