Every lift, every type
Chairs, gondolas, trams, T-bars, platters, J-bars, rope tows, magic carpets and funiculars in one list, with operational state, inspection history and what each one serves.
For alpine resorts and four-season mountains
One mountain, two seasons, one record
A resort that runs bikes in July and chairs in January usually runs them on different systems, and the ground is the same ground. TrailsIQ holds the lifts, the runs, the structures and the trail program together, all year.
What it has to handle
The parts that outlast the season
Snow reporting is well served. What tends not to be is everything underneath it — the asset list, the inspection trail, and the summer program that shares the same mountain.
Runs and trails on the same map
Winter runs and summer trails as records that carry their own status, difficulty and season — so a line that is a blue run and a bike trail is one object, not two.
Structures and their inspections
Bridges, gates, signage, kiosks — condition, install date, dated inspections and photographs, on the asset rather than in a shared drive.
A daily report the mountain shares
Lift states, status changes, crew notes and the day's events on one page, with a filtered public version so operations and guests read from the same record.
Counters and use data
Trail counter units, their positions and their readings kept against the trail — the evidence behind where the machine time goes next year.
Contractors, scoped tightly
Lend a builder the two trails they were hired for. They work those trails from their own account and can reach nothing else on the mountain.
On the hill and off it
Where a resort actually loses time
Not in the reporting. In the distance between where something is noticed and where it gets written down.
The field app
Recorded at the lift tower, not at the desk
A patroller or a lift mech logs what they found where they found it — GPS pin, photo, type, priority — and it is in the queue before they are back inside. Above the treeline and in the back bowls it works with no signal at all, then uploads itself.
- The mountain, downloaded Map, terrain, photos and the full work list, on the device before the shift starts.
- Nothing is lost to a dead zone Edits queue locally and send when signal returns.
- Roles carry to the phone A seasonal hire sees what their role allows, changed from the web and in force at the next sync.
The summer program
Plan and price new trail on real terrain
Walk a proposed line and the planner reads the ground under it — grade, side slope, the fall-line stretches, where drainage and structures will be needed. Group the season's lines into a project and it prices as one job.
- Sustainability from samples Scored against measured side slope and grade along the line, not a rule of thumb.
- A build estimate against your rates Your crew rate, your materials, priced off the ground you walked — and yours to hide on any share where the number is nobody else's business.
- A proposal you can send One link with the map, the profile and the numbers, for the board or the landowner.
Getting started
Start with one department
One department, one season. That is enough to change how the whole mountain keeps its records.
01
Bring in the trail and run map
Bulk import, then group into the pods and zones the mountain already uses.
02
Add the lifts
Type, what they serve, current state — the base for both the daily report and the inspection record.
03
Put it on one crew's phones
Trail crew or patrol, whichever loses the most to paper. That is where the first week's value shows up.
04
Decide what goes public
A conditions page and a daily report, or keep it internal while you run it alongside what you have.
Give one crew a season on it
Start free, put a single department on it, and finish the season holding the record you always wished the mountain had — the assets, the inspections, the hours and the work, all in one place.