← Guide

Reports

The coordination report: what a session is, scenes and the decisions that make the document, the Region-evolution rail beside each scene, the day peak it pre-ticks and the day-entry rule for when, the section switch, and the site's forward-days default.

The daily coordination report is built in the Report panel (R) and rendered to a PDF or Word file for the meeting. This page is the why behind it — what the pieces are and how the Region-evolution rail decides what to picture. The steps live on Building and exporting a report.

A session is not the document

A report starts as a coordination session: a draft built from a report template for one report day, filled from the live site. The session is what you work on — it saves as you go, and you can leave it and resume it from the picker's Resume Draft list. The PDF or Word file is rendered from the session whenever you export, as many times as you like, so the document always reflects the session's current decisions. Finalize locks the session against further edits once the meeting is done; exporting stays open after that — and from then on an export is the issuing act. Each export of a finalized session mints a Report issue: a copy kept exactly as it went out, listed newest first under the Commercial surface's Reports tile (I), where every role on the site — the client the paper is addressed to included — can download it. A draft's export is not paper, so the picker's Completed Reports card reads Not yet issued — export to issue until somebody exports the finished session; a re-export is a second issue, never an overwrite.

The picker also asks for a delivery lookahead (Report date only, 7 days, 14 days, a month). That widens the window the deliveries and permits sections read. It is a different question from how far a scene's Region-evolution rail looks, which is a site setting — see Site defaults below.

Scenes and decisions

The Clash Highlights section gathers the report day's clashes into ReportScenes — a piece of ground, the people and plant inside it, and the clashes between them — ranked on severity, cross-contractor exposure, diversity, proximity and temporal density, and tiered critical, notable and minor. You can draw your own scene where the ranking missed something.

Every scene starts unaccepted. The decision to accept one is what puts it in the document: an accepted scene prints with a headline map picture at the moment it clashes, and your note beside it. A scene you leave unaccepted stays out. The decisions are recorded against the session, which is also how the ranking learns what coordinators actually choose.

The Region-evolution rail

A headline picture shows a scene's ground at one moment. The meeting also wants to know where that ground is heading, so an accepted scene can switch on Region evolution — Show region evolution on the scene card. The rail walks the scheduled plan forward from the scene's moment (and back, if you ask it to) and lists every change point: each instant something enters or leaves the scene's ground, with what changed and how many things are in scope afterwards.

Each row carries a tick. A ticked row is captured at export as a full map picture of the scene's ground at that instant; an unticked row prints as a table line only — time, what changed, clash counts. A scene you have not accepted cannot switch a rail on: accept it first.

The rail is frozen when you switch it on. The plan can keep moving underneath without the report changing under you; Refresh recomputes the rail and keeps your ticks on every row that still exists — rows that are new arrive unticked, and ticks on rows that vanished are dropped with a hint saying how many. Redrawing the scene's outline is different: it is new ground, so the next Refresh resets the ticks. When you export, SimOps checks whether the plan has moved since you curated the rail and asks whether to go ahead with the frozen version or stop and refresh first.

The day peak

Ticking by hand means hunting through every row of every day for the one worth picturing. So the rail pre-ticks one row per day for you: the Day peak — for each site-local calendar day in the horizon, the change point after which the most things are in the scene's ground. If a day reaches its peak more than once, the tick goes to the earliest instant it gets there — the moment the day's crews come online. The peak is taken over the whole day, not a shift, so on a site where the day shift is busiest it lands in the day shift by construction.

Three edges keep that honest:

  • The report day gets no default tick. The headline picture already shows the report day at the scene's moment; a second picture of it would print the day twice. Its rows stay on the rail for a hand tick. Days looked back over do get one.
  • A quiet day gets nothing. A day with no change point has no peak, so no tick and no picture — nothing is invented to fill it.
  • A default tick is just a tick. Once placed, it is indistinguishable from one you placed yourself: untick it and it stays unticked. In the rail each day's peak row wears a small day peak tag, ticked or not, so you can always see where the rule would put it. The tag is for you; it never prints.

When the rule ticks: day-entry

The day peak is only ever ticked at Day-entry — the moment a calendar day first falls inside a scene's horizon, busy or quiet. That happens when you switch the rail on (every day is new, so the rail arrives pre-ticked), when you lengthen the horizon (only the added days are new, and only they get ticks), and when a redrawn outline resets the rail (every day is new again).

A Refresh with the same horizon has no new day, so it never re-ticks: a default you unticked stays unticked, a hand tick stays, and your curation survives. If a Refresh brings a day that was quiet its first changes, that day's peak arrives tagged day peak but unticked. Tick it by hand if you want it. There is no "tick the peaks again" button. If you want the rule's picks back, switch the scene's rail off and on again.

The section switch

Above the scene cards, beside Select All and Select None, sits Region evolution on all accepted scenes — the Section switch. It is not a setting and stores nothing; it reads the scenes. It shows ticked when every accepted scene has its rail on, half-ticked when some do, and empty when none do.

Ticking it switches the rail on for every accepted scene that does not have one yet, each with the site's forward-days horizon and its day peaks pre-ticked. Unticking it switches every rail off — hand ticks included — with no confirm, exactly like unticking one scene's rail. Nothing is inherited: a scene you accept afterwards arrives without a rail, and the switch drops to half-ticked until you deal with it.

What a ticked row costs

Every ticked row is a real capture at export: SimOps moves the map to that instant, waits until the site has loaded and painted, and photographs it — a couple of seconds a picture. When an export would take more than 20 of these extra pictures across all scenes, it stops first and tells you how many and roughly how long. With the default five days forward, four scenes' worth of day peaks passes quietly; a fifth scene is where the question starts.

Site defaults

How far a freshly switched-on rail looks forward is the site's call, not the report's. It lives under Settings ▸ Site ▸ Reports — Days a scene's Region evolution looks forward when it is switched on — defaulting to 5 days, anywhere from 1 to 31, and editable by whoever can build reports on the site. Because the rule ticks at most one row a day, that number is also roughly how many pictures each scene gets by default.

The setting only seeds a rail when it is switched on. A scene already carrying a rail keeps its own horizon when the setting changes, and on any scene you can still slide the rail's horizon forward or back for that scene alone.


See also: Building and exporting a report — the steps · Reports & exports — the feature at a glance · Planner & region evolution — the same engine, live on the map. Terms: glossary — ReportScene, Region evolution, Day peak, Day-entry, Section switch.

Reports guide: Reports · Building and exporting a report

Was this page useful? Report a problem

No cookies and no third-party analytics. A verdict records this page's path — and a search that finds nothing records the words you typed — in this site's own server log.

Generated from source · SimOops living system reference