A technician checks a sample at 09:10, enters the result at 09:25, and receives a review at 10:00. If the record displays only “completed: 10:00”, a colleague cannot tell when the measurement happened.

That distinction matters when a later investigation asks which procedure was in force at the time of measurement, or whether the result was reviewed before a decision. Giving each event its own label makes the sequence easier to reconstruct.

Give each time a meaning

Four events may need separate timestamps:

  • Activity: when the work or observation occurred.
  • Entry: when the information was recorded.
  • Review: when a person evaluated it.
  • Decision: when an approval or restriction took effect.

They can coincide. When they differ, the record should show the difference. Capture observations when the work happens where practicable, and identify delayed entries according to the local procedure. A system timestamp establishes a system event, not independently the time of a physical task.

Connect the result to its sample and method

The result also needs a connection to the sample, instrument, and responsible person. Keep the procedure revision used for the work available after a new revision is issued.

The W3C provenance model describes relationships among things, activities, and responsible people or systems. That is a helpful way to think about a laboratory result: which sample, which measurement, which person, and which equipment? GB cosmetics guidance also includes current documentation across manufacturing and QC in its GMP explanation.

Correct an entry without erasing the first one

Suppose an analyst entered the wrong instrument identifier. Retain the original entry and show the corrected identity, person making the change, time, reason, and supporting basis.

A reason such as “Selected PH-02 in error; original instrument output identifies PH-03” explains both the error and the basis for the correction. If that change alters which equipment history applies, review whether it affects an earlier conclusion.

Keep completed work distinct from permission to proceed

A cleaning task can be performed while residue remains under investigation. Maintenance can finish while a post-service check is outstanding. Define statuses so users know what they may do next and who can change the state.

If one person performs and reviews an activity under the local workflow, record both actions honestly. An automatic update should not appear to be an independent second-person review.

Try reconstructing a test

Choose one completed test and retrieve its sample, instrument, relevant checks, analyst, method revision, corrections, and review. Test the same retrieval from an export if software is involved. An “audit trail” label does not establish what the system records or who can alter it.

A missing instrument reference, procedure revision, or review entry shows where the record or handover needs attention before the next test.

Sources: GB cosmetics guidance; W3C provenance model primer.