Build a connected workspace centered on each sample, from receipt and assignments through custody, results, review, and final disposition, then adapt it as your laboratory process changes.
Opens the populated Jodoo example after sign-in. Start with the Free plan for up to five users; no credit card required.
This example coordinates operational sample work. It does not claim instrument integration, clinical diagnostics, an electronic laboratory notebook, or a validated regulated LIMS.
A useful sample system keeps the original identity intact while people add work, movements, exceptions, evidence, and decisions around it. The sample record becomes the stable point of reference rather than another row copied between departmental spreadsheets.
Record the external reference, source, sample type, quantity, condition, storage requirement, deadline, priority, and requested work. A leaking container or quantity mismatch can be held immediately instead of entering the normal queue.
Create one or more assignments for the sample, give each a method or activity, technician, due time, work state, result state, summary, and supporting file. Work can be queued, active, blocked, completed, or returned for correction.
Route a completed sample to a reviewer with work completeness, exception status, evidence reviewed, reviewer comments, and the final release, retain, return, or reject decision.
Keep the receipt details, location changes, assignment results, exceptions, review outcome, and disposition linked to the same sample number so a later question can be answered without reconstructing the story.
Putting everything into one very wide form makes ownership and history difficult. The example uses related records so multiple tests, moves, exceptions, and stock transactions can exist without overwriting the sample’s identity.
Owns the stable identity, receipt facts, storage, requested work, priority, coordinator, current stage, and final disposition.
Owns the method or activity, assigned technician, due date, work state, result state, summary, blocker, completion time, and evidence for each unit of work.
Owns each movement or handoff, from and to locations, time, person, container or seal condition, and handoff note.
Own the issue, severity, immediate control, action owner, due date, review evidence, reviewer decision, and final outcome without erasing the original operational record.
Laboratory delays rarely come from the ordinary path. The app keeps the normal queue usable while giving urgent exceptions a named owner, due date, control action, reviewer, and closure path.
Hold damaged, leaking, temperature-concern, or quantity-mismatch receipts before work begins. Keep the handling note and replacement or return decision beside the original receipt.
Show the affected sample, method, technician, due time, blocker, and correction needed. The work remains separate from other assignments for the same sample.
Retain the recorded result and summary, open an exception when needed, and prevent the release conversation from becoming a disconnected email chain.
Reviewers can see whether an exception remains open before they record the sample disposition. The app stores the decision and updates only the linked sample.
A receiving coordinator, technician, inventory owner, reviewer, and laboratory manager do not need the same screen. They can work from filtered forms and dashboards while the underlying records remain connected.
Focus on expected and newly received samples, condition problems, priority, required-by time, storage, and who owns the next step.
Focus on assigned work, method, due time, status, missing evidence, blockers, and results awaiting review.
Focus on out-of-specification results, blocked work, open exceptions, pending reviews, and recent custody changes.
See sample stages, stock risk, work requiring attention, due priorities, and the records behind each count rather than relying on a detached presentation.
Jodoo’s no-code builder is useful when sample types, intake questions, review roles, storage locations, or exception paths change. A trained business administrator can revise a focused application in hours rather than waiting for a long custom-development cycle.
Introduce a new sample category, source field, storage zone, priority rule, attachment, or result summary without forcing every team into an oversized industry package.
Add another assignment, movement, exception, or review record when the process needs a distinct owner or history instead of adding another repeated column to the sample form.
Update the responsible reviewer, evidence fields, decision choices, and downstream status changes when responsibilities or approval criteria change.
Begin with the records that solve the current coordination problem. Add integrations, controls, permissions, and reporting only when the operating need is clear.
A good pilot proves that the application fits the daily job. It should include routine, urgent, held, blocked, review-ready, and completed examples before the team relies on it for live work.
Agree what receives a sample number, when a submission becomes accepted, how child assignments are created, and what final dispositions mean.
Name who receives, coordinates, performs work, moves samples, owns exceptions, reviews evidence, and confirms disposition.
Test acceptable receipts, damaged or leaking material, overdue assignments, out-of-specification results, missing evidence, review, release, retention, and return.
Track receipt-to-acceptance time, overdue work, blocked assignments, open exceptions, review turnaround, location discrepancies, and samples awaiting disposition.
This workspace is designed for laboratories that need configurable intake, assignment, custody, exception, review, and disposition records without starting with a large enterprise LIMS project.
A strong fit: Teams replacing shared spreadsheets, email handoffs, and disconnected status trackers with one adaptable operational workspace.
What you can inspect here: Populated samples, assignments, containers, custody events, exceptions, review tasks, inventory context, and drill-down dashboards.
Plan separately when required: Instrument result capture, clinical diagnostics, ELN functions, validated electronic signatures, and regulated LIMS requirements need a dedicated evaluation.
This application covers configurable operational sample intake, work assignment, custody, inventory, exceptions, review, and disposition. It does not claim clinical diagnostics, instrument data capture, ELN capabilities, validated electronic signatures, or every requirement of a regulated enterprise LIMS.
Yes. Test assignments are related records, so a sample can have multiple methods, technicians, due dates, work states, results, blockers, and evidence without repeating or overwriting the sample record.
Jodoo supports barcode and QR-code use in forms and mobile workflows. The exact code format, labels, scanning steps, and device setup should be configured for the laboratory’s identity rules and tested before rollout.
Each custody or location event can store the sample, event type, date and time, from and to locations, handler, seal or container condition, and a handoff note. The example supports operational history but does not make a legal chain-of-custody claim.
Yes. Use the receiving or tracking workbook for a focused starting point, then move to the connected app when duplicate updates, multiple assignments, permissions, reminders, review, and history become difficult to manage in one file.
Inspect sample intake, work assignments, custody, inventory, exceptions, reviews, and dashboards together. Then copy the focused parts that fit your laboratory’s real responsibilities and controls.
