Uplef - Web Design & Branding

Policy Version: 1.6
Effective Date: 6^th August 2025

1. Introduction

UPLEF FZ LLC (“Company,” “we,” “us,” “our“) is committed to delivering high-quality digital solutions in a timely and professional manner. This Delivery Policy (“Policy“) outlines our standard procedures for project delivery, including timelines, client responsibilities, and the acceptance process.

This Policy is an integral part of our contractual agreements and Terms and Conditions. By engaging our services, you (“Client,” “you,” “your“) acknowledge and agree to the terms outlined herein.

2. Definitions

• Project:The scope of work as defined in the approved Proposal, Statement of Work (SOW), or Service Order.
• Deliverable:A distinct, specified item within the Project that is to be provided to the Client (e.g., design mockups, a functional module, source code, final deployed website).
• Milestone:A pre-defined point in the project timeline marking the completion of a key set of Deliverables, often tied to a payment.
• Deployment:The process of making the final Deliverable (e.g., a website or application) live and accessible to its end-users.
• Acceptance:The Client’s formal approval that a Deliverable or the final Project meets the agreed-upon specifications.

3. Project Initiation & Onboarding

Upon receipt of a signed agreement and any required initial payment, the Project is officially initiated. The Company will:

• Assign a dedicated project manager or point of contact.
• Provide access to necessary collaboration tools (e.g., project management software, communication channels).
• Schedule a project kick-off meeting to align on goals, timelines, and communication protocols.

4. Delivery Timelines & Estimates

• Estimates, Not Guarantees:Any timelines or deadlines provided in proposals are estimates based on the project scope and resources available at the time. While we make every reasonable effort to meet these estimates, they are not guaranteed fixed dates.
• Factors Affecting Timelines:Project timelines may be adjusted due to:
  • Client-Dependent Delays:Delays in providing content, feedback, approvals, or required information (see Section 5).
  • Scope Changes:Changes or additions to the initially agreed-upon scope (“Scope Creep”) will necessitate a revised timeline and may incur additional costs, governed by a formal Change Request.
  • Unforeseen Technical Challenges:Encountering unexpected complexities during development.
  • Third-Party Dependencies:Delays from external API providers, payment gateway integrations, or other third-party services.

5. Client Responsibilities for Timely Delivery

To ensure the Project remains on schedule, the Client agrees to:

• Provide all necessary materials, content, logos, brand assets, and access credentials in a timely manner and in the formats we request.
• Appoint a single primary representative with the authority to provide feedback and approvals.
• Provide clear, consolidated, and timely feedback during designated review periods. Feedback must be provided within the agreed-upon timeframe (typically 2-5 business days per review cycle) to avoid project delays.
• Communicate any issues or concerns promptly.

6. The Delivery & Acceptance Process

6.1. Staging Environment Delivery:
The completed Project or key Milestones will be delivered to a staging environment for the Client’s review. This is a private, non-public version of the solution where testing and review can be conducted.

6.2. Testing Period:
The Client will have a predefined period (typically 5-7 business days) to thoroughly test and review the Deliverable against the agreed-upon specifications and requirements outlined in the Proposal/SOW.

6.3. Submission of Feedback:
The Client must provide clear, written feedback (via email or project management tool), listing any identified bugs or deviations from the spec. Feedback is categorized as:

• Bug Fixes:Errors where the Deliverable does not function as specified.
• Revisions:Changes or additions that were not part of the original agreed-upon scope.

6.4. Revisions and Fixes:

• The Company will address all valid Bug Fixesat no additional cost.
• Requests for Revisionsthat fall outside the original scope will be treated as a Change Request, requiring a separate quotation and potentially adjusting the delivery timeline.

6.5. Formal Acceptance:

• Upon successful testing and resolution of all bugs, the Client must provide formal written acceptance(e.g., via email).
• Acceptance confirms that the Deliverable meets the requirements and triggers the next step, which may be the final payment invoice or proceeding to the launch phase.

7. Final Deployment (Go-Live)

Once final acceptance and payment (if applicable) are received, the Company will schedule the Deployment to the production (live) server. The Company will:

• Coordinate the launch process.
• Perform final checks post-launch to ensure functionality.
• Provide any necessary post-launch support as per the agreed support terms.

8. Delivery of Assets & Project Closure

Upon final payment and project closure, the Company will deliver the following to the Client, unless otherwise specified:

• Full access to the completed website/content management system.
• Source code for developed software (as per the licensing terms in the contract).
• Project documentation, login credentials, and any other relevant digital assets.
• A summary of third-party licenses and components used (Software Bill of Materials).

9. Policy Amendments

UPLEF FZ LLC reserves the right to modify this Delivery Policy at any time. Changes will be communicated to active clients and will be effective for all new projects initiated after the communication date.

10. Contact Information

For any questions regarding this Delivery Policy, please contact us at:

UPLEF FZ LLC
Email: [email protected]
Phone: +971 52 949 1380