Quality and Accountability

Learn how WARA’s intended engagement model defines quality expectations, responsibilities, safety requirements, issue resolution, acceptance and accountability for work delivered to organisations.

Reliable work requires more than assigning a worker or accepting an order. Organisations and providers need a shared understanding of the required quality, who is responsible for each part of the work, how completion will be checked, and how problems will be addressed.

Quality is part of the assignment

WARA’s intended work model connects demand with assignment, execution, quality checking, acceptance, payment, and work history. Each stage contributes to a reliable relationship between the organisation, the service provider, and the people carrying out the work.

Quality expectations should be defined before work begins, not introduced only after a customer reports a problem. The appropriate checks depend on the assignment. A garment production order, a household service, a technical installation, and a healthcare support assignment do not have identical requirements.

The objective is to make the expected outcome clear, assign responsibility appropriately, and create a reasonable way to determine whether the agreed work has been completed.

Define quality before delivery

Each engagement should establish quality requirements appropriate to its scope and risk.

Depending on the work, these may include:

Scope and specifications: What must be delivered, in what quantity, and to what standard?
Skills and suitability: What experience, training, qualifications, or authorisations are required?
Work procedures: Which instructions, operating procedures, or technical specifications must be followed?
Safety and compliance: What precautions, permissions, records, or regulatory obligations apply?
Inspection and verification: Who checks the work, and what evidence is needed?
Acceptance criteria: How will the organisation determine whether the result meets the agreed requirements?

These requirements should be proportionate. A simple assignment may need a short checklist and customer confirmation. A production order or recurring service may need documented specifications, inspection records, and defined escalation procedures.

Responsibilities must be explicit

Quality depends on the responsibilities of the parties involved. The exact arrangement must be agreed for each engagement rather than assumed to be identical across all services.

Participant	Responsibilities to define
Customer organisation	Explain the requirement, provide accurate specifications and necessary access or inputs, identify applicable constraints, and review the agreed deliverables.
Wara Systems	Where engaged for commercial coordination, clarify the arrangement, coordinate the relevant parties, and communicate issues within its agreed responsibilities.
Service provider or production coordinator	Accept responsibility for the work assigned to them, organise the required resources, follow the agreed specifications, and address delivery or quality issues within their scope.
Individual worker	Perform the assigned tasks within their competence and authorisation, follow applicable instructions and safety requirements, and report problems or limitations.
Quality reviewer or inspector	Where such a role is agreed and provided, check the specified aspects of the work and record the findings.

One person or organisation may perform more than one role. In other engagements, responsibility may be distributed across several parties. The agreement should identify who is accountable for delivery, who verifies quality, who can approve changes, and who handles unresolved issues.

The table describes a responsibility model, not a claim that every role is currently staffed or that WARA assumes all these responsibilities in every engagement.

Match responsibility to competence

A person should be assigned work that they are competent and authorised to perform. Training participation alone does not establish that someone is ready for every type of assignment.

The level of supervision and checking should reflect the nature of the work, the person’s demonstrated capability, and the consequences of an error.

For example:

A worker carrying out a defined task may follow established instructions and perform basic self-checks.
An independent worker may be responsible for completing an agreed job and checking the result against its specifications.
A service provider or production coordinator may organise several workers, manage resources and schedules, coordinate delivery, and arrange quality inspection.

Higher responsibility requires the ability to organise and oversee work, not simply a higher title or a certificate. Where professional qualifications, licences, or statutory authorisations are required, the applicable requirements must be verified separately.

Safety and compliance come first

Quality cannot be separated from safety. An assignment should not proceed on the assumption that a worker can perform a task merely because a customer has requested it or a provider has expressed interest.

Before confirming work, the parties should identify relevant requirements such as:

Professional qualifications, licences, or authorisations.
Site access, equipment, protective measures, and operating procedures.
Restrictions on the tasks an individual may perform.
Applicable laws, sector requirements, and customer policies.
Privacy, confidentiality, and responsible handling of customer information.
Procedures for stopping work or escalating an unsafe or non-compliant situation.

Healthcare, electrical work, security, construction, and other safety-sensitive services may require additional controls. The applicable requirements depend on the actual task and jurisdiction.

If essential competence, authorisation, equipment, or safety arrangements cannot be established, the assignment should be revised, deferred, or declined.

Check, accept, and record the work

A completed task should be assessed against the criteria agreed at the start.

A practical quality cycle may follow these steps:

Confirm the requirement: Keep the agreed scope and specifications available to the people doing and checking the work.
Perform the work: Follow the agreed instructions, schedule, and safety requirements.
Check the result: Carry out the appropriate self-check, inspection, test, or customer review.
Record the outcome: Document completion and any material findings in a form appropriate to the assignment.
Resolve discrepancies: Identify work that does not meet the agreed criteria and follow the agreed correction or rework process.
Confirm acceptance: Record whether the deliverable has been accepted and whether any agreed actions remain outstanding.

The form of evidence will vary. It may be a customer confirmation, a completed checklist, a test result, an inspection record, a delivery note, or another agreed document.

Acceptance should not be confused with a claim that every aspect of the work has been independently certified. Verification must be limited to the checks actually performed and the criteria agreed.

Handle problems through an agreed process

Even a carefully planned assignment may encounter delays, defects, misunderstandings, or changes in requirements. The parties should know how to report and resolve these issues.

An engagement may define:

The person or channel through which an issue should be reported.
The information needed to understand the problem.
Who decides whether work should pause while the issue is investigated.
Who is authorised to approve a change in scope or schedule.
How correction, rework, replacement, or other remedies will be handled.
How unresolved disagreements will be escalated.
Whether additional costs or time are involved and how they will be agreed.

A reported problem should be assessed on its facts. The purpose of an issue-resolution process is to establish what happened, determine the applicable responsibilities, and agree on an appropriate response.

The process should not presume that every defect is the worker’s fault or that WARA is automatically responsible for every outcome. Responsibility depends on the agreed scope, the parties’ actual roles, and the circumstances of the case.

Accountability across recurring work

For recurring assignments, quality should be reviewed over time rather than assessed only at the end of each individual task.

Where suitable records and review arrangements exist, the parties may consider:

Completion against agreed schedules.
Compliance with specifications and operating procedures.
Repeated defects, rework, or customer complaints.
Communication, attendance, and responsiveness.
Safety incidents and corrective actions.
Changes in capacity or resource availability.
Whether the arrangement remains suitable for the organisation’s needs.

These observations can inform decisions about further assignments, additional training, revised procedures, or changes to the working arrangement. They should be based on relevant evidence and interpreted in context.

The intended Marketplace model also treats work history as useful information for future matching and service-provider development. Any use of such records should follow the applicable privacy, access, accuracy, and data-handling arrangements.

Separate education from commercial accountability

Wara KarmaYoga Foundation Trust has an educational and social-development role that includes training, skills development, and livelihood preparation. Wara Systems is intended to operate the commercial Marketplace and coordinate customer engagements and provider participation where applicable.

These roles are related, but they are not interchangeable. Participation in a training programme does not guarantee employment, a commercial assignment, or a particular income. Nor does the Trust automatically become responsible for the quality, cost, or liabilities of a commercial engagement.

For every assignment, the parties should establish the actual contractual relationships, responsibilities, supervision arrangements, and applicable requirements. Any involvement of the Trust should be separately defined rather than presumed.

What organisations should expect

The intended approach is based on clear requirements, suitable assignment, defined responsibilities, proportionate quality checks, and documented completion.

It does not mean that every service domain is already available, that every assignment can be fulfilled, or that a complete quality-management platform is currently operational. The checks, records, personnel, and procedures available for a particular engagement must be confirmed before the work is accepted.

For organisations considering an engagement, the next step is to describe the required outcome and the quality, safety, timing, and acceptance conditions that matter to them.

Continue exploring

Services for Organisations: Review the service domains and potential engagement categories.
How Engagement Works: Understand scoping, feasibility, commercial terms, and delivery.
Care Services: Explore the intended coordinated care-giver partner model.
Production Services: Explore distributed production and bulk-order arrangements.
Work with WARA: Return to the overview for organisations.