Make your APEGA PACE plan. Back it with evidence you've already earned.
You decide what skills and knowledge to maintain and develop — PYPD gives you the structure and the vocabulary to build the plan, then interviews you about the work you've already done and turns it into the evidence that backs it.
Built by Canadian engineers. An independent tool, not an APEGA product. You write your own plan — there's no generate button.
You did the work. PACE asks you to describe it in competency language.
The template asks for the skills, knowledge, and competencies your work demonstrates — in vocabulary scattered across the standard, the guideline, and an FAQ, with no published bar for “good enough.” So most people write something vague and hope the Practice Review Board never asks to see it. The hard part was never the engineering. It's translating what you did into the terms the standard wants — without overstating, and without losing a Saturday to it.
Make the plan
Build from a catalog, not a blank box.
APEGA didn't publish a skills taxonomy, so we wrote one. The PYPD PACE Catalog is a searchable list of skills and knowledge — by practice area, keyword, or type. You choose what you're maintaining or developing and assemble your own plan. There's no generate button: PYPD gives you the structure and the wording, the judgment and the plan stay yours. It's our vocabulary, not an official APEGA taxonomy — a starting point you edit.
Back it with evidence
Describe your work. The interview draws out the evidence.
For each thing you did to stay current — a course, a conference, a project, mentoring — tell PYPD about it in plain language. It asks two or three focused questions, then writes it up as a PACE activity: a short account plus the written explanation a reviewer actually looks for — how it maintains or develops the competence you identified. Grounded only in what you told it, never invented.
One activity, every competency it shows.
Real engineering work touches several competencies at once. PYPD tags each activity with the skills and knowledge it genuinely demonstrates, each with a one-line reason tied to something you actually said. You confirm or cut — it's a starting point you control, not a verdict.
Peer review, inside the workspace.
APEGA recommends a licensed professional review your plan — and it doesn't have to be your supervisor. Send a request to any P.Eng or P.Geo in your contacts, capture their input, keep the record.
Evidence filed by competency.
Every supporting file and link sits with the activity it backs, organized by competency. If your plan is ever pulled for a Practice Review Board look, the trail is already in order — not assembled in a panic the week APEGA asks.
The five mandatory modules are tracked alongside too — certificates held, status flagged before renewal — but that's housekeeping, not the reason to be here.
How it works
- 1
Build your plan.
Search the catalog by what you do, and choose the skills and knowledge you're maintaining or developing. You write it; PYPD structures it.
- 2
Tell it about your work.
Describe a course, project, or activity in plain language. PYPD asks a couple of questions, then drafts the activity and the explanation of how it supports your competence.
- 3
Confirm, file, and keep.
Accept or cut the suggested competencies, attach your evidence, request a peer review. It's filed and ready if APEGA ever asks.
Straight answers, because PACE is new and skepticism is fair.
- PYPD is an independent tool built by Canadian engineers. Not an APEGA product, not endorsed by APEGA.
- The catalog is our vocabulary, not an official APEGA taxonomy.
- You write your own plan — there's no generate button.
- The interview drafts your activity evidence from your own words, and never invents facts, numbers, names, or outcomes. You stay the author and the judge of what goes in.
- The five mandatory modules are tracked, but PYPD doesn't deliver the training — that lives on APEGA's Learning Centre.
- Your work is yours: stored securely, deletable any time, with export coming soon.