What if raw data is missing?

If instrument output is unavailable, document the reason, note any attempted recovery steps, and escalate per your SOP; include written supervisor attestation to preserve auditability.

Can a retest be performed without authorization?

No. Most SOPs require pre-authorization for retests; unauthorized retests can invalidate results and lead to corrective actions or disciplinary review.

Is an electronic signature acceptable?

Yes; electronic signatures are legally recognized under the ESIGN Act and UETA when intent, consent, attribution, and record retention are demonstrated.

When is notarization required?

Notarization is rarely required for internal QC logs; if a document will serve as evidence outside the organization, consult legal counsel and state notary rules.

How long must logs be stored?

Retain logs according to the longest applicable rule: industry standards, IRS records, HIPAA where relevant, or company policy—commonly 3–7 years.

What to do after discovering inconsistent timestamps?

Record the discrepancy, preserve original files, notify QA, and perform an investigation; update entries with an explanatory note and approver signature.

Electronic Signature
Templates
Miscellaneous
Quality Control Retest Log

Quality Control Retest Log

This template is fully customizable. Edit the text, fill out the fields, and send it for signature. Give it a try!

QUALITY CONTROL RETEST LOG

Client Name: Service Provider Name:

RECITALS

WHEREAS, the Client engages the Service Provider to perform quality control testing and to document retest activities when initial test results require verification or correction; and

WHEREAS, the parties require a formal, auditable record of all retests, retest results, corrective actions taken, and verifications to ensure product integrity, regulatory compliance and continuous improvement.

WHEREAS, this Quality Control Retest Log (the Agreement) establishes the procedures for recording retest events and sets related administrative and contractual terms between the parties.

SCOPE OF WORK

Detailed Scope of Retest Services

RETEST LOG

Use this log to record each retest event. Enter one line per retest. Retest records are part of the official quality record and must be completed contemporaneously with the activity.

#	Sample ID	Original Test Date	Retest Date	Reason for Retest	Technician	Retest Result	Action Taken / Comments	Verified By

PAYMENT TERMS

Compensation for retest services shall be as set forth below. The Service Provider's obligation to perform retests is conditional upon timely payment in accordance with this section.

Retest Fee (per event) Billing Schedule Late Fee

TERM AND TERMINATION

This Agreement becomes effective on the Start Date and continues until the End Date unless earlier terminated in accordance with this section.

Start Date End Date Termination Notice Period

CONFIDENTIALITY

Each party acknowledges that retest records, test data, protocols, and related communications constitute Confidential Information. Confidential Information shall not be disclosed to third parties except as required by law or with prior written permission. The receiving party shall use at least the same degree of care to protect Confidential Information as it uses to protect its own confidential information, but in no event less than reasonable care.

REPORTING, RETENTION, AND AUDIT

All entered records shall be retained by the Service Provider for the retention period specified by the Client or by applicable law. Upon reasonable notice, Client may audit retest records on-site during normal business hours. Any discrepancies discovered in the log shall be corrected with a dated, initialed addendum explaining the reason for correction.

GOVERNING LAW

This Agreement shall be governed by and construed in accordance with the laws of the state of without regard to its conflicts of law rules.

ENTIRE AGREEMENT

This document, including any attached schedules and the retest records entered hereunder, constitutes the entire agreement between the parties with respect to retest services and supersedes all prior understandings and agreements, whether written or oral, relating to the subject matter.

CERTIFICATION

By signing below, the signatories certify that all information recorded in this Quality Control Retest Log is true and accurate to the best of their knowledge and that entries were made contemporaneously with the retest events described.

Client:

By:

Date:

Service Provider:

By:

Date:

What the Quality Control Retest Log Is and when it matters

A Quality Control Retest Log is a structured record used to document repeat testing performed after an initial quality control failure, deviation, or out-of-specification result. It captures the original test result, reason for retest, retest method, personnel involved, retest date and time, and final disposition. The log provides a clear audit trail for internal quality teams, external auditors, and regulators, and supports root-cause analysis, corrective actions, and trending to prevent recurrence of defects.

Why maintaining a clear Retest Log benefits operations and compliance

A well-maintained Quality Control Retest Log reduces ambiguity after a failed test, documents corrective actions, and demonstrates control during audits and regulatory reviews.

Who typically prepares and reviews the Retest Log

Production QA, laboratory technicians, and quality managers usually create and maintain the retest log after an out-of-specification event.

Laboratory technicians: record test details, methods, and observed deviations immediately after retest completion.
Quality assurance managers: review entries for completeness, authorize final disposition, and sign off on corrective actions.
Regulatory or audit staff: inspect logs during internal or external reviews to verify traceability and control.

Regulatory compliance teams and external auditors review the log to verify corrective actions and confirm results are properly documented.

Essential sections every professional Retest Log should include

A complete Quality Control Retest Log organizes information so any reviewer can reconstruct the event, the rationale for retest, the procedures used, and the final outcome without additional context.

Record ID

Unique identifier for each retest entry to cross-reference with original failed test records and production batch numbers.

Original Test

Capture original test name, date, operator, instrument, and measured result so the retest context is fully documented.

Retest Rationale

Explain why the retest was authorized (instrument error, sample handling, outlier, suspected contamination) to support corrective actions.

Retest Method

Document procedure, instrument ID, reagents, settings, and any deviation from standard method used during the retest.

Results & Disposition

Record retest values, pass/fail outcome, acceptance criteria used, and final disposition (release, quarantine, scrap, further testing).

Reviewer Signatures

Name, role, signature, and date of individuals who performed, reviewed, and approved the retest and final disposition.

Step-by-step: completing a Quality Control Retest Log

Follow these steps immediately after a retest to preserve evidence, maintain chain of custody, and reduce audit friction.

01

Identify the event: Record original failure and link to batch or sample ID.
02

Authorize retest: Obtain approval per SOP before retesting.
03

Perform retest: Follow the documented procedure exactly and note any deviations.
04

Document and review: Complete log fields, attach raw data, and have QA approve disposition.

How to configure a digital Retest Log workflow

Set up a repeatable digital workflow to ensure entries are complete, timestamped, and routed automatically to reviewers.

Field	Configuration
Template Name	Use standardized template per product line
Signer Order	Operator -> QA reviewer -> Quality manager
Conditional Fields	Show additional fields if result = 'Fail'
Authentication Method	Email link or SMS code as appropriate

Typical routing and submission flow for the Retest Log

Digital routing reduces delays and ensures each retest entry is reviewed by the correct role in order.

Record creation: Operator opens template and completes required fields.
Attach evidence: Upload instrument printouts, photos, or raw data files.
Reviewer notification: QA receives automated review request with attachments.
Final approval: Quality manager signs and records disposition.

Digital submission: platform capabilities to consider

Choose a platform that provides tamper-evident records, role-based access, and clear audit trails.

File formats: Accept PDF and DOCX with attached raw data files.
Authentication: Email, SMS code, or enterprise SSO as required.
Audit trail: Capture IP, timestamp, and action history.

Timelines and processing expectations for retest entries

Establish time limits for recording retests and routing approvals to keep investigations current and defensible.

Immediate entry:

Record retest details within 24 hours of completion.

Initial QA review:

QA to review within 48 hours of entry.

Corrective action start:

Begin corrective actions within 5 business days if required.

Final disposition:

Approver to sign off within 10 business days.

Audit readiness:

Maintain complete records accessible for scheduled audits and inspections.

Common mistakes to avoid when preparing a Retest Log

Incomplete entries: leaving required fields blank or using ambiguous phrases delays investigations and undermines traceability.
Missing raw data: failing to attach instrument printouts or photos prevents independent verification of retest results.
Inconsistent timestamps: using varied date/time formats makes sequencing events difficult during audits or root-cause analysis.
Unauthorized retests: performing or documenting a retest without SOP authorization can invalidate results and trigger corrective actions.

Consequences of an incorrect or missing Retest Log

Regulatory findings: Inspection citations and corrective action requests.

Product recalls: Costly recalls or market removals in severe cases.

Financial impact: Rework, scrap, and lost revenue.

Audit failures: Failed internal or third-party audits.

Data integrity risk: Loss of confidence in quality systems.

HIPAA/security fines: Potential fines for mishandled protected data.

eSignature vendor comparison for Retest Log workflows

Compare core pricing and capabilities for eSignature tools commonly used to capture and certify Retest Logs; signNow is listed first per vendor comparison conventions.

	signNow	DocuSign	Adobe Sign	PandaDoc	HelloSign
Starting Price	$8/user/mo	$15/user/mo	$14/user/mo	$19/user/mo	$15/user/mo
Free Trial	7-day free trial, no credit card	Trial varies	Trial varies	Trial varies	Trial varies
Bulk Send	Yes	Yes	Yes	Yes	No
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes	Yes	Yes	No	No
Envelope Cap	No cap	100 envelopes/user/year	Varies	Varies	Varies

Required data elements and security metadata for each log entry

Timestamp: ISO or MM/DD/YYYY format

Operator: Full legal name

Instrument ID: Serial or asset tag

Attachment Links: Raw data file references

Audit Trail: IP and action history

Approval: Approver name and signature

Common questions about using the Quality Control Retest Log

Answers to frequent questions about form completion, digital signatures, retention, and what to do when evidence is missing.

Need help? Contact support

What if raw data is missing?
If instrument output is unavailable, document the reason, note any attempted recovery steps, and escalate per your SOP; include written supervisor attestation to preserve auditability.
Can a retest be performed without authorization?
No. Most SOPs require pre-authorization for retests; unauthorized retests can invalidate results and lead to corrective actions or disciplinary review.
Is an electronic signature acceptable?
Yes; electronic signatures are legally recognized under the ESIGN Act and UETA when intent, consent, attribution, and record retention are demonstrated.
When is notarization required?
Notarization is rarely required for internal QC logs; if a document will serve as evidence outside the organization, consult legal counsel and state notary rules.
How long must logs be stored?
Retain logs according to the longest applicable rule: industry standards, IRS records, HIPAA where relevant, or company policy—commonly 3–7 years.
What to do after discovering inconsistent timestamps?
Record the discrepancy, preserve original files, notify QA, and perform an investigation; update entries with an explanatory note and approver signature.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now