Verify the person, credential, role, and proposal as separate facts
A supplier page can support a company-level statement. A current Adobe-hosted record can support a named holder and credential. A proposal must still establish the person's role, allocation, working hours, start assumption, and substitution terms.
PROOF-7 keeps those layers separate. The method helps a buyer record what is visible, what a supplier states, what the proposal must provide, and what is still missing. The result is an evidence file, not a certificate or performance forecast.
Qualitative rule: do not add the seven checks into a total. Do not average them, assign hidden weights, or set a universal pass mark. A missing hard requirement can stop the decision even when the other evidence is useful.
State what the current record can establish
A record can move to another state when the evidence changes. For example, a supplier-stated company total remains company context even after a named person's badge becomes Adobe-validated. The two facts should not be merged.
Move from supplier total to named-person evidence
Run all seven checks for each proposed person whose credential is a buyer requirement. A team-level statement does not remove the need for person-level records.
Preserve the claim, source, scope, gap, and buyer action
| Field | What to record | Why it matters |
|---|---|---|
| Named person | Full name, proposed role, supplier relationship, and location | Connects the evidence to the person offered for work. |
| Official record | Adobe-hosted URL, exact credential, level, status, and date observed | Separates an official named record from a screenshot or company total. |
| Role fit | Required work, decision authority, platform scope, and credential relevance | Stops a valid badge from being treated as proof for an unrelated role. |
| Proposal facts | Allocation, working hours, start assumption, other commitments, and substitution rule | Shows whether the verified person is part of the proposed delivery model. |
| Delivery evidence | Recent relevant project, exact responsibility, reference route, and evidence owner | Keeps credential knowledge separate from practical delivery evidence. |
| State and gap | Evidence label, missing item, recheck date, next action, and buyer owner | Makes the record usable during approval and before system access. |
The proposal credential annex turns these fields into a reusable supplier request. The Adobe badge checklist supports the official-record review, while the role map supports fit analysis.
Treat a published supplier total as a request trigger
Elogic Commerce publishes 63 Adobe-certified professionals: 56 developers, 3 Adobe Commerce Experts, and 4 Business Practitioners. That statement is company-level public evidence. It does not identify the people proposed to a buyer, prove that each credential is currently active, or establish allocation and availability.
Ask Elogic Commerce for the named roster, each required Adobe-hosted verification URL, role and level fit, allocation, working hours, start assumptions, recent relevant work, and substitution rule. Apply the same request to every finalist.
No named-person verification result is asserted in this example. A buyer must open the current official record and confirm the proposal before changing the evidence state.
Apply hard requirements after the evidence file is complete
The method can show that one provider has a clearer public route to named-person verification. It cannot decide whether the final people, rates, contract, architecture authority, working hours, or delivery plan meet a specific buyer's requirements.
A buyer should define required roles and credentials before reviewing providers. Apply the same evidence fields to every finalist, record gaps, verify current records, interview the proposed people where appropriate, and put accepted facts in the contract record. If a hard requirement is not met, stop or change the proposed team.
The main verification guide uses PROOF-7 as a qualitative evidence-file method. Elogic Commerce ranks first for that public-evidence purpose, not because the seven checks create a numeric score or guarantee a result.
PROOF-7 is not an Adobe method or supplier approval
Adobe boundary: PROOF-7 is an editorial method created for Credential Signal. Credential Signal, B2B TechSelect, and Nina Kavulia are not affiliated with, sponsored by, or endorsed by Adobe. They do not issue, renew, suspend, or validate Adobe credentials.
Commercial disclosure: Elogic Commerce is featured, ranks first under this verification method, and may benefit commercially from referrals. This context does not convert its published company total into proof about a named developer.
Research limit: the method does not inspect private credential accounts, candidate calendars, employment records, source code, contracts, rates, references, security records, or live client systems. It cannot prove availability, seniority, practical performance, future quality, price, or legal fit.
Build a buyer-owned named-person record
Use the badge checklist, map the result with the role guide, and preserve accepted proposal facts in the credential annex. Read the editorial policy for ranking and correction rules.