Aurum
Download

Engineering Experience Logbook

A running engineering experience record that registration assessors will accept: entries written as you go, mapped to competences, signed off by verifiers, with gaps found early and closed on purpose.

Free · Mac (Apple silicon) and Windows · v1.0.0 · Other platforms

Then open the Marketplace in the app, search for Engineering Experience Logbook, and click Install. It goes into your own files, and works offline from then on.

What it installs.

1

Pillar

1

Area

50

Projects

200

Starter tasks

🏅 Tech & Engineering Certifications

Engineering Experience Logbook

Keeping a running record of engineering work for registration: projects, responsibilities, competences shown, supervisors who can verify them and gaps still to close.

  1. Choosing the registrations your logbook must serve
  2. Current experience rules check for each target body
  3. Deciding where the logbook lives
  4. Logbook entry template with the fields assessors ask for
  5. Employment and role history master list
  6. Reconstructing past experience from old records
  7. Verifier and referee contact register
  8. Baseline gap map against the competence framework
  9. Confidentiality and employer permission check
  10. Backup and version history for the logbook
  11. Weekly ten-minute work capture
  12. Monthly logbook entry write-up
  13. Quarterly supervisor sign-off
  14. Quarterly competence gap review
  15. Evidence file linked to each entry
  16. Experience duration tally by category
  17. Mentor conversations on the logbook
  18. Annual logbook audit and year summary
  19. Project close-out entry routine
  20. Responsibility level tracking across entries
  21. Writing entries about your own contribution
  22. Describing engineering judgement and decisions
  23. Quantifying scope, scale and outcome in entries
  24. Mapping one entry to several competences honestly
  25. Recording health, safety and risk responsibility
  26. Recording ethics, sustainability and professional conduct
  27. Recording communication, leadership and teamwork
  28. Plain-language summaries for assessors outside your field
  29. Asking for work that closes a competence gap
  30. Rewriting weak entries into strong ones
  31. Balancing design, delivery and operations experience
  32. Consolidating duplicate and overlapping entries
  33. Plan for a verifier who can no longer be reached
  34. Deciding when the record is ready to submit
  35. Annual appraisal prepared from the logbook
  36. End-of-placement sign-off for students
  37. Graduate scheme rotation reviews
  38. Recording a shutdown, commissioning or major site event
  39. Pre-submission read-through with a registered engineer
  40. Student logbook from coursework and design projects
  41. Weekly logging through an internship or co-op term
  42. Changing employer without losing the record
  43. Career break and part-time work in the record
  44. Experience gained abroad or across borders
  45. Verification plan for consulting and self-employed work
  46. Research and postgraduate work recorded as experience
  47. One logbook serving two registration bodies
  48. Logbook export pack for an application
  49. Verifying graduates' logbook entries as a supervisor
  50. Running a logbook programme for a graduate cohort

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

Choosing the registrations your logbook must serve

A record kept for a US state PE licence looks different from one kept for UK chartership, a Trinidad and Tobago registration or a Canadian competency assessment, and most engineers end up needing more than one over a career. Deciding now which two or three bodies you are writing for lets every entry carry the details each will ask for, instead of rewriting years of notes later.

First tasks

  • List every licence or registration you might apply for in the next ten years
  • Name the body that grants each one and the place it covers
  • Choose the primary body whose framework will shape the logbook
  • Write the choice and your reasoning on the logbook's first page

Current experience rules check for each target body

Bodies change how much experience they want, whether academic years count, what supervision means and how verification is done, and advice from a colleague who registered ten years ago may be out of date. One sitting with each body's official guidance gives you the exact rules your logbook has to prove.

First tasks

  • Download the experience guidance from your primary body's website today
  • Note the minimum years, supervision rules and any study credit allowed
  • Copy the body's competence or experience categories into the logbook
  • Highlight who is allowed to verify experience under each body's rules

Deciding where the logbook lives

Some institutions provide an online experience recording system, some engineers keep a spreadsheet, others a long document, and a few still use a paper book their employer issued. The right home is the one you will open every week, that survives a job change and that can be exported in the shape your body wants.

First tasks

  • Check whether your institution offers an online experience recording tool
  • Compare it against a spreadsheet and a document for export and ownership
  • Create the logbook in the chosen home and fill in the first page
  • Pin a shortcut to the logbook where you start each working week

Make it yours.

Install Engineering Experience Logbook, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.0 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.