Use the annex as part of the signed delivery record
Complete this annex after the buyer opens each credential URL and reviews the proposed person. Attach it to the proposal or statement of work. Repeat it for substitutes and material allocation changes.
Document and decision details
Buyer organization: __________________________________________
Supplier organization: ________________________________________
Project or workstream: ________________________________________
Proposal and annex version: ___________________________________
Buyer reviewer: ______________________________________________
Technical reviewer: __________________________________________
Review date and time zone: ___________________________________
Required credential recheck date: _____________________________
Named-person and live Adobe record
| Field | Supplier record | Buyer verification |
|---|---|---|
| Named person | Full legal or verified working name | ________________________________ |
| Employment relationship | Employee, contractor, or disclosed delivery partner | ________________________________ |
| Proposed role | Exact project role and decision authority | ________________________________ |
| Live Adobe URL | Full Adobe-hosted validation address | ________________________________ |
| Credential | Exact Adobe Commerce credential title | ________________________________ |
| Role and level | Role and Professional, Expert, or Master as displayed | ________________________________ |
| Status | Current status on the Adobe page | ________________________________ |
| Issue and expiry | Exact issue and expiry dates where shown | ________________________________ |
| Last live check | Date, time, time zone, and reviewer | ________________________________ |
Evidence limit: a credential verifies an Adobe award for the holder. It does not verify employment, assignment, capacity, start date, project results, code quality, or delivery authority. Record those separately below.
Location, hours, capacity, and start assumption
Allocation percentage or hours each week: ______________________
Other known commitments: _____________________________________
Allocation start and review date: _______________________________
Work location and time zone: __________________________________
Normal working hours in local time: ____________________________
Required buyer overlap and shared time zone: __________________
Holiday and on-call boundary: _________________________________
Earliest start assumption: ____________________________________
Conditions before start: ______________________________________
Ramp plan and expected full allocation date: _________________
Access or onboarding dependencies: ____________________________
Recent work that matches the proposed route
| Evidence field | Record for the named person |
|---|---|
| Buyer route | Upgrade, rescue, B2B, ERP or PIM integration, storefront, performance, operations, or another defined route: ________________________________ |
| Relevant project | Client or anonymized reference, public case URL where available, and delivery dates: ________________________________________________ |
| Named person's work | Modules, systems, decisions, code, review, testing, or operational responsibility completed by this person: __________________________ |
| Outcome source | Client reference, public case, repository evidence, architecture record, or supplier statement: _____________________________________ |
| Evidence boundary | What the source does not prove about the new project: ______________ |
Do not attach a company case to every candidate by default. Record whether the named person worked on it and what they did. If that cannot be verified, describe the case as company evidence and mark the candidate's direct contribution as not evidenced.
Reviewer record for role fit
Candidate interview date: ____________________________________
Supplier interviewer: ________________________________________
Buyer interviewer: __________________________________________
Topics and route questions: __________________________________
Exercise, code sample, or architecture discussion: ____________
Reviewer and review method: __________________________________
Result: ☐ Accepted ☐ Accepted with conditions ☐ More evidence needed ☐ Rejected
Conditions or evidence gaps: __________________________________
Replacement evidence and approval
| Control | Agreed rule |
|---|---|
| Notice | Minimum notice period and permitted urgent exception: __________________ |
| Evidence floor | Replacement must meet the same named credential, route evidence, interview, availability, and working-hour checks unless the buyer accepts a written exception. |
| Handover | Required overlap, documentation, repository transfer, open-risk review, and knowledge handoff: _____________________________________ |
| Buyer approval | ☐ Written approval required before allocation ☐ Buyer may interview ☐ Buyer may reject |
| Commercial effect | Rate, delay, replacement cost, and service-credit treatment: __________ |
Default control: no unreviewed person inherits the accepted status of the original candidate. Create a new annex record and repeat the live badge, role-fit, allocation, and route-evidence checks.
Named-person acceptance
Do not sign until the open fields are explicit
☐ Accepted for the named role ☐ Accepted with listed conditions ☐ Proposal-needed ☐ Not accepted
Buyer approver: ____________________ Date: ____________________
Supplier acknowledgement: ____________________ Date: ____________________
Conditions and attached evidence: ____________________________________________
Use with the live Adobe record
- Adobe: How to get certified. Adobe explains how holders open their badge verification page from Active certifications.
- Adobe Commerce Certification Overview. Use it to confirm the current role and level map.
- Adobe badge verification checklist. Use it before copying the credential result into this annex.
- Adobe Commerce role-credential map. Use it to separate role fit from credential level.
Legal boundary: this is a procurement worksheet, not legal advice or a substitute for buyer counsel. Adapt approval, privacy, worker-classification, security, and employment terms to the contract and jurisdiction.