Enterprise Client Onboarding Protocol

Document ID: WBL-OB-ENT-[ID]-v1.0 Client Organization: [CLIENT LEGAL NAME] Engagement Name: [PROJECT / PROGRAM NAME] Webility Account Director: [NAME] — [EMAIL] — [PHONE] Date: [DATE] Contract Reference: WBL-MSA-[ID]-v1.0 + WBL-SOW-[ID]-v1.0

Purpose: This protocol governs the structured onboarding process for enterprise-tier engagements at Webility. It supplements the standard Kickoff Checklist (WBL-OB-KC) and Client Welcome Packet (WBL-OB-WP) with enterprise-specific requirements: stakeholder governance, approval workflows, security and compliance onboarding, escalation matrices, and multi-jurisdiction coordination.

Part 1 — Stakeholder Governance

1.1 Stakeholder Map

Enterprise projects frequently involve multiple layers of authority. Map all relevant stakeholders before the project begins to prevent approval bottlenecks, contradictory direction, and late-stage stakeholder surprises.

1.2 RACI Matrix — Key Project Decisions

(RACI: Responsible / Accountable / Consulted / Informed)

1.3 Approval Workflow

Standard approval process for deliverable submissions:

Total maximum review cycle per deliverable: [15] business days (standard). Longer cycles must be agreed in writing and adjust the project timeline accordingly.

Escalation: If the review cycle exceeds [15] business days without resolution, either Party may escalate to the designated Escalation Contacts in Section 1.4.

1.4 Escalation Matrix

Part 2 — Procurement & Commercial Onboarding

2.1 Procurement Requirements

Enterprise organizations often have procurement processes that must be completed before work begins. Please confirm the following:

2.2 Invoice & Payment Configuration

Part 3 — Legal & Compliance Onboarding

3.1 Applicable Legal Frameworks

Based on the Client's operating regions and the nature of this engagement, confirm which legal frameworks apply and the designated compliance contact:

3.2 Data Classification

For any engagement involving the processing of data:

3.3 Data Processing Agreement (DPA)

A Data Processing Agreement is required for any engagement where Webility processes personal data on behalf of the Client.

DPA status:

☐ Webility standard DPA is acceptable — [attach as Schedule to MSA] ☐ Client requires their own DPA — send to: legal@webility.local for review ☐ Not required for this engagement

Sub-processor disclosure: Webility's current list of sub-processors (third-party tools that may process Client data) is available at [webility.local/sub-processors] and will be included in the DPA Schedule.

3.4 Multi-Jurisdiction Compliance Notes

If the Client operates or the project will serve users across multiple jurisdictions:

Operating regions and applicable requirements:

Part 4 — IT Security Onboarding

4.1 IT Security Assessment

To be completed with the Client's IT Security or CISO function before any technical work begins or system access is granted.

4.2 Change Management Process

For enterprises with formal change management:

4.3 Security Contact

Part 5 — Communication & Governance Structure

5.1 Governance Meetings

For enterprise engagements, we recommend the following governance structure:

5.2 Reporting

Webility will provide the following reports on an enterprise engagement:

5.3 Document Management

Part 6 — Multi-Region & Multi-Market Coordination

6.1 Regional Stakeholders

If the engagement involves teams or markets in multiple countries, map regional stakeholders:

6.2 Regional Delivery Requirements

6.3 Translation & Localization

If content must be provided in multiple languages:

• Translation responsibility: ☐ Client provides translated content ☐ Agency to manage translation (via third-party, quoted separately) ☐ Split — see notes
• Languages required: _______________________________________________
• Translation review / approval: Who approves translated content on the Client side?
• Language variants: (e.g., Canadian French vs. European French; Brazilian Portuguese vs. European Portuguese)
• Right-to-left (RTL) languages: ☐ Required — languages: _______________ ☐ Not required

Part 7 — Onboarding Completion Sign-Off

Both Parties confirm that:

(a) All stakeholders have been identified and mapped; (b) Approval workflows and escalation paths are agreed; (c) Procurement requirements have been addressed; (d) Legal and compliance requirements are documented and being addressed; (e) IT security access requirements have been communicated to both IT teams; (f) Multi-region requirements have been identified and scoped; (g) The project may now proceed to the Kickoff Meeting.

Outstanding items before kickoff (if any):

Webility LLC — Account Director

Signature: ___________________________ Date: _______________ Name: ___________________________

[CLIENT LEGAL NAME] — Project Owner

Signature: ___________________________ Date: _______________ Name: ___________________________ Title: ___________________________

[CLIENT LEGAL NAME] — Executive Sponsor (if required)

Signature: ___________________________ Date: _______________ Name: ___________________________ Title: ___________________________

Webility — WBL-OB-ENT-[ID]-v1.0 | Enterprise Onboarding Protocol Confidential — for authorized project personnel only.