Establishing secure connection…Loading editor…Preparing document…

ASQ Six Sigma Black Belt Certification Project Affidavit/Verification Form

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

ASQ Six Sigma Black Belt Certification Project Affidavit/Verification Form

Please see the explanation of how to fill out this form on the reverse side.

One of the requirements for application approval to take ASQ’s Six Sigma Black Belt certification exam is the demonstration of experience. Six Sigma Black Belt affidavit(s) must be completed and submitted attesting to that fact. Provide two signed affidavits attesting to the completion of two Six Sigma projects, signed by the project champion(s). If two Six Sigma projects have not been completed, one completed project will be allowed providing you have at least three years of work experience covered by the Six Sigma Black Belt Body of Knowledge (BOK).

Check here if two projects have been completed.

Check here for one completed project and three years of experience.

If you have not completed at least one Six Sigma project, you will not be allowed to take the examination.

Completed, signed affidavits can be e-mailed to cert@asq.org. The signed Six Sigma affidavit(s) must be received at ASQ within one week of receiving your application. If not, your application will be cancelled and a partial refund (less the application fee) will be returned to you.

1. Six Sigma Project completed by

2. Six Sigma project title

3. Provide a brief description of the purpose of the project, and how it related to the business objective:

4. Six Sigma project’s start and completion dates by month/year:

5. Provide a brief description of applicant’s hands-on performance in completing Six Sigma project. Please include specific examples of tools used and how they were applied, e.g., process maps, metrics (DPU, DPMO, RTY), procedures, charts, etc. Do not send documentation.

6. Provide a brief statement on the benefits achieved by the successful completion of the project, including but not limited to financial savings, labor, material costs, cycle-time reduction, etc. (Measured before-and-after benefits must be included. For example, cycle-time reduction of 15%.)

7. Verification of completion by project champion

Verification form completed by:

Six Sigma Project Affidavit Explanation Page

Six Sigma is a statistical measure of variability, typically in a given process. Its use is not limited to manufacturing, but as an example, it could be used to measure the number of substandard products. In the service industry, it could quantify delays in delivery or lag time in other processes. A successful Six Sigma project should yield virtual defect-free performance. It is a project that will provide breakthrough performance or improvement, which typically equals great monetary benefit to a company.

Before being allowed to take ASQ’s Six Sigma Black Belt certification examination, an applicant must demonstrate experience in the use of the Six Sigma methodology. Six Sigma Black Belt affidavit(s) must be completed, signed, and submitted before an applicant will be allowed to take the examination. Completed affidavits can be e-mailed to Certification Offerings e-mailed to cert@asq.org. The signed Six Sigma affidavit(s) must be received at ASQ within one week of receiving your application. If not your application will be canceled and a partial refund (less the application fee) will be returned to you.

1. Please print name of Six Sigma Black Belt applicant, along with her/his member number.

2. List the official name of the Six Sigma Black Belt project, as listed on your Six Sigma charter.

3. Explain briefly the problem you needed solved and how it related to your organization’s objectives.

4. List the project’s start and completion dates by month and year.

5. Please list the Six Sigma tools used. Be specific as to the name of the tool; specify data, measures, and metrics used. Provide as many examples as possible. Do not send any actual charts, maps, etc.

6. Explain briefly how close you came to reaching your goal and list the success(es) of this project. These may include, but are not limited to, financial savings, labor savings, material costs, cycle-time reduction, increased customer satisfaction, etc.

7. Verification section must include the project champion’s signature and date signed. In addition, please print the name of the project champion and provide job title and company address. Please include telephone, and e-mail information for verification purposes.

If ASQ has any questions or needs to verify any of the information provided in this affidavit, we will contact the project champion.

What is the definition of a Six Sigma project?

Six Sigma is a method for reducing variation in manufacturing, service, or other business processes. Six Sigma projects measure the cost benefit of improving processes that are producing substandard products or services. Whether in manufacturing or service industries, such projects quantify the effect of process changes on delays or rework. The goal of each successful Six Sigma project is to produce statistically significant improvements in the target process; over time, multiple Six Sigma projects produce virtually defect-free performance. The Six Sigma Black Belt project is one that uses appropriate tools within a Six Sigma approach to produce breakthrough performance and real financial benefit to an operating business or company.

The tools are generic. It is the structure of the project and the associated process (improvement model) that distinguish a Black Belt project from other similar quality improvement projects. Financial impact as an outcome is also a requirement within a Black Belt project when compared to other projects.

The following examples are not all-inclusive, but will provide examples of acceptable and unacceptable projects:

Examples of projects that qualify:

• Manufacturing product defect reduction

• Human resources recruitment cycle-time reduction

• Reduced accounts payable invoice processing costs

• Reduced manufacturing machine setup time

Projects that do not qualify:

• Prepackaged or classroom exercises that are mock or simulated projects that were previously completed and/or that do not include actual “hands on” work

• No real organization or business unit; no current problem or cost benefit

• Basic product improvement projects not associated with process improvements

• Software maintenance or remediation without detailed process measurements

• Any project without measured before-and-after cost benefits

Enter text✕

What this affidavit/verification form is and how it’s used

The ASQ Six Sigma Black Belt Certification Project Affidavit/Verification Form documents the candidate’s project work required for Black Belt certification. It records project scope, objectives, key metrics, sponsor verification, and the candidate’s attestation that the work was completed as described. The form is used by ASQ reviewers to confirm project authenticity and by employers to record role-based approvals. Accurate completion supports credentialing decisions and creates a clear audit trail for the candidate’s certification file.

Why a correctly completed affidavit matters

A complete, accurate affidavit verifies project outcomes, supports ASQ review, and reduces rework or requests for additional evidence. Proper signatures and dates preserve legal validity under ESIGN (15 U.S.C. ch. 96) and state e-signature law (UETA where adopted).

Why a correctly completed affidavit matters

Who completes and reviews the affidavit

Typical participants include the Black Belt candidate, the project sponsor or manager, and the ASQ reviewer; HR or certification administrators may also retain copies.

  • Black Belt candidate — completes project details and attests to work performed.
  • Project sponsor/manager — verifies scope, outcomes, and signs to confirm oversight.
  • Certification administrator — receives, logs, and forwards affidavit to ASQ reviewers.

Who signs and why

Project Lead

Black Belt candidate (Project Lead) signs to attest that the project details, data, and outcomes are true and accurate; this signature is the primary attribution of authorship and responsibility.

Project Sponsor

Sponsor or manager signs to certify they supervised or provided oversight and that the project was implemented as described; sponsor attestation supports ASQ verification and confirms organizational approval.

Step-by-step: completing and submitting the affidavit

Follow this sequence to gather evidence, obtain signatures, and submit a verified affidavit to ASQ.

  • 01
    Prepare Evidence: Collect project report, data summaries, and control charts for attachment.
  • 02
    Fill Form: Complete all fields, using MM/DD/YYYY format for dates and exact names.
  • 03
    Obtain Sponsor Signature: Have the sponsor review and sign; consider notarization if required by employer.
  • 04
    Submit to ASQ: Upload affidavit and attachments via ASQ application portal per instructions.

Configuring an online workflow for affidavits

Set up a consistent digital workflow so candidate, sponsor, and administrator complete steps in order and records are retained securely.

Field Configuration
Upload PDF Require a single consolidated PDF with attachments for easy review.
Signer Authentication Use email + SMS code or organization SSO to attribute signatures.
Notification Settings Enable reminders for pending signatures and completion confirmations.
Retention Policy Automatically archive signed copies for the required retention period.

Typical eSubmission flow for certificate affidavits

A clear sending and signing flow reduces friction and ensures each signer is authenticated and the audit trail is captured.

  • Upload Document: Sender uploads the affidavit and attaches supporting reports.
  • Place Fields: Add signature, date, and text fields where required.
  • Assign Signers: Set signer order: candidate first, then sponsor, then admin.
  • Capture Audit Trail: System logs timestamps, IPs, and authentication evidence for each signer.

Technical requirements for digital completion and storage

Use a platform that supports common document formats, strong authentication, and secure long‑term storage to meet ASQ and organizational needs.

  • File formats: PDF, DOCX accepted
  • Integrations: Salesforce, Google Workspace
  • Authentication: Email + SMS or SSO

Ensure the chosen platform produces an audit trail and stores signed PDFs with tamper-evident protections and encryption to satisfy ESIGN/UETA and organizational retention policies.

Key components of a professional affidavit/verification form

A professional affidavit is structured to provide clear project identification, measurable outcomes, verifiable signers, and attached proof to support ASQ evaluation.

Header Information

Project title, candidate name, ASQ ID, and employer details placed prominently for immediate identification by reviewers.

Project Summary

Concise description of problem statement, scope, objectives, and methods used including DMAIC phases and key deliverables.

Quantified Metrics

Baseline and post-project metrics with units, sample sizes, and percent improvements to demonstrate measurable impact.

Sponsor Verification

Sponsor name, title, and signature block confirming oversight and acceptance of results; contact details for follow-up.

Attachments List

List attached evidence such as control charts, Pareto analysis, cost‑benefit summary, and final report references.

Signature Section

Candidate attestation, sponsor signature, and date fields formatted for electronic or wet signatures as required.

Security and compliance features to expect

Encryption in transit: TLS 1.2/1.3
Encryption at rest: AES-256
Audit trail: Timestamped event log
HIPAA support: BAA available
Regulatory certs: SOC 2 Type II
21 CFR Part 11: Support for regulated records

Risks and consequences of an incorrect or incomplete affidavit

Application Delay: ASQ may request clarifications, lengthening certification processing time.
Rejection Risk: Incomplete evidence or missing sponsor verification can cause denial of project credit.
Invalid Attribution: Mismatched names or credentials undermines signer attribution under ESIGN/UETA.
Data Discrepancies: Conflicting metrics invite auditor scrutiny and possible project re-evaluation.
Privacy Exposure: Improper handling of PHI may trigger HIPAA compliance issues.
Record Loss: Failure to retain signed copies risks noncompliance with retention policies.

Common pitfalls to avoid when preparing the affidavit

  • Submitting inconsistent dates between the affidavit and attached reports, which leads reviewers to request clarifying documentation.
  • Using informal or partial names for signers; always match names to employer records to avoid identity confusion.
  • Attaching inadequately labeled evidence files, making it difficult for reviewers to correlate metrics with claims.
  • Failing to capture a verifiable audit trail when e-signing, which can undermine legal enforceability under ESIGN.

Timing considerations and processing expectations

Plan ahead: assemble records and obtain sponsor verification before submitting your certification application to avoid processing delays.

Project Completion Date:

Affidavit should reflect when project work finished and metrics were finalized.

Sponsor Signature Timing:

Sponsor should sign after final review of attachments and before application submission.

ASQ Review Window:

Allow adequate time for ASQ to review and request clarifications; timelines vary by intake volume.

Document Retention Start:

Retention usually begins on the signature date of the affidavit.

Correction Timeframe:

Address any ASQ requests promptly to avoid application expiration or re-submission.

eSignature vendor comparison for affidavit signing and storage

Compare common plan features and compliance characteristics when choosing a platform to collect signatures and retain certified affidavit records.

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 Varies by vendor Varies by vendor Varies by vendor Varies by vendor
Bulk Send Yes (Business Premium) Yes Yes Yes No
Audit Trail Yes Yes Yes Yes Yes
HIPAA Compliant Yes (BAA) Yes Yes No No

Real-world examples of digital affidavit workflows

These brief examples show how organizations used digital signatures and verifiable records to manage project attestations and approvals.

Optica Ventures (COO)

The interface is simple and easy-to-use for our team; more importantly, it is just as easy for our customers.

  • Single workflow reduced turnaround for approvals.
  • With digital signatures and organized attachments, the company processed affidavits faster and maintained consistent records for certification audits.

Fertility Centers of Illinois (Founder)

The team has been exceptional, responsive, the API has been great, and we're extremely happy that we chose the platform.

  • Integrated eSign saved administrative time.
  • Centralized signed affidavits and clear audit trails improved internal compliance and simplified responses to external reviewers.

Frequently asked questions and quick answers

Answers to common questions about completion, signatures, notarization, and retention for the ASQ Six Sigma Black Belt Certification Project Affidavit/Verification Form.


Need help? Contact support

be ready to get more
Join over 28 million airSlate SignNow users