Competency examples.
What good looks like.

What a regulator is looking for

In the competency-based assessment you show each competency with an example from your experience, and a validator, usually your supervisor, confirms it. Your examples are how the assessors see your judgment, so they need to show what you did, not only what happened.

Strong examples tend to

• Describe one situation, not a summary of a whole job.
• Say "I", and make clear which part was yours and which was the team's.
• Name the decision you made and why, including codes, standards or limits you applied.
• Give the outcome, and what you'd do differently if it applies.
• Use real detail: dates, quantities, the type of structure or system, without client names or confidential details.

Weak examples tend to

• List duties ("responsible for site inspections") instead of telling what happened once.
• Describe what the project achieved without saying what you did.
• Stay vague where the competency asks for judgment: risk, safety, ethics, quality.
• Reuse one paragraph for several competencies without changing what it shows.

An illustration

For a competency about applying codes and standards: "In March 2026 I checked shop drawings for a precast box culvert against the design and the bridge code. Two connection details didn't match the specified cover, so I marked them up, explained the issue to the fabricator's drafter and had the drawings reissued before fabrication. The revised details met the specified cover and the culvert was installed on schedule." This is an illustration of the shape, not a model answer: yours has to be your own work in your own words.

Where Gusset fits

Gusset keeps the raw material: dated entries, in your words, filed against the competencies as you go. When you apply, Gus lays out the facts from your entries and an outline of questions for each competency, and checks what you wrote against your record. Gus never writes the example for you: some regulators don't allow AI to create or embellish them.