Lab Workspace
See how labs set expectations, invite practices, review the inbox, add outside submissions, and return clear fixes.
Setup Shapes Intake Quality
The lab side is strongest when setup is treated as operations, not as a one-time admin chore.
Publish Expectations Early
RX forms and supported case types define what the lab wants practices to send before the inbox becomes busy.
Work The Inbox As A Queue
The inbox should help the lab triage and move real work, not bury the team in preventable intake repair.
Fallback Should Still Feel Structured
When a case arrives outside the normal workflow, labs can still use the paid fallback lane to create the case, run PreCheck, and send a secure correction link without forcing practice signup first.
Where Lab Work Happens
The inbox is the working surface, but it depends on setup that happens before the first case arrives.
For labs, the main place to work is Inbox, but the inbox only works well after the lab has set the foundation around it. Details, location, supported case types, RX forms, and practice invites all shape the quality of what eventually arrives there.
That is why the lab side is more than a queue. It is a controlled way to make expectations visible before practices send the case.
How Labs Set Expectations
The lab should publish clear expectations before asking practices to send cases this way.
The lab setup path matters because it becomes the practice-facing standard later. When the lab uses RX forms and supported case types well, practices do not have to guess what the lab wants or repeat the same clarifying conversation every time.
The best setup is clear enough to improve intake without turning the lab into a form-design project.
How Invites Fit Into The Workflow
Invites connect practices to the lab in a way that improves the submission quality later.
Invites are how the lab brings practices into the same expectations-backed process. That matters because the practice experience gets better when the receiving lab is known early and the packet is prepared with that destination in mind.
Use Invites to connect the right practices to the lab.
Treat invites as part of the operating model, not as a one-time marketing tool.
A connected practice sees the lab relationship earlier and prepares cases against a clearer standard.
How The Inbox Should Be Worked
The lab inbox is strongest when it reflects triage and quality, not repeated intake cleanup.
When a case reaches Inbox, the lab should be able to judge what is ready, what needs review, and what still needs correction before real production work begins. The inbox should feel like a triage queue with clearer packets, not like a holding pen for preventable intake confusion.
This is also why the lab-side setup matters so much. Better setup creates a better queue. Better practice onboarding creates a better queue. The inbox is where the result becomes visible.
How Rejections And Statuses Work
Good review outcomes keep the correction path clear instead of making the team start over from scratch.
If the lab needs a practice to correct something, the goal is to return a clear, structured reason for the fix rather than creating another vague resend loop. The case should remain understandable to both sides, with the lab’s review and the practice’s next action staying tied to the same submission story.
Use structured review outcomes when a case is not ready to move forward.
Keep the case history attached to the same case instead of shifting the conversation into disconnected side channels.
Treat activity as case history and follow-up, not as a substitute for the inbox or the lab setup.
When To Use Lab-Created Cases
The fallback lane exists for manual rescue work, not as the preferred repeat workflow.
Labs sometimes need to rescue a case that was emailed, portal-uploaded, or otherwise received outside the normal direct-submission path. That is where the lab-created case lane fits. The lab can build the case, run PreCheck, and send the practice a secure correction link without asking the practice to create an account just to finish that one fix.
The fallback lane is useful because it keeps the correction process structured, but it is still a fallback. The better long-term outcome is to invite repeat practices into the direct workflow so the lab rules and PreCheck show up before the original handoff. For the public overview of that model, see Lab-Created Cases.
Use the fallback lane when the lab already has the submission outside LabPreCheck and still needs a cleaner correction path.
Keep the fallback narrow: create the case, run PreCheck, send the secure link, and move the practice toward direct submission next time.
Do not treat the fallback lane as the default intake strategy for repeat practices.
Common Lab Questions
Labs usually need clear answers about setup, invites, RX files, correction links, and fallback billing.
Lab support questions usually come from rollout and intake operations: what stays free, how RX forms become requirements, how invites work, and when the lab-created fallback lane should be used.
The strongest answer is usually to keep the preferred workflow clear. Direct practice submission is the normal path. Lab-created cases and secure correction links exist to rescue outside submissions and to help practices move toward the direct workflow next time.
Core lab setup, practice invites, direct-submission review, and normal lab workspace use are free for labs under the current commercial model.
The paid lab-side exception is the optional lab-created fallback lane. It starts with 30 free eligible cases or 30 free days from first use, whichever comes first, and then uses per-case monthly usage billing.
RX-form source uploads support PDF, DOCX, TXT, Markdown, PNG, JPG, and JPEG files. The AI-assisted setup can suggest case types and requirement hints, but the lab should review and keep only practical rules that practices can follow.
Supported case types should reflect what the lab actually wants to receive through LabPreCheck. A broad setup that does not match real operations can make the practice experience worse.
Practice invites connect a practice to the lab relationship and can support an invite-backed first month free when the practice location matches. Invites do not replace the practice’s own setup and billing requirements.
A lab-created correction link is protected by a secure token and access code, shows an expiration date, and lets the practice complete requested details without creating an account. If it expires or is already submitted, the lab should send a fresh request when more information is still needed.
Secure correction links are for requested case fixes only. They are not a general file portal, support form, marketing page, or long-term replacement for direct practice submission.
Labs should use structured return and review outcomes when a case is not ready. A clear reason tied to the same case is better than starting a disconnected email thread.
Lab admins manage lab details, location, RX forms, invites, billing for paid fallback usage, team access, and legal acceptance. Regular lab members may not be able to complete those admin actions.