A bid asks for evidence, and nobody has it to hand
A framework bid asks for evidence that your engineers keep their professional development up to date. A graduate asks their mentor whether they are ready to go for their professional review, and the mentor has no clear idea what experience they have covered. An insurer's questionnaire asks about staff competence. Each time, someone emails the team asking them to send their CPD records, and gets a mix of spreadsheets, Word files, institution portal screenshots and apologies.
The engineers are learning all the time: lunchtime talks, courses, site experience, self-study on a new Eurocode. It is the record that is missing.
Why development records fall apart
- Each engineer records CPD their own way, or only in their institution's portal at renewal time.
- Graduate experience is recorded in a development log that the mentor sees occasionally.
- Internal training, such as technical talks, is not registered against attendees.
- Project experience that counts towards chartership is not linked to real projects.
- The practice has no overview, only individual files.
Institutions such as ICE, IStructE and CIBSE each set their own requirements and have their own portals. The practice still needs its own view across staff, and that view is what nobody has built.
Mentoring is where the gap hurts most. A mentor may look after two or three graduates alongside their own design work. Without a shared record, each review meeting starts with the graduate trying to recall what they did six months ago, and the mentor trying to remember what they advised last time.
What the gaps cost
| Moment | What happens without a record |
|---|---|
| Framework or bid question | Scramble to collect evidence, weaker answer |
| Graduate asks about readiness | Mentor guesses, graduate loses confidence |
| Annual review | Development conversation starts from memory |
| Engineer leaves | Their development history leaves with them |
| Quality audit | Competence evidence assembled by hand |
Graduates notice when the practice cannot support their chartership well. It is one of the things they weigh when a competitor offers them a job.
How we build a development record
- Each engineer gets a simple log for CPD entries: what, when, how long, and what they took from it. Logging from a phone takes a minute.
- Internal technical talks and courses are set up once, and attendance registers create entries automatically.
- Graduates log project experience against the attributes their institution uses, with a link to the project and their role on it.
- Mentors see their mentees' logs, add comments and record review meetings.
- A practice-wide view shows CPD activity by person, graduate progress by attribute, and who has gone quiet.
- Exports are produced in formats that help engineers copy entries into their institution's portal, where the institution allows.
- Competence summaries for bids and audits are generated from the same record.
We do not tell anyone whether they meet their institution's requirements. The record shows what is there. The engineer, their mentor and the institution decide what it means.
We usually set up the attribute framework for each institution your engineers are working towards with a senior engineer who mentors, so the categories and language match what reviewers expect. Existing development logs can be imported, so nobody loses the record they already have.
What changes for engineers and mentors
Logging becomes a small regular habit rather than a panic before renewal. Mentors go into review meetings with the graduate's experience laid out, so the conversation is about gaps and next steps rather than recollection.
When a bid asks about competence and development, the answer is a report rather than an email campaign.
Could this be your practice?
- CPD records are collected by email when someone asks for them.
- Mentors cannot easily see a graduate's experience to date.
- Internal technical talks leave no record of who attended.
- Bids and audits ask about competence and the answer is assembled by hand.
- Graduates ask how the practice supports chartership and the answer is vague.