Scheme 'A' progress assessment judges competency evidence, not activity volume. Map every logbook entry to a training objective, write first-person actions with stated supervision levels, report gaps honestly with planned next steps, keep signatures current, and abstract confidential details — that is the record-keeping habit the assessment is built to examine.
What the Scheme 'A' progress assessment is designed to measure
A progress assessment checks whether you are meeting the HKIE training objectives for your discipline at the expected stage, using your recorded work and supervisor confirmation as evidence — not whether you logged a quantity of tasks.
Scheme 'A' is the Hong Kong Institution of Engineers' structured graduate training framework: a graduate employed by an approved organisation trains under published objectives, keeps records of that training, and has progress reviewed at defined points on the way to applying for corporate membership. The framework, current requirements, forms and review points are set by the HKIE, so confirm administrative specifics with the institution rather than relying on second-hand summaries.
The underlying difficulty is a language mismatch. Training objectives are written as competencies — applying engineering knowledge, exercising sound judgement in design, communicating with stakeholders, acting ethically and professionally. Daily work arrives as tasks: attend a meeting, check a drawing, run a test. Progress assessment sits between these two vocabularies, and your records must connect them explicitly, or a reviewer sees only a list of activities with nothing to judge progress against.
Training objectives versus competency evidence: two records that must agree
A training objective states what you must become able to do; competency evidence is documented work showing you doing it, at a stated level of independence, with an outcome someone else can verify. Keep both visible in every entry.
Compare two ways of recording the same week. 'Worked on drainage design' is an activity note: it names a task but no objective, no personal contribution, and no result. 'Applied stormwater sizing methods to prepare two catchment calculations, checked by my supervisor, feeding the Phase 2 drainage layout' is objective-linked: it names the knowledge applied, your action, the verification and the output. Only the second lets an assessor judge whether you are progressing toward the objective.
Apply this with a fixed entry structure: tag the objective or element the work serves; describe your own actions with first-person verbs; state the outcome or deliverable; note the level of supervision; and confirm your supervisor can vouch for it. Do this mapping monthly rather than at reporting time — reconstructing six months of work against objectives from memory produces generic, unverifiable claims that read like a job description instead of a record.
Worked scenario 1: rewriting a vague site logbook entry
Record the objective, your specific actions, the outcome and the supervision level. 'Assisted with inspection' fails on all four counts; a mapped entry shows what you personally did, what it demonstrated, and how it can be checked.
A civil trainee spends a morning on bored-pile inspections. Her logbook reads: 'Assisted the senior engineer with pile inspection.' At review this entry supports nothing: 'assisted' hides her actual contribution, no objective is referenced, there is no outcome, and months later neither she nor her supervisor could reconstruct what happened. The plausible mistake is treating the logbook as an attendance diary rather than a professional record of developing competence.
A stronger entry: 'Objective: construction supervision and quality control. Under supervision, carried out slump tests and cover measurements on three bored piles; recorded results on the inspection checklist; identified low cover at two locations and reported to the supervising engineer, who instructed remedial work.' Every clause maps to something an assessor can trace: the competence practised, the action taken, the finding and the follow-through. The same morning now evidences real, checkable progress.
Worked scenario 2: reporting a quarter dominated by drafting work
Report the period truthfully, including the gaps, and draw out the objectives routine work partly serves. Inflating drafting support into 'design experience' creates verification problems and conceals development needs your supervisor could otherwise address.
A mechanical trainee hoped for design exposure but spent a quarter updating HVAC drawings from engineers' sketches. Tempted to write 'assisted in the design of air-conditioning systems', he faced a choice. The inflated claim might survive a casual read, but if a reviewer probes which calculations he actually owned, or his supervisor signs against a different account, the report's credibility — and his — suffers at exactly the stage when scrutiny is expected.
The better report: 'Produced and coordinated ductwork layouts from engineers' mark-ups, applying company drawing and buildability standards; developed proficiency in coordination and clash resolution. Design calculation exposure remains a gap; I have agreed with my supervisor to shadow the next cooling-load calculation cycle.' This is honest about level, still extracts genuine competency growth from routine work, and converts the gap into a planned next step — which is precisely what progress reporting exists to enable.
Ethics and confidentiality inside your training records
Your logbook and reports are professional documents. Record truthfully, describe confidential projects generically, and keep required signatures current — the accuracy and integrity of the records is itself evidence toward professional conduct objectives.
Write entries you would be comfortable defending: no copy-and-paste months, no back-dated reconstruction, no claiming work you only observed. Where you observed or assisted, say so — supervised participation is a legitimate and expected stage of graduate training, and honest level-marking lets the assessment show a believable progression toward independence. Inflated records also put your supervisor in the position of certifying something untrue, which is a conduct problem, not just a formatting one.
Confidentiality is handled by abstraction, not omission. Instead of naming a client's commercially sensitive project parameters, describe the competency: 'prepared tender-stage cost comparisons for a private development, applying the company's estimating procedure; project details withheld for confidentiality, verified by my supervisor.' Professional conduct objectives are also evidenced through real events — declaring a conflict of interest, following QA procedures, raising a safety observation through the proper channel — so record these when they happen rather than inventing abstract essays about ethics.
Who does what: trainee, supervisor, mentor, employer and HKIE
You own the records and drive the training plan. Supervisors verify your day-to-day work; mentors advise on development and professionalism; employers provide structured exposure; the HKIE sets the framework and reviews your assessment submissions.
The supervisor–mentor distinction matters in practice. Your supervisor sees and can vouch for the work itself, so their signature belongs on entries and reports describing it. A mentor, often a senior engineer outside your direct reporting line, helps you read your progress strategically: which objectives are thin, what exposure to request next, how to handle ethical grey areas. Confusing the two roles leaves records unverified or development questions unasked.
Use the structure deliberately: agree with your supervisor when entries will be reviewed and signed; raise development gaps with your mentor; and route formal questions about requirements to your employer's training administrator or the HKIE. If responsibilities blur — a supervisor who signs without reading, a mentor who never meets you — escalate early within your company, because unsigned or unverified records are far harder to repair after the reporting period closes.
| Role | Primary contribution | A common confusion to avoid |
|---|---|---|
| Trainee | Maintains records, maps work to objectives, initiates reviews, drafts reports | You drive the training; it is not administered entirely by your employer |
| Immediate supervisor | Observes and verifies your actual work; signs off related records | Verifying work is not the same as career mentoring |
| Mentor | Advises on development, professionalism and progression decisions | The mentor need not verify every task you record |
| Employer / training company | Provides approved structured training and exposure across objectives | Providing exposure does not replace your own record-keeping |
| HKIE | Publishes the training framework and reviews progress toward corporate membership | The institution sets requirements; it does not write your daily log |
A rewrite exercise, self-check rubric and preparation sequence
Rewrite three recent logbook entries against the rubric below, then adopt a monthly cycle: plan against objectives, record weekly, map monthly, review quarterly with your supervisor, and draft each progress report well before it falls due.
Run the exercise on the last month of your own records. Expected observations: your earliest entries will lean on 'assisted', 'supported' and 'involved in'; objectives will be missing or generic; outcomes will often be absent because nothing was resolved. Score each rewritten entry against the five rubric points — a useful learning milestone is four of five on every entry across two consecutive practice months. That score reflects your record-keeping habit, not a prediction of any assessment outcome.
An adaptable sequence: in your first month, read your discipline's training objectives and draft a training plan with your supervisor; weekly, write short entries; monthly, map entries to objectives and flag gaps; quarterly, hold a review with your supervisor and mentor and update the plan. Before any submission, run readiness checks: you can state the evidence behind each objective, your supervisor can confirm entries without editing them, and every known gap has a documented action. For current forms, requirements and administrative details, refer to the HKIE at hkie.org.hk.
- Every entry names the training objective or element it serves
- Actions are first-person and specific, with your level of independence stated
- Each entry has an outcome, deliverable or finding someone could check
- Supervision and verification are recorded, and signatures are current
- Confidential information is abstracted, and any gaps are noted with a planned next step
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.