Seventeen emails to book one tank clean
Cleaning and disinfecting a cold water storage tank, or disinfecting a new system, is not a job you just drop into a route. The client has to agree a time when water can be isolated. Occupants may need notice. There might be a permit to work, a roof access arrangement, or a need to keep an alternative supply running. You need a crew of the right size, the right equipment, and follow-up sampling booked for afterwards.
So the booking happens over a long email thread. The facilities manager proposes a Saturday, then checks with the tenant, then comes back with a different Saturday. Your planner holds a crew, releases them, holds them again. The notice to occupants is written by the client, or by you, or by nobody. On the day, the crew arrives to find the permit was never issued.
Too many preconditions, no single checklist
- Shutdown window agreed with the client and their occupants.
- Notices issued to people affected.
- Site access and any permit to work confirmed.
- Crew, vehicle and equipment booked.
- Chemicals and consumables allocated.
- Post-works sampling booked with the lab.
- Any client-side contractor, such as a plumber, coordinated.
Each item is simple. The problem is that they are tracked across emails, calendars and memory, and one missed item stops the whole job.
The cost of a failed shutdown
A crew that turns up to an unconfirmed permit is a lost day for several people. A client whose occupants were not told is an unhappy client. A job completed without post-works sampling booked leaves the record incomplete. And the planner's time on each booking is large compared with the job's value.
A shutdown booking flow
- When a tank clean or disinfection is accepted, the system creates a job with a precondition checklist based on the job type.
- The client receives a link to propose shutdown windows, with a note of what the job involves and how long water may be off, in your own words.
- The planner sees proposed windows alongside crew availability and confirms one.
- Notices to occupants are generated from a template, for the client to issue or for you to send, as you agree with them.
- Each precondition is ticked off with a record of who confirmed it. The job cannot be released to the crew until all are done, or a supervisor overrides with a note.
- Post-works sampling is booked automatically for the interval your procedure sets, and the samples enter the sample register.
| Precondition | Owner | Evidence held |
|---|---|---|
| Shutdown window | Client and planner | Confirmed booking |
| Occupant notice | Client or you | Copy of notice sent |
| Permit or access | Client | Permit reference or email |
| Crew and kit | Planner | Booked crew and vehicle |
| Post-works sampling | Sampling lead | Samples scheduled |
Booking a tank clean in one place
The planner opens one job and sees exactly what is outstanding. The client proposes windows through a form rather than an email chain. Crews receive a job pack with the permit reference, access notes and method statement. The post-works sampling is already in the diary before the crew leaves site.
When a job is delayed, the reason is recorded against the precondition that held it up, which makes the next booking at that site easier.
Take a typical case. An office block needs its cold water storage tank cleaned and disinfected. The facilities manager proposes two Saturdays through the link. The planner picks the one where a crew of the right size is free. The notice to tenants goes out from a template with the date filled in, and the client ticks it off when issued. The roof access permit reference is recorded a few days before. The crew gets its job pack on Friday, and the post-works samples are already booked. Nobody had to rebuild the status from an email thread.
Recognise the pattern?
- Tank cleans take many emails to book.
- Crews have arrived to find access or permits not ready.
- Occupant notices are sometimes forgotten.
- Post-works sampling is booked separately and occasionally missed.
- Only one person knows the status of each shutdown job.