The OUT-OF-DATE cascade
- A programmer refreshes data or amends a spec on an upstream dataset.
- Verixa flips every validated downstream output to Out of date, forces re-QC, and writes an audit event for each one.
Why it mattersThis is the silent failure that fails inspections. The production program changes but QC never re-runs theirs. Verixa makes that impossible to miss, automatically.
Independent QC, reconciled in one place
- Production and QC are owned by different people. The app blocks anyone from QC-ing their own program.
- The cockpit shows the PROC COMPARE / diffdf result, the parsed log, and every finding with its root cause.
Why it mattersThe production-to-QC pair is the unit of work, not an afterthought bolted onto a generic task tracker.
A tamper-evident audit trail you can prove on the spot
- Every change is an append-only, hash-chained transaction with who, what, when, and why.
- One click recomputes the SHA-256 chain. Alter a single historical record and the chain breaks, pointing to the exact event.
Why it mattersAudit prep stops being a fire drill. Export an inspector-ready e-record in one click, filtered to what they asked for.
Electronic signatures bound to the exact version
- Sign-off re-authenticates the signer and records a meaning of Authored, Reviewed, QC-Approved, Approved, or Released.
- The signature is cryptographically bound to the record hash and invalidates the moment the record changes.
Why it mattersEnforced and guided out of the box, not a liberal e-sign that auditors have to take on faith.
Every program, every status, one board
- See production and QC progress as a sortable table or a kanban board.
- Filter by validation status. Assignments enforce segregation of duties.
Why it mattersThe real state of the study, finally out of a fragile spreadsheet and into a system of record.
A versioned repository your LSAF users already understand
- Check out to lock, edit, then check in with a comment. A new version supersedes and the prior signature invalidates.
- Version history carries a Signed column. Object-level ACLs control who can read, write, and sign.
Why it mattersAnyone who has used SAS LSAF or Oracle LSH is at home immediately, without the SAS lock-in, the cost, or the dated interface.
How an output was made, on a single coversheet
- Open any output to see the source-data snapshot and every program that touched it, each with its version and validation status.
Why it mattersThe auditor-facing artifact that answers how was this produced in seconds, not days.
Overview, versions, runs, QC, lineage, history, sign-offs
- Everything about a program lives on one record, including its run manifests and its full audit history.
Why it mattersNo more stitching the story together across five disconnected tools.
Process flows that drive the work
- Model the program life cycle as a process flow. The live diagram highlights the current step.
- Auto-Flow instantiates the right flow for each deliverable.
Why it mattersGovernance that guides the work instead of sitting in an SOP binder nobody opens.
Capacity planning tied to the deliverable backlog
- A demand-versus-supply heatmap shows who is over or under allocated, week by week.
- Spot the database-lock crunch before it derails the timeline.
Why it mattersThe resourcing view leadership has been running in a separate spreadsheet, finally connected to the work.
Every milestone, with the critical path
- All of a portfolio's milestones on one timeline, with the critical path and a today marker.
Why it mattersDatabase lock is the pivot. See slippage early instead of being surprised by it.
Submission readiness at a glance
- A composite readiness score, QC first-pass rate, utilization, and a rule-based study-health risk engine.
Why it mattersLeadership sees study health and risk without ever asking for a status update.
