What was found and what was fixed
Items opened and resolved over the period, what is still outstanding, and what is waiting on somebody to review it.
Reporting and records
Answer it in March with what you recorded in July
A grant application, a board meeting, a landowner asking what you did with the season. All three want the same four facts, and all three arrive months after the work — so the reporting has to be a rollup of what happened, not an act of memory.
The period report
A season, summarized from its own record
Pick any stretch of time and any network. Everything below is derived from entries somebody already made — nothing here asks a person to remember a number.
What it cost and who did it
Hours against the items they were spent on, paid and volunteer counted apart, with the expenses and materials that went with them.
Crew and costsDays open, caution and closed
Reconstructed day by day from your own condition changes, with every closure and reopening counted — so "how much of the season was rideable" has an answer.
And the weather that explains them
Rainfall and snowfall totals, the high and low, the peak gust and the wettest day of the period — beside the closures, where they answer for each other.
Trail conditionsPer network, or across everything
Report on one hillside for the landowner who owns it, or on the whole organization for the board.
CSV and PDF, everywhere it matters
Maintenance, structures, trails, points of interest and counter readings each export both — one to work with, one to attach to an application.
Seasonal checklists
Proof the walk actually happened
The hardest thing to produce a year later is evidence that a routine inspection round was done at all. A checklist run is that evidence, made as a side effect of doing the round.
01
Write the list once
A spring opening sweep, a pre-season bridge round, a post-storm check. The template is yours and it is reusable — you are not rebuilding it every April.
02
Start a run when you go out
From the field app, at the trailhead, with no signal needed. The run is dated and belongs to whoever walked it.
03
Each row lands in one of three states
Done, skipped or flagged — with up to four photographs on the row itself, taken where the decision was made.
04
A flagged row becomes work automatically
It raises a maintenance item against the same thing, linked back to the row that flagged it. Change your mind and clear the flag before anybody starts, and re-flagging later rejoins the item you already had rather than filing a second one.
05
And the run stays as the record
Complete or still open, with every row's state and photos attached — which is what somebody asking "when did you last walk this?" actually wants.
Records that hold up
Written down when it happened, by the person it happened to
Every one of these is a by-product of the work rather than a separate reporting chore — which is the only kind that stays true.
An inspection history per structure
Every walk on that bridge, dated, with its answers, its photographs and the condition it produced. The one time somebody asks is the reason it exists.
InfrastructureA history per item
Who changed it, when, and what was said about it on the way to being fixed — attached to the item rather than scrolling away in a group chat.
MaintenanceThe day, written up
A daily report collects the day's condition changes, work and notes into one page — assembled from what already happened, and publishable to your visitors.
Your public siteAttributed, including outside help
Work done by a contractor on a trail you lent them is labeled with their company on your item. A year later you can still tell your crew's work from theirs.
In the documentation
How this works, in detail
Step-by-step guides for setting each of these up.
Start recording it now, report on it later
The season you can report on is the one you wrote down while it was happening. Start free and have the first walk on the record this week.