C-09
Technical records and raw data management
What has to be recorded, how corrections are made, and what makes a record able to reconstruct a result years later.
TRAINING / C-09
The course
What has to be recorded, how corrections are made, and what makes a record able to reconstruct a result years later.
Who it is for
01 / 05Everyone who writes in a laboratory record — analysts, technicians, supervisors — and the quality staff who audit them.
Short, practical, and built around real records rather than clause numbers. Most of the day is spent looking at records that would and would not survive scrutiny.
What is covered
02 / 05The syllabus below is the standard shape of the course. It is adjusted to the matrices, methods and instruments you actually run, which is agreed before delivery rather than discovered on the day.
What a technical record is
The distinction between raw data, derived data and the report
Sufficiency
Recording enough that the result can be reproduced from the record alone
Amendments
Correcting an entry so the original stays legible, with who and when
Electronic records
Instrument data, spreadsheets, audit trails and access control
Data integrity
ALCOA principles applied to an ordinary testing laboratory
Retention
Retention periods, storage and controlled disposal
What you leave able to do
03 / 05Courses are written around what a delegate can do afterwards, not what was presented to them. These are the outcomes this one is built to produce.
- Judge whether a record contains enough to reconstruct the result.
- Amend a record correctly, and recognise an amendment that has destroyed the original.
- Identify where your electronic data is unprotected — usually the spreadsheet between instrument and report.
- Apply retention and disposal consistently rather than keeping everything indefinitely.
Why this course exists
04 / 05Almost every laboratory keeps records. Far fewer keep records that let someone else reconstruct a result without the analyst standing next to them, which is the actual requirement.
The weak point is nearly always the same: an uncontrolled spreadsheet sitting between the instrument output and the report, doing arithmetic nobody has checked and holding no audit trail.
How it is delivered
05 / 05Delivered over 1 day, at your site or at the laboratory, in English or Arabic. Sessions are built around real records, real data and real failures rather than slides of clause numbers, and the people delivering them spend the rest of the week doing the thing being taught.
Group size is agreed in advance — practical sessions are capped so that everyone works rather than watches. An attendance certificate is issued to each delegate on completion.
Ask about any subject not listed here. If it is not something we teach well, we will say so rather than build it for the sake of the booking.
At a glance
- Duration
- 1 day
- Delivered
- On site or at the laboratory
- Language
- English or Arabic
- Certificate
- Attendance certificate issued
CONTINUE
Where to next
Method validation and verification
The difference between validating a method and verifying one, and how to evidence either so it survives an assessment.
ReadMethod performance and result validity
Accuracy, precision, bias and recovery — what each one measures, and which of them your result actually depends on.
ReadAll courses
The full catalogue, grouped by subject.
ReadRequests are read at the bench.
Send the sample question or the instrument list. It is read by a bench professional, not routed through a ticket queue. Call +966 59 637 8052 or write to lab-mgr@qsinexus.com.