Skip to main content

Laboratory design for engineering accreditation: outcome mapping, maintenance records and the week before the visit

What an accreditation panel actually examines in a teaching laboratory, how to map experiments to course and programme outcomes, the records a department must be able to produce on request, and a twelve week preparation sequence.

The panel spends about twenty minutes in each laboratory. In that time they will pick up a lab manual, ask a student what they did last week, look at the equipment register, open a cupboard, and ask the technician when a particular instrument was last calibrated. Almost none of that is about how new the equipment is. It is about whether the laboratory can produce evidence that learning happens in it, repeatably, for every student, and that somebody is responsible for keeping it working.

Departments in Bangladesh preparing for accreditation under an outcome-based framework tend to over-invest in the self-assessment report and under-invest in the laboratory paper trail the report is supposed to describe. Work from the current accreditation manual you are assessed against for exact clause numbering and terminology, because those change. What follows is the shape of what is expected and how to build it into a laboratory rather than bolt it on.

Accreditation reads a laboratory as evidence, not as inventory

An inventory list answers the question what do you own. Accreditation asks a different question: can every student on this programme demonstrate the attributes the programme claims, and where is the proof. A laboratory contributes to that in four ways, and it is worth being explicit about which experiment does which job.

The uncomfortable implication is that a laboratory full of highly automated units where students press a button and export a spreadsheet evidences the third attribute and almost none of the second. Keep at least one open-ended investigative experiment in each core course, even if it is the least impressive rig in the room.

Mapping experiments to outcomes

The mapping table is the single most useful document a laboratory can hold, because it answers most panel questions before they are asked. Build one per laboratory course and keep it at the front of the manual.

ExperimentCourse outcome addressedGraduate attributeHow it is assessedEvidence held
Pipe friction and minor lossesDetermine friction factor experimentally and compare with published correlationsEngineering knowledge; investigationMarked report with error analysisSample scripts at high, middle and low grade bands
Heat exchanger performanceEvaluate overall heat transfer coefficient and effectiveness for parallel and counter flowEngineering knowledge; modern tool usageLogged data set plus reportRaw logged files and marked reports
PID tuning on a level loopTune a controller for a specified performance criterion and justify the settingsInvestigation; problem analysisObserved practical and vivaViva mark sheet with examiner comments
Transformer open and short circuit testsDerive equivalent circuit parameters from measurementEngineering knowledgeMarked worksheetSample worksheets across grade bands
Open-ended flow measurement taskSelect and justify a measurement method for a stated situationDesign of experiments; communicationGroup report and presentationPresentation rubric and recording or attendance record

Two disciplines make this table survive contact with reality. First, no experiment appears in the table unless it actually ran that semester for that cohort; an aspirational mapping is worse than an honest gap. Second, every row must name the physical evidence and where it is kept, because the panel will ask for one row at random and expect it produced within a few minutes.

The records a laboratory must be able to produce

Most departments hold some of this. Very few hold all of it in one place with a person responsible. Assemble it into a single laboratory file, physical and digital, per laboratory.

The arithmetic a panel does in their head

Standing in the room, an experienced assessor performs one calculation almost automatically: number of students in the cohort, divided by number of working stations, gives group size. If that number is eight or ten, they will ask how every student in the group personally performed the experiment, and there is rarely a good answer.

Have the answer ready and make it true. Either the stations support groups of four or five, or the section is split across additional sessions, or specific experiments are duplicated. Whichever it is, show it in the timetable and in the group allocation records. Where a rig is genuinely scarce, a documented rotation with individually assessed viva questions is a defensible arrangement; an undocumented crowd around one bench is not.

The same reasoning applies to equipment that is present but not working. A rig that has been out of service for two semesters counts against you more than an empty space, because it shows in the register and there is no maintenance action against it. Either repair it, or record the decision to retire it and remove it from the room.

Maintenance records are where departments lose marks

Almost every department fixes its equipment. Very few write it down. Since the panel can only assess what is recorded, the practical fix is to make recording the path of least resistance for the technician.

  1. One logbook per laboratory, kept in the laboratory, not in an office. Paper is fine. Digital is better only if the technician will actually use it.
  2. A single line per event: date, equipment and serial number, what happened, what was done, whether a part was used, and whether the item is back in service.
  3. A short planned maintenance sheet per rig, derived from the supplier manual: what to check monthly, what to check each semester, what to check annually. Signed and dated when done.
  4. Calibration due dates on a wall chart so that an overdue instrument is visible to everyone rather than buried in a file.
  5. A spares holding list with reorder points for the items with long import lead times, reviewed once a year against the breakdown log.
  6. An annual one-page summary of downtime by equipment. This is often the strongest evidence a department can put in front of a panel, and it also wins the budget argument for a replacement.

A twelve week preparation sequence

Preparation that begins two weeks before the visit produces a clean room and a thin file. Twelve weeks is enough to produce evidence rather than an appearance.

  1. Weeks one and two. Physical audit of every laboratory against the equipment register. Reconcile serial numbers. Identify items out of service and decide repair or retirement in writing.
  2. Weeks three and four. Review and reissue every lab manual with a version number and date. Check that each manual's experiment list matches what was actually taught last semester.
  3. Weeks five and six. Build or update the outcome mapping table for each laboratory course, and collect the named evidence for every row.
  4. Weeks seven and eight. Assemble marked student work across grade bands, check that feedback is present, and fill gaps by re-marking a sample with comments where feedback was thin.
  5. Week nine. Safety review. Risk assessments current, induction registers complete, first aid and eyewash serviceable and recently tested, chemical register reconciled, safety data sheets present in the room.
  6. Week ten. Calibration catch-up and instrument checks. Anything overdue either done or scheduled with a documented reason.
  7. Week eleven. Brief the technicians and the students. Technicians should know where every record is; students should be able to say what they measured, why, and what the result meant. Rehearsing answers is unnecessary and obvious; making sure students have genuinely done the work is the point.
  8. Week twelve. Walk each laboratory as an outsider. Sit at a bench. Read the notices. Open the cupboard nobody opens.

Things that look bad even when they are not

Nobody has ever failed an accreditation visit because a rig was five years old. Departments fail because nobody could show that the rig was used, maintained and assessed.: Vvon Technologies

Back to all Insights