Building and exporting a report
Start or resume a coordination session, accept the day's clash scenes in Clash Highlights, switch on Region evolution and curate its pre-ticked day peaks, then export the PDF or Word file — including the confirm above 20 extra pictures.
This is the coordinator's end-of-day job: turn the day's clashes into the report the meeting reads. Everything below happens in the Report panel — open it from the dock or with R. What a session, a scene and a day peak are, and why the rail ticks what it ticks, lives on Reports.
Before you start
You need the report band on the site — if the Report button is on your dock, you have it. How many days a scene's Region evolution looks forward by default is set under Settings ▸ Site ▸ Reports (five unless someone changed it); check it before a week where the meeting wants a longer view.
Task 1 — Start or resume a session
- Open the Report panel. It lands on the picker.
- Pick the Report Date — Tomorrow, +2 days, +3 days, or type a date into the box.
- Pick the Delivery Lookahead the deliveries and permits sections should read: Report date only, 7 day lookahead, 14 day lookahead or 1 month lookahead.
- Under Choose Template, pick the report to start. A new draft session opens on its first section.
- To pick up where you left off instead, open the draft under Resume Draft; a finished one reopens from Completed Reports. A finished session is read-only: its header says Finished · export options are not saved, the sections and scene decisions are frozen, and only the export's own options (screenshot options, tile subdivision, region evolution) still respond, for this print only.
Task 2 — Decide the scenes
- Open Clash Highlights from the section list down the panel's left edge (or step to it with Ctrl+PageDown). The header reads "{accepted} of {total} selected".
- Expand a scene to see its clashes, then tick its checkbox to accept it. Every scene starts unaccepted; Select All and Select None do the whole list at once.
- Write a note in Coordinator notes... on any accepted scene you want to explain in the meeting.
- Where the ranking missed a piece of ground, press Draw Custom and draw your own scene.
Task 3 — Add Region evolution
- Tick Region evolution on all accepted scenes beside Select All. Every accepted scene without a rail gets one — loading… shows while the rails are computed, and the box stays ticked. To add a rail to one scene only, tick Show region evolution on that scene's card instead.
- Read a scene's rail. Each row is a change point: its time, what entered or left, and how many things are in scope afterwards. The row after which each day is busiest wears a day peak tag and arrives already ticked, and the count above the rail reads "N of M ticked". The report day itself is never pre-ticked — its headline picture already covers it.
- Hand-tick any other row you want pictured, and untick any day peak you do not. An unticked row still prints as a table line.
- Slide the horizon to look further forward (or back). Only the days you add arrive with their day peaks ticked; the days you already curated are left as you left them.
- Press Refresh on a rail when the plan has moved. It recomputes the rows and keeps your ticks on every row that still exists — it never re-ticks a day peak you unticked. If ticked rows have gone, the rail says how many.
Note: The section switch stores nothing — it reads the scenes. A scene you accept after ticking it arrives without a rail, and the switch shows half-ticked until you give that scene one. Unticking the switch removes every rail, hand ticks included, without asking.
Task 4 — Export
- Press Export PDF or Export DOCX. The map moves through each scene and each ticked instant while the pictures are taken, so leave it be until the file arrives.
- If the plan has moved since you curated a rail, the export first asks "Plan has changed since you authored N lookahead scene(s)… Continue with the frozen version anyway?" Press OK to export what you curated, or Cancel to stop the export, press Refresh on the rails that moved, and export again.
- If more than 20 ticked rows are due across all scenes, it then asks "This export will capture N additional screenshots for Region evolution. This may take about T seconds. Continue?" Press OK to take them all, or Cancel to stop the export, untick rows down to the set you want, and export again. Cancel never drops the pictures and exports anyway: to export with no Region-evolution pictures at all, untick Region evolution on all accepted scenes (the Section switch) and export again.
- When the meeting is done, press Finalize to lock the session. You can still export it afterwards — and exporting a finalized session is what issues it: each export is kept as a copy that every role on the site can download from Commercial ▸ Reports (I). Until somebody exports it, its card under Completed Reports reads Not yet issued — export to issue.
Gotchas
- Accept before you add a rail. Show region evolution is greyed out on a scene you have not accepted, and the section switch only acts on accepted scenes.
- Want the day peaks back? There is no re-tick button: untick the scene's Show region evolution and tick it again, and the rail comes back pre-ticked — losing that scene's hand ticks.
- Redrawing a scene resets its ticks. Once the outline changes the rail says "Polygon changed — refresh to recompute (ticks will reset)." The next Refresh starts that rail's ticks again from the day peaks.
- Delivery Lookahead is not the rail's horizon. The picker's lookahead widens what the deliveries and permits sections read; the rail's default horizon is the site setting under Settings ▸ Site ▸ Reports.
See also: Reports — the session, scenes, the day peak and why · Reports & exports — the feature at a glance. Terms: glossary — Region evolution, Day peak, Day-entry, Section switch.
Reports guide: Reports · Building and exporting a report