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.
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.