Delivery Policy

Last updated: August 2025

1. Purpose

This Delivery Policy explains how RBConsult plans, executes, and hands over digital deliverables. It should be read with our Terms and Conditions, Refund Policy, and the project’s Statement of Work (SOW).

2. Project Timelines

Indicative delivery windows vary by scope and complexity:

  • Small projects: 2–4 weeks
  • Medium projects: 4–8 weeks
  • Large projects: 8–16 weeks
  • Enterprise projects: custom timeline

Final timelines are defined in the SOW after requirements analysis. Timelines are estimates and exclude third-party review or publication times (e.g., App Store/Play review).

3. Milestones and Deliverables

Projects are typically phased with milestone outputs:

  • Discovery and planning
  • Design and prototyping
  • Development
  • Testing and quality assurance
  • Deployment and launch

Each milestone has defined deliverables and acceptance criteria in the SOW. Change requests may adjust scope, budget, and schedule.

4. Delivery Methods

We deliver via one or more of the following, as agreed in the SOW:

  • Source code in Git repositories
  • Deployments to client infrastructure
  • App store submissions (iOS App Store, Google Play)
  • Provisioning on cloud platforms
  • Secure file transfer for packaged builds and assets

Store approvals and third-party verifications are outside RBConsult’s control and may extend overall launch dates.

5. Acceptance Criteria

A deliverable is deemed accepted when any of the following occurs:

  • It meets the specifications in the SOW and agreed test outcomes
  • Client provides written acceptance
  • No material feedback is received within 5 business days of delivery

Post-acceptance issues are handled through the defect remediation window or as new change requests, depending on scope.

6. Dependencies and Client Obligations

The client agrees to provide timely:

  • Access to required systems, accounts, and credentials
  • Brand assets, content, product data, and required legal texts
  • Stakeholder feedback and approvals within agreed time frames

Delays in the above may pause work and extend the schedule. Third-party outages, reviews, and policy changes may also impact delivery dates.

7. Delays, Extensions, and Force Majeure

If delay is likely, we will notify you and propose a revised plan. The timeline may extend due to:

  • Client-side delays or scope changes
  • Third-party approvals, audits, or reviews
  • Infrastructure changes or external dependencies
  • Force majeure events

Rush delivery, if offered, may require additional fees and is subject to feasibility.

8. Handover and Documentation

Upon delivery or launch, we provide, as applicable:

  • Source code access and build artifacts
  • Environment variables and deployment instructions
  • Admin credentials transfer and role assignments
  • Operational runbook or notes agreed in the SOW

9. Post-Delivery Support

Unless otherwise specified in the SOW:

  • 30-day defect remediation window for in-scope deliverables
  • Knowledge transfer and basic documentation handover
  • Optional maintenance contracts for ongoing updates and monitoring

New features or enhancements are handled via change requests and may require separate estimates and timelines.

10. Communication

We maintain regular communication through agreed channels:

  • Weekly progress updates
  • Milestone completion notifications
  • Email support during business hours
  • Scheduled calls as needed

11. Contact

For delivery-related inquiries:
Email: info@rbconsult.bh
Phone: +973 3958 7730