A sample record is useful only if someone can connect it to a real location. A spreadsheet may contain the correct identifier while leaving the freezer, rack, box, or position unclear. A box map may look complete while the sample has been checked out. Those are different information problems, and a useful inventory needs to make both visible.
This guide describes a recordkeeping method for research freezer inventories. It focuses on location naming, identifiers, movements, and reconciliation. It does not prescribe storage conditions, handling procedures, or scientific decisions. Use your laboratory’s approved procedures for those requirements.
The worked example uses fictional samples and locations. You can apply the method in a controlled spreadsheet, an existing laboratory system, or a focused inventory app. The aim is to make a retrieval question answerable: which record, which location, and what happened most recently?
Define the location hierarchy before entering samples
Start by listing the physical levels that matter in your laboratory. A hierarchy might be freezer, rack, box, and position. Another laboratory may use shelves, drawers, canisters, or another arrangement. Model the actual storage system rather than forcing it into a convenient but inaccurate diagram.
Give every level a stable identifier. For example, FR-02 might identify a freezer, RK-03 a rack within it, and BX-014 a box. A complete position could then be FR-02 / RK-03 / BX-014 / C07. The example format is a naming convention, not a standard you must adopt.
Decide whether a box identifier remains the same when the box moves. Keeping the container’s identity separate from its parent location can make movements easier to understand. If BX-014 moves to another rack, you can update its parent without pretending that it is a new box.
Write down the convention and check it with someone who retrieves material. A naming system that is easy to type but difficult to interpret at the storage location will create unnecessary questions.
Separate sample identity from storage position
A sample identifier answers which sample you mean. A location answers where it is recorded as being. Avoid treating the location as the sample’s permanent identity. Positions can change, containers can move, and a sample may have more than one related aliquot.
In the fictional example, SAMPLE-1042 is a parent record and SAMPLE-1042-A01 identifies one aliquot. Its location is C07 in BX-014. If that aliquot moves to D02, the identifier stays the same while the location record changes. This makes the history easier to follow.
Use your laboratory’s existing identifier rules where they are established. Do not create a competing numbering system merely because a new tool makes one available. If a legacy identifier must remain visible, store it as a reference rather than quietly replacing it.
Also distinguish identity from descriptive names. A project nickname or informal sample description may help people search, but it should not be the only way to distinguish two records that happen to have similar names.
Build a minimal, usable sample record
Begin with fields that support identification, retrieval, and the laboratory’s existing record requirements. Add specialized fields only when their purpose is clear. A long form can create the appearance of completeness while leaving the location information unreliable.
| Field | Purpose | Fictional example |
|---|---|---|
| Sample or aliquot ID | Stable record identity | SAMPLE-1042-A01 |
| Parent reference | Connect related records | SAMPLE-1042 |
| Project reference | Support authorized retrieval | PROJECT-17 |
| Container and position | Locate the item | BX-014 / C07 |
| Current state | Distinguish stored from checked out | Recorded in storage |
| Last movement | Explain the latest change | Returned by researcher A |
| Record owner | Assign questions and corrections | Project inventory coordinator |
Keep sensitive information in the systems and access boundaries your organization requires. An inventory may need a coded reference rather than identifying details. The example fields are about organization; they do not determine which information your laboratory is authorized to record.
Make the position map unambiguous
A box map should have a clear orientation. Someone looking at a screen needs to know how rows and columns correspond to the physical container. Record the orientation convention in the inventory instructions and use it consistently across maps and labels.
Mark occupied, empty, reserved, and uncertain positions distinctly if those states are part of your process. An empty-looking cell should not conceal a reservation. Similarly, a position under investigation should remain visibly uncertain until it has been reconciled.
Consider the difference between a position record and a visual highlight. A colored cell is helpful for scanning, but the underlying record should still identify the sample and the location. Color alone is difficult to interpret when a map is exported, printed, or viewed by someone with a different display.
Test the map using a fictional retrieval exercise. Ask another authorized user to identify a particular position from the record without coaching. Their questions can reveal an unclear orientation or naming rule before it affects actual work.
Record movements as events
Overwriting a location tells you the current answer but may erase the explanation. A movement log records what changed, when it changed, and who recorded it. Keep the old and new locations where your process needs that history.
A useful event might include the sample identifier, event type, timestamp, previous location, destination or checkout state, person, and a short reference. The reference can point to the relevant authorized activity without copying unnecessary detail into the inventory.
Differentiate the time an event occurred from the time it was entered when those are not the same. A delayed entry should not silently imply that the physical movement happened at the moment someone updated the software. Clear timestamps help later reconciliation.
Corrections also deserve a record. If a location was entered incorrectly, preserve an understandable correction rather than inventing a movement that never occurred. Your laboratory’s established documentation rules should determine the exact correction method.
A worked movement example
Suppose the fictional aliquot SAMPLE-1042-A01 is recorded at FR-02 / RK-03 / BX-014 / C07. Researcher A checks it out for an authorized activity. The record changes state, while the earlier storage location remains part of its history.
Later, the aliquot is returned to D02 in the same box. The return event records D02 as the new position. The previous C07 position should no longer appear occupied by that aliquot. If your process reserves the previous position during checkout, the reservation also needs an explicit resolution.
| Event | Recorded location or state | What the history explains |
|---|---|---|
| Initial placement | BX-014 / C07 | Starting recorded position |
| Checkout | Checked out | Why the item is not shown as stored |
| Return | BX-014 / D02 | New position and recorded return |
This example concerns record transitions only. The inventory should reflect the handling and authorization process your laboratory already requires. A completed software event is not evidence that every scientific or procedural requirement has been met.
Handle discrepancies without guessing
When the physical position and the record disagree, create a discrepancy entry. Record what was observed, which records were checked, who is responsible for investigating, and the next review point. Avoid filling an uncertain field with the most plausible answer merely to make the map look complete.
Separate a confirmed correction from a working hypothesis. “Record may belong to the neighboring position” is different from “Position confirmed and corrected.” Those statements should not share the same completed status.
Use a small reconciliation queue so unresolved discrepancies remain visible. The queue can include the sample reference, the location in question, the observation, and the assigned owner. Close an entry only when the laboratory’s required checks have been completed.
A periodic review can then focus on unresolved items rather than treating the entire inventory as equally uncertain. This makes it easier to explain what is known and what still needs attention.
Design a review routine around changes
Review the records most likely to have changed: recent checkouts, returns, container moves, newly created records, and unresolved discrepancies. The appropriate cadence depends on the laboratory’s workflow. A busy shared inventory may need a different review rhythm from a small, infrequently accessed collection.
At each review, look for specific problems. Are there checked-out records without an expected next action? Are two records assigned to the same exclusive position? Does a moved box still appear under its previous rack? Are identifiers duplicated or incomplete?
Document what the review covered. “Inventory checked” is vague. “Recent movements and the open discrepancy queue reviewed” describes the actual boundary. Avoid presenting a limited review as a comprehensive physical reconciliation.
When the same problem recurs, improve the workflow rather than adding another reminder. An unclear position convention, an awkward form, or a missing responsibility can produce repeated errors that extra notifications will not resolve.
Check export and recovery before you need them
An inventory backup is useful only if the appropriate person can restore and interpret it. Follow your organization’s storage and access requirements, and test recovery in an approved setting. Do not assume that having an exported file proves that the recovery process works.
Check whether an export contains only current positions or also the movement history and relationships you need. Record the export date and the version of the tool or format where relevant. A current map and a historical archive may serve different purposes.
Keep the means of accessing a protected archive under the organization’s approved process. Avoid storing an archive password beside the archive simply because it is convenient. Decide who is responsible for maintaining access when a project or team member changes.
A recovery exercise should answer whether the records can be located, opened, and understood. Capture any missing instructions and correct them while the normal system is still available.
Migrate existing records with a reconciliation boundary
If you already have an inventory, keep an untouched source copy before reorganizing it. Identify the fields that will be carried forward, the naming conventions that will change, and the records that cannot yet be mapped confidently. A successful import is not automatically a verified physical inventory.
For example, an old sheet might identify a box as “blue box, second shelf.” Preserve that description while the responsible person confirms its relationship to the new hierarchy. Do not silently translate it into BX-014 merely because the color appears to match. Keep a mapping table that distinguishes confirmed correspondences from unresolved ones.
Choose a clear cutover point for record updates. If some people continue editing the old sheet while others update the new system, the two versions can diverge immediately. Explain where new movements should be recorded and how any changes made during migration will be reconciled.
Finish by documenting the boundary of the work. You may have migrated all source rows while confirming only selected locations. Those are different achievements. Record them separately so later users understand the inventory’s state without assuming that a data transfer established more than it actually did.
Choose a tool that fits research inventory work
A controlled spreadsheet may be sufficient when the hierarchy and movement history are simple and the organization permits it. A laboratory’s established information system may already provide the required controls. Evaluate a focused app against the actual workflow rather than treating visual convenience as proof of suitability.
FreezerGrid is specifically a research inventory app. Its official listing describes visual freezer, rack, and box maps; sample and aliquot positions; barcode lookup; checkout and return history; and encrypted archive options. It is not presented as a validated GLP/GxP laboratory information management system.
Compare the current features with your laboratory’s requirements before adopting it. You can view FreezerGrid: Lab Inventory on the App Store for supported devices, current availability, and purchase information. The right choice depends on both the records you need and the controls your organization requires.
Start with one well-defined inventory area
Choose a bounded part of the inventory for the first organizational review. Agree on the location hierarchy, confirm the identifier convention, and define how movements and discrepancies will be recorded. Make the instructions readable by someone other than the person who designed them.
Then test a fictional placement, checkout, return, correction, and retrieval. If the record remains understandable through those transitions, you have a stronger starting point for an approved rollout. Keep improving the method from observed questions rather than assuming a fuller form is always a better inventory.
Product reference: FreezerGrid’s official App Store listing. Identifiers, locations, and movement events in this guide are fictional illustrations of record organization.