How to Build a Credible ACMG Logbook
What the Association of Canadian Mountain Guides actually wants to see — and how to build a logbook that gives your application the best possible chance.
Ascents Team
February 10, 2026
The single most common reason aspiring guides struggle with ACMG applications isn’t lack of experience. It’s lack of documentation.
You’ve done the days. You’ve climbed the routes. But when it comes time to compile your application, the records are scattered — notebooks, spreadsheets, faded trip reports, things you remember but can’t prove. An assessor reviewing your logbook can only evaluate what’s in front of them.
This guide is for aspiring guides who want to build a logbook that works as hard as they do.
What the ACMG actually requires
The ACMG’s certification streams — Ski Guide, Rock Guide, Alpine Guide, Mountain Guide — each have specific day and route requirements that candidates must demonstrate before attending a guide training course.
These requirements are not suggestions. They’re baseline thresholds designed to ensure candidates have enough foundational experience to benefit from the course and to guide safely afterward.
The key requirements vary by stream and are updated periodically — always check the current ACMG website for the definitive list. But in general terms, they look for:
Volume: A minimum number of days in the relevant terrain and season. For many streams, this runs into the dozens of days at specific grades or in specific conditions.
Breadth: Documented experience across different terrain types, conditions, and roles. A logbook that shows 60 days of sport climbing on the same crag is less useful than 60 days spread across single-pitch, multi-pitch, trad, and alpine approaches.
Progression: Evidence that your skills have developed over time — that you’re not just accumulating days but actually progressing toward the technical and leadership demands of guiding.
Verification: The ACMG takes seriously whether your logs can be corroborated. Entries that were witnessed by a certified guide carry significantly more weight than unwitnessed entries.
The verification problem
This is where most aspiring guide logbooks fall short.
A self-reported logbook is better than nothing. But an assessor reading your application has no way to verify that the alpine day you logged in 2021 happened as described, involved the terrain you say it did, or was at the technical standard you claim.
A logbook entry countersigned by an ACMG guide who was with you on that day is a different kind of document. It’s date-stamped, specific, and corroborated by a certified professional. It carries weight.
This is why we built verification into Ascents. When a lead guide countersigns your entry, it becomes a verifiable record — not just a personal note.
What a strong logbook looks like
The best logbooks we’ve seen share a few common characteristics.
Specificity. Vague entries are hard to evaluate. “Climbed in Squamish” tells an assessor almost nothing. “5 pitches, 5.10c multi-pitch trad, Northeast Buttress area, Squamish, BC — with [guide name]” tells them exactly what they need to know.
Consistency. Logs that stop and start, skip seasons, or have obvious gaps are harder to read than logs that show continuous engagement over time. Even easier days in poor conditions are worth logging — they show that you’re out there year-round.
Honest self-assessment. Notes on conditions, challenges, what you found hard, what went wrong. An assessor who sees that you logged a difficult day where you backed off a route, explained why, and described what you learned is reading a logbook from someone who will be a safe guide. Logbooks where everything is always perfect are less convincing.
Roles documented. Were you following, seconding, leading, co-guiding? The role matters. Document it.
Planning your seasons before it’s too late
One of the most useful things Ascents does for aspiring guides is show you your gaps before it’s time to apply.
If you’re working toward the ACMG Rock Guide course, you can set that as your goal in Ascents and see — in real time — how your logged experience maps against the published requirements. Which terrain types are underrepresented in your logbook? Which seasons have you not been out? Where do you need to focus your remaining seasons?
This isn’t a question you want to be answering two months before an application deadline. It’s a question to answer at the beginning of the season you have time to change.
A note on aspiring guides doing admin
Building a credible logbook takes effort. But the alternative — losing three seasons of hard-won experience to a missing notebook — is far more costly.
Ascents makes the documentation habit as low-friction as possible. Log from your phone at the trailhead, get your lead guide to countersign on the spot, and by the time your application is due, your logbook has been building itself all along.