Digiful · J.E Wallace Ltd · For discussion

Booking a job.
One question at a time.

This is a walk-through, not the finished tool — a way to agree what the form should ask you and how the safeguards should feel. Nothing here writes to a real calendar. The guard never blocks you — it stops, explains, and lets you decide.

Demo controls — not part of the form

Short-notice booking Tight travel time Clashes with another job

Turn these on to see a guard fire; turn them off to see the clean path. Toggle them live in the meeting.

Who is it for

Which company is this job for?

This is the only choice that decides who sees the job. You pick a calendar, so it can't be mistyped.

ENWL Electricity North West — high sensitivity. What they see matters most. IES IES Utilities. IUS Integrated Utility Services (Northern Powergrid).

What it is

What's the job?

A short title you'll recognise at a glance. This becomes the calendar entry.

Job title / reference

Where

Where is it?

Site name is enough. A postcode is optional — it lets the form work out drive time for you later on.

Site / location

Postcode — optional

Leave blank if you like — nothing depends on it yet.

When

When is it?

Date and times. The form checks two things here: whether there's enough notice, and whether you've left yourself time to travel.

Date

Start

End

Travel time

Auto — 2 hrs each side (ENWL default)

Before (mins)

After (mins)

Only other companies see this as blocked-out time. Your own diary shows the true hours.

⚠ Heads up — short notice

That's inside your 21-day notice window

The customer notification (PSI) normally needs 21 days. This date is 9 days away. You can still take it — but the paperwork will be tight, and it's a fair thing to push back on if you're being leaned on.

✓ You overruled this. Your call — you're the SAP.

⚠ Heads up — travel time

Only 30 minutes between this and your last job

You finish at Kirkby Lonsdale at 07:30 and this starts at 08:00 in Penrith — roughly a 1 hr 10 drive. That's not enough. Move the start, or take it knowing the drive is tight.

✓ You overruled this. Your call — you're the SAP.

What kind

What kind of block is this?

This is mostly so the form knows what to protect. Only on-site work is checked for clashes with other on-site work.

On site Billable site work — the actual switching day. Checked for clashes. Admin Paperwork, writing or checking a switch program — the desk side of a job. Pencilled in Provisional. You've said maybe, not yes. Held loosely until it firms up.

These three words aren't fixed. Tell us what you'd actually call them — this walk-through is partly here to settle the wording.

Check & commit

Here's what you're about to book

Everything on one screen before it goes in. This is the moment the form exists for — a deliberate yes.

Notes — optional

⚠ Heads up — clash

This sits on top of another on-site job

You're already booked on site for IUS that morning (Stanley — 07:30 to 12:00). Two on-site jobs at once isn't usually what you mean to do. Cancel one, move this — or take both if that's genuinely the plan.

✓ You overruled this. Your call — you're the SAP.

✓ Booked

That would be in your diary now.

In the real tool, the form writes this straight into Google Calendar — the right company, the right colour — and everything downstream (the feeds, the alerts, the privacy wall) picks it up from there.

Any guard you overruled goes in with it. The form never had the authority to stop you — only to make sure you meant it.

This is a walk-through. Nothing was written to any real calendar.

Document: Booking Form — Walk-Through
Client: J.E Wallace Ltd
Revision: A — 10 Aug 2026
Status: For discussion
Decision: Jared