How to Pass the APEGS Competency Assessment Without Losing Your Mind

How to Pass the APEGS Competency Assessment Without Losing Your Mind

A stress-free guide to passing the APEGS competency-based assessment. Learn how to write a strong APEGS competency report and stay calm through the process.

If you’re preparing for the APEGS competency-based assessment, you’re probably feeling a mix of excitement, stress, and maybe a little panic.

“I’ve been an engineer for years—why do I need to write a report about it?”
“What if I don’t explain it right?”
“What if I fail?”

I’ve been there.

I spent weeks staring at my laptop, rewriting the same paragraph, doubting myself, and drinking way too much coffee.

But guess what? I passed.

And so can you—without losing your mind.

Here’s how I got through the APEGS competency based assessment with my sanity intact—and how you can too.

What Is the APEGS Competency-Based Assessment?

APEGS (Association of Professional Engineers and Geoscientists of Saskatchewan) requires all engineers applying for a Professional Engineer (P.Eng.) license to go through the APEGS competency-based assessment.

It’s not an exam. It’s a way to prove you can think and act like a Canadian-trained engineer.

The main part? Your APEGS competency report—a detailed summary of your education, work experience, and professional judgment.

They want to see:

✅ How you solve real engineering problems
✅ How you communicate and lead
✅ That you understand ethics, safety, and standards

It’s not about being perfect. It’s about showing you’re competent, responsible, and ready.

Step 1: Stop Overthinking—Start Writing

The biggest mistake I made? Waiting for the “perfect” moment to start.

I kept thinking:

“I’ll begin when I have more time.”
“I’ll write it when I feel confident.”

Spoiler: That day never came.

So I did the only thing that worked—I just started.

I opened a blank document and wrote:

“In 2020, I worked on a water supply project in my hometown…”

It wasn’t perfect. But it was a start.

Tip: Don’t aim for perfection. Aim for progress.
Write rough drafts first. You can fix them later.

Step 2: Pick 2–3 Real Projects (Not Your Whole Career)

You don’t need to describe every job you’ve ever had.

Pick 2–3 key projects where you:

  • Made decisions
  • Solved problems
  • Used engineering principles
  • Worked with a team or client

For example:

“I redesigned a drainage system to prevent flooding in a low-income neighborhood. I used AutoCAD and Manning’s equation to optimize flow, and coordinated with local contractors.”

That’s specific, technical, and shows impact.

Avoid vague statements like:

“I helped with a construction project.”
No. Just no.

Step 3: Use the STAR Method (But Don’t Call It That)

You don’t need fancy terms. Just tell your story clearly.

For each project, answer:

  • Situation – What was the project?
  • Task – What was your role?
  • Action – What did you do?
  • Result – What was the outcome?

Example:

“The client needed a cost-effective foundation design (Situation). My task was to analyze soil reports and propose options (Task). I used PLAXIS software to model two designs and recommended a raft foundation, saving 20% in materials (Action). The design was approved and built without issues (Result).”

Now that’s a solid paragraph.

Step 4: Be Honest, Not Heroic

You don’t need to be the hero of every story.

In fact, the best reports show learning from mistakes.

One of my strongest sections was about a project that failed.

“I underestimated wind load in an early design. The senior engineer flagged it. I recalculated using ASCE 7, corrected the model, and learned to double-check environmental factors.”

That showed professional growth—and APEGS loved it.

Step 5: Keep Your APEGS Competency Report Simple

Your report doesn’t need to be 50 pages.

Include:

  • A short CV
  • Employment reference letters
  • Academic transcripts
  • 1–2 pages of project summaries (your competency report)
  • CPD (Continuing Professional Development) list

No jargon. No fluff. Just clear, honest writing.

And please—use your own words.
No copying from samples. No AI.
APEGS checks for plagiarism.

Step 6: Prepare for the Professional Discussion (It’s Not an Interrogation)

After submitting your APEGS competency report, you’ll attend a professional discussion—kind of like a friendly interview.

They’ll ask things like:

  • “Tell me about a time you faced a technical challenge.”
  • “How do you ensure safety on site?”
  • “What would you do if a client asked you to skip a code check?”

They’re not trying to trick you. They want to see how you think.

Tip: Practice with a friend.
Say your answers out loud.
Keep them short and real.

Recent News: APEGS in 2025

In 2025, APEGS has made the process easier:

  • Faster processing – Most applications reviewed in 6–8 weeks
  • Online submission only – No paper forms
  • Virtual interviews – Attend from anywhere in the world
  • More support for international applicants – New guides and webinars

They’re not making it easier to fake it—but they are making it easier to succeed honestly.

How to Stay Sane During the Process

Here’s what kept me calm:

Set small goals – “Today, I’ll write one project summary.”
Work 30 minutes a day – No marathon writing sessions.
Ask for help – Talk to someone who’s done it.
Take breaks – Go for a walk. Breathe.
Remember: You’re qualified – You’ve been doing this work. Now you’re just explaining it.

You don’t need to be stressed. You just need to be clear and real.

Final Thoughts

The APEGS competency-based assessment isn’t designed to fail you.

It’s designed to confirm you’re ready to be a licensed engineer in Saskatchewan.

Yes, it takes effort.
Yes, it can feel overwhelming.
But you’ve got this.

Just start.
Be honest.
Keep it simple.

And for the love of engineering—stop overthinking it.

Pass the assessment, get your P.Eng., and go build something great.

Author Bio:
This article was written by an engineer who went through the APEGS competency-based assessment while working full-time and raising a toddler. Our goal is to give you honest, simple advice—no jargon, no pressure. Just real tips from someone who survived the process (and still loves engineering).


Kelly Gray

7 وبلاگ نوشته ها

نظرات