How Engagement Works

From requirement to delivery

Organisations approach WARA with different needs. One may require a defined service for a single location, another may need a production order completed to specification, and a third may be exploring a recurring arrangement involving multiple workers or service providers.

These requirements need different levels of planning. WARA’s intended engagement model provides a common process for understanding the requirement, assessing whether it can be fulfilled, agreeing on responsibilities, and coordinating the work.

An initial enquiry is an opportunity to understand a potential assignment. It does not, by itself, confirm provider availability, establish a delivery commitment, or create an agreement to proceed.

The engagement process

1. Submit an enquiry

The organisation describes the requirement and provides enough information for an initial assessment.

Useful details include:

• The organisation’s name and contact information.
• The service, product, or operational outcome required.
• The location where the work must take place or the goods must be delivered.
• Expected quantity, frequency, schedule, or deadline.
• Required skills, equipment, materials, facilities, or other resources.
• Applicable quality, safety, regulatory, or documentation requirements.
• The expected budget or commercial constraints, where known.

Not every enquiry will require every detail at the outset. Additional information may be requested as the requirement becomes clearer.

2. Define the scope

The requirement is translated into a scope that both parties can understand.

Depending on the assignment, this may specify:

• The work to be performed or the products to be supplied.
• Deliverables, quantities, specifications, and expected outcomes.
• Work location, operating hours, milestones, or delivery dates.
• Responsibilities of the organisation, WARA, and any assigned provider.
• Required reporting, communication, documentation, and acceptance criteria.
• Activities explicitly excluded from the assignment.

A well-defined scope reduces the risk of misunderstandings about what has been agreed and what constitutes satisfactory completion.

3. Assess feasibility

Before making a commitment, the requirement must be assessed against the capabilities and resources needed to fulfil it.

The assessment may consider:

• Availability of suitable workers, service providers, or production capacity.
• Relevant skills, experience, qualifications, and authorisations.
• Geographic coverage and travel or logistics requirements.
• Equipment, materials, infrastructure, and other resource needs.
• Time constraints, dependencies, and scheduling.
• Quality expectations, safety measures, and applicable regulations.
• Commercial viability and the cost of delivery.

The outcome may be to proceed, request more information, revise the scope, propose a phased approach, or decline the requirement. A requirement should not be treated as feasible merely because it falls within a listed service domain.

4. Agree on the commercial and operational terms

If the requirement appears feasible, the parties establish the terms under which the assignment may proceed.

The agreement should address the matters relevant to the particular engagement, including:

• Scope and deliverables.
• Price, payment schedule, and applicable taxes.
• Start date, milestones, delivery schedule, or duration.
• Responsibilities and points of contact.
• Quality standards and acceptance procedure.
• Safety, compliance, confidentiality, and data-handling obligations, where applicable.
• Procedures for changes, delays, cancellation, complaints, or rework.
• Any specific conditions governing the use of subcontractors or other providers.

The formality of the agreement should reflect the scale and risk of the work. A simple assignment may need a concise written confirmation, while a recurring, production, multi-provider, or regulated engagement may require a more detailed agreement.

No work should be assumed to be authorised until the necessary terms and approvals have been confirmed.

5. Confirm the assignment

Once the scope, feasibility, responsibilities, and commercial terms are settled, the parties confirm whether to proceed.

Where relevant, this stage includes confirming the assigned provider, schedule, required resources, access arrangements, and any prerequisites that must be completed before work begins.

Provider selection and assignment depend on suitability and availability. An enquiry or preliminary discussion does not guarantee that a particular provider will be available.

6. Coordinate execution

During delivery, communication and coordination should follow the arrangements agreed for the assignment.

Depending on its nature, this may include:

• Confirming schedules and operational instructions.
• Coordinating the organisation with the assigned provider.
• Tracking agreed milestones or production quantities.
• Communicating material changes, delays, or emerging risks.
• Escalating issues that require a decision from the organisation.
• Maintaining relevant work records and delivery evidence.

The coordination effort should be proportionate to the assignment. A single service visit does not require the same controls as a recurring service involving several locations or a bulk production order.

7. Verify quality and complete handover

Completion should be assessed against the agreed scope and acceptance criteria.

For a service assignment, this may involve confirming that the work was performed as specified. For production, it may involve checking quantity, specifications, packaging, or other agreed requirements. For recurring services, it may involve reviewing records or performance against defined service levels.

Where a shortcoming is identified, the parties should follow the agreed procedure for correction, rework, or resolution. Completion should be recorded in an appropriate form, with any outstanding issues identified rather than treated as resolved without agreement.

8. Close the assignment

The final stage covers the administrative and commercial obligations associated with the work.

Depending on the agreement, closure may include acceptance confirmation, delivery documentation, invoice verification, payment settlement, resolution of outstanding issues, and a review of lessons relevant to future assignments.

For recurring engagements, the parties may also review performance and decide whether to continue, modify, or end the arrangement under the agreed terms.

The level of process depends on the work

Not every engagement needs the same amount of documentation or coordination.

These are planning categories, not guarantees that WARA currently has the capacity to fulfil every type of engagement.

Who does what?

Wara Systems is intended to operate the commercial engagement and Marketplace functions, including customer coordination and the organisation of suitable provider participation where applicable.

Wara KarmaYoga Foundation Trust has a separate educational and social-development role, including training, skills development, and livelihood preparation. Training activity should not be confused with confirmation that a trainee is qualified, authorised, available, or assigned to a commercial job.

The responsibilities of each party must be established for the specific engagement. Organisations should not assume that every assignment will involve the Trust, a trainee, or a particular provider.

Before you enquire

You can make the initial discussion more productive by preparing three things:

1. The outcome: What must be delivered, produced, installed, or performed?
2. The constraints: What are the location, quantity, schedule, quality, safety, and budget requirements?
3. The evidence of completion: How will you determine whether the work has been completed satisfactorily?

You do not need to have every operational detail finalised before making an enquiry. However, the more clearly the desired outcome and constraints are described, the easier it is to assess feasibility and identify the information still required.

Continue exploring

• Services for Organisations: Explore the service domains and potential engagement categories.
• Quality and Accountability: Understand the intended approach to quality, responsibilities, safety, and issue resolution.
• Work with WARA: Return to the overview for organisations.