Review, approval, and publication
Review and approval protect data integrity before results leave the lab. The exact names of review states and actions vary by tenant, but the control point is the same: confirm the sample record, result values, QC context, qualifiers, comments, and deliverable format before publication.
Before review#
Confirm that:
- sample identifiers, client, project, and collection/receipt dates are correct;
- requested analyses are complete or documented as canceled/not applicable according to SOP;
- result units, limits, qualifiers, and comments are appropriate;
- QC samples, blanks, spikes, duplicates, controls, or calibration checks have been reviewed when required;
- attachments, chain-of-custody records, bench sheets, and instrument files are present when required by the tenant workflow.
Review results#
- Open the sample, worksheet, batch, or review queue.
- Compare entered results against method expectations, units, limits, and qualifiers.
- Check exceptions, warnings, missing values, and comments.
- Confirm that any required QC review is complete.
- Return work for correction when sample information, results, qualifiers, comments, or attachments are incomplete.
- Approve the work only when it is ready for reporting under your lab SOP.
Publish or release deliverables#
Publication options depend on report templates, customer delivery rules, and tenant configuration. Before publishing, preview the deliverable and confirm that it includes the intended sample set, client details, result table, units, limits, qualifiers, signatures, disclaimers, attachments, and any required chain-of-custody pages.
Do not publish a deliverable when required review is incomplete, the wrong report template is selected, customer identifiers are incorrect, or the output does not match the approved format.
Support escalation#
Open a Clearline Support ticket when review actions are missing, results are stuck in the wrong state, a report-ready item cannot be approved, the release action fails, or a deliverable contains unexpected content. Include only sanitized internal references, the page URL, affected role or account type, current workflow status, what you tried, and exact error text. Redact sensitive values from screenshots. Do not attach regulated data, customer records, reports, credentials, or production exports; Clearline Support will provide a controlled transfer path if additional information is required.