Case-study proof methodology

Scope

This methodology governs the public presentation and promotion state of ITAD Lens case studies. It distinguishes Representative Model, Verified Deployment, and Verified Customer Result proof, and defines how scenario type, metric basis, source provenance, customer disclosure, assumptions, limitations, and evidence artifacts must be labeled so a buyer can tell product demonstration from substantiated reality.

Principles

• Assign every public case study exactly one proof level: Representative Model, Verified Deployment, or Verified Customer Result.
• Name the scenario type separately from proof level: actual, representative, or composite.
• Label every material metric as actual, illustrative, or modeled.
• Expose proof provenance, verification method, customer-disclosure state, and limitations before presenting an outcome.
• Preserve exceptions, uncertainty, and failed states rather than displaying only successful events.
• Connect each conclusion to the evidence, decision, or calculation that supports it.
• Never promote a proof level because the story is compelling, a partner is strategic, or a customer logo is available.

Limitations

• Representative Model proof does not establish actual customer deployment or performance.
• Verified Deployment establishes attributable deployment facts but does not automatically establish every claimed business outcome.
• Verified Customer Result requires actual outcome metrics, a defined result methodology, and customer permission before publication.
• Modeled economics depend on disclosed assumptions and are not guarantees, quotes, forecasts, or audited results.
• Environmental estimates require their own methodology and remain separate from verified physical disposition evidence.