Structured Curfew Schedules - RoadScope Documentation

Why Structured Curfews

A note saying "no moves at night downtown" is readable by a human but useless to analysis. Structured curfew schedules record the actual days and time window on the Curfew POI, so reports can print a precise restriction, exports can carry it as data, and calendar-window analysis can tell you whether a planned move conflicts with it.

Entering a Schedule

Open (or create) a POI of type Curfew. The editor shows a Curfew schedule panel:

**Days** — toggle Mon through Sun chips

**Start / End time** — 24-hour local times (an overnight window like 22:00–06:00 is supported)

**Timezone note** — free text such as "local time (America/Toronto)"

**Schedule notes** — exceptions, permit references, enforcement details

A schedule counts as structured once it has a day list and/or a start and end time.

Where the Schedule Surfaces

**Reports** — Curfew POI rows include the formatted window, e.g. "Mon–Fri 22:00–06:00 · local time", and curfews flow into derived findings for AI narratives

**Exports** — data exports flatten the schedule into dedicated fields (days, start time, end time) alongside the POI

**Shared maps & NAV** — the structured schedule travels with the POI to shared-map viewers and field payloads

Legacy Free-Text Curfews

Existing curfews recorded as plain notes keep working — nothing is rejected or converted behind your back. However, the pre-report data-gaps check flags free-text-only curfews so you know which ones cannot participate in calendar analysis until the structured fields are filled in.