List · reads checkin
Check-ins
Attendance events.
One row per item, the plainest possible view.
- Tomas RéalAtelier Nord
- Jonas WeissOberkampf
- Céramique Rive (delivery)Atelier Nord
- Aïcha BenaliOberkampf
What it does
Behaviours, not fields. Choosing between two modules is choosing between these.
Presence rather than intention, which is what makes it evidence after the fact.
Still-on-site is a live state, which is the reason a fire register exists at all.
Visitors and staff in one record, because an evacuation does not distinguish them.
How it works
- 1
Arrival is recorded when it happens rather than reconstructed later.
- 2
Still-on-site is a live state, which is the whole reason a register exists.
- 3
Visitors and staff share one record, because an evacuation does not distinguish them.
- 4
The register is per site, so two locations do not confuse each other.
Best for
Reading and scanning. It is the right default more often than it looks.
Not the right choice for
Comparing many fields at once — use a table.
What a row holds
Every field, and what the agent listens for to fill it — which is the difference between a page you type into and one that fills itself.
| Field | Type | Filled from |
|---|---|---|
| Whorequired | text | The person or visitor, matched against Team where possible. |
| Whererequired | text | Which site. Presence is per location. |
| Inrequired | time | Arrival. Recorded at the moment, which is what makes it evidence. |
| Out | text | Departure, or Still on site. The live state a fire register depends on. |
What it does not do
A module chosen for something it cannot do costs more than one that was never offered.
- Nothing enforces checking out, and people forget — which is itself the most common false alarm.
- No automatic check-in from a device or badge.
- It records presence, not hours worked; that is a different problem.
- No alerting if somebody is on site outside expected hours.
Before it works
What you have to provide, if anything.
- Decide which sites need it. A register on a site nobody uses trains people to ignore it.
- Pair with Facilities so the sites in the register are the sites you actually occupy.
In practice
A workshop with staff across two sites and regular deliveries.
“Tomas is at Atelier Nord from seven.”
What the agent built
A check-in with a time, and a check-out when he left.
What changed
At six one evening one person was still checked in. He had gone home and forgotten to check out — which is exactly the failure the record is meant to catch.
Better with
These do a different job on the same data. An agent can have all of them.
The business occupies more than one space under agreements that expire.
Attendance is recorded per session and no-shows matter for planning, billing or certification.
The site needs an about-us or team page, or the dashboard needs to show who is available for what.
Questions
What data does the Check-ins page use?
It reads checkin records the agent has collected. Attendance events. Nothing has to be imported first — the page appears once there is something to show.
Do I have to build or configure it?
No. You describe what you need in a sentence and the agent chooses the view and fills it. Custom pages exist for the cases no built-in view covers, and those are reviewed before they go live.
When is a list the wrong choice?
Comparing many fields at once — use a table. It is best for: reading and scanning. It is the right default more often than it looks.
Does it stay up to date?
Yes. The page is a view over the data rather than a copy of it, so anything the agent learns afterwards shows up without a rebuild or a re-import.
More in Places & logistics
- Oberkampf — 48 rue Oberkampf, 75011
- Marché des Vosges — Place des Vosges, 75004
- Café Bellevue — 12 rue de Charonne, 75011
Map / locations
Pinned places.
The Long Room
80 standing, 50 seated
Open, pillars
Atelier, 2nd floor
24 seated
Workshop, benches
Courtyard
120 standing
Outdoor, covered half
Meeting room
10 seated
Boardroom, screen
Venues
Candidate locations.
14–16 Oct
Lyon
TGV 06:52 from Gare de Lyon
16–18 Oct
Turin
Train, 4h, change Chambéry
18–20 Oct
Milan
Train, 1h50
20 Oct
Return
Flight MXP–CDG 19:40
Travel plan
Segments of a journey.
09:00
Coffee and briefing
Oberkampf
10:30
Roastery tour
Atelier Nord
12:30
Lunch
Café Bellevue
15:00
Cupping session
Oberkampf
Itinerary
Day-by-day plan.
Ask for it in a sentence
You do not configure this page. You tell your agent what you need and it builds it from what it has already collected.
Build your agent free