Delivery Policy

Last updated: 3 June 2026

This Delivery Policy explains how Elda Consulting Pty Ltd ("ELDA Consulting", "we", "us", or "our") delivers B2B technology consulting, cloud, web application, mobile application, integration, proof-of-concept, delivery support, documentation, training, and related professional services.

ELDA Consulting does not sell physical goods through this website. Delivery refers to professional services, digital deliverables, project outputs, documentation, meetings, workshops, source code, deployments, and handover materials.

1. Delivery Method

Services and deliverables may be provided through one or more of the following methods:

• remote consulting sessions, calls, workshops, demos, or meetings;
• email communication and written recommendations;
• shared documents, reports, architecture notes, plans, or training material;
• source code repositories, pull requests, commits, or release packages;
• cloud environments, staging environments, production deployments, or configuration updates;
• handover sessions, documentation, and agreed support channels.

2. Delivery Time Frames

Delivery time frames depend on the agreed scope, project complexity, dependencies, approvals, and availability of client stakeholders. Unless otherwise stated in writing, delivery time frames are confirmed in the applicable proposal, statement of work, project plan, or written agreement before work begins.

Typical delivery examples include:

• consulting calls or advisory sessions: scheduled by agreement;
• discovery workshops or technical reviews: usually delivered over agreed workshop or review dates;
• proof-of-concepts and prototypes: delivered according to agreed project milestones;
• web, mobile, cloud, and integration projects: delivered according to an agreed project plan and acceptance process;
• documentation, training, and handover: delivered after the relevant project phase or milestone.

3. Client Inputs and Approvals

Delivery may depend on your timely provision of information, system access, test data, credentials, stakeholder availability, feedback, approvals, and third-party service readiness. Delays in these inputs may delay delivery dates and milestones.

4. Acceptance of Deliverables

Deliverables are reviewed against the agreed scope, acceptance criteria, and project records. If you identify an issue, you must notify us within the review period agreed in writing, or otherwise within a reasonable time after delivery.

5. No Physical Dispatch

No physical shipping, courier dispatch, or postal delivery is provided unless expressly agreed in writing for a specific project.

6. Contact Us

Back to home