JWDT - Delivery Partner Evaluation Checklist

A public discussion aid, not a contract or a claim of completed client work.
Use it to clarify a potential partnership before agreeing an engagement.

1. Fit and scope
Which signed or planned work needs support? Which roles, deliverables and dependencies are involved?
Who owns product priorities and business acceptance?

2. End-client responsibilities
Who may contact the end client, through which channels and for which decisions?
Agree confidentiality, presentation/branding, change approval and escalation rules.
Do not assume white-label, exclusivity or unlimited access is included.

3. Engineering responsibility
Define code review, testing, acceptance evidence, technical decisions and environment ownership.
Distinguish dedicated engineering roles from allocated shared leadership.

4. Access and information
Which systems and approved records are required? Who authorizes access and revokes it?
Keep unrelated clients, credentials and private personnel material outside the engagement.

5. Collaboration and change control
Agree the decision owners, review rhythm, working constraints and blocker/escalation path.
Record changes against the exact scope/version; a draft is not approval.

6. Ownership and handover
Clarify source, configuration, document and operating responsibilities in the agreed terms.
Check licensing, dependencies, backup/recovery and the information required for transition.

7. Commercial and support boundaries
Agree allocation, inclusions/exclusions, acceptance and payment/support terms separately.
Do not substitute a checklist for legal review, a quotation or an executed agreement.

Do not include credentials, confidential client files or production records in an initial inquiry.
Discuss a partnership at https://jwdt.biz.id/?interest=Engineering%20partnership#contact