Loam
A useful trail condition report says what you observed, where you observed it, and when. Keep the trail surface, a maintenance problem, and an official closure separate. Each answers a different question.
Loam's condition model estimates how a network responds to weather, soil and terrain. Rider feedback helps check those estimates against what people encountered. It does not turn a network forecast into an inspection of every trail.
How to report trail conditions in Loam
When available, the network page's feedback prompt asks whether the estimate matched your ride. Confirm that you rode today or yesterday, then say whether Loam's estimate was drier than what you found, about right, or wetter than what you found.
The app's post-ride form can ask about tread condition, whether tires left ruts or smeared the surface, and when you observed it. Some networks also offer a segment choice. Answer for the ground you actually encountered; do not infer the condition of a section you did not ride.
These submissions support accuracy and calibration review. They are not a public trail-report feed, a photo or hazard-report service, or an automatic command to change the live verdict. See Loam's rider-agreement checks and their sample-size limits. Agreement with a report is different from independently measuring the trail surface.
A short checklist before you post
- Identify the place. Choose the correct network. If a local reporting channel accepts trail names or segments, name the section you checked rather than describing the whole region.
- Give the observation time. Say when you were there, not just when you submitted the report. A morning observation may no longer describe the tread after new rain or a thaw.
- Describe the surface. Separate firm damp ground, loose dry dirt, soft mud, standing water, snow and ice. If a tire left a groove or mud built on the tread, report that concrete sign rather than simply calling the ride good.
- State the limits. Distinguish a dry first section from the rest of the route, and the access road from the singletrack. Do not turn one observation into a claim about every trail.
- Use the right channel. Send a condition comparison to Loam. Send a downed tree, damaged bridge, drainage problem or access question to the responsible steward or land manager through its published reporting channel.
You do not need to continue through soft ground to complete a report. Use the trailhead firmness check and turn back when the tread is unsuitable. IMBA's Rules of the Trail advises respecting closures and considering other options when trails are soft.
Maintenance reports and closures have different jobs
Local workflows vary. For example, the Coast Mountain Bike Trail Association asks riders to report maintenance issues through Trailforks. Its guidance says photos and GPS locations can help locate the issue and plan the work. That describes its reporting channel, not a feature of Loam.
A rider saying the ground feels firm cannot reopen a closed trail. In Bend, COTA explains that it is not the land manager and cannot grant or deny access. Check the responsible manager's notice and posted signs even when a recent observation or model estimate looks favorable.
Use a report alongside the forecast
Check the report's time and coverage, then ask what has changed since: more rain, a freeze, a thaw, maintenance or a new access notice. A forecast is useful for planning; an observation describes a particular visit. Neither guarantees the rest of the network.
For a group or a trip, agree on the route, a turnaround decision and a separately checked backup before leaving. The trip-planning guide helps combine network forecasts, local reports and access checks without treating a favorable label as permission to ride.
Frequently asked questions
Does my feedback change the condition immediately?
No. Loam records feedback for checking estimates and reviewing calibration. It does not automatically replace the live model verdict with a rider's answer.
Can I report a hazard through Loam's condition feedback?
The feedback controls compare an estimate with observed conditions. For a hazard, maintenance need or access issue, use the responsible steward or manager's published channel.
What if the model and my observation disagree?
Report what you actually found. Follow official access rules and the condition of the tread ahead of a favorable forecast. Do not ride soft ground to prove the estimate wrong.
