A company assessment for a graduate training scheme examines the competency evidence behind your training record, and the exact format is set by your employer's process and the issuer, so confirm it early. The productive preparation is evidence-first regardless of format: audit your record, rewrite thin activity entries into first-person evidence statements naming the standard you worked to, the decision you made, and the checked outcome, then practise presenting those decisions in the format you will actually face. This article teaches the distinction between an activity report and competency evidence, walks through three worked scenarios with mistakes and better decisions, and gives a rewrite exercise with a self-check rubric plus an adaptable preparation sequence.
Competency evidence versus an activity report: the distinction that shapes every answer
An activity report says what happened on a project. Competency evidence shows that you, personally, applied engineering judgement against a recognised standard and produced a verified result. The second form is what can be examined and credited in any assessment format.
Compare two descriptions of the same month of work. An activity report reads: 'Attended site coordination meetings, assisted with drawings, visited the site twice.' A competency evidence statement reads: 'I coordinated the drainage layout with the structural team, resolved a clash against the agreed invert levels, and confirmed the revision through the drawing approval process.' The second names your role, a criterion, a decision, and a closure step. That structure lets an assessor test your understanding at any depth.
This distinction matters because follow-up questions, whether posed in a written reviewer's comments or in discussion, attach naturally to decision points: why that option, what standard applied, what you checked, what you would change. An entry with no decision point gives an assessor nothing to probe and you nothing to defend. When auditing your record, mark each entry as report or evidence, then convert reports by adding the missing role, criterion, decision, or outcome. The conversion is the same work regardless of how the assessment is delivered.
Structuring a work example so your own role and reasoning stay visible
Use a decision-first structure: brief situation, your specific task, the criteria and options you considered, the action you took, and the verified result. Write in the first person and name the standard or requirement behind every judgement.
Worked scenario 1 (a labelled practice example): a graduate helped reroute an external drainage run after a clash with a new foundation. Weak version: 'The team decided to reroute the pipe and it was installed successfully.' Problems: the team hides the individual, 'successfully' is unverified, and no criterion appears. An assessor asking 'what was your contribution?' has no material to work with, and the answer reads like borrowed experience.
Better version: 'I identified the clash during coordination, checked the specified invert levels and gradient against the available depth, compared rerouting the pipe with adjusting the foundation position, and proposed rerouting because it avoided redesign of the structure. I issued the proposal through the checker, and the as-built survey later confirmed the gradient.' This version is examinable at any depth: criteria, options, decision logic, and verification each invite a follow-up you can answer from your own work. Keep the structure stable whether you will write it or speak it; if discussion is confirmed as part of your assessment, rehearse it aloud as well.
- Role: use 'I' for your actions, 'we' only for genuinely shared ones.
- Criterion: name the specification, code, procedure, or instruction you worked to.
- Options: show at least one alternative you considered and why you rejected it.
- Verification: close with how the outcome was checked, not assumed.
Handling safety and risk questions in paper scenarios: hazard, risk, and the hierarchy of controls
For scenario-based safety questions, separate hazard (the potential source of harm) from risk (likelihood and severity combined), then rank controls using the hierarchy of controls before reaching for personal protective equipment.
Worked scenario 2 (a simplified classroom example, not real-world site guidance): you are asked how you would manage digging near live underground services. Weak answer: 'Wear hi-vis, get a permit, and be careful.' This jumps to the bottom of the hierarchy and treats the hazard as unavoidable. It also skips the risk rating that justifies any control. When pressed on why those controls suffice, the weak answer collapses because no reasoning sits behind it.
Better answer: identify the hazard (striking a live cable), rate the risk with a simple severity-times-likelihood matrix using your project's own scheme, then apply the hierarchy: eliminate by confirming the dig is necessary, substitute with vacuum or hand excavation where the service is close, engineer with service locators and exclusion barriers, then add permits, briefings, and supervision as administrative controls, with PPE last. State that site-specific method statements and competent persons govern actual execution. Why it matters: the hierarchy shows structured thinking, and flagging the limits of a paper example shows professional maturity rather than overconfidence.
Demonstrating quality assurance thinking: hold points, non-conformances, and documentation discipline
Quality questions test whether you know the process, not just the product. Learn how inspection and test plans, hold and witness points, non-conformance reports, corrective and preventive actions, and change control connect into one closed loop.
Worked scenario 3 (a labelled practice example): during inspection, concrete cover to reinforcement on a small pour is measured below specification. Weak response: 'The site team added spacers and re-poured, so it was fine.' This skips the non-conformance report, offers no assessment of structural effect, and quietly bypasses change control. It signals that documentation is optional, which contradicts the professional conduct and quality assurance expectations of any graduate framework.
Better response: raise a non-conformance report, record the measured values, have the responsible engineer assess the effect against the specification, agree a disposition (rework, repair, or accept with justification), verify completion, and ask what preventive action stops recurrence, such as a spacer check added to the inspection and test plan before the next pour. Why it matters: this single example demonstrates integrity, process knowledge, verification, and continuous improvement together, which is more efficient than describing four separate routine tasks.
- Hold point: work must not proceed until inspection is signed off.
- Corrective action fixes the instance; preventive action fixes the cause.
- Change control: even a 'small' fix follows approval, not replaces it.
Presenting your evidence in writing or in discussion: depth control and admitting uncertainty
Answer at three levels: headline decision, supporting criteria, then detail on request. Whether you write or speak, never pad; when you do not know something, say so and name what you would check and who you would consult.
Structured answers are a trainable skill in either medium. Lead with the decision ('I rerouted the pipe'), then the criteria ('invert levels and available depth governed'), then offer detail ('the gradient check is available on request'). In a written report this means short first-person paragraphs with the decision up front instead of a chronological diary. In discussion, it means letting the assessor choose the depth. If your assessment includes discussion, practise with a colleague who interrupts with 'why?' at random points; your example structure from the earlier sections keeps the answer coherent under interruption.
For stakeholder questions, distinguish the modes of engagement precisely: informing someone, consulting them before a decision, and obtaining their formal approval are different obligations with different records. A strong answer names who needed what, in which mode, and how it was documented. If asked about something outside your experience, an answer such as 'I have not done that yet; I would raise it with my supervisor and check the project procedure first' demonstrates judgement, which is exactly the competency a graduate framework exists to develop.
Mapping your logbook across the development areas and closing the gaps
Audit your record against each development area, rate the evidence in each as strong, thin, or missing, then plan coming months of training to generate missing evidence deliberately rather than hoping routine work fills the gaps.
For a re-assessment, this mapping is even more pointed: identify exactly what was assessed as not yet demonstrated, rebuild those specific entries with the decision-first structure, and be ready to explain what you have done differently since. Re-assessment preparation is gap repair, not a full rewrite, so precision about the gap saves weeks of unfocused effort.
Use the table below as an audit checklist. For every project you have touched, ask which areas it evidences and where the entries are thin. If a whole area, such as stakeholder engagement, has no first-person example, propose a small task with your supervisor that generates one, such as preparing and delivering a short progress briefing, then document it properly afterwards.
| Development area | Thin evidence looks like | Strong evidence looks like |
|---|---|---|
| Core engineering principles | 'Did calculations as instructed' | 'Checked the design against the governing criteria and queried an assumption' |
| Professional conduct and compliance | 'Followed site rules' | 'Identified a documentation gap against the procedure and raised it' |
| Health, safety, and risk | 'Attended toolbox talks' | 'Produced a risk assessment for a task and reviewed it after the work' |
| Project delivery and quality | 'Helped on site' | 'Closed a non-conformance through the reported process' |
| Technical communication | 'Sent emails' | 'Wrote a technical note that the reviewer accepted without major changes' |
| Graduate development framework | 'Kept a log' | 'Mapped log entries to competencies with supervisor sign-off' |
A preparation sequence, a rewrite exercise, and readiness checks you can score
Prepare in four passes over several weeks: audit, rewrite, rehearse, and simulate. Each pass has an observable output, so you can tell when a pass is complete instead of vaguely rereading notes.
Exercise: choose three logbook entries you consider weakest and rewrite each into a decision-first evidence statement. Expected observations when done well: every rewrite contains a first-person role, a named criterion, one considered alternative, and a verified outcome, and each fits in roughly five spoken sentences. If you cannot name a criterion or an outcome, that gap is your real preparation task, not more memorising.
Self-check rubric (learning milestones, not pass predictions): score each rewritten entry out of five, one point each for role, criterion, options, decision, and verification. Six or more points total across the weakest three entries signals your evidence base is ready for rehearsal; below that, return to the audit. Adaptable sequence: week one, audit and map all entries against the development areas; week two, rewrite the ten entries most likely to be discussed, matched to the format your employer confirms; week three, rehearse each aloud with a colleague asking 'why?' follow-ups if the assessment is discussion-based, or write full-page versions under time pressure if it is report-based; week four, run one full simulation in the confirmed format and repair whatever faltered.
- Readiness check 1: every core project you cite survives the five-point rubric.
- Readiness check 2: you can state your development objective for the next training period in one sentence.
- Readiness check 3: you have one rehearsed answer for 'tell me something you did not handle well and what changed'.
- Readiness check 4: you have confirmed the assessment format and adjusted your rehearsal mode to match it.
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.