Receive
Identify the sample, check condition and quantity, assign storage, record priority and required-by time, and accept, hold, replace, or return the receipt.
From receipt to disposition
Connect laboratory samples, work, exceptions, and approvals
Map the actual operating sequence, give every handoff an owner and due date, and route exceptions and release decisions without forcing the laboratory into a rigid universal process.
Opens the populated Jodoo example after sign-in. Start with the Free plan for up to five users; no credit card required.
Jodoo can coordinate human work, forms, records, reminders, and approvals. The example does not perform laboratory testing or automatically capture instrument results.
- Separate sample identity from assignments, movements, stock, exceptions, and reviews
- Use native review tasks for exception control and release decisions
- Change fields, roles, conditions, and dashboards as the operating process develops
6operating stages in the modelNativeexception and release reviewConfigurableroles, fields, and outcomes
Give each stage a record, owner, completion condition, and next step
A workflow is more than a list of statuses. The application should explain what starts the stage, what information is required, who owns the work, what can go wrong, and what decision moves the sample forward.
Plan and assign
Create the required activities or tests, assign technicians, set due times, and make dependencies or material constraints visible.
Perform and record
Capture work state, result state, summary, attachments, completion time, and a clear blocker or correction note when work cannot finish.
Handle exceptions
Open a separate issue with severity, immediate control, owner, due date, investigation state, review comments, and verified closure.
Review
Bring completed work, open exceptions, evidence, and proposed disposition to an assigned reviewer through a native task.
Dispose or retain
Record release, retention, return, rejection, or disposal and update only the linked sample while preserving the earlier work and decisions.
Avoid one crowded form and one universal permission model
Workflow quality improves when responsibilities are explicit. The record shown to a receiving coordinator should not be identical to the task shown to a reviewer, even though both refer to the same sample.
Receiving coordinator
Needs expected arrivals, source, condition, quantity, storage, priority, required-by time, and the authority to accept or hold the receipt.
Technician
Needs assigned activities, due dates, sample context, method, material availability, work state, result entry, evidence, and blocker fields.
Sample coordinator
Needs the cross-sample queue, workload, overdue work, current locations, exceptions, and samples waiting for review or disposition.
Reviewer
Needs completed work, result summaries, evidence, exception status, review criteria, comments, and the permitted disposition choices.
Inventory owner
Needs lots, quantities, expiry, storage, holds, transactions, reorder points, and the active work affected by availability.
Laboratory manager
Needs operational counts with drill-down to samples, assignments, lots, exceptions, reviews, and responsible owners.
A useful workflow explains what happens when receipt, work, evidence, or review is incomplete
Exceptions should not be an afterthought added as a free-text comment. Each important branch needs a visible state, owner, due date, correction path, and rule for rejoining or ending the main process.
Receipt cannot be accepted
Hold the sample, state the reason, protect the location, notify the right owner, and decide whether to replace, return, or continue under an approved control.
Assigned work is blocked
Keep the assignment open with the blocker, correction needed, technician, due date, and affected sample visible in the work queue.
Result needs investigation
Preserve the result and evidence, open an exception, assign immediate control and investigation, and prevent a casual status change from hiding the issue.
Reviewer returns the work
Record what is missing, who must correct it, and how the corrected evidence returns to review. Do not overwrite the original decision or comments.
Use reminders and exact-record updates where rules are clear
Jodoo can reduce coordination work by creating tasks, reminding owners, updating the linked record, and routing a review. The laboratory still owns the method, acceptance criteria, result interpretation, and final professional decision.
Create the next task
When a sample is accepted, create the required assignments or notify the coordinator to confirm the work plan.
Escalate overdue work
Use due dates, priority, and status to notify the owner and surface the exact assignment rather than sending a generic reminder.
Route native review
Send the exception or release record to the assigned reviewer with editable decision fields and read-only operating context.
Update the linked sample
After an approved decision, change only the exact sample’s status and disposition while retaining the review record and earlier history.
Measure time between handoffs and inspect the records behind the number
Turnaround time becomes useful when it can be separated into receipt, assignment, work, exception, review, and disposition intervals. That shows where to improve the process rather than blaming the total cycle.
Receipt-to-acceptance
Find samples waiting at intake and separate routine processing from held or incomplete receipts.
Acceptance-to-assignment
See whether samples wait because the plan is unclear, the owner is missing, capacity is constrained, or material is unavailable.
Assignment-to-completion
Compare due dates, work states, blockers, returns, and completion times by activity and responsible role.
Completion-to-decision
Show samples waiting for evidence review, open exceptions, reviewer action, or disposition confirmation.
Let a trained process owner make focused changes in hours
Laboratory work changes when methods, sample types, staff responsibilities, storage areas, review criteria, or reporting needs change. A no-code application is most valuable when those changes can be made without breaking the identity and history that already work.
Change one stage deliberately
Update the fields, choices, validation, task, and dashboard affected by the change instead of copying a new spreadsheet for the revised process.
Retest both normal and exception paths
Confirm what appears, what is required, who receives the task, which exact record changes, and which unrelated records remain unchanged.
Preserve prior records
Do not rename or remove fields casually when existing records, reports, automations, or integrations depend on them.
Publish clear ownership
Document who can change the app, who approves process changes, and how users report a field, route, or dashboard that no longer fits.
Built for human handoffs and review decisions
Use it when the laboratory process crosses roles, deadlines, exceptions, and approvals
The example shows operational queues plus native review tasks for sample exceptions and release decisions, rather than representing workflow as a status field alone.
A strong fit: Laboratories coordinating intake, assigned work, evidence, exception containment, correction, review, and final disposition across several people.
What the App demonstrates: Distinct records and owners, pending work, blockers, returned work, exception actions, review decisions, and exact updates to the linked sample.
Keep scientific execution separate: The workflow coordinates people and records. It does not perform testing or automatically collect instrument results.
Practical questions about laboratory workflow management
What does laboratory workflow management include?+
It can include sample receipt, acceptance or hold, work planning, assignment, execution, results, custody events, inventory availability, exceptions, review, disposition, retention, and management follow-up. The exact scope should match the laboratory’s responsibilities.
Can Jodoo route real approval tasks?+
Yes. The example uses native review tasks for sample exceptions and release decisions. Roles, decision fields, validation, return paths, and downstream effects must be configured and tested for the intended process.
Can the workflow change without programming?+
A trained administrator can change forms, fields, choices, conditions, views, dashboards, reminders, and workflows in Jodoo’s no-code builder. Material changes still need controlled review and testing.
Does Jodoo integrate with instruments or a LIMS?+
Jodoo provides APIs and integration options, but this example does not claim instrument connectivity or a ready-made LIMS integration. Define the source, identifier, timing, error handling, ownership, and validation needed for each integration.
How should we pilot the workflow?+
Use routine, urgent, held, blocked, out-of-specification, corrected, review-ready, released, retained, and returned examples. Confirm forms, permissions, tasks, notifications, exact-record updates, dashboards, and mobile use with the people who perform each handoff.
Explore the populated laboratory workspace
Explore the laboratory workflowSee how the laboratory handoffs connect in one populated workspace
Open the populated queues and forms, then map the stages, roles, exceptions, and decisions to your own laboratory before changing the application.