Identity
Use sample ID, external reference, and sample type. Do not combine these into one label because users need different lookup and grouping paths.
Start with a sortable XLSX register, then open the Jodoo app to see how movements, tasks, exceptions, reviews, and history become connected records.
Opens the populated Jodoo example after sign-in. Start with the Free plan for up to five users; no credit card required.
The workbook shows current state in one row. Use event and task records in the App when you need durable history, simultaneous work, reminders, permissions, or review.
Use the workbook to track the current sample state with filterable columns and controlled choices for sample type, lifecycle status, exception state, and final disposition.
The spreadsheet is designed for a focused tracker: one row per sample, one variable per column, typed dates, explicit statuses, and a notes field reserved for context that does not deserve another column.
Use sample ID, external reference, and sample type. Do not combine these into one label because users need different lookup and grouping paths.
Keep the received date and time as a typed value. The receiving log can hold the wider intake details when the tracker only needs the current view.
Record the latest known location and person responsible. Update both when a handoff occurs.
Choose an explicit stage such as received, held, assigned, in progress, awaiting review, released, retained, or disposed.
Name the active work, owner, immediate next action, and deadline. Use a separate work register or App when one sample can have several simultaneous tasks.
Show whether an exception is open and the final release, retain, return, or disposal decision when one exists.
A status list is only useful when users apply it consistently. Document the trigger, owner, required information, and next step for each stage instead of adding more labels whenever a new situation appears.
Received means the record exists; held means a condition or information problem prevents normal progression and has a visible owner or action.
Assigned means work and ownership are set; in progress means the activity has started. Keep the task and due time beside the stage.
Required work is recorded and the sample waits for evidence or disposition review. Open exceptions should remain visible.
Use a final stage only after the defined decision is recorded. Keep the last update and disposition for later reference.
The simple file can show current location and custodian. If you need every movement, add a movement sheet with one event per row or move to the related-event model in Jodoo.
Search or scan the sample ID and confirm the external reference before changing location or responsibility.
Update the location, custodian, lifecycle status, current task, owner, due time, and last-updated time as applicable.
Use the notes field for the specific handoff or problem, not as a replacement for the location, status, task, or exception fields.
Filter held samples, overdue tasks, open exceptions, missing locations, and undecided dispositions at an agreed frequency.
A tracker becomes fragile when users add Test 1, Test 2, Move 1, Move 2, Review 1, and Review 2 columns. Those are repeating records with their own owners and dates.
Use one related assignment per activity when methods, technicians, due dates, results, or blockers differ.
Use one custody or location event per receipt, move, handoff, check-out, return, or disposal.
Use a separate issue record when severity, containment, owner, due date, investigation, review, and closure need history.
Use an assigned native task when a reviewer needs controlled decision fields, comments, evidence, and a reliable outcome on the exact sample.
The populated example provides current queues and separate records for samples, work, movements, lots, transactions, exceptions, and release reviews. Users can open the record behind a dashboard count instead of maintaining another summary file.
Holds the stable identity, receipt facts, current stage, priority, storage, ownership, requested work, and disposition.
Shows assignments, technicians, methods, due times, work status, result status, summaries, and blockers.
Retains every movement with locations, time, handler, condition, and note while the sample shows the latest state.
Combines blocked work, out-of-specification results, open exceptions, pending review, and recent handoffs.
Whether you use the workbook or App, the review should lead to specific samples and owners. Avoid counts that cannot be traced back to the record requiring action.
Filter active samples with a blank or invalid current location or custodian and correct the latest handoff.
Compare due time with lifecycle status and task owner. Confirm whether the sample is blocked, awaiting review, or simply not updated.
Review severity, immediate control, owner, due date, investigation, and what prevents closure.
Find samples with completed work but no release, retain, return, or disposal decision and route the required review.
The workbook gives a concise register for location, owner, next action, and status. The App adds containers, aliquots, assignments, movements, exceptions, and reviews without widening one row indefinitely.
Workbook fit: A small team can maintain one current row per sample and does not need simultaneous tasks, durable movement history, or role-based review.
App fit: Samples split into containers, move between locations, pass between people, collect several assignments, or require reminders and review.
Define before rollout: Agree the sample ID, container ID, status choices, location hierarchy, custodian meaning, disposition, and exception path before importing records.
Use sample ID, external reference, sample type, received date, current location, custodian, lifecycle status, current task, task owner, due time, exception state, final disposition, last updated, and focused notes.
Use the row for current state. If movement history matters, keep one event per row in a related table or use an App. Repeated move columns become difficult to search, validate, and extend.
The workbook can support operational tracking, but it is not presented as a legal or regulated chain-of-custody system. Define and validate the required identities, signatures, controls, retention, and auditability for your use.
Use a separate assignment table or the Jodoo App. Each assignment should have its own method, technician, due time, status, result, blocker, evidence, and link back to the sample.
Yes. Clean identifiers, dates, statuses, owners, and locations first. Import the stable sample records, then create or import related movements and assignments separately so history and ownership remain clear.
Use the XLSX for a focused register. Open the App when each sample needs several tasks, movement history, owned exceptions, review tasks, and management queues.