Availability

Issued, not sent. A row records that a link was minted, not that it reached anybody. Whether a send went out is recorded in Audit — as mail.suppressed when it did not. About this screen has the rules on replacing, revoking and Tape-issued links.

Import pulls Site Surveyor and Site Survey Tech / Lead only — matching on role ILIKE '%Survey%' would make 8 schedulers and 8 reviewers bookable. OWEDB has no home lat/lon, so set a home base below or drive time can't be measured.

Home lat/lon is what makes “drive from the previous job” work — without it the first job of the day has no origin and drive time reads as unknown.

Which offices this surveyor works out of. A travelling day starts at whichever of these is nearest that day's first booking; a day in their own market still starts at their home address. Assignments end by date, never deleted — the row stays so a day routed last month can still be explained.

Changing hours adds a dated row rather than rewriting history, so a slot offered last month can still be explained. Times are local wall clock — they survive DST.

Hours may differ by day. Unticking a day ends that day's pattern; ticking a new one adds it. Editing deliberately can't move effective from — that would rewrite history and change what was offered in the past. To start a different pattern, add one above and this week closes automatically.

A one-off day change replaces the pattern for that single date and is set below. An absence over a date range is a blackout scoped to one surveyor — it subtracts from whatever hours they have, so the pattern stays intact. A market move is an assignment with a date range, and it changes which market's clock and centre their day runs on.

A temporary move outranks the home market for its date range and then hands back automatically — the home assignment is left intact. Their working day starts from the destination market's centre and runs on that market's timezone, so sending a Phoenix tech to Houston gives a 7 AM Central start, not 7 AM Mountain. Setting a new home market auto-closes the previous home the day before this one starts.

An assignment says where somebody is; it does not say when they work. Their default hours already carry over, so skipping is safe — but the moment anyone gives them hours in this market, the default stops applying there. Saving now makes the move explicit. Their default hours are left exactly as they are, which is what keeps them working everywhere else.

Remove is gone on purpose (P3.1). It ran a hard DELETE, which destroyed the record that a surveyor had ever covered a market — and this table is effective-dated precisely so that a slot generated last month can still be explained. To end an assignment, set its To date using the form above; the row stays and greys out. Creating a home assignment still auto-closes the previous one.

The centre point is no longer a day origin. Until 060 an away day was measured as driving out from the market's centre; it is now measured from whichever of that surveyor's own assigned offices is nearest their first booking of the day. The centre is still read by the Coverage map and by the configuration warnings, so a market without one is simply drawn without a pin — it no longer weakens a drive-time check. A state-wide market needs no zip3s and acts as the fallback for anything in that state a region does not claim.

An office point IS a routing origin. This changed twice and the note here did not: 057 made a surveyor's home office the fallback origin when they have no coordinate of their own, and 060 made it the origin for any day they work away from base — whichever of their assigned offices is nearest that day's first booking. A day in their own market still starts at their own address. So the point here is read by the scheduling engine, and an office without one cannot be a day origin at all.

A state-wide row is the fallback for anything in that state no region claims; it sits last in its group. Click a market to see who covers it and how it is configured. Offices are listed under the market they belong to.

Configuration, not work. Shaded state = a market exists there. Ring = a market's centre. Pin = a base a survey tech reports to. No shape here means a job, a booking or a person, and the centre is neither a radius nor a day origin. About this screen has how coverage is actually decided.

Every “PTO” field in OWEDB means Permission To Operate (utility interconnection), not leave — none of them are wired to this. Only approved time off removes availability; pending never does.

We deliberately don't derive coverage from OWEDB's zip→office table: it's populated for only ~8,945 of ~22,000 ZIPs (CA has 10) and is empty for NY/IL/VA/MA/NJ/MD/ME/CT/VT. Since this serves all markets, coverage lives here. A state row is a fine start for a one-surveyor market.

Leave To empty for a single day. A blackout removes availability for everyone it covers, whatever their working hours say — it is a closure, not a person's leave. One person's absence belongs in Time off, which needs approval and warns you about surveys already booked in the range; a blackout applies immediately and asks nobody.

Every window here works on the route, not just on paper. The tech finishes their last job, drives over, and is at the door somewhere inside the arrival window — each chip is the whole window, not a start time — and can still reach their next customer inside the window that customer was given.

Every arrival window each surveyor has, and which are already taken. Click a free one to book into it. Name a project at the top of this tab and this narrows to the people who can actually take that job, with the drive time checked.

Everything the team has raised, what was actually done about it, and whether it's finished. Anyone here can add one or move one along — you shouldn't have to ask for a status.

“Cleared QC” is read as: the project is ACTIVE, it has a sale date, its survey is waiting to be scheduled, and no link has been sent and nothing booked for it yet. Turning this on still respects the email switch on Config — with email suppressed, nothing leaves either way.

Amber and red are computed from real drive time between consecutive addresses, not a gap rule — a red day contains a job the tech physically cannot reach. Map overview opens the whole route in Google Maps. Click a job to move or cancel it; reviewing a day records who cleared it, and the review lapses automatically if the day changes afterwards.

Click a scheduled survey to open it. The detail opens over the list and the list does not move — the row you clicked stays where it is and is highlighted, so when you close it you are back where you were and a second click cannot land on somebody else's booking (#29). Move and Cancel are on the detail.

Loading…

Open the Tape record, enter the survey as Scheduled with the date, arrival window and tech below, then tick it off. It's undoable from the list underneath, and a booking that later cancels comes back into this queue so Tape gets updated too.

The tick is your word; the check is separate. Ticking a row records who said they entered it and when. The app then re-reads OWEDB's copy of the Tape survey record for that OUR#, and a row reads VERIFIED only if that copy shows the survey scheduled. Anything else stays ADDED with the status OWEDB actually returned — including "not there yet", which is a normal thing to see while the sync catches up. Not verified never means Tape is missing it; it means the check has not seen it yet. Use Check Tape again on the row.

The hourly sync files a booking here instead of guessing, because a guess puts a real job on the wrong technician. Most of these are fixed in Tape, not here. Once Tape is right the next sync brings the booking in and closes the row itself — you only need to resolve a row by hand when the answer is that nothing is coming (a duplicate, a cancellation), or when you have done the fix and want it off the list.

Read this before changing it. off sends nothing at all — no sign-in links, no rep links, no homeowner confirmations; bookings still record normally. internal is testing mode: only @ourworldenergy.com addresses receive mail, and every suppressed message is recorded in Audit as mail.suppressed. on means real customers and outside reps receive real email. This screen is the only place in the app that can change it.

Shown read-only on purpose. The fields above write global; a scoped row wins over them for the surveyor, survey type or state it names, so changing a global value would look like it had no effect. Use the advanced editor below to change a state: or surveyor: row — type: scopes are seeded by migration and the API will not write them.

Listing an email that is already here updates their role rather than adding a second entry — the change is recorded in the audit trail, and the original grant's author and date are kept.

Two gates still protect this app, but the first one moved. OWE sign-in (ScaleKit → the company directory) decides who can authenticate; this list decides what they can do — and anyone not on it is refused outright, even with a perfectly good OWE login. Cloudflare Access used to be the front door and no longer is, so this list is now the only place a new person is let in. A surveyor login must be linked to its surveyor record — that's what scopes them to their own day.

Hiding a tab is convenience, not the security boundary: every endpoint behind every tab re-checks the role itself, so a URL typed by hand still gets refused. A surveyor login is additionally scoped to its own record — that's what keeps a field tech out of the whole company's day.

Loading…

Nothing on this screen changes anything — it is a read of four other tabs. Every number links to the screen that owns it.