Define scope
Identify the product, producer, facility, claims, batches, and standard version being assessed.
No BrainerCertified®
Evidence before claims
This center explains how certification is intended to work, what records support a decision, how ongoing oversight is handled, and what the public can expect to see.
Methodology
Every decision should connect a defined product scope to traceable evidence and a documented review.
Identify the product, producer, facility, claims, batches, and standard version being assessed.
Gather controlled records for identity, safety, quality, traceability, testing, and consumer-facing claims.
Separate evidence preparation from decision-making and record conflicts, findings, and corrective actions.
Show status, scope, dates, standard version, and supporting disclosure detail through the product record.
Governance
Commercial activity and evidence preparation should not determine the certification outcome.
Reviewers should disclose relevant interests, recuse when necessary, and document the resolution.
Qualifications and assigned scope should match the technical evidence being evaluated.
Decisions, evidence versions, changes, and access should remain traceable and auditable.
Ongoing oversight
Public trust depends on keeping the approved product and its evidence current after the initial decision.
Review scheduled records, complaints, tests, and material changes.
Reassess the defined scope before the certification period ends.
Evaluate product, process, facility, ownership, or claim changes before continued use of the mark.
Restrict the mark when requirements are no longer met and publish the current status.
Appeals and complaints
Public disclosures
Empty or pending fields are disclosed plainly instead of being filled with unverified credibility signals.
Put the framework to work