A solution log that survives a busy week

Every lab has a log that worked for two weeks and then stopped. The reason is almost never that people stopped caring. It is that the log lived somewhere other than the bench, so writing in it became a separate task, and a separate task loses to a busy afternoon.

One line per opening, not one page per week

A page-per-week template invites people to batch their entries at the end of the day, which is exactly when the details are gone. A single line per opening, written at the moment of the opening, survives because it is small. The next person who opens the vial adds their own line, and the history of the container builds itself.

Five fields are enough

• Date and time of the opening
• The lot number from the vial or the diluent bottle
• The volume made or drawn off in this session
• The operator's initials
• The storage position the container went back to

More fields are fine if they are used. The problem with long templates is that half the boxes end up blank, and a blank box is ambiguous: it can mean the field did not apply or that the person forgot. Five fields that are always filled beat fifteen that sometimes are.

Where logs break, and the fix

• A shared sheet with a single pen: use one sheet per container instead
• Entries written from memory at the end of the day: move the sheet to the bench
• No entry when a container is discarded: make discarding an event with a line
• A log that sits in a binder away from the fridge: keep the sheet with the tray

The closing entry

When a series ends, the last line should say so: the volume remaining, what happened to it, and who made that decision. This entry is what turns a list of openings into a record with a beginning and an end. Without it, the next person finds a container with no explanation and a sheet that stops mid-story.

What the log is for

The log is not paperwork for its own sake. It is the document that lets someone reproduce your preparation weeks later, and the first thing a reviewer asks for when a result looks unusual. A log that takes thirty seconds per session is the one that is still there when it matters.

Keeping the log honest

Everyone writes an entry late at some point. The difference between a log that survives and one that quietly rots is whether a late entry is marked as late. Write the time of writing next to the time of the step, and the sheet stays trustworthy even when the week was bad.

Initials should mean one thing: this person performed the step. If initials are also used to mean approved or seen, the log stops answering the only question anyone asks it later. Keep approval and performance in separate columns, or in separate documents.

A five-minute weekly check

• Reconcile the volumes in the log against the containers in the tray
• Look for a container with no entry or an entry with no container
• Confirm that each stored item is in the position its entry claims
• Check that the last line of each finished series actually says finished

The check is short and it catches the errors that a month of entries would otherwise hide. Do it on a fixed day, because a check that happens when someone remembers is a check that happens after the first surprise.

When the sheet is already inconsistent

It happens: a gap in the middle, two entries for one opening, or a volume that cannot be right. The repair is not to rewrite history. Add a note at the next free line saying which earlier entry looks wrong and why, sign it, and continue from the current state of the container. A log with a documented correction is worth more than a tidy one that was quietly edited.

If your lot record and your own log disagree, trust the vial and re-check the log. Write down that you did, because the re-check is part of the record too.