FAQ
Questions a compliance team would actually ask
If you don't see your question here, our team is happy to go deeper on a call.
No. LABPROOF is assistive, not autonomous. It surfaces potential ALCOA+ issues with an explanation and a confidence score, but no finding is ever resolved, dismissed, or finalized without a named human reviewer. Final reports require an electronic sign-off from an authorized role.
CSV, Excel (.xlsx), and PDF, plus manual entry. During import you map source columns to record fields and confirm the mapping before scanning. The original source file reference is preserved and linked to every record for traceability.
All nine: Attributable, Legible, Contemporaneous, Original, Accurate, Complete, Consistent, Enduring, and Available. Each rule names the field that failed, the evidence behind the flag, and a suggested remediation a reviewer can act on.
The audit trail is append-only. Each event carries an integrity hash and records the actor, role, timestamp, target, and outcome. Events cannot be edited or deleted, only superseded by new events — which is what makes the chain defensible during inspection.
No. LABPROOF complements your LIMS. It ingests exports (or connects via integration on Enterprise) and adds the integrity-review and audit-readiness layer on top, without changing where your primary data lives.
On Professional and Enterprise plans, yes. You can tune severity, acceptance thresholds, and which principles apply to which methods. Policy changes are themselves logged in the audit trail.
Data is encrypted in transit (TLS 1.3) and at rest (AES-256), isolated per workspace, and access is governed by role-based controls with SSO and SCIM available. Enterprise customers can configure data residency and retention windows.
Most teams import their first dataset and run a scan in under an hour. We provide guided setup for roles, reviewers, and rule policies, and a seeded demo workspace so your team can practice the workflow before going live.
Still have questions?
Contact our team