QuickQuid

Service Delivery & Fulfilment Policy

Effective date: 6 October 2026

Effective date: 6 October 2026

QuickQuid is a marketplace for customised digital professional services. We do not ship physical goods.

1. How fulfilment works

Each project has its own scope, deliverables, milestones, timeline and acceptance criteria recorded in the applicable Project Pact.

A typical project follows this flow:

Brief → Agreement → Funding → Work → Delivery → Client Review → Acceptance / Revision → Handover → Completion

2. Delivery timeline

There is no single shipping or delivery period for all QuickQuid projects because projects are customised services.

The Client must be shown the applicable project or milestone timeline before committing to that Project Pact or funded milestone.

If the scope, timeline or price changes materially, the parties should approve a Scope Change before the changed work becomes part of the agreed project.

3. Digital Delivery Package

A Freelancer may submit a Delivery Package containing, as applicable:

  • completed deliverables;
  • files or repository references;
  • evidence against acceptance criteria;
  • implementation notes;
  • known limitations;
  • setup or usage instructions; and
  • approved deviations or Scope Changes.

4. Client review

The Client should review the Delivery against the effective Project Pact and acceptance criteria.

Available outcomes may include:

  • Accept;
  • Request Revision;
  • Partial Acceptance where the Project Pact allows it; or
  • Raise a Dispute.

A revision should identify the agreed requirement or acceptance criterion that needs correction.

5. Delays

A delay may result from Freelancer performance, Client input, third-party services, approved Scope Changes or other project dependencies.

Where a delay changes a contractual milestone or project deadline, the change should be recorded rather than silently editing an approved commercial commitment.

6. Client inputs

Clients are responsible for providing agreed information, approvals, access, content or other dependencies on time. A Client-caused delay may affect the project timeline where the Project Pact or an approved Scope Change records that consequence.

7. Handover

Where required, project fulfilment includes a structured handover. Handover may include:

  • final accepted files;
  • source/repository access;
  • deployment/setup information;
  • architecture or context notes;
  • dependency information;
  • known issues and outstanding work;
  • ownership-transfer steps; and
  • protected-resource or credential-transfer requirements.

A project may remain incomplete until required handover is finished.

8. Service problems

For missed delivery, material non-performance, disputed acceptance or other fulfilment problems, contact contact@quickquid.in and include the Project ID and relevant milestone/Delivery details.

We aim to acknowledge support requests within 2 business days.