QBench August 17, 2026 Product Release Notes

Design and enforce exactly how your Tests move through their statuses with Status Workflows, now available for more labs. This release also brings consent signing into the Customer Portal, where the people submitting cases can now generate consent Documents and request signatures themselves.

Are you a QBench customer with ideas for new features? We’d love to hear them. Use the "Submit Feedback" link in the Help menu to submit your ideas and vote on feature requests. The requests with the most votes get considered first in our roadmap planning.

‍

Customer Requests (You asked, we delivered!)

• Consent Signing in the Customer Portal: Generate Documents and request signatures via Dropbox Sign from the Customer Portal, with recipients filled in from the Order. See details below.

Status Workflows

Status Workflows lets you design and enforce exactly how your Tests move from one status to the next. Build your lab's process once and let QBench hold everyone to it, with a complete audit trail at every step. Set it up in Configuration > Application > Status Workflows.

• Electronic signatures on status changes: Require an e-signature to move a Test between statuses, capturing the signer, timestamp, and comment in the Test's history.
• Two-person signoff: Require a second signature from a different reviewer on critical transitions, meeting separation-of-duties expectations for regulated labs.
• Control over who can change statuses: Restrict each transition to specific people or teams, so only authorized users can move a Test forward.
• API-only transitions: Reserve a transition for your integrations so it runs automatically and is never exposed to users in the app. Every API-driven transition is recorded in history and attributed to the API client that made it.
• Required fields on status changes: Configure fields that must be completed to move a Test forward, so the right data (a reading, a reason, a result) is captured at the moment of the transition.
• Locking during a step: Lock a Test in a given status so results cannot be entered early. Pair it with a time-based Automation, set up in Automations, to advance the Test when the window closes, for example, moving it from Incubating to Ready for Analysis after 48 hours.

🧪 Status Workflows is included with Foundation, Growth, and Advanced packages. Contact your QBench account representative to learn more.

Dropbox Sign

Consent Signing in the Customer Portal: Collect signed consent Documents via Dropbox Sign without retyping names or email addresses.

• Your Customer Portal users can now generate consent Documents and send them for signature themselves, on the Orders they submitted. Previously, this could only be done from the LIMS.
• Recipient name and email fill in automatically from the Order's Source on both LIMS and Customer Portal. On Orders carrying two sets of details, each Document goes to its own recipient, so a patient consent and a partner consent are addressed correctly without any manual entry.
• Recipients stay editable before you send, so you can correct or complete anything the Source does not carry yet.
• The Test list gained a signature filter. "Signed" returns Orders where every Dropbox Sign Document has been signed, and "Not signed" returns everything else, so you can confirm consent before building a Batch.
• A signature status column on the Test list shows where each Order stands, including partial states like "1 of 2 signed."
• Applies to Document configurations that have Dropbox Sign enabled.

A special treat for those who read all the way here:

What do you call iron blowing in the wind?

Fe-breeze.

v2.113