Digiful  ·  J.E Wallace Ltd  ·  For discussion

Two ways in.
One of them has a gate.

Once a job is in your diary, everything downstream is identical — the same feeds, the same alerts, the same privacy. The only real choice is what happens at the moment you put it in. This is a trade between speed and safeguards. There is no option that gives you both.

The honest version

Google Calendar will not warn you about a clash. Not before you save, not after. It saves silently and draws the two jobs side by side. That isn't a setting we can turn on — it doesn't exist.

So the question is: do we catch problems before they're saved, or seconds afterwards? Both are workable. They cost different things.

01

The two ways in

Everything below the fold is the same either way
Option A · Fastest

Straight into Google Calendar

What you do today. Open the app, add the job, done.

1

You open the calendar app

Phone, laptop, watch, voice. Three taps. Works with no signal, in a substation, in the rain.

Nothing new to learn
2

You pick the company's calendar

ENWL, IES or IUS — each its own colour. Everything already booked that week is on the same screen, in front of you.

A clash is visible before you save
3

You save it — and it saves

Even if it sits on top of another job. Even if you picked the wrong company. Even if you've a two-hour drive from the last one.

Nothing stops you
4

Seconds later, we tell you

If it clashes, the event renames itself in front of you — ⚠ CLASH — and your phone buzzes. You can fix it, or ignore it. Your call, every time.

The job is already in. The fix is on you.
Option B · Safest

Through your own booking form

A private page only you can open. It checks before it writes.

1

You open the form

A web page, on your phone or laptop. You need a signal and a minute — so not while you're standing in a substation.

Needs internet. Slower.
2

You choose the company and the dates

Company from a list. Site, times, travel. It shows you what you're about to book before you commit.

3

It checks — before it saves

Every calendar, all at once. Clash with another job? Not enough travel time? Inside the 21-day notice window? It stops and tells you, in plain English, before anything is written.

The problem never reaches your diary
4

You overrule it if you want to

It is not a wall. If you've weighed it up and you still want the job, you tick to confirm and it goes in. It cannot refuse you. It only makes sure the decision was made, rather than drifted into.

You stay in charge — always
5

Then it writes it into Google Calendar

Same calendar, same colours, same everything. The form isn't a second diary — it's a gate in front of the only one.

Clean by the time it lands
Identical either way — from here on

Once it's in the calendar, nothing else changes

Both routes end in the same place. The choice above only affects the moment of entry.

Google Calendar holds it

One diary. Every job, every company, one screen. This is the only place anything is ever written.

The system reads it

Works out which company it belongs to, spots clashes, keeps the history. It never changes your diary on its own.

Each company gets its feed

They see their own jobs in full. Everything else — other clients, family, anything private — is a blank wall marked Busy.

02

Side by side

Where each one genuinely wins
  A · Straight into Google Calendar B · Through your booking form
Friction Almost noneThree taps. It's what you already do. NoticeableOpen a page, fill it in, submit. A new habit to build.
Safeguard before it's saved NoneGoogle gives no warning of any kind. The only protection is that you can see the clash on screen. Real — but never a wallChecks every calendar before writing. Stops, explains, and asks you to confirm. You can always overrule it.
Can you overrule it? Nothing to overruleIt never stops you in the first place. Yes — alwaysIt cannot refuse a job you've decided to take. It only makes sure you decided, rather than drifted.
Safeguard after it's saved Yes — within secondsEvent renames itself, phone buzzes. But the job is already in the diary. Yes — same systemIdentical. You get this either way.
Speed Seconds A minute or two
Works offline / no signal YesSubstations, moors, basements. Voice and lock screen too. NoNeeds a working connection, every time.
Right company guaranteed NearlyYou pick a calendar from a list, so you can't mistype it — but you could still pick the wrong one. NearlySame risk, but it shows you a summary before you commit.
Travel time protected Flagged afterwards"This starts as Penrith ends — that's a two-hour drive." Raised upfrontWarns before it writes. Overrule it if the drive is fine.
21-day notice floor Not enforced Default, with overrideShort notice is blocked unless you deliberately say yes. Something to hide behind when you're being leaned on.
Platforms involved OneGoogle Calendar. That's it. TwoThe form, then Google Calendar. One more thing that can be down.
Digiful build LowThe alerts and feeds are needed regardless. MediumThe form is built on top of everything in column A — not instead of it.
Read this before choosing

The form can't replace the app — it can only sit alongside it

Even if we build the form, the Google Calendar app stays on your phone and keeps working. We can't switch it off, and you wouldn't want us to — it's the only thing that works with no signal.

Which means the gate only guards one door. And ask yourself when you'd use the other one: when you're rushed, on site, with no bars. Exactly when you most need protecting.

So the alerts, the clash detection and the feeds get built either way. The form is an addition, not a replacement. That's why its build cost is medium rather than instead of — and it's the honest reason we'd suggest proving the alerts work in practice before spending on the gate.

Three things only you can answer

01

How often do you actually add a job while you're out on site?

If it's most of them, the form will get bypassed and we shouldn't build it yet. If you mostly add jobs from the van or at home, the gate is worth having.

02

Would a 21-day floor protect you, or cost you work?

It gives you something to hide behind when you're being leaned on — and you can always overrule it for a job you actually want. So it's a speed bump, not a wall. The question is whether the speed bump is worth having.

03

Would you act on an alert, or ignore it?

Be honest. If a buzzing phone gets swiped away at 6am, the fast option isn't actually protecting you and the gate earns its cost.

Document
Two Ways In
Client
J.E Wallace Ltd
Revision
A — 12 Jul 2026
Status
For discussion
Decision
Jared