Two warehouse managers, whom we will call Nadia and Karl, each spent an afternoon last spring on a call with the same kind of partner: a systems integrator who would bring in a small fleet of mobile robots to move totes between stations. The calls were friendly, covered almost identical ground, and ended with equally warm handshakes over video. What differed was the next ten minutes. Nadia sent a short written confirmation. Karl moved on to his next meeting. This comparison follows both projects and shows where the paths parted.
The call, in common
On both calls, the integrator described what the work would involve. A site walk would come first. Robots would be configured to follow marked routes, floor conditions would be checked, and staff would receive an introduction to the system. Someone said that “the usual commissioning checks” would be done before go-live. Someone else mentioned that changes to the routes after installation “can usually be handled”. Both managers left feeling that the plan was sound.
Both were also left with spoken phrases that carried a great deal of weight: “the usual checks”, “usually be handled”. Those two phrases are where the comparison begins.
Warehouse one: Nadia sends a note
Within an hour, Nadia emailed the integrator. Her message had five short lines. She restated the sequence: site walk, route setup, floor check, staff introduction, commissioning. She asked which checks “the usual” referred to and requested a list. She wrote the target week for go-live. She asked what the process would be if she wished to change a route after installation, and whether that would be treated as part of the original work. She closed by inviting corrections.
The integrator replied the next morning, with a clear list of checks, a note that route changes in the first month would be treated as adjustments, and a correction: the staff introduction was a single session, not two as Nadia had assumed. Everything was now visible, and the one mismatch was found on day two.
Warehouse two: Karl keeps the memory
Karl trusted his notes, which consisted of three words on a pad: “site walk, routes, go-live”. Weeks later, when installation began, he assumed that two staff sessions would be provided and that every route change was included. The integrator, working from its own records, planned one session and counted route changes after the first month as extra work. Neither side had been dishonest. They had held different pictures since the call.
The difference emerged only when Karl asked for a third training session, shortly before go-live, and received a quote for it. Karl felt let down. The integrator felt surprised at the reaction. A fair project had become a tense one.
Side by side
- Time to discover the mismatch. Nadia: the next morning. Karl: several weeks later, close to go-live.
- Cost of fixing it. Nadia: one reply and a minor adjustment to her plan. Karl: an unplanned expense and a strained relationship.
- Clarity on “the usual checks”. Nadia: a written list. Karl: an assumption.
- Route change expectations. Nadia: a defined first-month window. Karl: an open-ended hope.
- Mood on go-live day. Nadia’s team: prepared and calm. Karl’s team: still discussing what was owed to whom.
The machines were comparable, the integrator was comparable, and the technical plan was comparable. The only controlled difference was an email.
The same comparison, one level down
It is tempting to read the story as being about contracts, but nothing in either project involved a dispute over a signed document. The friction lived in the gaps around the paperwork: how many staff sessions, which checks counted as routine, how long route changes stayed free. These are the small operational questions that fill a robotics rollout, and they are almost always settled in conversation because they feel too minor for a document.
That is why a short message works better than a longer formal approach here. It matches the size of the question. A one-page change request for a training session would be absurd; a sentence in an email is exactly proportionate. Nadia’s note was effective precisely because it was light enough to send the same day and specific enough to be corrected.
Karl, to his credit, adopted the habit on his next project. He keeps a template on his desktop and fills in the blanks after each vendor call. When asked about it, he says it is the dullest automation he owns, yet it has spared him more grief than any other.
What the comparison teaches about robotics operations
Robot deployments involve many fine details that sit between the technology and the contract: floor preparation, safety checks, training sessions, change handling, ownership of spare parts. Our guide to driverless vehicles moving goods around a warehouse lists how many of these moving parts are involved. Each one is a place where a spoken assurance can differ from the written plan.
The teams most at ease with automation tend to be the ones who treat the human agreements around it with the same care as the equipment. A sensor integration, such as those explained in our walkthrough on fitting sensors into factory robots, is specified down to the interface. The agreement about who will do the integration deserves some of that precision too.
What a good confirmation contains
- The sequence of steps and who performs each.
- Definitions for any phrase that sounds routine but is open to interpretation.
- The target dates for each stage.
- How changes after installation will be treated and what the window is.
- An invitation to correct anything.
Why Nadia hesitated, and why she did it anyway
Nadia admitted she nearly skipped the note. The call had gone so well that writing it seemed fussy. What tipped her was an earlier experience from a different job, where a verbal promise about spare parts had evaporated after a change of contact. She decided the three minutes were cheaper than the risk. Later, the integrator’s project lead told her that her note was the clearest summary any client had sent in months.
A note on other kinds of advice
Automation projects also raise financial questions: how equipment purchases are recorded, how a lease compares with outright ownership in the books. Those belong with a professional adviser. Anyone hunting for a chartered accountant might begin at an online listing of such accountants, where the results can be sorted by place, area of expertise and meeting style. Whoever is chosen, the written follow-up habit carries over unchanged.
Bringing it back to the floor
You do not need to be running a robot fleet to use Nadia’s approach. After the next call where anything is agreed, spend a few minutes writing the sequence, the dates, the definitions and the change plan. Send it before the day ends. File the reply where your colleagues can find it.
The two warehouses ended up with similar robots, similar routes and similar throughput. They did not end up with a similar mood. One team went live knowing exactly what it had been promised; the other went live with an invoice dispute running in the background. If you want to be the first kind of team, the cheapest piece of equipment you will ever buy is a short written confirmation, and it is available right after your next call.
