MENTARA
Submit a requirement
Legal

How and when the work is delivered.

MENTARA ships no physical goods. This sets out what delivery means for professional services — when an engagement starts, what you receive, and what makes a date move.

Contact us Explore
Scope

MENTARA delivers professional services: software engineering, platform implementation, security, data and analytics work, and workforce solutions. Nothing is dispatched, couriered or physically shipped, so there is no shipping address, no tracking number and no delivery charge.

What is delivered is work — code, configuration, documentation, assessments, decision records and, in workforce engagements, people. This page explains when that starts, how it arrives, and what happens when a date slips.

What delivery means

Delivery, by the kind of work.

The specific deliverables and dates for your engagement are defined in your statement of work. These are the shapes they take.

01Engineering and platform workDelivered continuously into environments you control — your repositories, your cloud accounts, your platform tenancies. There is no handover moment where code arrives; it is in your systems from the first increment. Access is set up during mobilisation.
02Assessments and discoveryDelivered as a written report and a working session, on the date agreed in the statement of work. These are the most commonly fixed-scope, fixed-date engagements we run, and typically complete in two to six weeks.
03Managed services and runDelivered as an ongoing service against agreed coverage hours and response commitments, starting on the service commencement date. What is covered, and what falls outside agreed hours, is stated in the engagement document rather than assumed.
04Workforce engagementsDelivered as named people starting on an agreed date. Candidate submission timelines, notice periods on their side and right-to-work verification all sit between agreement and start, and are the usual reason a start date moves.
05Documentation and the decision recordDelivered throughout, not at the end. Ownership sits with you during the engagement rather than on final payment, so there is no point at which we are holding documentation you have paid for.
Getting started

From signature to work beginning.

Mobilisation is where most avoidable delay lives, and almost all of it is access and decision-making rather than availability.

  1. 01 Engagement document signed

    Scope, model, named team, commercial terms, acceptance criteria and exit terms are agreed in writing. Nothing starts before this, and we do not begin work against a verbal go-ahead and reconcile later.

    • Acceptance criteria written before work, not after
    • Exit terms agreed at the start

  2. 02 Mobilisation, within 10 business days

    The named team is confirmed, governance and decision rights are set, environments and access are requested, and the handover package that will apply at exit is defined. This runs in parallel with your access provisioning.

    • Decision rights explicit before delivery
    • Standard target; larger engagements may agree longer

  3. 03 Delivery begins

    Work starts on the commencement date in the statement of work, subject to access being in place. Where access is not yet available, we say so rather than billing time against a blocked start.

    • Blocked starts are flagged, not quietly charged

  4. 04 Reporting against the plan

    Progress is reported at the agreed cadence against the plan and the acceptance criteria. Where a date is going to move, you hear it at the point we know rather than at the point it is missed.

    • Bad news travels at the same speed as good
What you receive

The handover package.

Defined at mobilisation rather than negotiated at exit, so that leaving is a known quantity from the first week.

  • The deliverables themselves, in the environments and repositories you control.
  • Documentation sufficient for another team to operate and change what was built — assessed against that standard, not against whether a document exists.
  • The decision record: what was decided, when, by whom and on what basis.
  • Credentials, access and administrative ownership of anything created for you, transferred in full.
  • Knowledge transfer as defined at mobilisation, delivered inside the engagement or the notice period rather than sold separately afterwards.
  • Outstanding risks and known defects, written down honestly, including the ones that reflect badly on us.
Delays

What actually moves a date, and who owns it.

The single largest cause of slippage in this kind of work is decision latency on the client side. Work that waits four days for an answer is not paused; it is being paid for. Our estimates state the decision cadence they assume, so when a date moves, it is possible to see why rather than argue about it.

The others are familiar: environment and access provisioning taking longer than planned, third-party dependencies outside either party's control, a scope change accepted through change control, and — occasionally — us being wrong about the estimate. We name that last one when it applies rather than filing it under an ambiguous heading.

Where a date is at risk, you are told when we know, with the reason and the revised date. Where a delay is ours, the remedy is in your contract; where it is a dependency, we say what we need and from whom. We do not treat a missed date as an opportunity to raise a change request that recovers margin.

Where we work

Remote delivery, and working across jurisdictions.

Delivery is primarily remote, from India, working to the hours agreed in the engagement document. Coverage hours and response commitments are agreed rather than assumed, and work outside them is quoted separately as the engagement and pricing page sets out.

On-site presence is available where the work genuinely needs it. It is agreed in advance, with the cost stated up front rather than assumed and billed afterwards.

Because delivery is remote, work reaches clients in any jurisdiction we can lawfully contract with. Contracting entity, invoicing currency, applicable taxes and any withholding obligation are confirmed in the proposal. For workforce engagements specifically, employment classification, right-to-work verification and local statutory obligations are addressed per market — the arrangement that is correct in India is not the one that is correct in the UK or the US.

07

The framework behind this.

Related

This page states delivery commitments. The delivery framework page explains the method they come from — how work is structured, governed and handed over — and the engagement and pricing page covers the commercial side, including what happens when scope changes mid-flight.

If an engagement ends early, the refunds and cancellation policy sets out what is charged and what comes back, including the requirement that handover happens inside the notice period rather than after it.

Read the delivery framework

Ask what delivery would look like for your work.

Share the business context, constraints and expected outcome. MENTARA will identify the relevant accountable route.

Submit your requirement

One partner. One plan. Measurable outcomes.