Runwisp / recurring QC report review for lab teams
Spreadsheet and CSV QC batch review
For environmental and analytical laboratory teams, recurring QC review can move across spreadsheet tabs, instrument exports, and reviewer notes. Analysts may have to reconstruct the story and reviewers reconstruct it again. Runwisp keeps source context, controls, results, exceptions, and reviewer notes together for a clearer, reviewable handoff.
Free sample CSV / input format
Download a small file with synthetic, illustrative water and wastewater QC rows to see the expected CSV shape before using the demo or proof path.
Format demonstration only: this is not real customer data and is not evidence of performance.
The demo and proof paths use CSV exports. This page does not promise direct XLSX ingestion or support for every spreadsheet layout.
QC REVIEW / EXAMPLE
Batch review summary
- Method
- EPA 8260D · VOCs
- Instrument
- GC/MS-02
- Batch
- RW-2609-014
QC observations
4 SYNTHETIC ROWSSample
EW-014-A · Benzene
1.8 µg/LPassMethod blank
MB-014 · Target VOCs
NDPassLCS
LCS-014 · Recovery panel
96% meanPassSurrogate
EW-014-A · 1,2-DCA-d4
71% recoveryReview
Example reviewer decision
Qualify EW-014-A and retain the exception note.
The 1,2-DCA-d4 surrogate recovery is 71%, below the example control window. Keep that exception with the batch context in this illustrative report.
This is not a customer result or compliance determination.
Free review aid / email unlock
Get the QC review checklist
Use a one-page prompt to keep source context, results, controls, exceptions, dispositions, and handoff notes together during a recurring review.
Free review aid / email unlock
Get the QC review checklist
Use a one-page prompt to keep source context, results, controls, exceptions, dispositions, and handoff notes together during a recurring review.
Enter your email to unlock the checklist PDF.
The handoff problem
The evidence is familiar. The context gets scattered.
Recurring reports often span spreadsheet tabs, CSV or instrument exports, and reviewer notes. Analysts repeatedly reconstruct source context, batch/control/result relationships, exceptions, and notes from separate artifacts, then reviewers have to piece the handoff together again before sign-off.
One recurring workflow
Keep the review path together from source to draft.
01
Bring the source context
Start with the spreadsheet workflow your lab already uses. For the demo and proof paths, use a CSV export.
02
Keep batch details visible
Keep method, batch, control, and result context together as the QC record is reviewed.
03
Review exceptions in context
Read an exception alongside its related records and keep reviewer notes with the handoff.
04
Prepare a report draft
Prepare a report draft with the evidence path and reviewer notes available for the next handoff.
Demo and proof / bounded evidence
An exception should stay attached to its batch story.
The synthetic preview places an illustrative exception beside the batch details and reviewer decision. It shows the review context in one view; it is not customer proof, a compliance determination, or a promise that every spreadsheet layout is supported.
Fit and boundaries
A reviewable handoff alongside the systems your lab already uses.
- Existing spreadsheets, LIMS, and instrument software remain in place.
- Runwisp organizes review context; it does not replace a LIMS or instrument system.
- It does not provide compliance certification or a regulatory guarantee.
- It does not claim universal method or spreadsheet-format coverage.
Use synthetic data in the demo. For the proof path, use one recent, fully redacted CSV instrument export.
Next step / paid-pilot fit
Check paid-pilot fit
Start with workflow qualification. Fit review comes before any paid-pilot scope or checkout.