Strong evidence does not need to be dramatic. It needs to be specific enough for a reviewer to understand the context, your responsibility, the engineering reasoning and the resulting outcome.
Situation
What was the problem or constraint?
Responsibility
What was yours to decide or recommend?
Action
What did you investigate or do?
Decision
Why this option, and why not another?
Result
What changed, and how do you know?
Learning
What will you carry into later work?
A writing aid for reflection, not an official assessment model. Use your institution’s current guidance when mapping evidence.
Keep the project context short
State only what the reviewer needs to understand why the issue mattered: system, scope, constraint and risk. Do not spend most of the paragraph describing the project.
Make your responsibility visible
Explain the boundary of your role. What was yours to investigate, coordinate, decide, recommend, sign off, manage or escalate?
Show the reasoning
Evidence becomes stronger when you show the information considered, options compared and engineering judgement applied. A statement that you “ensured compliance” is weaker than a concise account of how you checked a requirement and acted on the result.
Finish with a real outcome
Explain what changed technically, operationally, commercially or in risk terms. Where useful, state what you learned and how that influenced later work.
From a general statement to an explainable decision
Illustrative example, not a client case
Too broad: “We coordinated the works and resolved the access problem.”
More specific: “I compared two equipment layouts against the maintenance-access requirements and the available space. I found that the proposed layout restricted access to a service point. I recorded the constraint, discussed an alternative with the designer and recommended a revised arrangement. After approval, I checked the updated drawing against the agreed access requirement.”
The second version shows the comparison, the reason for the recommendation and the boundary of approval. A final application would still need the actual technical facts and a verified outcome from that person’s work. Do not borrow the example as your own.
Try it with your own work
These notes stay in this open page. They are not sent or saved by Massar Prime. Print or save a PDF before leaving; use non-confidential descriptions.