Reading your Dashboard

Dashboard is the first screen after you sign in, and it answers one question: what needs a decision today. Four numbers across the top, a table of every trail you look after with its status and its outstanding work side by side, and a column beside it carrying what those numbers are made of and what has happened lately.

Everything on the page is a link. Tapping a number takes you to the list it counted — and where that number is a single item, straight to the item itself rather than to a list of one.

The four numbers at the top

Open tasks is work somebody still has to go and do — maintenance items that are Open or In progress. Submissions waiting on a decision are deliberately not in this number; they appear on the line underneath as to review, because accepting them is a separate call from doing them.

Under the big number: how many of those open tasks are marked critical.

Structures at risk is every piece of infrastructure rated Poor or Failed. It counts bridges, signs and gates that are not attached to any trail as well as ones that are, so it can be a larger number than the trails below it account for — that difference is infrastructure sitting at a trailhead or a parking area rather than on a line. Tapping it opens your infrastructure list with the At risk filter already on.

Expenses to review is the count of submitted expenses waiting on an approval. You only see this tile if you are allowed to approve them; if you are not, the same slot shows Awaiting review instead — reports from the public that need triaging before they become work.

Closed trails counts trails that read as closed to a visitor right now, which is not the same as trails somebody closed by hand. A trail set to inherit takes its status from its area, and then from its network, so closing a whole network closes every trail under it and this number moves with it. The line underneath adds how many are on caution.

The column on the right

Four things sit beside the table, in the order you are likely to need them.

Network status is one row per network: its condition, and a tap to change it. This is the only place on the page that answers "is a whole valley shut", so it is worth a glance before reading the table — a network that is closed closes every trail under it, and each of those trails reads as closed without anybody having touched it.

Three breakdowns take the biggest tiles apart. They add up to the numbers above them — if a breakdown and its tile ever disagree, trust neither and tell us.

• Open tasks by type is the same open work split by what kind of job it is: blowdown, drainage, signage, whatever your types are. It is the fastest way to see that half your season is one recurring problem.
• Open tasks by priority is that work ranked. A tall critical bar is the one reading on this page that should change what you do this week.
• Structures at risk by type splits the poor and failed infrastructure by what it is. Six failed signs and one failed bridge are the same number on the tile and completely different jobs.

Long lists are cut off at nine bars and the rest are collected into a gray Others — counted, never dropped, so the numbers still add up. Press a bar to open its list, filtered to exactly what the bar counted; the whole row is the target, so a short bar is no harder to hit than a long one. The gray Others is the one that does not open anything, because it is several kinds at once and there is no single list to send you to. A breakdown with nothing in it draws a gray outline of itself and says so in words.

Recent activity is the last few things that changed anywhere in the workspace — a condition flipped, a bridge updated, a task filed — each one a link to the thing it happened to.

Trail Health

One row per trail: its name, the network it belongs to, its status, its open work and its structures.

A trail that is in more than one network is listed once, under the first — the same one its status is inherited from — so the Network column always names the network the status came from.

Every trail carries its difficulty icon in front of its name, in the same shapes and colors the Trails list uses. Which shapes you see depends on what the trail is mainly for: mountain-biking trails get the familiar circle, square and diamond; alpine and nordic trails get the ski-area signs; everything else gets a plain colored disc, where the color carries the meaning on its own. A trail with no difficulty set shows a gray disc, so the names stay in line.

Status

The Status column is what the trail actually reads as, not what somebody typed on the trail itself. A trail with no opinion of its own takes the worst status of any area that has one, and failing that, its network's. Rest the pointer on a pill and it tells you where the status came from — Set on this trail, From area: Wet Bottom, From network: Cedar Butte.

Press a pill to change it. It opens Trails → Trail Conditions with that trail scrolled to and outlined. It is the shortest route from noticing a trail reads wrong to fixing it, and it works the same way in the field app, where the pill opens the editor over the list rather than leaving the screen.

A trail that belongs to no network is the one exception: there is no band for it on Trail Conditions, so its pill opens the trail's own settings instead.

This matters more than it sounds. A trail that looks open in its own settings can be closed to the public because the valley is closed, and the pill is the only place on this row that difference is visible.

Open tasks

One number: work on that trail somebody still has to go and do — Open plus In progress. It is the same definition the tile at the top of the page uses, so the column adds up to it.

A dash means none.

Beside it, when there is one, a review chip: reports filed against that trail that nobody has accepted yet. They are deliberately not in the number, because a submission is not a job until somebody says it is.

Tapping either opens what it counted — the item itself when it is a single one, that trail's filtered queue when it is more.

Structures

A chip per condition rating that is worth reading — Failed, Poor, Marginal or Fair — with how many. The ratings come from your inspections; filing one from the field app sets the structure's condition from the answers.

Anything in Failed or Poor is on the Structures at risk tile above.

Two shorthands keep the column readable. A trail whose structures are all sound says N good once rather than printing four zeros, and a trail with no structures at all says None — an empty cell would look like a row that failed to load.

Tapping a chip opens what it counted: the structure itself when it is one, your infrastructure list filtered to that trail and that rating when it is more.

Finding one trail quickly

Two controls sit in the panel's header:

• Find a trail filters the table as you type. It searches names only, and it filters what is already on screen, so there is no waiting.
• Needs attention narrows the table to trails that have something to act on — anything not fully open, any outstanding work, or any structure rated Poor or Failed. The number beside the button is how many that is.

A line at the foot of the panel says how many of your trails you are looking at, with a Show all link back when a filter is hiding rows, and a way through to the full trail manager.

On a phone

The table becomes a card per trail: the difficulty icon, the name, then its status and only the counts that are not zero, and the network underneath. A trail with nothing outstanding still shows its status, so a card is never blank.

Everything else works the same way. Search still filters, Needs attention still narrows, and the numbers below the table stack into one column in the same order.

What you see depends on your role

The tiles follow what you are allowed to do. Somebody who cannot approve expenses does not get an expenses number they can only look at; they get the submissions queue instead. The rest of the page is the same for everybody in the organization.

If a whole section of the product is switched off for your workspace under Settings → Workspace modules, its numbers do not appear here either.