Lend a trail without handing over the keys

Shipped the week of August 10.

Trail work involves people who do not work for you. A contractor hired for two trails. A club that maintains the section above yours. A land manager who needs to see the plan before they will sign it. This week was about all three.

Lend a trail to another organization

You can now give another TrailsIQ organization access to one trail — not your whole workspace, not a membership, one trail.

They see it read-only on their own map, in their own Trails list, alongside their own work. If you tick the box for it, they can also work its maintenance: file items, work them, close them. Everything they file is labeled with their company name so your crew can tell at a glance whose work it was.

Take it back whenever you like. The trail stops being visible the moment you withdraw the share, and both sides are told — you when somebody accepts, them when you withdraw, because a trail that vanishes with no word reads as an app that lost somebody's work.

It works offline too. A borrowed trail comes down in an offline download like any other, and carries a two-week lease — a builder who syncs at all never notices it, and one who is out of contact for a fortnight loses the borrowed trail and keeps their own.

TrailsIQ for builders, not just operators

TrailsIQ serves two kinds of team who need different things: people who run a trail network and people who build them. Until this week everyone got the operator's product.

Now you are asked what your team does when you set up a workspace, and the answer sets the starting point for what appears in the menu. A trail-building business gets clients, jobs and job costing, and does not get lift status or trail counters. Everything is a switch you can change afterwards, and switching something off hides it rather than deleting anything — turn it back on and your data is where you left it.

You can also spin up a second workspace at any time, which is the case for somebody who volunteers for a club and also runs a building business. They are fully separate, and a switcher appears once you have more than one.

Proposals a client can actually read

A project's proposal page got the treatment it needed to be sent to somebody outside the organization:

• A cover image you frame yourself on the map, and can draw on before it is saved
• An elevation profile per trail, not one for the whole project
• A QR code, so the page opens from a printed sheet at a meeting
• Rejected options stay off it — a client sees the proposal, not the thinking behind it

The money side is on the phone now too: open a project in the field app and its estimate is there beside its trails.

Also this week

A real edit screen for a planned trail in the field app. It used to offer a rename and nothing else.

The report app is quicker to get through. The "checking your location" step takes about half the time it used to, which is the step standing between somebody who wants to report a problem and actually reporting it.