Some competencies in the P.Eng. Competency‑Based Assessment (CBA) are harder than others to score well on. Competency 1.4 – Apply Engineering Knowledge is one of the 10 most frequently rejected.
On the 0 to 5 rating scale, assessors want clear evidence that you personally used engineering theory and calculations to solve a problem or design a system – not just that you were involved with a project where engineering happened.
If you want an overview of all 34 competencies and how 1.4 fits into the full framework, visit the CBA competencies guide.
Why 1.4 gets rejected
From real assessor feedback, Competency 1.4 is often rejected because:
- It is not clear what you actually did. The submission mixes specialist consultant recommendations or team activities, and assessors cannot see the applicant’s own engineering steps.
- There is not enough engineering theory. The example uses only very basic equations or arithmetic that could be done at a technologist or technician level.
- The focus is on project management, not design. Statements of work, cost estimates, or schedules are described, but there is little or no use of engineering principles or calculations.
- The work does not clearly require an engineer. Assessors ask, “Why did this task need an engineer?” when the example is mostly procedural or administrative.
- Explanations are vague or incomplete. Phrases like “summation of active and reactive forces” appear without a clear explanation of what was analyzed, which method was used, or why.
- Key technical details are missing or confused. For example, not explaining why some members carry more load, not naming the design method, or describing member types that do not match the referenced code.
To score well on 1.4, you must show a specific situation where you applied university‑level engineering theory and calculations, step by step, to arrive at a solution.
What assessors want to see for 1.4
A strong 1.4 example shows that you can:
- Describe the engineering problem you were responsible for, not just the project context.
- Name the theory, method, or design standard you used to solve it (for example, Darcy–Weisbach, finite‑element analysis, heat transfer equations, design codes).
- Show your calculations and reasoning in plain language – what you calculated, what assumptions you made, and why they were reasonable.
- Connect the math to decisions, such as sizing, layout, material selection, or control logic changes.
- Explain why an engineer was needed for this work rather than a technician following a procedure.
How to structure a strong 1.4 example
Pick one project and write in first person (“I + verb”). A clear 1.4 example usually covers:
- Situation: The project, your role, and the specific technical problem you needed to solve.
- Theory and method: Which engineering theory, equations, charts, or design standards you used and why they applied.
- Calculations and assumptions: The key steps in your calculations, the assumptions you made, and any checks you did to confirm they were reasonable.
- Decision and design: How your calculations led to a particular design, size, layout, or configuration.
- Outcome: How your engineering work reduced risk, improved performance, or met requirements.
Mini example: weak vs stronger 1.4 evidence
Weak: “I calculated the flows and updated the statement of work and cost estimate based on the results.”
Here, the assessor does not know what theory you used, what equations you applied, or why an engineer was required.
Stronger: “For a chilled‑water plant upgrade, I applied the Darcy–Weisbach equation to size new distribution piping. I estimated friction factors using the Moody diagram, calculated head loss for several pipe diameters, and checked pump curves to confirm we could maintain the required flow and pressure at peak load. Based on these calculations, I specified a larger pipe size than originally proposed to reduce velocity and noise and documented the design rationale in the technical specification.”
This second version names the methods used, shows real calculations, and makes it clear why your engineering knowledge mattered.
Need more help with your CBA?
Inside the full CBA Blueprint course, you will find:
- 11 fully accepted submissions from past clients.
- Examples across civil, mechanical, electrical, petroleum, environmental, software, and chemical disciplines, so you can see what assessors have already approved.
- Over 200 individual competencies you can study for structure, depth, and level of detail.
If you want structured guidance and real examples of what assessors have already accepted, consider starting the course here: View CBA Blueprint course options.