Your experience log.
A minute a day, four years of record.
An experience log is a running record of the engineering work you do while you're working toward your licence: what you did, when, what you decided and who supervised it. Kept as you go, it's what you write your competency examples from when you apply, instead of trying to remember four years at once.
Why keep one
Regulators assess your experience against competencies, and each one needs a real example with detail. Details fade fast: by the time you apply, the dates, numbers and your own reasoning from two or three years ago are hard to recover. A log keeps them while they're fresh.
What to write in each entry
- The date, or the date range for work that ran over weeks or months.
- What you did, in one or two plain sentences.
- The decision or judgment that was yours, and why.
- Codes, standards or tools you applied.
- The outcome, if you know it yet.
- Your supervising engineer for that work.
How often
Little and often beats long and rare. A sentence on the days something happened is enough; a weekly catch-up works too. Leave out client names and confidential details: keep it generic.
Where Gusset fits
Gusset is an experience log built for this. Tell Gus what you did in a sentence, typed or said, and Gus dates it, files it against the 34 competencies and shows what's covered. You can export it all, any time, free.
Sources: APEGNB, Competency-Based Assessment guidelines; PEO, Navigating Competency-Based Assessment (2024). Your regulator's current guide is the authority.
Gusset is independent and not affiliated with or endorsed by any engineering regulator.