
You finished a strong improvement project. The savings are real, the control chart is stable, and the sponsor signed off. Then the certification body asks for the project file, and your legal team says no. For Green Belt and Black Belt candidates, disclosure restrictions can complicate an otherwise complete submission.
This guide walks through how to prepare certification evidence when your employer restricts disclosure. You will see how to request permission, check provider-specific review rules, redact identifiers without destroying the analysis, preserve calculations, and arrange controlled reviewer access. A practical evidence-package checklist sits near the end, along with a clear line between anonymization and fabricated results.
Key Takeaways
- Confirm your provider's evidence rules before preparing a submission.
- Obtain written approval for the exact information and access proposed.
- Remove identifiers and hidden content, then assess disclosure risk.
- Preserve analytical validity and document every data transformation.
- Use genuine project results and agree on any restricted review arrangements.
How Can You Submit a Confidential Six Sigma Project?

Prepare a confidential Six Sigma project by separating the method from sensitive content and agreeing on what reviewers need. Aim to show the problem logic, analysis, and verified result while withholding unnecessary customer names, employee IDs, contract pricing, and system identifiers.
Get written employer permission, confirm what your certification provider reviews, and agree on redactions or controlled access before sharing anything. Keep the original calculations reproducible internally and explain any transformations in the review copy.
This approach can reduce disclosure risk, but it does not guarantee anonymity or acceptance by the certification provider.
Why Certification Evidence Rules Differ Across Providers
Evidence requirements vary by credential, belt level, and provider; an exam, a signed affidavit, and a full project review are different forms of assessment. For Air Academy Associates, the Green Belt certification requirements include an approved project, a written report, and verification of benefits.
The Black Belt certification requirements also include project reports and benefits verification. Confirm the requirements for your chosen pathway and ask what confidential information can be withheld before preparing the package.
Do not assume that a sponsor letter replaces a required report or that an exam-only credential validates completed project work. Use the comparison below to frame questions for your provider; it is not a list of review options every provider offers.
| Review Model | What Gets Examined | Confidentiality Pressure |
|---|---|---|
| Affidavit based | Signed attestation of completed project work | Usually less detail, but the affidavit itself may disclose sensitive information |
| Full document review | Charter, analysis, control plan, financials | Depends on required content and approved redactions |
| Exam only | Body-of-knowledge mastery | No project-file disclosure if none is required |
| Controlled access review | Supervised viewing, no file transfer | Depends on access restrictions and information viewed |
Ask your provider which model applies before you spend a weekend redacting slides.
Getting Employer Permission for an Anonymized Project

Request written, dated approval from the people authorized to approve disclosure under your organization's policies and applicable client agreements. Specify the content, recipients, access method, and retention period; do not assume a supervisor's verbal approval or a short email is sufficient.
Here is what that request should cover.
- Scope of disclosure. State exactly which artifacts you want to share, such as a charter summary, a capability analysis, and a control plan.
- Redaction commitments. List the categories you will remove, including client names, site locations, pricing, and system identifiers.
- Reviewer identity. Name the certification body and note whether reviewers sign confidentiality terms.
- Retention terms. Ask whether the provider stores or returns the submission, and pass that answer to your approver.
- Approval signature. Capture a name, title, and date so the permission is traceable later.
Attach a sample redacted page to make the proposed disclosure easier to evaluate.
With permission secured, the redaction work begins.
Redaction Methods That Protect Proprietary Data
NIST's guidance on de-identifying government datasets addresses direct identifiers, quasi-identifiers, and re-identification risk. Apply those principles to the review copy, while having your organization assess proprietary information and any sector-specific restrictions separately.
NIST describes protected enclaves and query interfaces as data-sharing models. These can inform a restricted review arrangement, but NIST does not establish what a Six Sigma certification provider must accept.
- Remove direct identifiers. Customer names, employee names, badge numbers, serial numbers, and account references come out first.
- Review indirect identifiers. Use consistent site and product codes where approved, but assess whether dates, rare events, or combinations of details still reveal identities. Generalize dates only if the change preserves the time order and analytical detail needed for review.
- Agree on financial summaries. Ask whether percentages or indexed values are acceptable, document the calculation basis, and retain the original financial validation internally. Relative results do not disclose absolute savings and may not satisfy a monetary eligibility threshold.
- Clean hidden content. Check document properties, comments, attachments, embedded workbooks, and hidden layers; Adobe explains how to remove hidden PDF information. Inspect source workbooks separately before sharing them.
- Apply real redactions. A locked PDF or a black rectangle is not a substitute for removing content. Use a tool that can permanently redact sensitive PDF content, save a separate sanitized copy, and inspect the result before release.
- Assess re-identification risk. Have an authorized reviewer consider what the recipient could infer using the remaining details and other available information. An informal colleague check alone is not evidence that the file is anonymous.
Coded labels are not automatically anonymization: the ICO's guidance on pseudonymising personal data distinguishes replacing identifiers from making people unidentifiable. Keep any re-identification key separate and access-restricted.
Preserved Calculations That Keep Certification Evidence Credible

Removing context can make a submission impossible to evaluate. Preserve the evidence needed to follow the analysis, subject to the disclosure agreement.
Use the following elements to plan the review copy.
1. DMAIC Logic End to End
Reviewers need to follow the reasoning from problem statement through control. Each phase should show a decision and the evidence behind it; AirAcad's DMAIC project charter examples can help organize the scope, goals, and measures.
2. Measurement System Analysis
Gage R&R evaluates repeatability and reproducibility; it does not by itself establish that every measurement is accurate or suitable. NIST's guidance on gauge studies also addresses stability and bias. Report the study design, relevant results, and limitations, even when the instrument name is masked.
3. Baseline and Improved Performance
Show before-and-after capability, defect rates, or cycle times on a consistent scale. Use indexed values only with reviewer approval, explain the transformation, and verify that the reported analysis remains valid.
NIST's explanation of process capability relates capability indices to process variation and specification limits. If you rescale measurements, apply the same positive scale factor to the relevant limits and confirm the process stability and distribution assumptions used in the analysis.
4. Statistical Tests With Outputs
Include sample sizes, effect estimates, confidence intervals, and p-values where appropriate, alongside assumptions and limitations. The ASA's statement on statistical significance explains why a p-value alone does not establish effect size or practical importance. Review statistical outputs for disclosure risk too.
5. Root Cause Linkage
Connect the evidence supporting the root cause to the solution and its measured result. Explain alternative explanations or unresolved limitations rather than listing tools without showing how they informed decisions.
6. Control Plan and Sustainment
Include the response plan, monitoring method, and owner role instead of owner name. Sustainment evidence separates a finished project from a one-time fix.
Sometimes redaction alone will not satisfy a cautious legal team, and that is where access controls help.
Controlled Reviewer Access as an Alternative to File Transfer
If files cannot leave the network, ask your employer and provider whether a restricted review is feasible. Viewing information remotely is still disclosure, so obtain approval for the access itself.
- Supervised screen share. Propose an approved live review with agreed restrictions on recording, screenshots, and note-taking. Screen sharing alone cannot guarantee that no copies are made.
- On-site review. The reviewer examines materials at your facility under your security rules.
- Protected environment. Propose access limited to approved reviewers, with logging and download restrictions implemented by your organization.
- Sponsor attestation. Ask whether the provider accepts written verification and who is eligible to sign it.
- Redacted affidavit. Obtain provider approval before withholding required fields or replacing exact benefits with a range.
Not every provider offers these. Ask directly, in writing, and accept that some will decline.
The checklist below pulls the pieces into one package.
Evidence Package Checklist for Confidential Six Sigma Projects

Use this checklist as a starting point, then adapt it to the provider's requirements and your organization's disclosure approval.
- Written employer permission with named approver and date
- Redacted project charter with masked scope boundaries
- Process map using generic step labels
- Measurement system analysis summary
- Baseline and improved performance in an approved, consistently defined format
- Analysis outputs with sufficient approved detail to evaluate the conclusions
- Improvement description and pilot results
- Control plan with role-based ownership
- Benefit summary in the format required and approved for review
- Sponsor verification or provider-approved affidavit, where required
- Redaction log explaining what was withheld and why
The redaction log should describe withheld categories and transformations without revealing the restricted values or the re-identification key.
Anonymized Project Work Versus Fabricated Results
De-identification changes how information is disclosed; fabrication invents results. Do not present invented observations, altered outcomes, or simulated savings as evidence of completed project work.
Verifiable but Masked
A masked review copy should remain traceable to genuine records retained securely by your organization. An authorized verifier should be able to reproduce the original calculations and explain how the review copy was prepared.
Unverifiable Claims
Missing calculation methods, sample sizes, units, or verification arrangements make claims difficult to assess; they do not by themselves prove fabrication. Resolve those gaps with approved supporting evidence or clearly state the limitation.
Training Exercises
Classroom simulations and synthetic datasets can help explain a method, but they do not establish actual project outcomes. Label them clearly and ask whether the provider permits them as supplementary material.
Keep the original records and the transformation log under your employer's access and retention policies. Identify who can verify the work if the provider has follow-up questions.
AirAcad Support for Preparing Reviewable Certification Projects

Candidates working under disclosure restrictions usually need two things: a defensible project design and someone experienced to review the documentation approach. The four resources below connect directly to the evidence steps described above.
One-to-One Training and Coaching
One-to-One Training and Coaching supports project scoping and appropriate tool use. Ask about reviewing your proposed documentation approach before sharing restricted records. Confirm the scope of support and confidentiality arrangements in advance.
Lean Six Sigma Green Belt Online Course
The Lean Six Sigma Green Belt Online Course covers DMAIC through self-paced modules. Topics include capability analysis, measurement system analysis, hypothesis testing, and statistical process control. Use that foundation to explain your methods clearly in a redacted write-up.
Lean Six Sigma Black Belt Online Course
The Lean Six Sigma Black Belt Online Course includes regression and designed experiments alongside DMAIC. This depth can help candidates document why an analysis was selected and how its results support a decision. It does not replace employer approval or the provider's evidence requirements.
Project/Study Definition
The Project and Study Definition course covers opportunity selection, scope, and charter development before work begins. A tightly defined scope makes it easier to identify which information belongs in the study and which details may need to be withheld.
Final Thoughts
Confidentiality and credible documentation can coexist. Mask the identifiers, keep the mathematics intact, and let a verified sponsor stand behind the result. Talk with our team at Air Academy Associates if you want help planning your submission.
Talk with Air Academy Associates about training and coaching to strengthen your project methods and documentation. Explain your disclosure restrictions before sharing materials so the team can discuss an appropriate next step.
FAQs
Can a Confidential Project Be Used for Six Sigma Certification?
A confidential project may be usable if your employer authorizes the disclosure and the certification provider accepts the proposed evidence and access arrangements. Confirm those conditions before preparing the submission; masking identifiers alone does not guarantee eligibility.
What Evidence Can Be Anonymized Without Losing Traceability?
Names and identifiers may be removed or replaced with consistent codes, but assess whether dates, rare events, or combined details still reveal identities. Preserve enough approved information to follow the analysis, and keep the original records and any re-identification key separately under your organization's control.
What Should an Employer and Certification Reviewer Approve Before Submission?
Agree on the information that may be disclosed, the permitted recipients and access method, retention terms, and the required report or verification documents. Obtain approval from the relevant employer or client authorities and confirm the provider's acceptance of any proposed redactions.
