Your users become your eyes on the trails
Your trails are ridden every day by people who are not on your crew. When a tree comes down across a descent on a Tuesday morning, somebody saw it — and you will hear about it the following Saturday, in a Facebook comment buried under thirty others, or never.
What was missing was never their goodwill. It was the path: create an account, remember a password, find the right page. Nobody does that standing in a trail with a bike in their hands.
Sentinel 3.0.0 opens up public reports. The user opens the app, takes a photo, sends. No account, no email address, no password. You receive the report with its location and its photo, in an inbox to be triaged.
One photo, and it's sent — That is the only thing asked for: the location goes on its own, the rest is optional. The user is never asked what kind of problem it is — sorting problems out is your job, and you will do it better at triage. With no signal, the report waits on the device and leaves as soon as coverage comes back.
Nothing reaches your planning on its own — A report is information to be checked, not a task. So it lands in a separate inbox, and someone on your crew is the one who decides what becomes of it. That is what keeps your task board clear of duplicates and problems already fixed.
Three outcomes, and nothing to retype — Turn it into a task and your usual form opens already filled in. Attach it to an existing task, when somebody reports a problem you already know about. Or refuse it, sharing the reason if you want to. When the same problem comes in several times from the same spot, the app offers to group them all at once. And triage works from the phone too: on site, you are standing in front of the problem.
Nobody is left without an answer — This is what decides whether a user reports a second time. From "My reports" they follow theirs, and they can ask to be told when it moves along. They see no more than that: not your planning, not your assignments, not your discussions. What they get is the certainty that somebody looked.
None of this opens without you: the feature is off by default, and a single page decides everything — what you accept, what the public may consult in return, and how you get found.
Your structures name themselves
Out in the field, whoever installs the thirtieth marker on a trail shouldn't have to decide what it's called. Until now,
every structure name was typed by hand — with everything that comes with it: PV 12 sitting next to PV-012, skipped
numbers, and duplicates you only discover three months later while preparing an inspection.
Sentinel 3.0.0 brings automatic structure numbering. You describe the shape of the name once, and the app proposes the next one every time you create a structure — at the office as much as in the field, with or without a connection.
One rule per type and per activity — Structure types now have a new tab, Numbering, where a live preview shows the next three names. A boardwalk for mountain biking and a boardwalk for hiking stay two independent sequences, with their own prefixes if that's what you want.
One sequence per trail — Numbering restarts at 1 on every trail: the first boardwalk on one trail is PV-001, and
so is the first boardwalk on the next. Off-trail structures form their own sequence. It matches the way people talk on
the ground — "the second boardwalk on La Coulée", not "boardwalk number 47 on the network".
The name is still yours — It arrives pre-filled, never imposed,
and the app simply warns you if the one you pick is already taken on the same trail. The sequence also picks up from
what you already have: if your structures are named Bridge 12 and Bridge 13, the next one is proposed as
Bridge 14, even without any rule configured.
Even deep in the woods — Offline, the proposal accounts for the structures already on the device and for the ones waiting to be synchronized. Two boardwalks created back to back in the same area can't end up with the same number.
Numbering is configured from the web app, and mobile uses your rules as they are.
The trail you tap finally stands out
On the Field map, tapping a track filters tasks down to that trail. That was already true — but nothing really showed it: the chosen trail got a halo in its own colour, so pale green under a green line, in the middle of fifty other coloured tracks. You tapped, something changed, and you weren't sure what.
The other trails recede — As soon as a trail is selected, every other one drops into the background, very pale, names faded, while yours thickens. Nothing disappears: you keep the shape of the network in view. The contrast comes from recession rather than from adding a colour, which makes it read just as well on satellite as on the light basemap.
A pill tells you what you're filtering on — Zoomed in on a task, the chosen track no longer fits on screen: a pill at the top left names it. And when you filter several, it gives way to a quieter capsule showing the symbols of the ratings in play, then the count — the same size whether you filter two trails or fifteen.
Tap the same trail again to go back to the full view. It's the same filter as the panel's: what you set with your finger on the map shows up under "Trail", and the reverse holds too.
Your task folders reach the phone
Folders group the tasks that get done together — "May 12 work party", "Before opening day". You filled them from the web app, but the phone never showed them: out in the field you had to piece the work party back together from memory, task by task, in the middle of the whole list. The tidying done at the office stopped at the door.
Sentinel 3.0.0 shows your folders in the Field list, and lets you open the contents of each one.
A Folders heading, between the projects and the tasks — One row per folder: its name, and a gold icon that tells it apart from a project.
Three ways to look at it — Tap a folder and its contents open like a project's: three tabs at the bottom of the screen, Map, List and Kanban. The map frames itself on the folder's tasks, and the kanban is the one you know from My planning. Every folder reopens in the mode you left it in — a scouting folder on the map while a work-party folder reopens as a kanban — and a project's details now behave the same way.
A shortcut, not a drawer that hides things — Filing a task in a folder doesn't remove it from the list: it stays visible further down, in its status group. A folder opens a second path to the same tasks, it diverts none of them.
Even with no network — Folders are part of the data installed on the device, like the trails and the task types. The heading shows up and a folder's contents can be browsed offline, with nothing to prepare.