Work with WARA

• 1: Why WARA
• 2: How It Works
• 3: Services
• 4: Delivery Model
• 5: Examples
• 6: Work with WARA
• 6.1: Services for Organisations
• 6.2: How Engagement Works
• 6.3: Quality and Accountability
• 6.4: Care Services
• 6.5: Production Services
• 6.6: Partnerships
• 6.7: Frequently Asked Questions
• 7: Become a WARA Work Partner
• 7.1: Why Partner with WARA
• 7.2: How Assignments Work
• 7.3: From Demand to Livelihood
• 7.4: Payment and Settlement
• 7.5: Joining and Verification
• 7.6: Care Partners
• 7.7: Growth and Enterprise
• 7.8: Learning and Skills
• 7.9: Frequently Asked Questions
• 8: The Philosophy of the WARA Marketplace
• 8.1: The Problem and the Opportunity
• 8.2: From Demand to Livelihood
• 8.3: Delivery-Based Work
• 8.4: Distributed Work
• 8.5: The Partner Model
• 8.6: Learning to Work
• 8.7: Quality at Scale
• 8.8: Technology and Coordination
• 8.9: Economic and Social Impact
• 8.10: Long-Term Vision

1 - Why WARA

The gap between capability and work

People develop skills through education, training, experience, and practice. Organisations accumulate technical knowledge, equipment, local relationships, and the ability to provide services. Yet these capabilities do not always translate into productive work.

A skilled person may not know where to find customers. A local service provider may be capable of completing an assignment but lack access to larger requirements. A customer may need a service but struggle to identify a suitable provider, define the expected result, or coordinate delivery.

The problem is not always a shortage of skills or a shortage of demand. Often, the two exist without a reliable way to connect them.

WARA’s work ecosystem is intended to help organise that connection.

Why skills alone are not enough

A person can be competent at a task and still face several practical barriers to earning from that capability.

• Customer access: Finding people or organisations that need the service may require networks, marketing, and repeated communication.
• Unclear requirements: Customers may describe a problem without defining the expected output, specifications, or conditions for acceptance.
• Irregular demand: Work may arrive unpredictably, making it difficult to plan time, materials, and resources.
• Limited coordination: Larger assignments may require several people, complementary skills, or work across multiple locations.
• Trust and verification: Customers need confidence in the provider’s capability and the quality of the result. Providers also need clear expectations and fair treatment.
• Commercial complexity: Pricing, scope changes, deadlines, responsibilities, acceptance, and payment need to be agreed and managed.

These barriers affect people differently. An experienced worker may need better access to customers, while a new learner may first need to develop and demonstrate the required competence. A service provider may need help coordinating a larger assignment rather than performing the underlying work.

A useful system must recognise these differences instead of treating every participant as having the same problem.

Customers face a related challenge

The same gap appears from the customer’s side.

A customer may know what needs to be accomplished but not know which provider can deliver it reliably. Finding a provider is only the beginning. The customer may also need to clarify the scope, compare proposals, agree on responsibilities, monitor progress, verify the result, and resolve problems.

For a simple service, these activities may be straightforward. For a larger requirement involving multiple contributors, they can become a significant part of the work itself.

Customers need more than a list of people who claim to possess particular skills. They need a workable way to engage suitable capability and establish what successful delivery means.

This is why WARA’s intended model focuses on the organisation of work as well as the connection between demand and capability.

Turn requirements into defined assignments

The first practical step is to translate a customer’s requirement into work that can be understood and organised.

A requirement should be clarified sufficiently to establish:

• What the customer needs.
• What is included in the assignment.
• What output or outcome is expected.
• Which capabilities and resources are required.
• Who will perform and coordinate the work.
• What quality criteria and completion conditions apply.
• What commercial terms govern the engagement.

The level of detail depends on the work. A small household service may need a simple scope and clear price. A production order may require specifications, quantities, materials, stages, inspection criteria, and delivery arrangements.

Once the requirement is sufficiently clear, the parties can determine whether suitable capability is available and whether the assignment can be undertaken on workable terms.

A request for a service is not automatically a confirmed order. The scope, availability, responsibilities, and terms still need to be established.

Organise delivery around the work

Not every requirement should be delivered in the same way.

Some assignments are best handled by one experienced individual. Others require a local service provider to organise resources and contributors. Larger requirements may need a coordinated team or work distributed across several locations.

The delivery arrangement should match the nature of the assignment, the capabilities available, and the responsibilities that must be managed.

For example, a customer needing a single garment alteration may be served by an individual tailor. A larger uniform order may require material planning, multiple workers, coordinated production, inspection, and delivery. The second requirement is not simply more of the same task; it introduces additional coordination and quality responsibilities.

WARA’s intended approach is to make these different arrangements possible where the work and commercial terms support them, rather than assuming every assignment must be completed by one individual or by a centrally employed workforce.

Connect learning with actual requirements

Where capability is missing, learning can help people prepare for suitable work.

WARA’s broader learning approach supports the development of knowledge and practical competence through learning, practice, demonstration, verification, and qualification where applicable. The intended connection with commercial activity is to help ensure that relevant capabilities can be developed in response to practical needs.

However, training and work remain distinct. A course may prepare someone for an occupation without guaranteeing that a suitable assignment will be available. An existing skill may also need further practice, assessment, or a relevant professional qualification before it is suitable for a particular engagement.

Commercial requirements can inform learning priorities, while experience from completed work can help identify areas for improvement. This relationship should improve preparedness without turning every training programme into a promise of employment or income.

The role of WARA

WARA aims to provide an organised way to connect customer requirements with suitable organisations, service providers, and workers.

The intended commercial Marketplace model can support activities such as defining requirements, arranging engagements, coordinating delivery, establishing verification processes, maintaining relevant records, and managing settlement according to agreed terms.

Wara Systems is responsible for the commercial Marketplace and its associated operating activities. The Wara KarmaYoga Foundation and associated trust activities focus on social education, training, outreach, scholarships, and livelihood preparation.

These roles can complement each other, but they are not interchangeable. The Marketplace is intended to be open to participating organisations beyond WARA itself, and the responsibilities of each party depend on the particular engagement.

The model does not remove the need for genuine customer demand, suitable capability, clear agreements, or accountability. It aims to make these elements easier to bring together.

What success should mean

The purpose of organising work is not merely to increase the number of profiles, enquiries, or assignments recorded by a platform.

A useful work arrangement should address a real requirement, match it with suitable capability, establish clear responsibilities, and deliver an acceptable result under agreed terms.

For workers and service providers, the model may create access to suitable assignments, practical experience, repeat work, specialisation, or opportunities to organise services and build an enterprise. For customers, it should help make requirements easier to define and delivery easier to coordinate.

These are intended outcomes, not guaranteed results. Their achievement depends on demand, competence, service quality, commercial viability, and how effectively the arrangements work in practice.

The next step is to understand how a requirement moves through the delivery lifecycle, from initial clarification to accepted output and settlement.

Continue with How It Works.

2 - How It Works

From requirement to accepted work

WARA’s work model is designed to organise the steps between a customer needing something and the agreed work being completed.

The process must work for different kinds of services. A small individual assignment may require only a clear description, an agreed price, and confirmation of completion. A larger production order or multi-location service may need detailed specifications, task allocation, intermediate checks, and coordination among several contributors.

The underlying lifecycle remains consistent even when the level of detail changes.

Requirement → Scope → Agreement → Assignment → Execution → Quality Verification → Acceptance → Settlement

Each stage has a distinct purpose. Moving through these stages helps the parties understand what has been requested, what has been committed, who is responsible, and what must happen before the engagement is considered complete.

This describes the intended operating model. The precise process and available mechanisms depend on the service and the arrangements implemented for the particular engagement.

1. Requirement: Understand what is needed

The process begins when a customer identifies a need for a product, service, or defined outcome.

The initial request may be broad. A customer might need a website updated, equipment installed, garments produced, a property maintained, or a service delivered at a particular location.

Before the work can be organised, the parties need enough information to understand the requirement. This may include:

• The problem to be addressed or the result required.
• The quantity, location, or intended users.
• Relevant specifications or constraints.
• The required timing and any dependencies.
• The resources or access the customer must provide.
• Any safety, qualification, or regulatory requirements.

Not every detail must be known at the first enquiry. The purpose of this stage is to identify what is known, what remains unclear, and what information is needed before a workable scope can be agreed.

An enquiry is not a confirmed order, and submitting a requirement does not guarantee that a suitable provider will be available.

2. Scope: Define the work

Once the requirement is understood, it must be translated into a defined scope.

The scope describes what the assignment includes, what it excludes, and what the customer should expect to receive. It also provides the basis for estimating resources, time, cost, and delivery responsibilities.

Depending on the service, a scope may specify:

• Tasks or deliverables.
• Quantities, dimensions, materials, or technical requirements.
• Milestones and dependencies.
• Completion and acceptance criteria.
• Responsibilities of the customer and provider.
• Assumptions, exclusions, and conditions that could affect delivery.

For example, a request for a batch of uniforms may need to define garment types, sizes, fabric, quantities, finishing requirements, packaging, and delivery arrangements. Without these details, different parties may interpret the same request differently.

The scope should be proportionate to the work. Simple assignments should not require unnecessary documentation, while complex or higher-risk work needs enough detail to manage expectations and accountability.

3. Agreement: Confirm the terms

After the scope has been sufficiently defined, the relevant parties can establish the terms under which the work will proceed.

The agreement should make clear what each party is committing to. Depending on the engagement, this may include:

• The agreed deliverables and acceptance criteria.
• Price, payment schedule, and settlement conditions.
• Expected timing and important milestones.
• Responsibilities for materials, equipment, access, and coordination.
• How changes to the scope will be handled.
• How defects, delays, disputes, or other exceptions will be addressed.

The appropriate form of agreement depends on the nature and value of the work, applicable law, and the parties involved.

A proposal or estimate should not be confused with an accepted engagement. Work should proceed on the basis of the commitments and authorisations required for that particular arrangement.

Clear agreement protects both the customer and the delivery participants by establishing a common reference for execution and later verification.

4. Assignment: Arrange suitable delivery

Once the engagement is agreed, the work can be assigned to an appropriate person, service provider, team, or organisation.

The delivery arrangement should reflect the nature of the work and the capabilities required. A simple task may be assigned to one qualified individual. A larger requirement may need a local provider to organise several workers, or an organisation to coordinate contributions across locations.

Assignment decisions may need to consider:

• Demonstrated capability and relevant experience.
• Required qualifications, licences, or permissions.
• Availability and location.
• Equipment, materials, and other resources.
• Dependencies between contributors.
• Responsibility for coordination and final delivery.

The parties must also understand who is responsible for the overall engagement and how the work will be coordinated.

WARA’s intended Marketplace model can support connections between requirements and suitable delivery capability. The actual assignment depends on availability, suitability, the commercial arrangement, and confirmation by the relevant parties.

5. Execution: Carry out the agreed work

During execution, the assigned people or organisations perform the agreed tasks and manage the resources and dependencies needed to complete them.

The method depends on the service. Some work can be completed independently. Other work requires customer access, material supply, scheduled visits, staged production, specialist input, or coordination between multiple contributors.

Execution should remain aligned with the agreed scope. Where progress updates are needed, the parties should know what information will be shared and when. Changes that affect cost, timing, quality, or responsibilities should be handled through the agreed change process rather than assumed to be included automatically.

For distributed work, coordination becomes especially important. Contributors need clear task boundaries, access to relevant instructions, and an understanding of how their outputs fit into the complete assignment.

The aim is to complete the work in a way that satisfies the agreed requirements while making delays, dependencies, and exceptions visible enough to address.

6. Quality verification: Check the result

Completed work must be checked against the criteria established for the assignment.

The form of verification depends on the service. It may involve a checklist, inspection, measurement, demonstration, testing, review of records, or confirmation that specified tasks have been completed.

For complex assignments, checks may be needed at intermediate stages as well as at the end. Early checks can identify problems before they affect later work.

Verification should be based on the agreed requirements rather than an unstated or newly introduced expectation. Where professional standards, safety procedures, or regulatory requirements apply, the relevant obligations must also be met.

If a result does not meet the criteria, the parties need to identify the gap and determine the appropriate response under the agreement. This may involve correction, further work, revised arrangements, or another agreed resolution.

Verification and acceptance are related but distinct. Verification examines whether the requirements have been met; acceptance is the authorised decision made under the engagement terms.

7. Acceptance: Confirm completion

Acceptance establishes whether the delivered work satisfies the conditions agreed for the engagement.

The responsible party reviews the result and confirms acceptance according to the applicable process. If the work is incomplete or a requirement remains unmet, the outstanding issue should be recorded and addressed under the agreement.

Acceptance criteria should be clear before execution begins. Otherwise, the parties may disagree about whether the work is complete or what additional effort is required.

Some engagements may allow partial acceptance of milestones or separate deliverables. Others may require the entire output to meet the agreed conditions before final acceptance.

The acceptance process should also respect any contractual or statutory rights and obligations. A general description of the WARA lifecycle does not override the specific agreement or applicable law.

8. Settlement: Complete the commercial process

Settlement follows the payment and other commercial conditions established for the engagement.

Depending on the agreement, settlement may be linked to accepted deliverables, completed milestones, verified quantities, recurring service periods, or another defined event.

The relevant records should make it possible to understand:

• What work was agreed.
• What was completed and accepted.
• What amount or payment obligation applies.
• Whether any agreed adjustments or unresolved issues remain.
• What settlement action is due and whether it has been completed.

For assignments involving multiple contributors or service providers, the commercial arrangement should clarify the responsibilities for payments and settlement. Participants should not have to infer these responsibilities from an informal understanding.

The exact payment flow depends on the parties, contracts, and operating arrangements. Participation in the Marketplace should not be taken to imply a particular payment schedule unless that schedule has been agreed.

How the lifecycle changes with the work

The same lifecycle can support different kinds of engagements, but not every assignment needs the same level of process.

These examples illustrate how the model may be applied. They do not establish that every listed service is currently available through WARA.

The governing principle is to use enough coordination to deliver the agreed result reliably without adding unnecessary process to straightforward work.

Responsibilities throughout the engagement

The delivery lifecycle involves different responsibilities, and these should remain clear even when several parties participate.

• The customer explains the requirement, supplies agreed information or resources, and fulfils the obligations established in the engagement.
• The service provider or assigned contributor performs the work it has accepted and follows the applicable requirements and procedures.
• A coordinating organisation, where involved, manages the coordination and delivery responsibilities it has agreed to undertake.
• The party responsible for verification and acceptance applies the relevant criteria and records the outcome according to the agreed arrangement.
• The party responsible for settlement fulfils the payment or other settlement obligations established by the engagement.

One organisation or individual may perform more than one role. The important point is that the responsibilities are explicit and consistent with the agreement.

WARA’s commercial role depends on the particular engagement. It should not be assumed that WARA directly employs every contributor, performs every service, or accepts responsibility for obligations assigned to another participating organisation.

What a well-organised lifecycle achieves

A clear lifecycle helps reduce misunderstandings between customers and delivery participants. It creates a shared reference for scope, responsibilities, execution, quality, and settlement.

It also provides a basis for learning from completed work. Repeated delays may indicate a planning problem. Recurring defects may reveal unclear specifications or a need for additional training. Settlement disputes may point to incomplete agreements or missing records.

These observations can help improve future assignments when they are supported by reliable evidence and appropriate review.

The lifecycle cannot guarantee that every engagement will succeed. Its purpose is to make expectations clearer, responsibilities more manageable, and problems easier to identify and resolve.

The next page explains how the service catalogue should present offerings and distinguish current availability from services that are only proposed or open for enquiry.

Continue with Services.

3 - Services

Services in the WARA Work Ecosystem

WARA’s work ecosystem is designed to support different kinds of services, from individual assignments to coordinated work involving multiple people or organisations.

The purpose of a service catalogue is not simply to list what people know how to do. It is to explain what a customer can request, what the work involves, how delivery will be organised and whether the service is currently available.

A service may be technically feasible without being ready for immediate delivery. Availability depends on factors such as suitable providers, location, capacity, required equipment, quality expectations and agreed commercial terms.

Service Domains

The following domains provide a framework for organising potential services. Inclusion in a domain does not mean that every service within it is currently available.

Digital and Business Services

Work involving digital tools, business operations, information processing and technology-supported services.

Illustrative areas include:

• Data entry, document preparation and digital administration
• Customer communication and enquiry coordination
• Business process support and routine operational tasks
• Website, software and technology-related services
• AI-assisted business support, where appropriate and agreed

Education and Learning

Work related to learning support, practical instruction and the development of occupational capabilities.

Illustrative areas include:

• Learning assistance and educational support
• Practical and vocational instruction
• Training-related content and learning materials
• Support for digital literacy and workplace readiness

Training activity and commercial service delivery are distinct. Completing a course does not, by itself, establish that a person is qualified or authorised to provide every service in the corresponding domain.

Healthcare and Community Support

Services that support healthcare organisations and community needs, subject to the qualifications, supervision and regulatory requirements applicable to the work.

Illustrative areas include:

• Administrative support for healthcare facilities
• Appointment and enquiry coordination
• Non-clinical operational assistance
• Community-oriented support services

Clinical work and other regulated activities require appropriate qualifications, permissions and professional oversight. A listing in this domain must not be interpreted as authorisation to perform regulated work.

Technical and Infrastructure Services

Practical services involving installation, maintenance and technical support.

Illustrative areas include:

• Computer and peripheral setup
• Networking and connectivity support
• CCTV installation and related technical work
• Equipment installation and maintenance
• Other technical services matched to suitable skills and equipment

The actual scope must reflect the provider’s competence, the equipment involved and any applicable safety or licensing requirements.

Textiles, Production and Rural Enterprises

Services involving practical production, repair, small-scale manufacturing and distributed work.

Illustrative areas include:

• Tailoring and garment alteration
• Textile-related production
• Product preparation and finishing
• Small-scale manufacturing support
• Work coordinated across local producers or service providers

Assignments in this domain may require samples, material specifications, production quantities, delivery schedules and defined acceptance criteria.

Hospitality, Tourism and Local Services

Services supporting hospitality businesses, travel-related organisations and local service requirements.

Illustrative areas include:

• Booking and enquiry coordination
• Guest communication and administrative support
• Tourism-related operational assistance
• Local service coordination
• Other hospitality and community-facing services

Requirements vary by customer, location and assignment. A service listing should specify the expected responsibilities rather than relying on a broad category name.

These domains are an organising framework, not a representation that WARA currently operates every listed service.

Understanding Service Availability

Each specific service should have a clear availability status. The following distinctions provide a practical convention for presenting the catalogue.

These statuses should be applied to individual services rather than inferred from the presence of a broad service domain. Availability may also vary by location, required capacity, timing and assignment conditions.

A service should not be presented as available merely because a relevant training course exists or a potential provider has expressed interest.

What a Service Listing Should Explain

A useful service listing should help both the customer and the delivery team understand the assignment before work begins.

Depending on the service, the listing should identify:

• The requirement: What problem is being addressed or what result is needed?
• The scope: What work is included, and what is outside the assignment?
• The deliverable: What must be produced, completed or handed over?
• The delivery conditions: What information, materials, equipment, access or customer cooperation is required?
• The quality criteria: How will the result be checked and accepted?
• The schedule: What deadlines, milestones or service windows apply?
• The commercial terms: How will the price, payment milestones and other agreed costs be handled?
• The availability: Is the service ready for engagement, open for enquiry or still in development?

Not every service requires the same level of detail. A small, clearly defined assignment may need only a concise specification, while a complex assignment may require a fuller scope, milestones and documented acceptance criteria.

From Service Catalogue to Actual Work

The service catalogue is the starting point for a customer conversation, not a substitute for agreeing on an assignment.

Once a customer identifies a suitable service, the requirement must be reviewed and its scope, delivery arrangements, responsibilities, quality expectations and commercial terms established. Only then can the work proceed under the applicable agreement.

WARA Systems is intended to support the commercial side of the work ecosystem, including customer engagement, assignment coordination and the organisation of delivery where applicable. Actual responsibilities depend on the service and the agreed arrangement. Providers and partner organisations may participate in delivery, and their roles should be made clear.

The Wara KarmaYoga Foundation Trust has a distinct social and educational role, including training, outreach and livelihood preparation. Participation in Trust activities does not automatically make a person a confirmed provider for a commercial assignment.

Keeping the Catalogue Trustworthy

A service catalogue is useful only when its descriptions and availability remain accurate.

Service information should be reviewed as provider capacity, locations, delivery arrangements and commercial conditions change. Proposed services should remain distinguishable from established offerings, and any commitment should be based on confirmed details rather than assumptions.

WARA’s aim is to make the path from a customer requirement to organised delivery clearer. The next page explains the delivery model: how scope, responsibilities, quality expectations and payment terms fit together in an assignment.

Continue with Delivery Model.

4 - Delivery Model

From Requirements to Deliverables

A service category describes the kind of work that may be performed. A delivery model explains how a particular assignment is organised and completed.

For a customer, the objective is to receive an agreed result with clear expectations about scope, timing, quality and cost. For a service provider, the objective is to understand the responsibility, resources, acceptance criteria and payment conditions before committing to the work.

WARA’s intended delivery model is built around a simple principle: define the assignment before expecting the result.

The level of coordination depends on the work. A small, self-contained task may need only a short specification and a clear handover. A larger assignment may require multiple providers, milestones, progress reviews and formal acceptance.

The Assignment Lifecycle

A typical assignment can be organised into the following stages.

1. Requirement and Scope

The customer explains the need, expected result, relevant constraints and any deadline.

The requirement is then translated into a workable scope. This should clarify what is included, what is excluded and what information or resources are needed to begin.

Where important details remain uncertain, they should be resolved before a delivery commitment is made.

2. Delivery Arrangement

The assignment is matched with an appropriate provider or delivery team, taking account of relevant skills, experience, availability, location, equipment and other requirements.

For work involving several people or organisations, responsibilities and coordination arrangements should be established in advance.

A potential provider match is not, by itself, a confirmed engagement. The assignment proceeds only when the relevant parties have agreed to the arrangement.

3. Commercial Agreement

The parties establish the commercial terms before work begins.

Depending on the assignment, these may include:

• Price and payment schedule
• Start date, milestones and delivery deadline
• Materials, equipment and other agreed costs
• Customer responsibilities and dependencies
• Changes to scope and their effect on cost or timing
• Quality requirements and acceptance conditions
• Treatment of delays, rework, cancellation and disputes

The agreement should be proportionate to the assignment. A routine task does not need the same documentation as a complex, multi-stage project.

4. Execution and Coordination

The provider performs the agreed work. Where coordination is required, the responsible parties track progress, resolve dependencies and communicate material changes.

If the customer changes the requirement or a delivery constraint arises, the effect on scope, cost, timing or quality should be discussed rather than silently absorbed into the original assignment.

5. Quality Verification

The completed work is checked against the criteria agreed for the assignment.

Verification may involve inspection, testing, review of documents, confirmation of quantities or another method appropriate to the deliverable.

The criteria should be understandable before execution begins. This reduces the risk of disagreement about whether the work is complete.

6. Acceptance and Handover

The customer or designated authorised party reviews the deliverable and confirms whether it meets the agreed acceptance criteria.

If it does not, the parties should identify the specific gaps and determine the appropriate next step under their agreement.

Acceptance and quality verification are related but distinct. A provider may perform an internal quality check, while formal acceptance may remain the customer’s responsibility.

7. Settlement and Closure

Payment is handled according to the agreed commercial terms and the applicable completion, milestone or acceptance conditions.

The assignment can then be closed with the necessary handover, records and follow-up actions.

The exact settlement process depends on the agreement. The delivery model does not imply that every assignment uses the same payment schedule or that a particular digital settlement system is already operational.

Responsibilities in a Delivery Arrangement

Clear responsibility helps prevent tasks from being overlooked or assumed to belong to someone else.

These are functional roles, not a requirement for five separate participants. One person or organisation may perform several roles in a small assignment. Responsibilities should nevertheless remain explicit.

Quality, Acceptance and Rework

Quality must be defined in terms that fit the work.

For a document, this might mean completeness, accuracy and an agreed format. For an installation, it might include specified functionality, safe operation and completion of agreed checks. For a production assignment, it might include dimensions, quantities, material specifications and permissible defects.

A sound assignment should distinguish between:

• Completion: The provider has performed the specified work.
• Verification: The work has been checked against the agreed requirements.
• Acceptance: The authorised party confirms that the deliverable meets the agreed conditions.
• Rework: Identified deficiencies are addressed according to the agreement.

The responsibility for rework, its limits and any additional costs should be agreed where relevant. These conditions should not be left entirely to assumptions after delivery.

Different Assignments, Different Levels of Coordination

The same basic principles can support different delivery arrangements.

These are examples of how the model may be applied. The actual arrangement should be selected according to the requirements and risks of the work.

The Role of WARA

WARA Systems is intended to support the commercial work ecosystem, including customer engagement, assignment coordination, provider networks and delivery organisation where applicable. The precise role depends on the service and the agreement among the parties.

The Wara KarmaYoga Foundation Trust has a separate social and educational role, including training, outreach and livelihood preparation. Training may help people develop capabilities for future work, but a training participant is not automatically an assigned provider, and completing a course does not guarantee work.

The wider ecosystem is intended to create a more organised path between skills, customer demand and work delivery. Its practical value depends on suitable providers, clear requirements, realistic commitments and reliable execution.

What This Model Does Not Promise

A defined delivery process can reduce ambiguity, but it cannot eliminate every operational risk.

It does not guarantee that every requirement can be fulfilled, that a suitable provider will always be available, that every deliverable will be accepted or that work will generate a particular income. These outcomes depend on the assignment, the parties, the applicable terms and actual execution.

Any service offered to a customer should therefore be based on confirmed capacity and a specific agreement, rather than on the general description of the WARA model.

See the Model in Practice

The next page presents illustrative scenarios showing how the delivery model may apply to different types of work. These examples explain possible arrangements; they should not be interpreted as evidence that every illustrated service or workflow is already operational.

Continue with Examples.

5 - Examples

Seeing the Delivery Model in Practice

A delivery model becomes easier to understand when applied to familiar situations.

The examples below show how different kinds of work may be organised through clear requirements, suitable providers, agreed responsibilities and defined completion criteria. The level of coordination varies with the assignment, but the underlying principle remains the same: both the customer and the provider should understand what has been agreed before the work begins.

Example 1: Customer Enquiry Support

A small hospitality business receives enquiries about room availability, facilities, bookings and local services. The owner wants these enquiries handled consistently without personally responding to every message.

The requirement

The customer defines the communication channels, enquiry types, expected response times, languages, escalation rules and information that staff may provide.

The delivery arrangement

A suitable person or team is assigned to handle the agreed enquiries. The business provides accurate information, approved response guidelines and a process for referring unusual requests to the responsible staff member.

Quality and acceptance

Performance can be assessed against criteria such as response accuracy, adherence to approved procedures, completeness of enquiry records and compliance with the agreed response schedule.

What this illustrates

A service described broadly as customer support becomes a manageable assignment when its responsibilities, boundaries and performance expectations are explicit.

The example does not imply that every hospitality business can be supported remotely or that a provider is available for immediate engagement. Those conditions must be confirmed for each requirement.

Example 2: Tailoring and Garment Production

A customer needs a batch of garments produced to specified measurements and a delivery schedule. The work may involve one tailor or a group of production providers.

The requirement

The customer specifies garment designs, measurements, materials, quantities, finishing requirements, delivery dates and acceptable quality standards.

The delivery arrangement

The provider confirms capacity, material availability, pricing and the production schedule. If several people participate, responsibilities for cutting, stitching, finishing and final checking are allocated.

Quality and acceptance

Completed garments are checked against the agreed measurements, construction, finishing and quantity requirements. Any defects or deviations are handled according to the agreed terms.

What this illustrates

Practical skills can be organised into a defined production assignment. Clear specifications and acceptance criteria help both sides understand what constitutes completed work.

The scenario does not establish that WARA currently operates a tailoring network or can fulfil a particular production order.

Example 3: Technical Installation

A business requires a network connection or equipment installation at its premises.

The requirement

The customer identifies the location, required equipment, expected functionality, site conditions and any relevant access or safety constraints.

The delivery arrangement

A suitably competent provider assesses the requirement and confirms the scope, equipment, schedule and commercial terms. Work requiring particular qualifications, licences or permissions must be assigned accordingly.

Quality and acceptance

The installation is checked against the agreed specification. Depending on the work, this may include connectivity tests, functional checks, equipment handover and documentation.

What this illustrates

Technical work requires more than identifying someone who has relevant experience. The assignment must account for the site, equipment, safety requirements and evidence that the result meets the specification.

Example 4: Digital Administration

An organisation needs a collection of records digitised and organised into a consistent format.

The requirement

The customer defines the documents or records involved, the required fields, naming conventions, output format, deadline and rules for handling confidential information.

The delivery arrangement

The provider receives the necessary instructions and authorised access. The assignment defines how incomplete, illegible or inconsistent records should be handled and when clarification is required.

Quality and acceptance

The completed output is checked against agreed criteria such as record counts, field completeness, formatting consistency and error rates. Sensitive information must be handled according to the applicable instructions and obligations.

What this illustrates

A routine digital task can become a repeatable service when its inputs, processing rules, output format and quality checks are defined.

Example 5: Coordinated Work Across Multiple Providers

A customer needs several related tasks completed, but no single provider is expected to perform every part of the assignment.

The requirement

The customer describes the overall outcome, component tasks, dependencies, deadlines and acceptance conditions.

The delivery arrangement

The parties divide the work into manageable assignments. Each assignment has a responsible provider, a defined output and any dependencies on other tasks. A coordinator may be appointed to manage scheduling, communication and integration.

Quality and acceptance

Each component is checked as appropriate, followed by a review of the combined result. The parties clarify who is responsible for resolving defects that affect more than one component.

What this illustrates

Coordinated delivery can make a larger requirement manageable, but it introduces additional dependencies. Clear ownership, communication and integration criteria become especially important.

Comparing the Examples

The evidence shown is illustrative. The actual criteria must be agreed for each assignment and adapted to its risks and requirements.

From Illustration to a Real Assignment

Before an illustrative scenario becomes a real engagement, several questions need to be answered:

• Is the service currently available for the required location, scope and schedule?
• Is a suitable provider or delivery team available?
• Have the scope, deliverables and responsibilities been agreed?
• Are the necessary equipment, information, permissions and other resources available?
• Are the quality and acceptance criteria clear?
• Have the price, payment terms and arrangements for changes or rework been agreed?

If these questions cannot yet be answered, the appropriate next step is to clarify the requirement or establish whether the service can be offered. A catalogue entry or example alone is not a delivery commitment.

The Principle Behind the Examples

Across different domains, the same approach applies: understand the requirement, define the work, establish responsibilities, agree on commercial conditions, deliver the result and assess it against the agreed criteria.

WARA’s intended work ecosystem seeks to make this process clearer for customers, service providers and coordinating organisations. Its usefulness depends on accurate service information, suitable delivery capacity, realistic commitments and transparent agreements.

The work pages describe the intended model. Specific service availability, provider participation and operating arrangements must be confirmed independently for each engagement.

Continue to the Work overview to revisit the wider ecosystem and its entry points.

6 - Work with WARA

Turn Your Requirements into Organised Work

Organisations regularly need work completed beyond the capacity of their existing teams. A business may need help with customer enquiries, a technical installation, a batch of products, routine administrative work or a service that requires several people working together.

Finding someone who can perform an individual task is only part of the challenge. The organisation must also define the requirement, identify suitable capability, agree on responsibilities and commercial terms, and establish how the completed work will be checked.

WARA’s intended work ecosystem is designed to help organise this process. It brings customer requirements and service capabilities into a common framework for scoping assignments, coordinating delivery where appropriate and establishing clear expectations between the parties.

The starting point is not a promise that every requirement can be fulfilled. It is a structured discussion about what needs to be done, what successful delivery would look like and whether a suitable arrangement can be established.

Who Can Approach WARA?

The work ecosystem is intended for organisations with practical requirements that can be defined and delivered through suitable people, providers or coordinated teams.

Potential participants include:

• Businesses and service companies that need support with defined operational tasks or recurring services.
• Hotels, resorts and hospitality operators that need assistance with guest-facing or back-office activities.
• Healthcare organisations that require appropriate administrative or non-clinical support within clearly defined responsibilities.
• Manufacturers, producers and product businesses that need production assistance, batch fulfilment or distributed work arrangements.
• Educational and community institutions that require suitable services or practical support.
• Other organisations with requirements that can be scoped, assessed and matched with appropriate delivery capability.

These are potential customer groups, not a statement that every service is currently available to every sector. Feasibility, location, capacity, qualifications, safety requirements and commercial conditions must be considered for each engagement.

The marketplace is intended to be open to organisations and suitable providers beyond WARA itself. Its purpose is to organise work around actual requirements rather than restrict participation to a single organisation’s internal activities.

What Organisations Can Bring to WARA

An organisation does not need to have a fully designed assignment before making an enquiry. It should, however, be able to explain the problem or outcome it needs help with.

Typical starting points include:

A Defined Service Requirement

You know what needs to be done but need to explore suitable providers, delivery arrangements or the appropriate scope.

Examples include digital administration, customer communication, technical support and other clearly defined operational tasks.

A Recurring Operational Need

You need a service to be performed repeatedly rather than as a one-time assignment.

The discussion may consider workload, frequency, service expectations, staffing or provider arrangements, supervision and the commercial terms needed for an ongoing engagement.

A Production or Bulk Order

You need a quantity of products or components produced, assembled, finished or prepared according to defined specifications.

The requirement may need to be broken into production stages, with attention to materials, quantities, capacity, delivery schedules and quality checks.

A Coordinated Assignment

The requirement involves several tasks, providers or locations and needs a clear allocation of responsibilities.

The feasibility review should establish whether the work can be divided into manageable assignments and how the individual outputs will be coordinated and checked.

A Longer-Term Partnership

You are exploring a continuing relationship for recurring requirements, service delivery or production work.

Such an arrangement requires a separate discussion of demand, capacity, operating responsibilities, commercial terms and the conditions under which the relationship may continue.

These examples describe the kinds of requirements the work ecosystem is intended to address. They do not imply that a particular provider, production network or recurring delivery arrangement is already available.

How an Engagement Begins

An organisation can begin by describing its requirement and the result it expects.

The engagement process is intended to move through five practical stages:

1. Understand the requirement. Establish the business need, expected output, constraints and relevant deadlines.
2. Define the scope. Clarify what is included, what is excluded and how completion will be assessed.
3. Assess feasibility. Review suitable capability, availability, resources, location, safety and other delivery constraints.
4. Agree on the arrangement. Establish responsibilities, pricing, schedules, quality expectations, payment terms and other relevant conditions.
5. Proceed with delivery. Begin only after the necessary arrangements and commitments have been confirmed.

The amount of work required at each stage depends on the assignment. A straightforward task may need a concise scope, while a complex or recurring engagement may require a more detailed plan.

Read How Engagement Works for the proposed process in greater detail.

What WARA Needs to Assess Your Requirement

A useful enquiry gives enough information to determine whether the requirement can be considered further.

Where possible, include:

• The organisation’s name and the nature of its business or activity.
• A description of the work or problem.
• The expected output, quantity or service level.
• The location where the work must be performed, or whether remote delivery is possible.
• The expected start date, deadline and frequency.
• Any relevant technical specifications, equipment or materials.
• Required qualifications, permissions, safety conditions or confidentiality obligations.
• An indicative budget or preferred commercial arrangement, if known.

You do not need to resolve every detail before making contact. If the requirement is still being developed, explain what is known and which decisions remain open.

The purpose of the initial discussion is to identify the information needed for a responsible feasibility assessment, not to create an expectation that work has already been accepted.

Quality and Accountability

Organised delivery requires more than finding a provider. The parties need a shared understanding of the expected result, the responsibilities involved and the evidence that will establish completion.

Depending on the assignment, this may include written specifications, defined milestones, agreed inspection or testing procedures, customer acceptance and documented payment conditions.

Responsibilities must also reflect the nature of the work. Healthcare-related, technical, safety-sensitive and other regulated activities require particular attention to competence, authorisation and the applicable requirements.

WARA’s intended delivery model aims to make these expectations explicit before work begins. The specific checks, responsibilities and remedies must be established for each engagement rather than assumed to be identical across all services.

See Quality and Accountability for further details.

The Role of WARA’s Organisations

The commercial and educational activities associated with WARA have distinct purposes.

**Wara Systems ** is intended to support the commercial work ecosystem, including customer engagement, the Marketplace, assignment coordination, commercial delivery arrangements and provider networks where applicable.

Wara KarmaYoga Foundation Trust focuses on social and educational activities, including training, outreach and livelihood preparation. These activities can help people develop useful capabilities, but participation in training does not automatically make someone available for a commercial assignment.

An organisation’s requirement must therefore be assessed on its own merits. Suitable capability, actual availability, agreed responsibilities and the conditions of the engagement determine whether work can proceed.

Discuss Your Requirement

If your organisation has a defined service need, recurring operational requirement, production order or potential partnership, the next step is to describe the requirement clearly enough for an initial discussion.

WARA can then consider what information is needed to define the scope and assess whether a suitable delivery arrangement may be possible. Any commitment to provide a service, fulfil an order or establish a recurring engagement must follow confirmation of feasibility and agreement on the relevant terms.

Explore the organisation pages to understand the available service framework, engagement process, quality considerations and potential partnership models.

• Services: understand the service domains and how availability should be represented.
• How Engagement Works: understand scoping, feasibility, agreement and delivery.
• Quality and Accountability: understand responsibilities, quality expectations and safety considerations.
• Care Services: explore the proposed coordinated caregiver partner model.
• Production Services: explore distributed production and bulk-order arrangements.
• Partnerships: consider institutional and recurring commercial engagements.
• Frequently Asked Questions: review common commercial and operational questions.

6.1 - Services for Organisations

What WARA Can Deliver

Organisations have different operational needs. Some require a clearly defined task to be completed once. Others need recurring support, a coordinated team or a production arrangement that can handle multiple orders.

WARA’s intended work ecosystem is designed to organise such requirements around defined outputs, suitable capability, delivery responsibilities and agreed commercial terms.

The services described on this page represent the domains in which requirements may be considered. They are not a promise that every service is currently available. Whether an engagement can proceed depends on the exact scope, location, schedule, resources, provider capability and applicable requirements.

Service Domains

1. Digital, AI and Business Services

Organisations often need routine digital work and operational support that can be defined through clear tasks and outputs.

Potential requirements include:

• Data entry, document processing and digital record management.
• Customer enquiry handling and follow-up.
• Booking coordination and service administration.
• Digital content preparation and catalogue maintenance.
• Website and content-management support.
• Business process assistance and suitable AI-assisted workflows.

The scope should specify the systems involved, access permissions, required accuracy, data-handling responsibilities and expected outputs. AI-assisted work must include appropriate human review where accuracy, confidentiality or business consequences require it.

2. Education and Learning Support

Educational institutions and learning organisations may require support for defined learning activities and related operations.

Potential requirements include:

• Preparation and formatting of learning materials.
• Digital classroom and learning-platform assistance.
• Learning administration and record management.
• Practical learning support within the provider’s demonstrated competence.
• Assistance with educational content and training operations.

Teaching, assessment and other specialised educational responsibilities must be assigned according to the competence and requirements of the particular activity. The existence of a learning pathway does not establish that a corresponding commercial service is available.

3. Healthcare, Care and Community Support

Healthcare and community-facing organisations may have requirements for administrative assistance or appropriately scoped support services.

Potential areas for consideration include:

• Appointment and enquiry coordination.
• Non-clinical administrative support.
• Care-related assistance within a defined scope.
• Community support activities appropriate to the provider’s competence.

These activities require careful separation of responsibilities. Clinical work, medication-related duties and other regulated activities must not be assigned without the required qualifications, authorisation, supervision and safeguards.

The proposed coordinated caregiver partner model is discussed separately in Care Services.

4. Security, Technical and Infrastructure Services

Businesses, institutions and property operators may need installation, maintenance or technical support.

Potential requirements include:

• Computer setup and routine IT support.
• Network and connectivity assistance.
• Broadband and fibre-related work.
• CCTV installation and maintenance.
• Equipment installation and troubleshooting.
• Other defined technical and infrastructure tasks.

Each requirement must be matched to suitable competence, tools, site conditions and safety requirements. Work requiring a licensed or otherwise authorised professional must remain within the applicable legal and professional boundaries.

5. Textiles, Manufacturing and Rural Production

Product businesses and organisations with production requirements may need work completed in batches or across a distributed group of producers.

Potential areas for consideration include:

• Sewing, tailoring and garment production.
• Product assembly and finishing.
• Handicrafts and selected local products.
• Packaging and preparation of finished goods.
• Production support for defined quantities and specifications.

These assignments may require sample approval, material planning, production capacity assessment, inspection criteria and delivery scheduling.

The proposed distributed production approach is described in Production Services.

6. Hospitality, Tourism and Local Services

Hospitality operators, travel businesses and local service organisations may need support with recurring tasks or specific customer requirements.

Potential areas for consideration include:

• Guest enquiry and booking coordination.
• Front-office and administrative support.
• Housekeeping-related services.
• Tourism and travel-related operational assistance.
• Coordination of local service requirements.

The precise service, location, schedule and required experience must be established before an engagement can be confirmed. A general service category does not establish that a suitable person or team is available for a particular assignment.

7. Agriculture, Household and Essential Services

Organisations and local enterprises may have requirements involving practical work, maintenance, production support or essential services.

Potential areas for consideration include:

• Agricultural and horticultural support.
• Household and premises-related services.
• Basic maintenance and repair tasks within an appropriate scope.
• Local production, preparation and support activities.
• Other clearly defined work arising from local demand.

The feasibility of these services depends on the location, equipment, working conditions, provider competence and actual demand.

What Determines Whether a Service Can Be Offered?

A service domain provides a starting point. A specific engagement requires a more detailed assessment.

A requirement should proceed only when the relevant conditions have been assessed and the necessary commitments established.

Understanding Service Status

Service information should distinguish between what can be engaged, what needs further discussion and what remains a future possibility.

These distinctions should apply to individual services rather than entire domains. Availability can vary by location, timing, quantity and customer requirements.

No service should be treated as available merely because it appears in this catalogue, is included in a proposed training pathway or could theoretically be delivered by a suitably skilled person.

From Service Requirement to Engagement

When an organisation identifies a relevant service, the next step is to describe the intended outcome and establish whether a suitable arrangement is possible.

The engagement process should cover:

1. Understanding the customer’s requirement.
2. Defining scope and deliverables.
3. Assessing feasibility and suitable delivery capability.
4. Agreeing on responsibilities, quality criteria and commercial terms.
5. Confirming the engagement before delivery begins.

For a simple assignment, this process may be brief. For recurring services, regulated activities, production orders or multi-provider work, more detailed planning may be necessary.

Read How Engagement Works for the scoping, feasibility and agreement process.

A Commercial Marketplace, Not a Closed Provider Network

Wara Systems is intended to support the commercial side of the work ecosystem, including customer engagement, Marketplace activity, assignment coordination and provider networks where applicable.

The Marketplace is intended to be open to suitable organisations and providers beyond WARA itself. The objective is to organise real demand and suitable delivery capability, rather than assume that every requirement must be fulfilled internally.

The Wara KarmaYoga Foundation Trust has a separate social and educational role, including training, outreach and livelihood preparation. People who participate in training may develop capabilities relevant to these service domains, but training does not automatically establish provider availability, qualification for every task or a guaranteed assignment.

Discuss a Specific Requirement

If your organisation has a service requirement, the most useful next step is to describe the expected result, location, schedule and relevant constraints.

WARA can then consider what further information is needed to assess feasibility. Any offer, delivery commitment or recurring arrangement must be based on confirmed capability and agreed terms.

Continue with How Engagement Works to understand how a requirement moves from initial discussion to a possible service engagement.

6.2 - 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.

6.3 - Quality and Accountability

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.

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:

1. Confirm the requirement: Keep the agreed scope and specifications available to the people doing and checking the work.
2. Perform the work: Follow the agreed instructions, schedule, and safety requirements.
3. Check the result: Carry out the appropriate self-check, inspection, test, or customer review.
4. Record the outcome: Document completion and any material findings in a form appropriate to the assignment.
5. Resolve discrepancies: Identify work that does not meet the agreed criteria and follow the agreed correction or rework process.
6. 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.

6.4 - Care Services

A coordinated approach to care

Families, healthcare organisations and community service providers may need assistance with everyday care, support for older adults, non-clinical patient assistance or related activities. Finding an appropriate person is only one part of the challenge. The work must also fit the individual’s needs, the family’s expectations, the care setting and the capabilities of the person providing support.

WARA’s proposed model approaches care as a coordinated service rather than simply a worker-placement activity. It is intended to connect a clearly described requirement with a suitable provider, an agreed scope of work and an appropriate arrangement for communication, supervision and review.

The model is a proposed service framework, not a representation that a fully operational care network or guaranteed supply of care-givers is already available.

Who may use the service?

The model is intended to support organisations and service arrangements that require care-related assistance, including:

• Home-care service providers that need suitable personnel for defined non-clinical support assignments.
• Healthcare facilities that require support workers for appropriate non-clinical tasks within their operating procedures.
• Elder-care organisations that support older adults with daily routines, companionship and practical assistance.
• Community organisations that coordinate appropriate assistance for people who need support.
• Other service organisations whose care requirements can be defined and delivered within the competence and authorisation of the assigned personnel.

Families may also have care needs, but the appropriate engagement route, provider availability and service arrangements would need to be confirmed separately.

Care-support areas

The actual scope of a care assignment depends on the individual’s needs, the care setting, the provider’s capabilities and the applicable requirements.

Home and elderly care

Potential activities include:

• Assistance with agreed daily routines and personal care.
• Support with mobility and everyday activities within the worker’s training and competence.
• Companionship and assistance with appropriate recreational or social activities.
• Support with hygiene and infection-prevention routines.
• Observation and reporting of relevant changes to the designated family member or care professional.
• Basic care records where required by the agreed care plan.

Personal care and mobility assistance can involve significant risks. They should only be assigned when the worker is suitably prepared, the required precautions are in place and the activity is within the worker’s permitted scope.

Non-clinical patient support

Healthcare facilities or home-care providers may require assistance with tasks such as:

• Supporting patient comfort and routine non-clinical needs.
• Assisting with appropriate movement and daily activities under the applicable care instructions.
• Communicating observations to the authorised care team.
• Maintaining relevant non-clinical records.
• Helping coordinate routine activities within the assigned role.

These activities must not be confused with independently providing medical treatment, diagnosis or other regulated clinical services.

Digital healthcare and coordination support

Some care organisations may also need administrative and digital assistance, including:

• Appointment and schedule coordination.
• Organising authorised patient documentation.
• Maintaining records through approved systems.
• Supporting non-clinical communication and follow-up.
• Helping users navigate approved digital health services.

Access to personal or medical information must be limited to authorised purposes and handled according to applicable privacy, confidentiality and security requirements.

These categories describe potential service areas. Each specific service must be assessed before it is offered to an organisation.

The care-giver partner model

The proposed model brings together three connected responsibilities.

1. The organisation defines the care requirement. The organisation or authorised representative explains the type of support needed, the care setting, schedule, expected duties, relevant risks and reporting arrangements.

2. A suitable care-giver is identified. The assignment should consider demonstrated capability, relevant training, experience, required qualifications or authorisations, availability and suitability for the specific setting.

3. The service is coordinated against an agreed arrangement. The parties establish who gives instructions, who supervises the work, how concerns are reported, how completion is recorded and who is responsible for decisions that fall outside the care-giver’s role.

The precise division of responsibilities will depend on the contractual arrangement. A care-giver, a care-service provider, the customer’s organisation and a commercial coordinator may have different duties. Those duties must be made explicit before an assignment begins.

From enquiry to care delivery

Care assignments need particular attention to suitability, safety and continuity. A proposed engagement should address the following stages.

1. Understand the care requirement

The organisation describes the support needed, including the person’s circumstances to the extent necessary and authorised, the location, schedule, expected tasks and any relevant limitations.

The initial discussion should establish whether the requirement is for companionship, daily-living assistance, non-clinical patient support, administrative coordination or another defined service.

2. Review suitability and feasibility

The requirement is assessed against the availability and suitability of potential providers. Relevant considerations include training, demonstrated capability, experience, language and communication needs, schedule, travel, supervision, safety and any required qualifications or authorisations.

A requirement should not proceed simply because someone is available. If appropriate capability or safe working arrangements cannot be established, the scope should be revised or the assignment declined.

3. Agree on the care arrangement

Before work starts, the parties should confirm:

• The duties included in the assignment and tasks that are excluded.
• Schedule, duration, location and continuity expectations.
• Who provides care instructions and who may authorise changes.
• Reporting and escalation contacts.
• Safety precautions, privacy expectations and relevant documentation.
• Commercial terms, payment arrangements and procedures for cancellation or replacement, where applicable.

4. Coordinate the service

The care-giver performs the agreed activities within their competence and role. Communication arrangements should allow relevant concerns, schedule changes and limitations to be reported promptly.

Where continuity is important, the parties should establish how absences, handovers, replacement requests and changes in the individual’s needs will be managed.

5. Review and address concerns

Feedback and appropriate records can help determine whether the agreed service is being delivered. Concerns about safety, conduct, attendance, quality or the person’s changing needs should be escalated to the designated responsible party.

The review process must respect privacy and should not substitute for professional clinical assessment where that is needed.

Safety, dignity and professional boundaries

Care work involves a relationship of trust. A suitable service arrangement must protect the dignity and reasonable privacy of the person receiving care while defining the limits of the worker’s responsibilities.

The engagement should address the following principles:

• Respect and consent: Treat the person receiving care respectfully and follow applicable consent and decision-making requirements.
• Competence: Assign only tasks that the worker is trained, capable and authorised to perform.
• Privacy: Access and share personal information only as permitted and necessary for the service.
• Safeguarding: Establish appropriate procedures for reporting suspected abuse, neglect, exploitation or other serious concerns.
• Safe practice: Follow relevant hygiene, infection-prevention, mobility and workplace safety procedures.
• Escalation: Identify when the worker must contact a supervisor, responsible family member or authorised healthcare professional.
• Professional boundaries: Do not treat a care-support assignment as authority to perform clinical procedures, change treatment, administer medicines or make professional decisions unless the person is appropriately authorised and the arrangement expressly permits it.

The specific controls will vary according to the service, the care setting and applicable law. Any required background checks, documentation, qualifications, training or insurance arrangements must be confirmed before the service is offered.

Training and readiness are not the same as assignment

Wara KarmaYoga Foundation Trust has an educational and social-development role that includes skills development and livelihood preparation. Its intended learning pathways include healthcare, care and community-support occupations.

Training may help people prepare for suitable care-related work, but completing a course does not automatically establish readiness for every care assignment. Competence, assessment, applicable qualifications, authorisations, experience and the needs of the particular service must be considered separately.

Wara Systems is intended to manage commercial Marketplace and customer-engagement functions where applicable. Its role should be distinguished from the Trust’s educational role and from the professional responsibilities of care providers.

Neither training participation nor inclusion in a proposed provider network guarantees a job, an assignment, a particular income or continuing work.

Continuity and service accountability

For recurring care arrangements, the service design should consider continuity rather than treating every visit as an isolated task.

Depending on the engagement, useful arrangements may include:

• A documented scope of duties and agreed schedule.
• A designated contact for the organisation and care-giver.
• Appropriate records of completed visits or assigned activities.
• A process for reporting changes and escalating concerns.
• Clear arrangements for absence, replacement and handover.
• Periodic review of service suitability and performance.
• A defined process for complaints and corrective action.

Not every engagement will require the same level of documentation. The arrangements should be proportionate to the person’s needs, the complexity of the service and the risks involved.

Discuss a care-service requirement

Organisations considering a care-related engagement should begin with a clear description of the service, the setting, the required capabilities, the schedule and the applicable safety or compliance requirements.

WARA can then assess whether the requirement fits the intended service model and whether a suitable arrangement can be explored. Any commitment depends on verified feasibility, provider suitability and availability, and agreed commercial and operational terms.

Continue exploring

• Services for Organisations: Explore the wider service domains.
• How Engagement Works: Understand scoping, feasibility, agreement and delivery.
• Quality and Accountability: Review the intended approach to quality, safety and responsibility.
• Production Services: Explore the proposed model for distributed production and bulk orders.
• Work with WARA: Return to the overview for organisations.

6.5 - Production Services

Connecting production demand with distributed capacity

Many organisations need products manufactured, assembled, stitched, processed or prepared in quantities that exceed what a single small producer can conveniently supply. At the same time, skilled workers, tailoring units, small workshops and rural producers may have useful capabilities but limited access to larger or recurring orders.

WARA’s proposed distributed production model aims to connect these two sides through coordinated work arrangements.

Instead of treating a bulk order as a simple transaction between a buyer and an individual producer, the model considers the complete requirement: specifications, quantity, production capacity, materials, timelines, quality expectations, packaging, logistics and commercial terms.

The approach may be relevant to textiles and tailoring, selected manufacturing activities, rural production and other forms of repeatable work. Actual feasibility depends on the product, the required standard, available capacity and the resources needed to fulfil the order.

Potential production areas

The following areas illustrate the kinds of work that may fit the model. They are potential service categories, not confirmation that production capacity or an active supplier network is currently available.

Textiles and tailoring

Potential assignments may include:

• Garment stitching and alteration.
• Uniforms for schools, organisations, hotels or other institutions.
• Workwear and reusable fabric products.
• Simple textile products made to defined dimensions.
• Batch production of approved designs.
• Finishing, labelling and packaging of completed items.

Textile orders often require a sample or approved reference, size specifications, fabric and colour requirements, stitching standards, tolerances and a clear method for inspecting finished pieces.

Small-scale manufacturing and assembly

Depending on available facilities and technical capability, distributed production may also be explored for selected assembly, fabrication or repeatable manufacturing tasks.

Possible requirements could include:

• Defined components or subassemblies.
• Standardised product specifications.
• Repetitive assembly or finishing.
• Labelling and packaging.
• Batch-based inspection and reporting.

The technical complexity of the product matters. Work involving specialised machinery, electrical systems, hazardous materials, safety-critical components or regulated products requires appropriate facilities, qualified personnel and applicable compliance arrangements.

Rural production and value-chain support

Some rural production activities may be suitable for coordinated orders when products, quantities and quality requirements can be defined clearly.

Potential areas include:

• Sorting and grading agricultural produce.
• Preparation and packaging of selected products.
• Production of suitable local goods.
• Basic processing activities where the required facilities and controls are available.
• Coordination between producers, collection points and buyers.

Food-related activities may require specific hygiene, processing, storage, labelling and licensing arrangements. No activity should proceed until its applicable requirements and the producer’s capability have been verified.

How a production order works

A production engagement should begin with a sufficiently detailed order brief. The sequence below describes the intended model.

1. Define the order

The organisation specifies what it needs and how the completed goods will be evaluated.

The order brief may include:

• Product description, drawing, design or reference sample.
• Quantity and any permitted variation.
• Materials, dimensions, sizes, colours and other specifications.
• Functional, durability or finishing requirements.
• Packaging, labelling and delivery instructions.
• Inspection and acceptance criteria.
• Target dates, delivery location and commercial constraints.

The more precisely the product is defined, the easier it is to assess whether the order can be produced consistently.

2. Assess production feasibility

The requirement is reviewed against the capacity and capabilities needed to complete it.

The assessment may consider:

• Suitable producers, workshops or production units.
• Available skills, equipment and workspace.
• Access to materials and components.
• Expected production rate and available capacity.
• Sample approval and any required trial production.
• Quality-control requirements.
• Labour, material, transport and other costs.
• Delivery schedules and dependencies.

A large order should not be accepted merely because the individual tasks appear straightforward. The combined capacity, coordination effort and quality requirements must also be feasible.

If the full order cannot be supported, alternatives may include a smaller initial batch, staged production, revised specifications or a different delivery schedule, subject to the organisation’s agreement.

3. Confirm the commercial arrangement

Before production begins, the buyer and the relevant parties should agree on the commercial and operational terms.

These may cover:

• Final specifications and approved samples.
• Order quantity, price and payment schedule.
• Responsibility for materials, tools and consumables.
• Production schedule and milestones.
• Ownership and handling of supplied materials or designs.
• Inspection, rejection, correction and rework procedures.
• Packaging, transportation and delivery responsibilities.
• Treatment of shortages, defects, delays and changes in quantity.
• Applicable confidentiality, intellectual-property and compliance obligations.

Where multiple producers are involved, the agreement should clarify how work is divided and who coordinates the overall order. Responsibilities should not be left implicit.

4. Organise production

Once the necessary terms and prerequisites are confirmed, production can be organised according to the agreed plan.

Depending on the order, this may involve allocating quantities to suitable production units, arranging materials, communicating specifications, scheduling work and establishing checkpoints.

For distributed production, consistent instructions are especially important. Different units must work to the same approved design and specifications rather than relying on informal interpretation.

A production coordinator, where one is appointed, may help consolidate status information and communicate issues. The precise coordination role and its responsibilities must be agreed for the engagement.

5. Inspect quality

Quality checks should be planned before the production run begins.

A suitable inspection approach may include:

• Approval of an initial sample.
• Verification of material and component specifications.
• In-process checks during production.
• Sampling or inspection of completed quantities.
• Checks for dimensions, finishing, functionality, labelling or packaging.
• Recording defects and agreed corrective actions.

The inspection method depends on the product, the order size and the consequences of a defect. Some products may require specialist testing or independent inspection.

Inspection should be performed by the party designated in the agreement. A statement that an order has been checked should reflect the checks actually carried out.

6. Consolidate and deliver the order

Where several production units contribute to one order, completed goods may need to be counted, inspected, sorted, labelled, packed and consolidated before dispatch.

The delivery plan should establish:

• Where completed goods will be collected or delivered.
• Who arranges transportation and bears the relevant costs.
• How quantities and packaging will be verified.
• What delivery documentation is required.
• How shortages, damage or discrepancies will be reported.
• When delivery is considered complete and the order can be accepted.

For repeat orders, delivery records and feedback may help improve future planning, provided appropriate recordkeeping arrangements are in place.

Why standardisation matters

Distributed production works best when a task can be described clearly and its output can be checked against an agreed standard.

A standardised production package may contain:

• An approved design, drawing or sample.
• A bill of materials or material specification, where applicable.
• Step-by-step production instructions.
• Defined tolerances and finishing requirements.
• A quality checklist.
• Packaging and labelling instructions.
• An acceptance and defect-reporting procedure.

Standardisation does not mean that every product must be identical in every respect. It means that acceptable variation is understood in advance and that producers have a common reference for the work.

For products requiring craftsmanship or local variation, the specification should distinguish the essential requirements from the features that may legitimately differ.

Working with small producers and local units

The distributed model is intended to create a practical way for smaller production units to participate in suitable orders without assuming that every unit has the resources of a large factory.

An order may be divided into manageable batches where the product and quality requirements permit it. However, dividing production creates additional coordination needs.

Before adopting this arrangement, the parties should consider:

• Whether each unit can meet the required specification.
• Whether all units can obtain consistent materials.
• How quantities and schedules will be allocated.
• Who provides instructions and resolves production questions.
• How quality will be checked across different batches.
• How transport and consolidation costs affect the overall price.
• How payment and responsibility are allocated among participating parties.

The suitability of a distributed approach must be established for each product. Some orders may be better handled by a single specialist producer.

Responsibilities and accountability

A production engagement should define the responsibilities of the organisation placing the order, the commercial coordinator where applicable, the producer and any inspection or logistics provider.

Wara Systems is intended to operate the commercial Marketplace and coordinate customer engagements and provider participation where applicable. This does not automatically make it the manufacturer, quality certifier, logistics operator or legal guarantor of every order. The actual contractual responsibilities must be stated for each engagement.

Wara KarmaYoga Foundation Trust has a separate educational and social-development role, including vocational learning and livelihood preparation. Training and skills development may help people prepare for suitable production work, but training participation does not guarantee an order, a job or a particular income.

Starting with a manageable order

For an organisation considering distributed production for the first time, a small initial batch or pilot order may help test the specification, production process, quality requirements and delivery arrangements.

A pilot can provide evidence about:

• Whether the product specification is sufficiently clear.
• Whether the production method is practical.
• Whether the required quality can be achieved consistently.
• Whether the schedule and cost assumptions are realistic.
• Whether coordination and logistics work as intended.

A pilot should have its own agreed scope and acceptance criteria. Successful completion of one batch can inform a larger order, but does not automatically prove that unlimited or recurring capacity is available.

Discuss a production requirement

To explore a production engagement, an organisation should be prepared to describe the product, quantity, specifications, target schedule, delivery location and required quality standard.

Drawings, photographs, reference samples, existing product specifications or previous order details can help make the discussion more concrete.

WARA can then assess whether the requirement fits the intended production model and whether suitable capacity can be explored. Any commitment depends on verified feasibility, producer availability and agreement on the commercial and operational terms.

Continue exploring

• Services for Organisations: Explore the wider service domains.
• How Engagement Works: Understand the engagement process from enquiry to closure.
• Quality and Accountability: Review the intended approach to quality checks and responsibility.
• Care Services: Explore the proposed coordinated care-giver partner model.
• Work with WARA: Return to the overview for organisations.

6.6 - Partnerships

Building relationships around shared requirements

Organisations often need more than an individual service or a one-time order. A hotel may require recurring operational support, a manufacturer may need a dependable production arrangement, or an institution may want to explore a longer-term collaboration around training and service delivery.

These situations call for a partnership approach that starts with a defined purpose and develops according to demonstrated feasibility.

WARA aims to connect organisational requirements with suitable capabilities, service providers and work arrangements. The nature of the relationship depends on what the parties want to achieve, what each can contribute and what responsibilities they are prepared to accept.

A partnership discussion is not a guarantee that a proposed service, programme or commercial arrangement will be implemented. Each initiative needs its own assessment and agreement.

Who can explore a partnership?

Businesses and commercial organisations

Businesses may approach WARA to discuss defined services, production requirements, recurring assignments or operational support.

Potential participants include:

• Hotels, resorts and hospitality businesses.
• Healthcare organisations and care-service providers.
• Manufacturers, producers and distributors.
• Tourism and travel businesses.
• Local service businesses.
• Organisations with digital, administrative or customer-support requirements.

The purpose is to understand the organisation’s actual needs and determine whether a suitable engagement can be structured.

Educational and training institutions

Schools, training centres and educational institutions may explore collaboration around learning, practical capability development, vocational preparation and exposure to real-world tasks.

Potential areas for discussion include:

• Introducing relevant digital and vocational learning.
• Connecting course outcomes with practical activities.
• Exploring supervised workplace exposure where appropriate.
• Identifying the capabilities needed for specific occupational pathways.
• Understanding potential links between training and suitable work opportunities.

Any training partnership must define the learning objectives, delivery responsibilities, facilities, assessment arrangements and applicable recognition requirements. Collaboration alone does not establish formal qualification recognition or guarantee occupational outcomes.

Service providers and production units

Independent professionals, small businesses, workshops and production units may explore participation in suitable commercial assignments.

Potential areas include:

• Defined service assignments.
• Tailoring, textile work and selected production activities.
• Technical and infrastructure services within the provider’s competence.
• Digital, administrative and customer-support work.
• Local service delivery and other suitable occupational activities.

Participation depends on the provider’s capability, availability, suitability for the requirement and willingness to work under agreed commercial and operational conditions.

Community and development organisations

Community organisations, charitable institutions and development partners may explore initiatives involving digital literacy, skills development, livelihood preparation or access to suitable service opportunities.

Such discussions should distinguish educational and charitable objectives from commercial transactions. The intended outcomes, funding arrangements, participant responsibilities and accountability requirements must be clear before an initiative proceeds.

Partnership models

Different objectives call for different forms of collaboration. The following are possible models to explore, not a list of confirmed or currently active partnerships.

1. Recurring service engagement

An organisation has a continuing requirement for a defined service.

The parties agree on the scope, schedule, service expectations, communication arrangements, commercial terms and review process. The arrangement may be revised as the organisation’s needs or delivery capacity change.

This model is relevant where continuity and predictable responsibilities matter more than treating each requirement as an isolated assignment.

2. Production and supply partnership

An organisation needs goods produced or supplied repeatedly, while one or more suitable producers may be able to fulfil the requirement.

The parties establish product specifications, quantities, production capacity, pricing, quality checks, delivery arrangements and procedures for changes or defects.

Where multiple production units are involved, the agreement should also identify how production is coordinated and who is responsible for consolidation and delivery.

3. Provider-network participation

A suitable service provider or production unit may participate in the wider WARA Marketplace ecosystem.

The purpose is to explore whether the provider’s capabilities match requirements received through the commercial engagement model. Any actual assignment remains subject to suitability, availability, customer requirements and agreed terms.

Joining or expressing interest in a network should not be presented as a promise of regular work or income.

4. Training and livelihood collaboration

Wara KarmaYoga Foundation Trust may explore educational and social-development initiatives with appropriate institutions and partners.

Potential areas include foundational digital literacy, vocational learning, practical capability development and preparation for suitable occupational pathways.

Where a commercial organisation contributes to such an initiative, the parties should separately define the charitable or educational activity and any subsequent commercial engagement. Learners should not be promised jobs, assignments or earnings as an automatic result of participation.

5. Institutional or programme partnership

An institution may wish to explore a broader initiative involving several activities, locations or stakeholder groups.

Such an initiative may require a written concept, defined objectives, responsibilities, delivery phases, resource commitments, governance and an agreed method of evaluating progress.

A broader partnership should be developed incrementally. Its scale should reflect the resources, capabilities and commitments that the participating parties can substantiate.

How a partnership develops

A partnership should progress through clear stages rather than relying on a general expression of interest.

Step 1: Identify the shared objective

The parties explain what they want to achieve, why the collaboration is useful and who is expected to benefit.

The objective should be specific enough to guide decisions. For example, it may concern a recurring service requirement, a defined production order, a training programme or a pilot involving selected participants.

Step 2: Understand each party’s contribution

The parties identify the capabilities and resources each can contribute.

These may include customer requirements, specialist knowledge, facilities, equipment, personnel, training, funding, production capacity or access to a relevant market.

Potential contributions should not be treated as commitments until the responsible party has confirmed them.

Step 3: Assess feasibility and risks

The proposed arrangement is reviewed for practical, operational, financial and regulatory feasibility.

Relevant questions include:

• Is there a clearly defined need?
• Are the required capabilities and resources available?
• Can the parties meet the expected quality and schedule?
• Are the costs and commercial terms sustainable?
• Who carries the operational, financial and legal responsibilities?
• Are there safety, privacy, qualification or regulatory requirements?
• How will disagreements, changes or failure to meet commitments be handled?

The assessment may lead to a revised proposal, a smaller pilot, a request for further information or a decision not to proceed.

Step 4: Define the agreement

Before implementation, the parties should record the relevant terms.

Depending on the arrangement, these may include objectives, scope, contributions, ownership of deliverables, pricing or funding, payment, timelines, confidentiality, data handling, quality standards, reporting, termination and dispute resolution.

The appropriate agreement may range from a simple service confirmation to a more detailed institutional or commercial contract. The form should reflect the nature and risk of the relationship.

Step 5: Start with a defined activity

Where feasible, the parties may begin with a limited assignment, pilot or initial phase.

A defined starting point makes it easier to test assumptions, understand coordination requirements, evaluate quality and identify changes needed before expanding the arrangement.

A pilot should have agreed objectives, responsibilities, costs, duration and criteria for evaluating the result.

Step 6: Review and decide what comes next

The parties review the outcome against the original objectives and the evidence available.

They may decide to continue, adjust the scope, introduce additional activities, expand to another location or conclude the arrangement. Expansion should follow demonstrated capability and renewed agreement, not an assumption that a successful initial activity can be scaled without further planning.

The distinct roles of WARA’s organisations

Wara Systems and Wara KarmaYoga Foundation Trust have related but distinct purposes.

**Wara Systems ** is intended to operate the commercial Marketplace, customer engagement and coordination of suitable providers and assignments where applicable.

Wara KarmaYoga Foundation Trust has a social-development and educational role, including digital literacy, vocational learning, skills development and livelihood preparation.

A partnership may involve one organisation or, where appropriate, separately defined activities involving both. The parties should identify which legal entity is responsible for each commitment, who signs the agreement, how funds are handled and which obligations apply.

The Trust should not automatically be treated as the commercial service provider, nor should a commercial engagement be represented as a charitable programme without an appropriate basis.

What makes a partnership workable?

A productive partnership needs more than a shared vision. It needs practical alignment on several points:

• A real requirement: There is a defined need or objective that the collaboration addresses.
• Complementary capabilities: Each party contributes something relevant to the intended outcome.
• Clear accountability: Responsibilities and decision-making authority are explicit.
• Sustainable terms: The arrangement accounts for the actual cost and resources required.
• Appropriate standards: Quality, safety, compliance and reporting expectations are understood.
• Open communication: The parties have a way to raise problems and agree on changes.
• Evidence of progress: Results can be assessed against the agreed objectives.

Not every relationship needs to become a large, long-term partnership. A well-defined single assignment may be the right starting point and may remain the most suitable form of engagement.

Start a partnership discussion

Organisations interested in exploring a partnership can begin by describing:

1. The objective or requirement they want to address.
2. The people, capabilities, facilities or resources they can contribute.
3. The intended beneficiaries or customers.
4. The expected scale, location and timeframe.
5. The constraints, standards and responsibilities that must be considered.

This information provides a starting point for assessing whether a practical collaboration can be developed. Any proposal remains subject to feasibility, availability, the appropriate approvals and mutually agreed terms.

Continue exploring

• Work with WARA: Explore the overall engagement model for organisations.
• Services for Organisations: Review potential service domains.
• How Engagement Works: Understand how individual requirements move from enquiry to delivery.
• Quality and Accountability: Review the intended approach to responsibility and quality.
• Frequently Asked Questions: Find answers to common commercial and operational questions.

6.7 - Frequently Asked Questions

About working with WARA

What is WARA’s role when an organisation approaches it?

WARA’s intended commercial model is to connect organisational requirements with suitable services, providers and coordinated work arrangements through Wara Systems .

The process begins by understanding the requirement and assessing whether it can be fulfilled. Depending on the engagement, the work may involve a single provider, a production unit or coordination across multiple participants.

The exact role of Wara Systems must be established for each engagement. Organisations should not assume that WARA directly employs every worker, performs every service itself or manufactures every product listed within a potential service domain.

What kinds of organisations can approach WARA?

Potential customers include businesses, hotels and resorts, healthcare organisations, manufacturers, tourism businesses, educational institutions, community organisations and other organisations with defined service or production requirements.

The relevant question is whether the requirement fits a service area that WARA can feasibly support. Inclusion of a sector in the service catalogue does not, by itself, establish that a particular service is currently available.

Does WARA work only with its own trained workers?

The intended Marketplace is not limited to people trained through WARA-related programmes. It is designed to allow suitable organisations and independent service providers to participate, subject to the requirements of the assignment.

Provider selection should consider demonstrated capability, availability, relevant experience, qualifications or authorisations where required, and suitability for the specific work.

Participation in a training programme does not automatically qualify someone for every assignment.

Services and availability

Are all the services listed on the website available now?

Not necessarily. The service catalogue describes potential domains and engagement categories, but each specific service must be assessed for actual availability and feasibility.

Before committing to a requirement, WARA should confirm whether suitable providers, resources, facilities, capacity and the necessary arrangements are available.

Where a service is still being developed or is open only for enquiry, that status should be made clear.

What if our requirement does not fit a listed service exactly?

Describe the desired outcome rather than trying to fit the requirement into a category.

WARA can consider the scope, required capabilities, location, resources, timing and constraints to determine whether the work can be supported, whether the scope needs to change or whether the requirement should be declined.

A related service category is not sufficient evidence that a new or specialised requirement can be fulfilled.

Can WARA support recurring work?

Recurring work may be explored where the requirement, provider capacity, commercial terms and coordination arrangements are sustainable.

The parties should agree on the expected frequency, service standards, reporting, handling of absences or delays, review arrangements and the process for changing or ending the engagement.

Recurring work should not be treated as guaranteed until the relevant agreement establishes the commitment.

Can WARA serve organisations in different locations?

The intended model includes local and distributed work, but geographic coverage depends on the service, provider availability, travel or logistics, infrastructure and other practical requirements.

The organisation should specify the work location or delivery destination during the initial enquiry. Coverage must be confirmed for the particular assignment.

Enquiry, feasibility and delivery

What information should we provide in our first enquiry?

Provide as much of the following as is reasonably available:

• A description of the service, product or outcome required.
• The location and expected schedule.
• Quantity, frequency or approximate order size.
• Required skills, equipment, materials or facilities.
• Quality, safety, regulatory and documentation requirements.
• Budget or commercial constraints, where known.
• Any relevant specifications, reference documents or samples.

The initial enquiry need not contain every final detail. Further information may be requested during scoping and feasibility review.

How does WARA decide whether to accept an assignment?

The requirement is assessed against the capabilities and resources needed to deliver it.

Factors may include provider suitability and availability, technical requirements, schedule, geography, materials, equipment, quality standards, safety, applicable regulation and commercial viability.

The result may be to proceed with a proposal, request more information, revise the scope, explore a phased arrangement or decline the assignment.

Does submitting an enquiry mean the work is confirmed?

No. An enquiry initiates a discussion; it does not establish that a provider has been assigned or that a delivery date, price or outcome has been guaranteed.

The parties should confirm the scope, feasibility, responsibilities, commercial terms and any necessary approvals before work begins.

Can we begin with a small assignment or pilot?

A limited initial assignment may be a practical way to assess a service arrangement or production process before considering a larger commitment.

The pilot should have a defined scope, schedule, cost, responsibilities and acceptance criteria. Any subsequent expansion should depend on the results, available capacity and a further agreement where needed.

Commercial terms and responsibilities

How are prices determined?

Pricing depends on the nature and scope of the work. Relevant factors may include labour, materials, equipment, travel, logistics, supervision, quality checks, service frequency and coordination effort.

The commercial proposal should make clear what is included, what is excluded, any additional charges and the applicable payment terms.

There is no single price that can be assumed to apply across all service domains or assignments.

Who is responsible for the quality of the work?

Responsibility depends on the agreed engagement and the roles of the organisation, Wara Systems , the assigned provider and any other participating party.

The agreement should define the required standard, who performs the work, who checks the result, how acceptance is recorded and how defects or complaints are handled.

Organisations should establish these responsibilities before the assignment begins rather than assuming that a coordinating role automatically includes every delivery or certification obligation.

What happens if the work does not meet the agreed requirements?

The parties should follow the correction, rework, replacement or dispute-resolution procedure established in the agreement.

The issue should be assessed against the agreed specifications and the evidence available. The response may depend on the cause of the problem, the responsibilities of each party and the applicable commercial terms.

The remedy, associated costs and any revised schedule should be handled according to the agreement and applicable law.

Who handles payment and invoicing?

The agreement should identify the contracting parties, the entity responsible for invoicing, the payment recipient, the payment schedule and the applicable taxes.

Where several providers participate, the arrangement should also clarify how their commercial responsibilities and payments are handled.

Organisations should verify these details before authorising work or making a payment. The payment process must be confirmed for each engagement rather than assumed to follow one universal arrangement.

Production orders and distributed work

Can WARA coordinate a bulk production order?

Distributed production and bulk-order coordination are intended areas of the WARA model. Their feasibility depends on the product, specifications, quantities, producer capacity, materials, quality requirements and delivery arrangements.

A production proposal may include sample approval, batch planning, inspection, packaging and logistics where relevant.

An order should not be confirmed until sufficient capacity and the necessary commercial and operational arrangements have been established.

How is consistency maintained when several producers are involved?

The arrangement may use common specifications, approved samples, production instructions, quality checklists and agreed inspection procedures.

The parties should also define how quantities are allocated, how materials are managed, how defects are reported and who consolidates the completed goods.

The exact controls depend on the product and the risk associated with variation. Any claim about inspection or quality certification should reflect the checks actually performed.

Can we place repeat orders?

Repeat orders may be explored when the product requirements, pricing, production capacity and quality arrangements support continued delivery.

A previous successful order can inform future planning, but it does not automatically guarantee capacity for a larger quantity, a tighter deadline or a different specification.

Each repeat order should follow the applicable ordering and confirmation procedure.

Care and safety-sensitive services

Can organisations request care-givers or patient-support personnel?

Care and community support are part of the intended service framework. Potential activities include appropriate home-care, elderly-care, non-clinical patient support and related coordination.

The availability of a suitable provider must be verified for the particular requirement. The assessment should consider the care setting, duties, competence, relevant qualifications or authorisations, safety, supervision and continuity requirements.

Can a care assistant perform clinical tasks?

Only where the person is appropriately qualified and authorised, and the task is permitted within the applicable professional and legal requirements.

A general care-support assignment must not be treated as permission to diagnose, prescribe, perform regulated clinical procedures or make clinical decisions.

The duties, escalation arrangements and professional boundaries must be defined before the assignment begins.

What happens if a worker is unavailable or a safety concern arises?

The arrangement should establish how absences, replacements, urgent concerns and service interruptions are reported and managed.

For safety-sensitive work, it should also identify who can suspend an assignment, who must be contacted and what steps are required before work can resume.

Replacement cannot be assumed to be immediate or guaranteed. A suitable alternative must be assessed against the requirements of the service.

Training and partnership

Does working with WARA guarantee access to trained workers?

No. Training programmes and commercial assignments are separate activities. Completing training does not guarantee employment, an assignment, a particular income or immediate availability for work.

A worker’s suitability must be assessed against the actual duties, demonstrated competence and any applicable qualification or authorisation requirements.

Can our organisation collaborate on vocational training or livelihood programmes?

Potentially. Educational institutions, employers and development organisations may explore collaboration with Wara KarmaYoga Foundation Trust around digital literacy, vocational learning, practical capability development and livelihood preparation.

Any initiative should define its objectives, responsibilities, resources, delivery arrangements and assessment requirements.

Formal qualification recognition, funding eligibility and authority to deliver or certify a programme must be established separately where applicable.

What is the difference between Wara Systems and Wara KarmaYoga Foundation Trust?

Wara Systems is intended to operate the commercial Marketplace, customer engagement and coordination of providers and assignments where applicable.

Wara KarmaYoga Foundation Trust has a distinct educational and social-development role, including training, skills development and livelihood preparation.

The relevant legal entity, contractual responsibilities and financial arrangements should be confirmed for each engagement. The Trust should not automatically be treated as the commercial service provider, and a commercial transaction should not be represented as a charitable activity without an appropriate basis.

Starting a discussion

What is the next step if we want to work with WARA?

Begin by describing the requirement, desired outcome, location, schedule, quality expectations and known constraints.

The next step is to clarify the scope, assess feasibility and determine whether a suitable commercial or partnership arrangement can be developed. A commitment should follow only after the necessary terms, responsibilities and approvals have been confirmed.

For an overview of the process, see How Engagement Works. To understand the broader service domains, visit Services for Organisations. For quality, safety and delivery responsibilities, see Quality and Accountability.

If your organisation has a specific requirement, prepare a short description of the work, expected outcome, location, quantity or frequency, timeline and relevant constraints. This provides a practical starting point for an initial discussion.

7 - Become a WARA Work Partner

Turn your capabilities into opportunities for work

People develop useful capabilities in different ways. Some learn through formal training, others through practical experience, and many combine the two. WARA’s work-partner model is intended to help suitable people connect these capabilities with organisations and customers that need particular services or products.

The model covers a range of potential work, from digital and administrative services to care support, technical services, hospitality, tailoring, manufacturing and rural production. The work available to any individual will depend on the actual requirements received, the person’s capabilities, location, availability and the conditions of the assignment.

Becoming a WARA work partner is intended to be a way to participate in this wider ecosystem. It is not a promise of employment, a guaranteed source of assignments or a commitment to a particular income.

What is a WARA work partner?

A work partner is an individual or service provider who may participate in suitable work arrangements within the WARA ecosystem.

Depending on the work and the person’s capabilities, participation may involve:

• Completing a defined service assignment.
• Supporting an organisation with digital, administrative or customer-service tasks.
• Performing suitable technical, household, hospitality or care-support activities.
• Contributing to tailoring, production, assembly, finishing or packaging work.
• Working with other providers on a coordinated assignment.
• Developing the capability to undertake independent work or eventually organise a service of one’s own.

The nature of participation depends on the assignment and the agreed arrangement. A work partner should understand the tasks, responsibilities, quality expectations, payment terms and applicable safety requirements before accepting work.

Partner status should not be confused with a permanent job, a formal employment relationship or guaranteed access to customer requirements. The actual relationship must be established by the applicable agreement.

What kinds of work may be relevant to you?

WARA’s broader work and learning framework identifies seven domains. These provide a way to organise potential occupational pathways, not a guarantee that every type of work is currently available.

1. Digital, AI and business services

Potential areas include documentation, data processing, digital content, customer support, booking coordination, online-service assistance, business administration and suitable technology-support tasks.

Some work may be performed locally, while other assignments may be suitable for remote or distributed delivery. The requirements depend on the customer, the tools used, the task and the expected standard.

2. Education and learning

Potential activities include learning-centre support, digital classroom assistance, preparation of learning materials and supervised tutoring within a person’s demonstrated subject competence.

Teaching and tutoring responsibilities should match the person’s actual knowledge, capability and any applicable requirements.

3. Healthcare, care and community support

Potential pathways include home-care assistance, elderly-care support, non-clinical patient assistance and digital healthcare coordination.

Care work requires particular attention to dignity, safety, competence and professional boundaries. Training or general experience does not authorise a person to perform regulated clinical tasks.

4. Security, technical and infrastructure services

Potential work may include broadband and networking support, equipment installation, CCTV-related technical work and other infrastructure tasks within the person’s competence and authorisation.

Some activities require specialist training, equipment, permissions or licences. These requirements must be verified for the particular assignment.

5. Textiles, manufacturing and rural production

Potential activities include sewing, garment production, alterations, finishing, production assistance, quality checking, packaging and selected small-scale manufacturing tasks.

Where production is distributed across several workers or locations, clear specifications, material arrangements, deadlines and quality checks become especially important.

6. Hospitality, tourism and local services

Potential work may include housekeeping, hospitality support, food-service assistance, tourism coordination, homestay support and other local service activities.

The specific role will depend on the customer’s requirement, the worker’s readiness and any applicable safety or service standards.

7. Agriculture, household and essential services

Potential activities include farm and nursery support, produce handling, selected rural enterprise activities and household services.

The required skills, facilities, equipment and safety arrangements depend on the actual task.

Digital capability supports work across these domains. It is a common foundation that can help people communicate, manage information, use digital tools and participate in modern service arrangements.

How work participation is intended to happen

The intended model connects the needs of customers with the capabilities of suitable workers and service providers.

A typical assignment may follow this sequence:

1. Requirement received: An organisation or customer describes the work that needs to be done.
2. Scope clarified: The tasks, expected result, location, schedule and relevant constraints are established.
3. Suitability assessed: Potential participants are considered against the required skills, experience, availability and any applicable qualifications or authorisations.
4. Terms confirmed: The responsibilities, payment, timing, quality expectations and other conditions are agreed.
5. Assignment accepted: The selected participant confirms their willingness and ability to undertake the work under those terms.
6. Work completed: The participant performs the agreed tasks and follows the relevant instructions and safety requirements.
7. Completion and settlement: The work is checked against the agreed criteria, and payment is handled according to the applicable terms.

This describes the intended assignment model. The actual procedure, available opportunities and responsibilities must be confirmed for each engagement.

What you should bring as a work partner

You do not need to possess every possible skill. You do need to understand your current capabilities and the requirements of the work you accept.

Useful foundations include:

• Practical capability: The ability to perform the required tasks, supported by training, experience or demonstrated competence.
• Reliability: Communicating clearly, respecting agreed schedules and reporting problems promptly.
• Quality awareness: Understanding the expected result and checking your work against the agreed requirements.
• Safety and responsibility: Following appropriate procedures and recognising when a task is beyond your competence or authorisation.
• Willingness to learn: Improving your skills and adapting to suitable new tasks.
• Professional conduct: Treating customers, colleagues and the people you serve with respect.

Different assignments require different levels of preparation. Some may be suitable for an entry-level worker under supervision; others require an experienced independent worker or a properly qualified specialist.

Learning can support your next step

Wara KarmaYoga Foundation Trust has an educational and social-development role that includes digital literacy, vocational learning, skills development and livelihood preparation.

The intended learning framework uses progressive stages of capability and responsibility:

Foundation → Certificate → Diploma

Broadly, these stages are intended to support foundational capability, more specialised occupational skills, and the ability to organise work or develop a service enterprise. The requirements depend on the particular course and pathway.

Training is not a substitute for assignment-specific assessment. A person may need further practice, verification, experience or external qualifications before being suitable for particular work. Any formal recognition of a course or certificate must be established separately.

Learning can help you prepare for opportunities, but it does not guarantee that a suitable assignment will be available when you complete a programme.

From individual work towards greater independence

Participation may begin with a defined task and develop as your skills, experience and ability to take responsibility increase.

For some people, a possible progression may be:

Learner → Skilled Worker → Independent Worker → Service Provider or Enterprise

This is an illustrative pathway, not a fixed career ladder. Not everyone needs to become an entrepreneur, and progression depends on demonstrated capability, personal circumstances, market demand and the opportunities available.

A person who wants to organise a service or coordinate other workers may eventually need additional capabilities in planning, customer communication, pricing, quality control, resource management and financial administration.

The purpose of the framework is to make these possible next steps visible without treating them as guaranteed outcomes.

Understand the distinction between the Trust and the Marketplace

Wara KarmaYoga Foundation Trust and Wara Systems have different roles.

The Trust focuses on educational and social-development activities, including training, skills development and livelihood preparation.

**Wara Systems ** is intended to operate the commercial Marketplace, customer engagement and coordination of suitable providers and assignments where applicable.

The two roles may connect, but they are not interchangeable. Participating in a Trust training programme does not automatically enrol someone in the commercial Marketplace, establish eligibility for every assignment or guarantee paid work.

The requirements for training, verification, Marketplace participation and individual assignments should be explained separately.

Take the next step

If you are interested in participating, start by understanding the model and identifying the work you can currently perform or want to prepare for.

The following pages explain the main aspects of participation:

• Why Partner with WARA: Understand the potential benefits and limitations of the model.
• The Partnership Model: Learn about partner status, responsibilities and assignment-based participation.
• How Assignments Work: Understand how work may be offered, accepted and completed.
• Payment and Settlement: Learn why payment terms and completion criteria must be agreed in advance.
• Joining and Verification: Understand the intended approach to checking capability and suitability.
• Learning and Skills: Explore how learning may support preparation for suitable work.

7.1 - Why Partner with WARA

A different way to approach work

Finding work is not only about possessing a skill. A person also needs access to customers, a clear understanding of what those customers require, and the ability to deliver work to an agreed standard.

An individual worker may be good at tailoring, technical support, care assistance, digital services or another practical occupation but lack the resources to find customers independently. A small service provider may have the opposite problem: customers are available, but organising people, schedules, materials and quality becomes difficult as the work grows.

WARA’s intended work-partner model aims to address some of these challenges by connecting customer requirements with suitable workers and service providers through a coordinated commercial ecosystem.

The model is designed to support different ways of participating. You may undertake individual assignments, contribute to a team, gain experience in a defined occupational area or, over time, explore independent service provision.

Potential benefits of partnership

Access to suitable work opportunities

The intended Marketplace model provides a route through which customer requirements can be considered for assignment to suitable providers.

Rather than requiring every worker to find every customer independently, the model aims to coordinate demand and provider participation where appropriate.

Access to work is not guaranteed. Opportunities depend on customer requirements, location, timing, capability, provider availability and the commercial terms of the assignment.

A clearer understanding of what customers expect

Work becomes easier to plan when the requirements are explicit.

A defined assignment should explain what needs to be done, what result is expected, when and where the work must be completed, and how completion will be assessed.

Clear requirements can help you understand whether a task is suitable for your current capabilities before accepting responsibility for it.

An opportunity to build practical experience

Suitable assignments may allow you to apply what you have learned in real working situations. Depending on the task, this can help you practise communication, time management, quality checking, problem-solving and customer service alongside your occupational skills.

Experience should be built through work that matches your competence and is performed under appropriate conditions. You should not be assigned responsibilities beyond your preparation or authorisation.

A pathway to improve your capabilities

The WARA learning framework connects foundational learning, specialised skills and increasing responsibility.

You may identify a need to improve a practical skill, develop digital capability, learn how to communicate with customers or understand how to organise a service. Relevant learning can help prepare you for future opportunities.

Training and commercial assignments remain separate processes. Completing a course does not automatically qualify you for a particular job or guarantee access to paid work.

Participation without immediately building your own business

Running an independent service involves more than performing the work. It may require finding customers, preparing quotations, managing schedules, buying materials, maintaining records, handling complaints and collecting payments.

An assignment-based arrangement may provide a way to undertake defined work without assuming every one of these responsibilities independently, depending on the agreement.

This does not remove your responsibility for the tasks and commitments you accept. It means the division of responsibilities should be established before the work begins.

A possible route towards independent work

Some partners may eventually want to serve customers directly or organise a small service business.

With suitable experience and additional capability, a worker may explore how to price services, plan resources, manage quality and coordinate other workers. These skills can support a transition towards independent work or enterprise.

This is a possible progression, not a required outcome. You may prefer to remain an individual skilled worker, specialise in your occupation or participate in team-based assignments.

Different ways to participate

The most appropriate form of participation depends on your skills, experience, circumstances and ambitions.

These are illustrative participation paths, not automatic membership grades or a promise of promotion. The requirements for each role must be defined and verified.

Work across different occupational domains

The WARA work framework covers seven broad domains. Your opportunities, if available, will depend on the specific assignments and the suitability of your capabilities.

• Digital, AI and business services: Documentation, data handling, customer support, booking coordination, digital content and other defined business-support tasks.
• Education and learning: Learning assistance, digital classroom support and other activities within demonstrated subject competence.
• Healthcare, care and community support: Appropriate home-care, elderly-care and non-clinical support activities.
• Security, technical and infrastructure services: Suitable networking, equipment installation and technical support tasks, subject to required competence and authorisation.
• Textiles, manufacturing and rural production: Tailoring, garment production, finishing, packaging and other defined production tasks.
• Hospitality, tourism and local services: Housekeeping, hospitality assistance and other suitable service activities.
• Agriculture, household and essential services: Selected farm, nursery, produce-handling and household-support activities.

The framework is intended to accommodate both locally delivered work and suitable distributed assignments. It does not establish that every domain or task is currently open for participation.

Understand the commercial arrangement

Wara Systems is intended to operate the commercial Marketplace, customer engagement and coordination of suitable providers and assignments where applicable.

Wara KarmaYoga Foundation Trust has a separate educational and social-development role, including digital literacy, vocational learning, skills development and livelihood preparation.

The distinction matters because training, network participation and commercial work are different activities.

Before accepting an assignment, you should understand:

• Who is engaging you and under what arrangement.
• What work you are expected to perform.
• Whether you are responsible for supplying tools, materials or transport.
• How the work will be assessed and accepted.
• How much you will be paid, by whom and under what conditions.
• What happens if the requirements change or the work cannot be completed as planned.
• What safety, confidentiality and other obligations apply.

Do not assume that joining a training programme or expressing interest in the network creates a right to receive assignments.

What WARA expects from work partners

A coordinated work model depends on participants who take their commitments seriously.

Partners should be prepared to:

• Describe their skills and experience accurately.
• Accept only work they can perform safely and competently.
• Follow agreed instructions, specifications and schedules.
• Communicate delays, difficulties and changes promptly.
• Maintain the quality required for the assignment.
• Respect customers, colleagues and the people receiving a service.
• Protect confidential information and follow applicable safety requirements.
• Raise concerns when a task exceeds their competence or authorisation.

Reliability and professional conduct are part of occupational capability. A strong technical skill is valuable, but it must be accompanied by responsible working practices.

What partnership does not guarantee

It is important to understand the limits of the model before joining.

Participation does not automatically guarantee:

• Employment or a permanent job.
• A minimum number of assignments.
• A particular monthly income.
• Immediate placement after training.
• Work in a preferred location or occupational domain.
• Progression to a higher responsibility level.
• Formal recognition of a course or certificate by an external authority.

The purpose of the model is to create a structured way to explore suitable work opportunities. Actual outcomes depend on customer demand, demonstrated capability, availability and the arrangements agreed by the relevant parties.

Decide whether the model suits you

WARA’s intended work-partner network may be relevant if you want to apply an existing skill, develop practical experience, explore suitable assignments or gradually prepare for more independent work.

Before proceeding, consider three questions:

1. What can I do now? Identify the tasks you can perform competently and any limits to your current skills.
2. What do I need to develop? Consider additional training, practice, tools, experience or qualifications that may be necessary.
3. What kind of work arrangement suits me? Decide whether you prefer defined assignments, team-based work, specialist services or a longer-term goal of independent service provision.

These answers can help you identify a realistic next step without assuming that every opportunity will be immediately available.

Explore the work-partner pathway

• The Partnership Model: Understand partner status, responsibilities and assignment-based participation.
• How Assignments Work: Learn how assignments may be offered, accepted and completed.
• Payment and Settlement: Understand the importance of agreed payment and completion terms.
• Joining and Verification: Learn about the intended approach to assessing suitability.
• Learning and Skills: Explore how training may prepare you for suitable work.
• Frequently Asked Questions: Find practical answers about participation.

7.2 - How Assignments Work

From a customer requirement to an assignment

An assignment begins with a real requirement. A customer, organisation or service provider needs a particular task or outcome to be delivered. The work must then be described clearly enough for a suitable worker to understand what is expected.

The intended KarmaYoga Marketplace model connects customer demand with workers whose demonstrated capabilities are appropriate for the work. The Marketplace may help coordinate the assignment, but the actual process and responsibilities depend on the occupation, the customer’s requirements and the applicable arrangement.

The basic workflow is:

Customer Demand → Assignment Definition → Worker Offer → Decision → Work → Quality Check → Acceptance → Payment → Work History

Each stage serves a purpose. A worker should not be expected to accept an unclear commitment, and a customer should not have to guess whether the submitted work meets the agreed requirements.

1. How an assignment is offered

Before an assignment is offered, its essential requirements should be defined. Depending on the occupation, these may include:

• Scope: What work must be performed, and what is outside the assignment?
• Expected result: What must be delivered or completed?
• Location: Where must the work take place, or can it be performed remotely?
• Schedule: When can the work begin, and when must it be completed?
• Resources: Who supplies the tools, materials, equipment or access required?
• Quality and safety: What standards, precautions and checks apply?
• Payment: How much will be paid, how is the amount calculated, and what conditions govern payment?
• Completion and acceptance: What evidence or inspection is required before the work is considered complete?

Not every assignment needs a lengthy specification. A small, familiar task may need only a concise description. A technical installation, production order or multi-stage project may require detailed instructions and milestones.

The principle is the same: the assignment must communicate the commitment clearly enough for the worker to make an informed decision.

2. How a worker decides whether to accept

An offer is an opportunity, not an obligation. A worker should review the requirements before committing.

The worker should consider:

• whether the task matches their demonstrated skills and authorised scope of practice;
• whether they understand the instructions and expected result;
• whether they have the time and availability to complete the work;
• whether the required tools, materials, transport and other resources are available;
• whether the location, schedule and safety conditions are suitable;
• whether the payment and acceptance terms are clear.

If important information is missing, the worker should seek clarification before accepting. If the work exceeds their capability, creates an unacceptable safety risk or conflicts with an existing commitment, they should decline rather than make a promise they cannot reasonably fulfil.

Once an assignment is accepted, the worker is expected to honour the agreed commitment. If circumstances change, the worker should inform the relevant customer or coordinator as early as possible.

Accepting an assignment means accepting responsibility for the agreed work, not guaranteeing that every unforeseen problem can be prevented.

3. Responsibility depends on the worker’s capability

The assignment model recognises different levels of capability and responsibility.

Foundation: Skilled Worker

A Foundation-level worker develops practical skills and performs defined tasks under appropriate supervision. Assignments should remain within the worker’s demonstrated capability and the supervision arrangements required for the occupation.

The supervisor or responsible service provider retains the responsibilities assigned to them. A learner or newly trained worker should not be treated as an independent professional merely because they can perform an individual task.

Certificate: Independent Worker

A Certificate-level Independent Worker is intended to be capable of accepting and completing work within the defined scope of their occupational competence.

They are expected to understand requirements, assess their own capacity, plan the work, maintain quality, report problems and submit the result for acceptance.

Independence does not remove the need to follow safety requirements, applicable laws, customer specifications or the Marketplace’s relevant quality processes.

Diploma: Service Provider, Distributor or Employer

A Diploma-level participant develops the capability to organise work and coordinate its delivery as a service or business.

Depending on the arrangement, a Service Provider may receive a larger order, divide it into smaller tasks, allocate work to suitable workers, coordinate resources and schedules, and take responsibility for overall delivery and quality.

These stages describe the intended progression of responsibility. The requirements for each occupation must be defined separately, and completing a course alone does not establish eligibility for every type of work.

4. How the work is completed

After accepting an assignment, the worker should turn the agreed requirements into a practical plan.

A responsible worker will:

1. Confirm their understanding of the task and any unresolved details.
2. Check the tools, materials, access and other resources required.
3. Plan the work within the agreed schedule.
4. Follow the relevant procedures, specifications and safety precautions.
5. Check the quality of the work as it progresses.
6. Inform the customer or coordinator promptly about delays, unexpected conditions or changes that may affect delivery.
7. Complete the agreed work and prepare the required evidence or handover.

The worker should not silently change the scope, substitute materials where approval is required, or leave a material problem undisclosed.

If the requirement changes after acceptance, the revised scope, schedule and payment implications should be clarified and agreed by the relevant parties before proceeding wherever practicable.

5. Self-check and submission

Completion is not simply a statement that the worker has finished. The result should be checked against the original requirements.

Before submitting the work, the worker should verify that:

• all agreed tasks have been completed;
• the result meets the specified quality criteria;
• the work area, equipment or deliverables have been handed over as required;
• defects or limitations have been disclosed;
• any required records, photographs, measurements, documents or test results are provided;
• the customer or responsible coordinator knows that the work is ready for review.

The evidence required depends on the occupation. A garment-production assignment might require the completed items to be checked against measurements and finishing standards. A technical installation might require functional tests and a handover record. A digital-service assignment might require a completed document, updated record or confirmation that a defined process has been performed.

These are illustrative examples. Each trade must define its own completion and evidence requirements.

6. Quality check and customer acceptance

After submission, the work may be reviewed by the customer, a supervisor, the service provider or the Marketplace, according to the assignment and its applicable quality arrangements.

The review should compare the actual result with the agreed scope and acceptance criteria.

Three outcomes are possible:

• Accepted: The work meets the agreed requirements, and the assignment can proceed to closure.
• Correction required: Specific deficiencies need to be addressed under the applicable terms.
• Disputed: The parties disagree about the scope, quality, completion or another material aspect of the assignment.

Where correction is required, the issue should be described clearly enough for the worker to understand what needs attention. Where there is a dispute, the parties should refer to the agreed requirements and available evidence rather than relying only on general impressions.

The process should be fair to both sides. Customers should receive the work they agreed to, and workers should be assessed against the requirements that were actually communicated and accepted.

Quality checks may include customer acceptance, technical inspection, random quality control or other occupation-specific methods. The appropriate process must be defined for the particular service; it should not be assumed that every assignment will use every form of review.

7. Payment and assignment closure

Payment should follow the payment terms agreed for the assignment and the applicable legal and contractual arrangements.

Depending on the nature of the work, compensation may be based on:

• a completed job or assignment;
• an accepted item or unit of output;
• a project;
• agreed milestones;
• another defined, lawful payment arrangement.

The intended KarmaYoga model connects compensation to productive work wherever practical. However, the precise amount, payment timing, deductions if any, treatment of rework, and conditions for acceptance must be established for the relevant arrangement. They should not be left ambiguous until after the work has been completed.

Once the applicable completion and payment steps have been resolved, the assignment can be closed and its outcome recorded.

A work record may include the assignment scope, dates, completion status, acceptance result, quality findings, corrections, customer feedback and payment outcome where appropriate and lawful.

Accurate records help the worker understand their progress and give future customers or service providers better evidence of relevant experience. They also help identify recurring quality problems and opportunities for further training.

8. What happens when something goes wrong?

Not every assignment proceeds exactly as planned. Materials may be unavailable, site conditions may differ from the description, a customer may change the requirement, or a completed result may fail an agreed quality check.

The appropriate response depends on the circumstances, but the operating principles are straightforward:

• Raise problems early. Do not wait until the deadline has passed if a material issue is already known.
• Keep the facts clear. Record what happened, when it happened and how it affects the work.
• Avoid unauthorised changes. Obtain the necessary agreement before changing scope, cost or schedule.
• Use the agreed review process. Refer to the assignment terms and available evidence when a disagreement arises.
• Protect people and property. Stop or escalate work when continuing would create an unacceptable safety risk.
• Record the outcome. Resolved issues can inform future planning, training and quality improvement.

A fair system should not treat every delay or disagreement as proof that a worker is unreliable. It should consider the facts, the agreed responsibilities and the circumstances of the assignment.

Likewise, a worker remains accountable for their own commitments, the quality of their work and the problems they could reasonably have prevented or reported.

9. How assignment history supports progression

An assignment can contribute more than immediate payment. When properly recorded, it creates evidence of what a worker has actually done.

Over time, an appropriate work history may show:

• types of assignments accepted and completed;
• skills demonstrated in practical work;
• completion and quality outcomes;
• customer acceptance and feedback;
• recurring corrections or areas for improvement;
• experience with particular tools, processes or work settings;
• readiness for assignments involving greater responsibility.

A certificate and a verified work history serve different purposes. A certificate records an achievement against defined learning or assessment requirements. A work history records experience and outcomes from actual assignments. Neither should be used to claim capabilities that have not been demonstrated.

As a worker gains experience, they may be able to pursue more complex assignments, take greater responsibility or progress towards organising work for others. These are possible pathways, not automatic entitlements or guaranteed outcomes.

10. The role of the Marketplace

The intended KarmaYoga Marketplace workflow is designed to connect demand with appropriate capability and make the assignment process more transparent.

Depending on the services implemented and the arrangement in place, Marketplace functions may include presenting assignments, helping match work to worker capabilities, coordinating communication, recording assignment status, supporting quality review and maintaining relevant work history.

These are intended functions, not a claim that every feature or process is already operational.

The Marketplace is not a substitute for the worker’s professional judgement, the customer’s responsibilities or any supervision required for the occupation. Nor should participation in the Marketplace be understood as a guarantee of assignments, employment or income.

Wara KarmaYoga Foundation and Trust focus on education, training, community development and livelihood preparation. The intended commercial Marketplace role belongs to Wara Systems , with scope for suitable external organisations and providers to participate. The specific operating arrangements will need to be established as the Marketplace develops.

The central principle

A good assignment process protects clarity and accountability at every stage.

The customer should know what is being requested. The worker should understand what they are accepting. The work should be completed against defined requirements. Quality should be checked fairly, payment should follow the agreed terms, and the outcome should provide a reliable record of experience.

Offer clearly. Accept responsibly. Work safely. Check quality. Close fairly. Learn from every assignment.

7.3 - From Demand to Livelihood

Start with demand, not just training

A livelihood programme should begin by understanding what people, businesses and communities actually need.

A customer may need a garment produced, a network installed, a room maintained, a booking enquiry handled or a local service delivered. Each requirement represents a potential piece of work. Whether it becomes a livelihood opportunity depends on its practical scope, budget, timing, location, quality requirements and the availability of people capable of doing it.

This changes how training opportunities should be identified. Instead of starting only with the question, “What course can we teach?”, we also ask:

• What useful work is needed in the local economy?
• Who needs that work, and under what conditions?
• What capabilities are required to perform it?
• Can those capabilities be taught, practised and assessed responsibly?
• What tools, materials and supervision are needed?
• Is there a credible route from training to actual work?

These questions do not mean that every course must lead directly to a paid assignment. Digital literacy, academic learning and personal development have value in their own right. For occupational training intended to support livelihoods, however, demand should be part of the design from the beginning.

The connection between learning and livelihood

The intended progression is:

Demand → Defined Work → Required Capability → Learning and Practice → Demonstrated Capability → Suitable Work → Quality and Acceptance → Income

Each stage addresses a different requirement.

1. Demand: Identify a genuine need from a customer, employer, institution or community.
2. Defined work: Describe the task, expected output, working conditions and acceptance criteria.
3. Required capability: Identify what a person must know and be able to demonstrate.
4. Learning and practice: Develop the necessary knowledge, skills, judgement and work discipline.
5. Demonstrated capability: Establish whether the person can perform the required tasks to the relevant standard.
6. Suitable work: Connect the person’s demonstrated capabilities with an appropriate assignment, where an opportunity is available.
7. Quality and acceptance: Check that the agreed work has been completed to the required standard.
8. Income: Apply the agreed payment terms when the relevant conditions are fulfilled.

This is a design principle, not a promise that every learner will progress through every stage. Demand may change, a learner may need more practice, and an assignment may not be available. The system should make those dependencies visible rather than treating course completion as proof of employability.

Why training alone is not enough

A person may complete a course and still face practical barriers to earning.

They may lack access to equipment, materials, transport, a suitable workspace, customers or the confidence that comes from supervised experience. They may know how to perform a task but have no way to demonstrate the quality of their work to a prospective customer.

These are different problems and require different responses.

Not every barrier can be solved by a training organisation. Some depend on household circumstances, local infrastructure, financing, regulation or the availability of customers. The purpose of the model is to identify these requirements and coordinate suitable responses, not to imply that training can remove every obstacle.

The five connected elements of a livelihood system

WARA’s broader concept brings together five elements that reinforce one another.

1. Training

People develop the knowledge and practical capabilities needed for defined work. Learning should include appropriate practice, assessment and evidence of what the learner can do.

2. Equipment and productive resources

Some occupations require tools, machines, computers, materials, transport or access to a suitable workspace. The availability and cost of these resources can determine whether a person can turn capability into productive activity.

Resources may be provided through different arrangements, depending on the occupation and project. Ownership, maintenance, operating costs and responsibility for loss or damage need to be addressed where relevant.

3. Work

Capability must connect with a real requirement. Work may come from an employer, an individual customer, an institution, a production order, a service provider or another suitable channel.

The form of work matters. A one-time assignment, recurring service, production order and employment relationship have different requirements and should not be treated as interchangeable.

4. Quality

Customers need confidence that the promised work will be completed properly. Clear specifications, suitable supervision, defined acceptance criteria and reliable communication help establish that confidence.

Quality also protects workers. They should understand what is expected, what resources will be provided, how changes will be handled and what constitutes completed work.

5. Marketplace and coordination

A marketplace can help connect demand with capable workers and service providers. Coordination may include defining requirements, identifying suitable participants, communicating assignment details, tracking progress and recording outcomes.

A digital platform may support these activities, but the underlying process does not depend on sophisticated technology from the outset. A small pilot can begin with appropriate records, direct communication and manual coordination, provided responsibilities and decisions remain clear.

Together, these elements form a practical model:

Training + Equipment + Work + Quality + Marketplace = A stronger basis for livelihood

The formula describes connected requirements. It does not mean that combining them automatically produces sufficient work or income.

An example: distributed garment production

Consider a buyer who requires a batch of garments made to a defined specification.

A training-only approach might teach sewing and then leave participants to find their own customers, purchase materials and establish a production business.

A demand-linked approach begins differently.

1. Confirm the requirement. Establish the product, quantity, measurements, materials, delivery schedule, budget and quality criteria before treating the requirement as a viable order.
2. Identify the work. Break production into suitable tasks and determine which tasks can be performed by individual workers or small production groups.
3. Assess capability. Determine the skills, equipment and practice required for each task.
4. Prepare participants. Provide relevant training and assess whether participants can perform the defined work to the required standard.
5. Organise production. Arrange materials, equipment, instructions, supervision and task allocation according to the agreed production plan.
6. Check quality. Inspect work at appropriate stages and address defects before final delivery.
7. Complete delivery and settlement. Confirm acceptance against the agreed requirements and apply the payment terms established for the order.
8. Learn from the result. Record quality issues, actual production effort, costs, delivery performance and lessons that may improve future orders.

This model can create a practical connection between training and production. It also makes risks visible. The buyer may cancel or change an order, costs may be higher than expected, participants may need additional practice, or the work may not meet the specification. A responsible pilot must address these possibilities before scaling.

The example illustrates a proposed approach. It does not imply that a particular buyer, production order or operating arrangement has already been secured.

From a worker to an independent provider

Livelihood development can extend beyond performing individual tasks. With experience and appropriate further learning, some people may become capable of accepting work independently, coordinating other workers or operating a service business.

WARA’s intended occupational progression is:

Foundation → Certificate → Diploma

The corresponding occupational direction is:

• Foundation: develop capability to perform defined work under supervision.
• Certificate: develop the capability required for independent work within the defined scope.
• Diploma: develop service-provision and enterprise capabilities, including organising work and resources.

These stages are intended to represent increasing capability and responsibility. Their exact requirements depend on the pathway, its competencies and assessment arrangements.

Progression is not automatic. A person may prefer to remain a skilled worker, may not have access to the resources needed for independent work, or may choose a different educational or occupational direction. Enterprise also requires capabilities beyond technical skill, including customer communication, costing, planning, record-keeping and responsibility for delivery.

The objective is to make different paths possible, not to require every participant to become an entrepreneur.

The roles of the Trust and the commercial Marketplace

The proposed model separates the social and educational work of Wara KarmaYoga Foundation/Trust from the commercial functions intended for Wara Systems .

Wara KarmaYoga Foundation focuses on education, skill development, community engagement and preparation for livelihood opportunities within its programmes.

Wara Systems is intended to develop and operate the commercial Marketplace, including customer engagement and the coordination of suitable work and service providers, subject to the relevant arrangements being established.

The Marketplace is intended to be open to suitable organisations and providers beyond WARA’s own training network. A participant’s training history may be relevant evidence, but access to work should depend on the actual requirements, demonstrated capability, suitability and applicable terms.

Neither training participation nor a relationship with the Trust should be presented as a guarantee of Marketplace assignments, employment or income. Any specific commercial relationship, payment obligation, safeguarding requirement or regulatory responsibility must be defined for the relevant activity.

Start with a manageable pilot

The complete livelihood model does not need to be implemented all at once.

A practical pilot can focus on one defined type of work, a specific group of participants and a credible source of demand. Before proceeding, the project should establish:

• the customer or demand source and the evidence that the requirement is genuine;
• the work specification, budget and expected delivery conditions;
• the capabilities and resources required;
• the selection, training and assessment arrangements;
• the responsibilities for supervision, safety and quality;
• the terms for acceptance, payment and handling changes or disputes;
• the records needed to measure actual results.

Success should be assessed through evidence, not only the number of people trained. Useful measures may include demonstrated competencies, work completed, quality acceptance, delivery performance, participant experience, actual income where applicable and the viability of repeating the work.

A pilot that reveals weak demand or unsuitable economics can still provide valuable evidence, provided those findings are recorded honestly and used to improve the model.

The larger cycle

When demand, learning and work are connected responsibly, experience from completed assignments can inform future training. Repeated work may help improve methods, quality and productivity. Experienced workers may support new learners, and capable providers may organise work for others.

The intended long-term cycle is:

Train → Work → Earn → Learn → Improve → Organise → Create Work → Train More People

Each link depends on real conditions. Income must be earned through agreed work, quality must be maintained, and any expansion must be supported by viable demand and appropriate resources.

The central idea is straightforward: learning should prepare people for meaningful capability, and livelihood programmes should make a serious effort to connect that capability with real opportunities to contribute.

The next page, Delivery-Based Work, explains why defined outputs, clear responsibilities and acceptance criteria are important when work is organised around deliverables rather than simply attendance or training completion.

7.4 - Payment and Settlement

Agree on the work before agreeing on the payment

A payment arrangement is only meaningful when both parties understand what they are paying for.

A customer may request a completed product, a specific service, a set of units, a technical installation or a larger project. Each requires a clear definition of the expected result.

Before accepting an assignment, the worker and the relevant customer or service provider should establish:

• Deliverables: What must be produced, performed, installed or handed over?
• Quantity and scope: How much work is included, and what is excluded?
• Quality criteria: What standards must the result meet?
• Completion conditions: What evidence, inspection or approval is required?
• Compensation: What amount or rate applies, and how is the total calculated?
• Payment conditions: When does payment become due, and what events trigger it?
• Resources and expenses: Who provides materials, tools, transport and other required inputs?
• Changes and exceptions: How will additional work, delays, incomplete delivery or disputed results be handled?

The level of detail should be proportionate to the assignment. A small, routine task may need a short written agreement. A complex project may require a detailed scope, milestones and documented acceptance criteria.

The objective is not paperwork for its own sake. It is to prevent avoidable disagreement after the work has been performed.

1. Define the deliverable

A deliverable describes the result the worker is expected to provide. It should be specific enough that both parties can determine whether the agreed work has been completed.

For example:

• A garment assignment may specify the number of garments, measurements, materials, stitching requirements and finishing standard.
• A digital-services assignment may specify the number and format of documents, the data fields to be completed, validation requirements and handover method.
• A technical installation may specify the equipment to be installed, the work area, functional tests and required handover records.
• A hospitality assignment may specify the service tasks, expected schedule and applicable hygiene or service standards.

These examples illustrate the principle; they do not imply that every listed service is currently available through the Marketplace.

A deliverable should distinguish between the required result and the method used to achieve it. Where the customer requires a particular method, material or procedure, that requirement should be stated explicitly. Otherwise, the worker should have appropriate freedom to choose a suitable method within the agreed safety and quality standards.

2. Choose a suitable compensation model

The payment model should reflect the nature of the work, how its output can be measured and where responsibility for the overall result lies.

The intended KarmaYoga approach favours connecting compensation to productive work wherever practical. Depending on the occupation and arrangement, this may take several forms.

Per job or assignment

A defined amount is agreed for completing a specific job or assignment.

This works best when the scope is sufficiently clear and the likely effort and resources can be estimated.

Per unit or accepted output

Payment is calculated using a defined quantity, such as each completed item or unit of work that meets the agreed standard.

The parties should define what counts as an acceptable unit, how quantities are recorded and how defective or incomplete items are treated.

Per project or milestone

A larger assignment is divided into defined stages or deliverables. Each milestone has an identifiable completion condition and an associated payment arrangement.

This can help both parties manage work that takes longer or requires several stages of delivery.

Other agreed arrangements

Some occupations may require a different payment model, including time-based compensation or a combination of methods. The appropriate arrangement depends on the work, the responsibilities involved and applicable law.

The Marketplace should not force every occupation into the same compensation structure. The model should make the relationship between the work, the expected result and the payment understandable.

3. Calculate the amount fairly

Before an assignment is accepted, the parties should understand how the agreed compensation is calculated.

Depending on the work, the estimate may account for:

• the quantity and complexity of the deliverables;
• the time, skill and responsibility required;
• materials and consumables;
• tools, equipment or specialist resources;
• travel or other agreed expenses;
• inspection, testing, packaging or handover requirements;
• applicable taxes and other lawful charges.

The agreement should clarify whether the quoted amount includes these costs or whether particular items are handled separately.

For example, a garment-production rate may include stitching labour but exclude fabric and accessories. A technical installation price may include labour but require the customer to supply equipment. Either arrangement can be workable if it is understood before the commitment is made.

A worker should be able to estimate the work they are accepting. A customer should be able to understand what the quoted amount covers.

The amount should not be changed retrospectively simply because one party later discovers that the original arrangement was inconvenient. Where an unforeseen condition materially changes the work, the parties should discuss and agree on a revision before proceeding wherever practicable.

4. Agree on acceptance before work begins

Payment and acceptance are closely related, but they are not the same thing.

Completion means the worker has performed the agreed work. Acceptance means the result has been reviewed against the applicable requirements and accepted under the agreed arrangement.

Before work begins, the parties should know:

• what will be checked;
• who is responsible for checking it;
• what evidence must be supplied;
• what happens if a deliverable does not meet the stated criteria;
• how corrections or disagreements will be handled;
• which acceptance event triggers payment, where payment is conditional on acceptance.

Acceptance criteria should be objective wherever possible. Measurements, quantities, test results, required documents and clearly described service outcomes are generally more useful than an undefined expectation that the work must be satisfactory.

A customer should not introduce new requirements after delivery and treat them as if they were part of the original scope. Similarly, a worker should not consider a deliverable accepted merely because it has been submitted.

The agreed terms should govern the review and settlement process.

5. Decide when payment becomes due

Payment timing must be agreed as part of the assignment, not left until the work is finished.

Depending on the work and the parties’ arrangement, payment may be linked to:

• completion of the assignment;
• acceptance of a defined deliverable;
• acceptance of individual units of output;
• completion of agreed milestones;
• another clearly specified event permitted by the applicable terms and law.

The agreement should identify the event that makes payment due and the expected settlement period. If the assignment has several milestones, the amount or calculation method for each milestone should be clear.

Where an advance, deposit or staged payment is appropriate, the parties should document its amount, purpose and treatment if the work changes or does not proceed.

No single payment schedule is suitable for every occupation. A small service task and a multi-stage production order may require different arrangements.

The guiding principle is to agree on the payment trigger before accepting the work, then follow the agreed terms consistently.

6. What happens when output is incomplete or rejected?

A settlement process must address exceptions as well as successful completion.

A deliverable may be incomplete, a quantity may be disputed, or an inspection may identify a defect. The response should depend on the original scope, the acceptance criteria, the facts and the applicable agreement.

A fair process should distinguish between:

• work that has not yet been completed;
• work that has been completed but needs a defined correction;
• output that does not meet an agreed quality requirement;
• additional work requested by the customer after the scope was agreed;
• problems caused by unavailable resources, changed conditions or another party’s actions;
• disagreements about whether the stated requirements have been met.

Where correction is required, the issue should be described specifically. The parties should establish what must be corrected, who is responsible and how the correction affects the schedule and settlement.

The treatment of rework, rejected units, partial completion and cancellation should be agreed in advance where reasonably foreseeable. Any deduction, withholding or adjustment must be consistent with the agreement and applicable law.

A quality concern should not automatically be treated as proof of misconduct. Equally, a worker should not be paid as though all requirements were met when the agreed terms establish that material work remains incomplete.

Where the parties cannot resolve a disagreement directly, they should use the applicable dispute-resolution process.

7. Keep evidence of work and payment

A reliable settlement process depends on records that allow the parties to understand what happened.

Depending on the assignment, relevant records may include:

• the original assignment description and agreed scope;
• the accepted compensation model and amount;
• approved changes to the work;
• quantities produced or services completed;
• submission dates and completion evidence;
• inspection and acceptance results;
• corrections or disputed items;
• invoices, receipts or other relevant payment records;
• payment due dates and settlement confirmation.

The records should be proportionate to the value, complexity and risk of the work. A routine small assignment does not need the same documentation as a large project.

Where a Marketplace is involved, its intended role may include maintaining appropriate assignment and settlement records. The precise capabilities, access permissions, record-retention rules and payment arrangements must be defined before those functions are treated as operational.

Records should be handled responsibly, with appropriate regard for privacy, confidentiality and applicable legal requirements.

8. Understand who is responsible for settlement

The parties involved in an assignment may differ.

A customer may engage an Independent Worker directly, request a service through a Service Provider, or obtain work through an organisation participating in the Marketplace. The payment responsibilities must match the actual arrangement.

Before work begins, the parties should know:

• who is engaging the worker;
• who owes the payment;
• who confirms completion or acceptance;
• whether a Service Provider coordinates payment to other workers;
• whether the Marketplace is facilitating the arrangement or is itself a party to it;
• what records and procedures apply if settlement is delayed or disputed.

The involvement of a Marketplace does not, by itself, establish that the Marketplace is the employer, contracting customer, payment intermediary or guarantor of payment. Those roles must be expressly defined in the relevant arrangements.

Wara KarmaYoga Foundation and Trust focus on education, training, community development and livelihood preparation. The intended commercial Marketplace role belongs to Wara Systems , with participation open to suitable external organisations and providers. The specific contracting, payment and settlement model must be established for the service being offered.

9. Payment arrangements should support worker independence

A clear payment model helps a worker evaluate an opportunity before committing time and resources.

For an Independent Worker, this includes understanding the scope, estimating the effort, accounting for agreed costs and deciding whether the assignment is suitable. For a Service Provider, it also includes estimating the resources needed to deliver the overall service and agreeing on how work distributed to other workers will be compensated.

The responsibility grows with the scope of the commitment. A person coordinating a larger order should not agree to a customer price without considering the cost of delivery, the quality requirements, the payment terms for participating workers and the risks involved.

This is one reason the Foundation, Certificate and Diploma pathways represent increasing levels of responsibility. The progression is not merely about performing more tasks. It is also about understanding and managing the commitments associated with the work.

The principle of fair settlement

A good payment arrangement begins before the work begins.

The deliverables should be clear. The compensation model should be understandable. Acceptance criteria and payment triggers should be agreed in advance. Changes and exceptions should be handled transparently, and the final settlement should follow the applicable terms.

This protects both the customer and the worker. It also creates better records of completed work, supports responsible service delivery and provides a stronger basis for future assignments.

Define the work. Agree on the terms. Deliver against the standard. Settle according to the agreement.

7.5 - Joining and Verification

Joining begins with capability

People arrive with different backgrounds. Some have completed a KarmaYoga training pathway. Others may have learned a trade through employment, apprenticeship, family work or independent practice.

A fair onboarding process should recognise these different starting points while maintaining consistent standards for the work being offered.

The central question is:

What work can this person demonstrate that they are capable of performing, and under what conditions?

The answer helps determine which assignments may be suitable, whether supervision is needed and what further training or assessment may be appropriate.

Registration alone does not establish occupational competence. Likewise, prior experience should not be dismissed simply because it was gained outside a particular training programme. The relevant capability must be assessed against the requirements of the intended work.

1. Understand the worker’s background

The first step is to establish the worker’s intended occupation, relevant experience and current capabilities.

Depending on the occupation and the onboarding arrangement, this may involve reviewing:

• the worker’s chosen occupation or service area;
• completed training and relevant credentials;
• previous work experience and practical exposure;
• capabilities the worker claims to possess;
• the tools, equipment or work settings they are familiar with;
• any applicable licence, registration or other occupational requirement;
• the type of work and level of responsibility they wish to undertake.

The purpose is to understand the worker’s starting point and identify the evidence needed for the next step.

The process should not assume that every applicant has formal certificates, nor that every certificate proves the person can independently perform every task in the occupation.

2. Verify identity and relevant information

Where onboarding involves customer-facing work, the relevant organisation may need to confirm a worker’s identity and verify information material to the assignment.

The exact checks should depend on the nature of the work, the risks involved and applicable law. They may include confirming relevant credentials, occupational permissions or experience where these are required.

Additional checks may be necessary for regulated or sensitive work. For example, healthcare, electrical work and other safety-critical occupations may have requirements that do not apply to ordinary low-risk tasks.

Identity verification and capability verification are separate activities:

• Identity verification helps establish who the worker is.
• Capability verification establishes what the worker can demonstrate.
• Credential verification checks the authenticity and relevance of a claimed qualification or licence where applicable.

Passing one check does not automatically satisfy the others. The required checks must be defined for the particular occupation and service arrangement.

Personal information should be collected only for legitimate purposes, handled securely and retained in accordance with applicable requirements.

3. Demonstrate practical capability

KarmaYoga’s learning architecture is based on demonstrable competence:

Learn → Practise → Demonstrate → Verify → Qualify → Work

For worker onboarding, the important distinction is between knowing about a task and being able to perform it to the required standard.

Where capability needs to be established, suitable evidence may include a practical assessment, an observed task, a work sample, a relevant verified competency record or other evidence appropriate to the occupation.

The assessment should define:

• the task or capability being assessed;
• the conditions under which it must be performed;
• the expected quality and completion standard;
• the evidence required to demonstrate performance;
• the level of independence required;
• any safety precautions or limits that apply.

The method should fit the task. A worker’s ability to prepare a digital document can be demonstrated differently from the ability to install equipment or produce a garment to specification.

Assessment should focus on the actual capability required, not unnecessary formalities. At the same time, a worker should not be approved for work that has not been adequately assessed where assessment is required.

4. Determine the appropriate level of responsibility

The intended KarmaYoga model distinguishes three occupational outcomes.

Foundation: Skilled Worker

A Foundation-level worker can perform defined work within the demonstrated scope and the required supervision arrangements.

The onboarding record should make clear which tasks the worker can perform and what guidance, oversight or restrictions apply.

Certificate: Independent Worker

A Certificate-level Independent Worker is intended to perform the defined occupation independently within the scope of demonstrated competence.

This includes understanding the assignment, planning the work, selecting suitable methods, performing the task, checking quality, communicating problems and completing the required handover.

Independent status does not mean unrestricted authority. The worker must remain within their competence and comply with relevant legal, safety and occupational requirements.

Diploma: Service Provider

A Diploma-level participant develops the capability to organise and deliver work as a service or business.

This may involve coordinating workers, scheduling assignments, managing resources, handling customer requirements and maintaining overall delivery quality.

The assessment at this level should address the responsibilities of organising work, not only the ability to perform an individual trade task.

These stages are part of the intended internal KarmaYoga framework. They must not automatically be represented as nationally recognised qualifications, licences or statutory permissions.

5. Recognise prior learning and experience

An experienced worker should not necessarily have to repeat an entire training programme simply because their skills were developed elsewhere.

Where appropriate, prior learning and experience can be considered through:

• review of existing training and competency records;
• verification of relevant credentials;
• practical assessment against defined competencies;
• recognition of demonstrated capabilities;
• targeted bridging training for identified gaps.

The decision should be based on the requirements of the intended work and the evidence available.

For example, a person with substantial tailoring experience may already demonstrate several garment-production competencies. An assessment can identify which capabilities are established and which require further practice or verification.

Recognition of prior capability does not mean that every claimed skill is accepted without assessment. Nor does it remove any separate licence, regulatory or formal qualification requirement that applies to the occupation.

6. Prepare the worker profile

Once the necessary checks have been completed, the worker’s record should describe their verified capabilities and the scope of work they may be considered for.

An intended worker profile may include:

• identity and contact information appropriate to the service;
• occupation and relevant specialisation;
• completed training and verified competencies;
• relevant credentials and their verification status;
• tasks the worker has demonstrated they can perform;
• whether supervision or other restrictions apply;
• applicable occupational permissions, where required;
• relevant experience and work history;
• availability and service location, where relevant;
• other assignment-specific information needed for suitable matching.

The profile should distinguish between a skill that has been claimed, a qualification that has been documented and a capability that has been assessed and verified.

These are different kinds of evidence and should not be presented as interchangeable.

Only information necessary for the intended service should be made available to customers or other parties. Sensitive personal records and verification documents should not automatically become public profile information.

7. Complete onboarding before accepting suitable work

Onboarding should establish that the worker understands how assignments operate and what responsibilities follow from accepting one.

Depending on the arrangement, this may include explaining:

• how assignments are described and offered;
• how to evaluate and accept or decline an offer;
• how deliverables, compensation and payment terms are agreed;
• how to communicate delays or unexpected problems;
• how quality checks and customer acceptance work;
• how work records and feedback are handled;
• what safety, conduct, privacy and confidentiality requirements apply;
• how concerns or disputes can be raised.

A worker should know what they are committing to before accepting an assignment. Where the worker’s role requires supervision, the relevant responsibilities and escalation arrangements should also be clear.

Related guidance should be provided as part of onboarding where it is available. The precise onboarding materials and process will depend on the service model implemented.

8. Decide the next step

Verification does not have to result in a simple pass-or-fail decision.

Depending on the evidence and requirements, the appropriate outcome may be:

• Ready within the assessed scope: The worker has demonstrated the required capabilities for the defined work.
• Ready with supervision: The worker can perform specified tasks, but requires the applicable oversight.
• Further assessment required: The available evidence is insufficient to establish one or more necessary capabilities.
• Additional training recommended: Specific gaps should be addressed before the worker takes on the relevant responsibilities.
• Restricted to a narrower scope: The worker has demonstrated some capabilities, but not the full range claimed or required.
• Not eligible for the intended work at present: A required competency, permission or other essential condition has not been met.

Any restrictions or outstanding requirements should be communicated clearly. Where further training or assessment is appropriate, the worker should be told what needs to be demonstrated.

This approach makes verification useful for both the worker and the organisation. It identifies readiness while providing a practical route for addressing gaps.

9. Maintain and update verification records

Capabilities can develop over time, and the work a person wishes to undertake may change.

A responsible system should therefore distinguish between the original onboarding decision and later evidence of progress.

Relevant updates may include new verified competencies, additional credentials, completed training, work history, changes to applicable permissions or a revised scope of work.

Feedback from completed assignments can help identify areas for improvement, but customer feedback alone should not automatically establish or revoke a professional qualification. Decisions should use the appropriate evidence and process for the issue being considered.

Where an occupation requires periodic renewal, supervision or revalidation, those requirements should be handled according to the applicable rules.

A record of verification should state what was checked, the result, the relevant scope and any conditions. It should not imply a broader approval than the evidence supports.

10. What verification does and does not mean

Verification provides evidence about a defined capability or requirement. It is not a universal guarantee.

A verified worker may still need to decline an assignment that exceeds their competence, requires an unavailable resource or creates an unacceptable risk. A customer must still define the work clearly and follow the applicable agreement. A Service Provider remains responsible for the commitments associated with organising delivery.

Likewise, completing onboarding does not guarantee access to assignments, employment, earnings or a particular volume of work. Opportunities depend on actual demand, the worker’s capabilities, the nature of the assignment and the applicable arrangements.

The purpose of verification is to improve the quality of decisions about suitable work, not to promise an outcome that the process cannot control.

The role of the KarmaYoga ecosystem

Wara KarmaYoga Foundation and Trust focus on education, training, community development and livelihood preparation. The learning framework supports the development and verification of competencies through defined learning outcomes and assessment.

The intended commercial Marketplace role belongs to Wara Systems , with participation open to suitable external organisations and providers. Worker onboarding, capability records, assignment matching and related processes must be implemented with clear responsibilities and appropriate safeguards before they are described as operational services.

The wider objective is to connect learning with meaningful work while preserving a clear distinction between training, demonstrated competence, occupational eligibility and actual work opportunities.

Understand the worker. Verify the capability. Define the scope. Record the evidence. Match responsibility to what has been demonstrated.

7.6 - Care Partners

Care is more than completing tasks

Caregiving involves helping another person live with dignity, safety and as much independence as their circumstances allow.

A caregiver may help with everyday activities, provide companionship, support mobility within their training, assist with household routines or follow an agreed care plan. The exact responsibilities depend on the person’s needs, the care setting, the caregiver’s demonstrated capabilities and any applicable professional requirements.

At KarmaYoga, care-related work belongs to the Healthcare, Care & Community Support domain. The intended learning and work model connects practical capability with increasing responsibility.

The central principle is simple:

Provide the support agreed, respect the person receiving care, and never undertake a task beyond your competence or authority.

1. Understand the person, not just the assignment

Every person receiving care has their own preferences, routines, abilities, concerns and circumstances.

Before beginning an assignment, the caregiver should understand the agreed requirements and, where appropriate, learn directly from the person receiving care and their authorised representative.

Important questions include:

• What assistance has been requested and agreed?
• What can the person do independently?
• What assistance do they prefer, and how should it be provided?
• Are there relevant care instructions, safety precautions or restrictions?
• Who should be contacted if a concern arises?
• What tasks are outside the caregiver’s role?
• What schedule, communication and handover arrangements apply?

A person’s need for assistance does not remove their right to make choices about their everyday life. Whenever possible, explain what you are going to do, ask permission and respect the person’s preferences.

Care should support independence rather than unnecessarily replace it.

2. Protect dignity, privacy and personal choice

Caregivers may be invited into someone’s home, assist with personal routines or learn information that the person would not ordinarily share with others. This creates a special responsibility to maintain trust.

A responsible caregiver should:

• speak respectfully and avoid humiliating or dismissive language;
• ask permission before providing personal assistance;
• respect privacy during personal care and conversations;
• handle personal information discreetly;
• follow agreed arrangements for photographs, records and communication;
• respect cultural practices and reasonable personal preferences;
• avoid discussing the person’s private circumstances with unauthorised people;
• report concerns through the appropriate channel.

Consent and communication matter even when assistance is part of a regular routine. If a person refuses assistance, becomes distressed or expresses discomfort, do not respond with force or intimidation. Respect the person’s wishes, consider immediate safety and seek appropriate guidance.

Where a person has difficulty communicating or making a particular decision, follow the applicable care plan and legal requirements. Do not assume that another person can make every decision on their behalf.

3. Know the scope of your role

The word caregiver can describe different kinds of work. A companion, a home-care assistant and a trained healthcare professional do not necessarily have the same responsibilities.

The tasks a caregiver may undertake must be determined by their training, demonstrated competence, the agreed assignment and applicable law.

Depending on the role, an assignment may involve:

• companionship and conversation;
• assistance with agreed everyday routines;
• support with meals or household activities within the care plan;
• helping maintain a safe and orderly environment;
• supporting movement or mobility where appropriately trained;
• observing and communicating changes in the person’s condition;
• maintaining agreed records and handover notes;
• accompanying a person to an appointment where agreed.

These are examples of possible responsibilities, not a universal task list. Each care role requires a clearly defined scope.

Some activities require specific training, supervision, professional authorisation or other legal conditions. A caregiver must not assume that general caregiving training permits them to perform clinical procedures, administer or alter medication outside their authorised role, diagnose an illness or make clinical decisions.

When a task is unclear, request guidance before proceeding.

4. Follow the agreed care plan

A care plan or set of care instructions helps establish what support is expected and how it should be provided.

Before accepting an assignment, the caregiver should understand the relevant instructions, the agreed schedule, the responsibilities of other people involved and the process for reporting problems.

During the assignment:

1. Follow the agreed instructions within your training and authority.
2. Explain your actions and respect the person’s choices.
3. Maintain the agreed hygiene, safety and privacy practices.
4. Observe and report relevant concerns without making unsupported medical conclusions.
5. Record the information required by the care arrangement.
6. Communicate incomplete tasks or changes that may affect the next caregiver or responsible person.

A caregiver should not independently change an important care instruction simply because another approach appears more convenient.

If the person’s needs appear to have changed, or an instruction seems unsafe or unclear, seek guidance from the designated responsible person or appropriate healthcare professional.

5. Recognise concerns and respond responsibly

Caregivers may notice changes in a person’s comfort, behaviour, mobility, appetite or general condition. These observations can be important, but noticing a change is not the same as diagnosing its cause.

A responsible caregiver should:

• pay attention to significant changes from the person’s usual condition;
• report observations clearly and promptly to the designated contact;
• distinguish what was observed from what is assumed;
• follow the agreed escalation procedure;
• seek emergency assistance when the situation appears urgent;
• never delay urgent help while waiting for routine approval.

If there is an immediate threat to life or safety, follow the applicable emergency procedure and contact local emergency services as appropriate.

Caregivers should also know how to raise concerns about neglect, abuse, exploitation, unsafe conditions or inappropriate conduct. Such concerns should be handled through the applicable safeguarding and reporting procedures, with due regard for the person’s immediate safety and confidentiality.

The exact reporting requirements depend on the care setting and applicable law. These must be established as part of the relevant training and service arrangements.

6. Communication with family members and other care professionals

Care often involves several people. A family member may arrange the service, another caregiver may cover a different shift, and a healthcare professional may provide instructions relevant to the person’s care.

Clear communication helps prevent missed tasks and misunderstandings.

A caregiver should understand:

• who is the authorised contact for routine matters;
• who provides or updates relevant care instructions;
• which information can be shared and with whom;
• how urgent concerns should be escalated;
• how shift handovers or changes in responsibility are managed.

When reporting a concern, describe the facts as accurately as possible. For example, report that the person was unable to complete a usual activity or appeared unusually confused, rather than presenting an unverified medical diagnosis.

Conflicting instructions should not be resolved through guesswork. Seek clarification from the appropriate responsible person, and do not carry out an instruction that would create an unacceptable risk or fall outside your authority.

7. Prepare for a care assignment

Care work requires preparation, just as other occupational assignments do. The caregiver should not accept a task without understanding its requirements and determining whether they can carry it out safely.

Before accepting an assignment, confirm:

• the person’s care needs and the agreed support tasks;
• the location, schedule and expected duration;
• the level of assistance and supervision required;
• the resources or equipment that must be available;
• any relevant safety precautions;
• the person to contact if circumstances change;
• the agreed compensation, payment terms and completion conditions;
• any tasks that are specifically excluded from the assignment.

If the assignment requires a capability the caregiver has not demonstrated, the appropriate response is to disclose the limitation and seek clarification, additional training or a different arrangement.

Caregivers should never feel compelled to accept work they cannot safely perform.

8. Complete the assignment and hand over responsibly

A care assignment should end with a clear understanding of what was completed and whether anything requires follow-up.

The caregiver should complete the agreed tasks, record relevant information where required, communicate any unresolved concern and ensure that the handover follows the established arrangement.

A handover may need to cover:

• the tasks completed and any tasks left incomplete;
• relevant observations during the assignment;
• concerns reported and the person contacted;
• changes to the agreed routine that were authorised;
• information the next responsible person needs to know;
• any outstanding action requiring follow-up.

Records should be factual, respectful and limited to information relevant to the care arrangement. Personal details should be shared only with authorised people through appropriate channels.

The caregiver should not conceal a mistake, omit a material concern or claim that a task was completed when it was not.

9. Capability, training and progression

KarmaYoga’s intended occupational pathway connects increasing capability with increasing responsibility.

Foundation: Skilled Worker

The Foundation pathway develops defined capabilities for work performed under the appropriate supervision. In care-related work, this means learning the relevant routines, communication practices, safety requirements and boundaries of the assigned role.

Certificate: Independent Worker

The Certificate pathway aims to develop the ability to accept and complete defined occupational work independently within the demonstrated scope. This includes planning tasks, following instructions, checking one’s work, communicating concerns and completing a responsible handover.

Independent work does not authorise a person to perform regulated healthcare activities without the required qualifications or permissions.

Diploma: Service Provider

The Diploma pathway focuses on organising work as a service or business. Depending on the intended service, this may involve coordinating suitable workers, scheduling assignments, communicating with customers, maintaining service standards and managing delivery responsibilities.

Organising a care service brings additional responsibilities. A Service Provider must ensure that the people assigned to particular tasks have appropriate capabilities and that the service complies with applicable requirements.

These are intended internal KarmaYoga stages. They must not be presented as nationally recognised care qualifications or professional licences unless the relevant recognition and authorisation have been established.

10. Caring for yourself is part of responsible care

Caregiving can be physically and emotionally demanding. Fatigue, unclear expectations, difficult situations and repeated exposure to distress can affect a caregiver’s ability to work safely.

A responsible caregiver should recognise their own limits and communicate when they cannot safely continue a task or fulfil an assignment.

This includes:

• following safe working practices and using appropriate equipment;
• seeking assistance with tasks that exceed physical capability or training;
• reporting unsafe working conditions;
• taking agreed breaks and respecting working-hour arrangements;
• asking for support after a difficult incident;
• maintaining professional boundaries with the person receiving care and their family.

A caregiver is not expected to solve every problem alone. Requesting appropriate help is a sign of responsible practice, not a failure of commitment.

11. What joining the KarmaYoga care pathway means

The intended KarmaYoga model seeks to connect practical training with suitable work opportunities. For care-related occupations, this requires particular attention to the dignity and safety of the person receiving care.

Training, assessment and onboarding should establish what a worker has demonstrated, what responsibilities they may undertake and what supervision or permissions remain necessary.

The intended commercial Marketplace role belongs to Wara Systems , while Wara KarmaYoga Foundation and Trust focus on education, training, community development and livelihood preparation. Suitable external organisations and providers may also participate in the wider Marketplace model.

The specific care services, onboarding checks, safeguarding arrangements and operational procedures must be established for each service before they are represented as available.

Joining the pathway does not guarantee an assignment, employment or income. It provides a route for developing and demonstrating capability that may support suitable work opportunities.

The responsibility at the heart of care

Good caregiving combines practical ability with patience, respect, clear communication and sound judgement.

The caregiver must understand the person’s needs, follow the agreed plan, protect privacy, remain within their competence and speak up when something is wrong.

Care with dignity. Work within your competence. Communicate clearly. Protect the person who has placed their trust in you.

7.7 - Growth and Enterprise

From independent work to enterprise

Learning a trade can create the ability to perform useful work. With practice and experience, a person may become capable of completing defined assignments independently. Some may eventually want to go further: coordinate other workers, manage customer orders, supply materials or operate a small service business.

The KarmaYoga learning model recognises this progression:

Foundation → Certificate → Diploma

Each stage develops a different level of capability and responsibility.

• Foundation — Skilled Worker: Performs defined tasks under appropriate supervision.
• Certificate — Independent Worker: Accepts and completes defined work independently within the limits of their competence.
• Diploma — Service Provider, Distributor or Employer: Develops the ability to organize people and resources, manage delivery and take responsibility for a service or production activity.

Progression depends on demonstrated capability, relevant experience, the requirements of the occupation and the learner’s circumstances. Completing one stage does not automatically qualify a person for the next.

Three ways to grow

Not every worker needs to establish an enterprise. Growth can take several forms, and people should be able to choose a direction that fits their abilities and ambitions.

1. Become a more capable independent worker

An Independent Worker may deepen their technical skills, improve the quality of their work, handle more complex assignments and develop a stronger record of reliable delivery.

This path can include:

• improving speed, accuracy and consistency;
• learning additional techniques within the same occupation;
• building a portfolio of completed work;
• communicating clearly with customers and coordinators;
• estimating the time, materials and resources needed for a job;
• understanding costs, agreed compensation and payment conditions;
• maintaining safety, professional conduct and customer trust.

Greater experience can help a worker assess which assignments they can accept responsibly. It does not remove the need to follow applicable safety requirements, professional boundaries or occupational regulations.

2. Coordinate work with other people

An experienced worker may begin coordinating a small group for a larger assignment. This is a meaningful change: the person is no longer responsible only for their own output but must help ensure that the combined work meets the agreed requirements.

Coordination may involve:

• understanding the customer’s complete requirement;
• dividing work into manageable tasks;
• identifying the skills and resources required;
• assigning responsibilities according to demonstrated capability;
• agreeing on schedules and dependencies;
• checking progress and quality;
• communicating delays or changes;
• ensuring that workers understand safety requirements and acceptance criteria.

Coordination should not be treated as a purely administrative activity. The coordinator must understand the work well enough to plan realistically, identify problems and arrange appropriate support.

3. Develop a service or enterprise

A person who wants to take broader responsibility may progress towards becoming a Service Provider, Distributor or Employer through further learning and practical preparation.

At this level, the central question changes from “Can I complete this job?” to “Can I organize the people, materials, time and processes needed to deliver this service reliably?”

A service provider may need to develop capabilities in:

• identifying customer needs and understanding demand;
• defining the scope and expected result of an order;
• estimating costs and preparing quotations;
• planning materials, equipment and labour;
• organizing workers and allocating responsibilities;
• managing schedules, quality and delivery;
• maintaining records of orders, costs and payments;
• handling customer communication and service concerns;
• understanding business risks and applicable legal obligations;
• reviewing whether the activity is financially sustainable.

The appropriate responsibilities depend on the type and scale of the enterprise. A small local service may begin with a limited range of work, while a production or distribution operation may require more substantial planning and resources.

The change in responsibility

The distinction between independent work and enterprise is not simply the size of the job. It is the scope of responsibility the person can reliably accept.

These are functional descriptions of the intended pathway, not automatic job titles or guarantees of eligibility. One person may perform several roles in a small operation, while a larger operation may distribute them among different people.

An example: from tailoring to a garment service

Consider a learner who begins with sewing and garment construction.

Foundation: The learner develops the ability to perform defined sewing tasks, use equipment safely and follow specifications under appropriate supervision.

Certificate: The worker learns to complete defined garments independently, check measurements and finishing, meet agreed requirements and manage an individual assignment.

Experience: The worker builds a record of completed orders, learns to estimate material and time requirements, communicates with customers and improves consistency.

Diploma: The learner develops the ability to plan a larger order, estimate costs, arrange fabric and other materials, coordinate suitable workers, check quality and manage delivery.

The resulting service provider might eventually accept a larger uniform order and organize a team to fulfil it. The provider does not necessarily need to perform every stitch personally. Their responsibility is to ensure that the overall delivery meets the agreed specification.

This example illustrates the intended progression. It does not imply that every learner will establish a business or that suitable orders will always be available.

Build enterprise capability before taking enterprise risk

Technical skill alone is not enough to operate a sustainable service. A capable worker may still need to learn pricing, customer management, cash-flow planning, purchasing, scheduling and the legal responsibilities associated with the proposed activity.

Before accepting a larger order or engaging other workers, an aspiring service provider should consider the following questions:

• Demand: Is there evidence that customers need this service?
• Capability: Can the work be completed to the required standard?
• Capacity: Are suitable workers, materials, equipment and time available?
• Cost: Have labour, materials, transport, overheads and other relevant expenses been considered?
• Payment: Are the price, payment conditions and responsibilities clearly agreed?
• Quality: How will the work be checked and accepted?
• Risk: What could cause delays, losses, safety problems or customer dissatisfaction?
• Compliance: What registrations, permissions, licences, tax obligations or employment requirements may apply?
• Sustainability: Can the activity cover its costs and continue without relying on unrealistic assumptions?

These questions help distinguish a promising idea from an activity that is ready to accept customer commitments. Where the risks or requirements exceed the person’s current capability, the responsible choice may be to begin on a smaller scale, seek advice or gain further experience.

The role of the Diploma pathway

The KarmaYoga Diploma is intended to develop enterprise and service-management capability beyond individual occupational competence.

Its focus is on organizing delivery:

Demand → Organization → Delivery → Quality → Payment → Sustainability → Growth

Learners should develop an understanding of how these elements depend on one another. A service provider who accepts an order without checking capacity may fail to deliver. A business that calculates revenue but ignores costs may not be sustainable. An enterprise that grows without adequate quality controls can damage customer trust.

The Diploma pathway should therefore connect technical understanding with practical exercises in planning, costing, resource allocation, customer communication, quality control and responsible management.

The precise curriculum, prerequisites and assessment requirements need to be defined for each occupational pathway. The internal KarmaYoga Diploma stage should not be presented as a nationally recognized qualification unless the relevant recognition and approval have been established.

How the Marketplace may support progression

The intended KarmaYoga Marketplace, operated commercially through Wara Systems, is designed to provide a channel through which customers and suitable service providers can connect. Depending on the services and operating arrangements implemented, such a marketplace could help providers present their capabilities, receive enquiries, understand requirements and coordinate service delivery.

For a developing service provider, a marketplace may offer a route to explore demand beyond an existing personal network. It may also create opportunities to work with other qualified providers or workers when a service requires more capacity than one person can supply.

However, marketplace participation does not guarantee assignments, customers, income or business success. Access to work depends on actual demand, suitability, availability, verification requirements, service quality and the arrangements governing each assignment. Providers should not accept commitments on the assumption that future orders will arrive.

The marketplace is also not intended to be an exclusive channel for WARA-trained workers. Subject to applicable requirements and operating policies, suitable external organizations and providers may participate in the wider service ecosystem.

Responsible growth and fair working relationships

Enterprise development should create value for customers and workers alike. A service provider takes on additional responsibility and should manage it transparently.

Good practice includes:

• agreeing on the scope, price, schedule and acceptance criteria before work begins;
• assigning tasks according to workers’ actual capabilities;
• communicating changes promptly;
• respecting workers’ agreed compensation and payment conditions;
• maintaining appropriate records of orders, costs, work and settlement;
• handling customer complaints and quality concerns fairly;
• following relevant safety, privacy, consumer-protection and employment requirements;
• avoiding commitments that cannot reasonably be fulfilled.

Growth should not come at the expense of quality, safety or fair treatment. A smaller, reliable operation may be a better starting point than accepting an order that exceeds available capacity.

Choose the next step that fits

Progression is not a race through course levels. Some people may prefer to remain independent workers and deepen their occupational expertise. Others may want to coordinate projects, provide a complete service or build an enterprise over time.

A sensible next step is to identify the capability gap between the work a person can perform today and the responsibility they want to take on next.

That may mean further technical practice, more experience with complete assignments, learning to coordinate a team or undertaking structured enterprise training. Where suitable, previous learning and demonstrated capability can inform the next learning plan, subject to the relevant assessment and recognition arrangements.

The guiding principle remains:

Learning → Skill → Work → Income → Enterprise

Each stage represents a possibility supported by capability, responsible decisions and available opportunities. The purpose of the pathway is to help people prepare for those possibilities, not to promise an outcome.

Growth begins with doing today’s work well. Enterprise becomes a realistic next step when a person is ready to take responsibility not only for their own work, but also for the people, resources and commitments involved in delivering a service.

7.8 - Learning and Skills

From learning to suitable work

Completing a course and being ready to perform a particular job are related, but they are not the same thing.

A learner may understand the principles of an occupation but still need guided practice. Another learner may be able to perform individual tasks but need further experience before taking responsibility for a complete assignment. An experienced worker may already possess many of the required skills but need to demonstrate them against defined assessment criteria.

KarmaYoga is designed to connect these different starting points with appropriate learning and work opportunities.

The underlying progression is:

Learn → Practise → Demonstrate → Verify → Qualify → Work

Each stage has a distinct purpose:

• Learn: Understand the knowledge, methods and principles required for a task.
• Practise: Develop the ability to apply them through guided and progressively independent activities.
• Demonstrate: Perform the required task or solve the relevant problem.
• Verify: Assess the evidence against defined competency requirements.
• Qualify: Complete the applicable course or qualification requirements.
• Work: Apply the demonstrated capability in a suitable real-life, occupational or service context.

The purpose is not to send every learner into work as quickly as possible. It is to help each person develop the capability and responsibility needed for the next appropriate step.

Courses begin with competencies

KarmaYoga organizes learning around what a person should be able to do, rather than treating a course as a collection of chapters or a fixed number of classroom hours.

A competency is a clearly defined capability that a learner can demonstrate.

For an occupational course, the design begins by identifying the work to be performed. The course then defines the competencies, tasks, lessons, practice activities and assessment requirements needed to develop that capability.

This creates a direct connection between training and work.

For example, a networking course should identify the tasks a learner is expected to perform, the equipment and tools involved, the required safety practices, the expected results and the situations that require assistance or escalation.

The course can then teach the relevant concepts, provide practical exercises and assess whether the learner can perform the tasks to the required standard.

The same principle applies to tailoring, digital services, hospitality, care-related work and other occupational pathways. Each occupation requires its own defined competencies and appropriate assessment.

How training prepares a learner for an assignment

A suitable assignment should be matched to the worker’s demonstrated capability, not merely to the name of a course they have attended.

The intended process connects five elements.

1. Define the work

The assignment must have a reasonably clear scope. This includes the expected result, relevant tasks, working conditions, available resources, schedule, quality requirements and applicable safety constraints.

Without a clear definition of the work, it is difficult to decide which competencies are required.

2. Identify the required competencies

The assignment is examined to determine what a person must know and be able to do.

Some assignments may require one defined skill. Others may involve several competencies, practical experience, specific equipment knowledge or additional occupational requirements.

Where work involves regulated activities, formal licences, external certification or other mandatory conditions, these must be considered separately from internal course completion.

3. Match the requirements with demonstrated capability

The worker’s learning record, verified competencies, relevant experience and assessment evidence can help determine whether the assignment is suitable.

The match should also consider the limits of the worker’s competence. A person may be ready for some tasks within an occupation without being ready for every task associated with that occupation.

4. Provide the appropriate level of responsibility

The work arrangement should reflect the person’s demonstrated capability.

A learner who needs guidance may be assigned suitable practice under supervision. A worker who has demonstrated independent occupational capability may be considered for a complete assignment within that scope. Work requiring coordination of several people or resources calls for additional capabilities.

5. Review the result and identify the next step

After the work is completed, the result can be reviewed against the agreed requirements. Where the process supports it, feedback and appropriate work records can help identify strengths, gaps and further learning needs.

A successful assignment may provide useful evidence of practical experience. An unsuccessful or incomplete assignment may reveal areas that require further practice, clearer instructions or additional support.

An assignment is therefore both a work responsibility and, where appropriate, an opportunity to continue developing capability. It should not be used as a substitute for training or as an excuse to assign work beyond a person’s competence.

The Foundation, Certificate and Diploma pathway

KarmaYoga uses three principal stages for occupational progression. Each stage represents a change in capability and responsibility.

Foundation itself contains progressive levels:

• L1 — Assisted Work: The learner performs defined tasks with guidance.
• L2 — Skilled Work: The learner performs a broader range of defined work with limited supervision.
• L3 — Complete Foundation: The learner demonstrates the defined Foundation competency set for the occupation.

These levels represent progression within Foundation; they are not separate qualifications.

The exact scope of each stage depends on the occupational pathway, its competency requirements, assessment standards and any applicable external requirements. A course title alone does not establish eligibility for a particular assignment.

An example: from networking training to suitable work

Consider a learner developing skills for a networking and CCTV-related occupation.

During Foundation, the learner practises defined tasks, becomes familiar with relevant equipment and procedures, and learns to recognize situations that require assistance. Depending on the demonstrated competencies, suitable work may involve assisting a more experienced worker.

During Certificate training, the learner develops the capability to complete defined work independently. Assessment may cover the tasks, quality requirements, safety practices and troubleshooting responsibilities included in the specified occupational scope.

After demonstrating the required capability, the worker may be considered for suitable independent assignments that match the verified scope and any additional requirements.

With further experience and learning, the worker may choose to develop service-management capabilities, such as estimating a larger job, planning resources, coordinating other workers and managing customer delivery.

The progression is not automatic. Each step depends on the capability required, the evidence available, relevant occupational conditions and the suitability of the actual work.

Matching work to capability

A useful assignment-matching process should consider more than whether a worker has completed a course.

Relevant factors include:

• Competency: Has the person demonstrated the specific skills required?
• Scope: Does the work fall within the person’s defined capability?
• Experience: Does the assignment require practical experience beyond the course assessment?
• Supervision: Is guidance or oversight necessary?
• Safety: Can the work be performed under the applicable safety requirements?
• Equipment and resources: Does the worker have access to the tools, materials and support needed?
• Additional requirements: Are licences, credentials, permissions or external assessments required?
• Availability and conditions: Can the person meet the agreed schedule, location and other assignment conditions?

A worker should not be considered suitable simply because their course name resembles the job title. Equally, a person should not have to repeat learning unnecessarily when relevant prior capabilities can be properly demonstrated and verified.

Recognizing existing skills and continued learning

People enter training with different levels of experience. Some are beginners, while others may have learned through employment, apprenticeships, family businesses, independent practice or previous courses.

The intended KarmaYoga model allows demonstrated prior capability to inform a learner’s progression. Where appropriate assessment and recognition arrangements exist, the learner’s next step can focus on competencies that remain to be developed rather than automatically repeating everything.

Recognition must be based on suitable evidence and the applicable assessment requirements. Previous experience alone does not establish that every required competency has been demonstrated.

Learning also continues after a person begins working. New equipment, changing customer requirements, more complex assignments and increased responsibility may create additional learning needs. Work history can help a learner and trainer identify what to practise next and whether further assessment is appropriate.

The role of the Marketplace

The intended KarmaYoga Marketplace, operated commercially through Wara Systems, is designed to connect customer demand with suitable workers and service providers.

In this model, verified competencies and relevant work information can help inform assignment suitability. The Marketplace may also provide a channel for presenting worker capabilities, coordinating enquiries and supporting the assignment process, depending on the operating features implemented.

The charitable training function and the commercial work function have different responsibilities:

• Wara KarmaYoga Foundation Trust and training partners, including Ramakrishna Mission where agreed, support education, skills development, practical learning and livelihood preparation.
• Wara Systems , through the intended Marketplace, is intended to support commercial customer engagement and coordination of suitable work and service providers.

These functions can complement one another without being treated as the same activity.

Training does not guarantee a job, a Marketplace assignment, a particular income or a steady supply of customers. Work depends on actual demand, capability, availability, applicable requirements and the terms of the assignment. Suitable external organizations and providers may also participate in the intended wider Marketplace ecosystem, subject to its operating rules.

What training success should mean

Attendance and course completion are useful records, but they do not tell the whole story.

A strong training pathway should make it possible to understand:

• which competencies the learner has developed;
• what evidence supports the assessment;
• which tasks the learner can perform;
• what level of supervision is appropriate;
• what work remains outside the learner’s current scope;
• what further practice or assessment is needed;
• which next learning or occupational steps may be suitable.

Where work outcomes can be measured reliably, additional indicators may include successful assignment completion, customer acceptance, work quality, repeat work and progression towards independent work. These are outcomes to evaluate, not results that can be promised to every learner.

Any national occupational qualification, external certification or formal recognition must be treated according to its actual approval and assessment status. KarmaYoga’s internal Foundation, Certificate and Diploma stages must not automatically be equated with national qualification levels.

Learning that opens a path to work

The purpose of connecting training with assignments is to make learning useful beyond the classroom. Learners should understand what they have achieved, workers should know the scope of their capability, and those offering work should be able to define the requirements clearly.

The intended pathway is:

Learning → Demonstrated Competency → Suitable Work → Experience → Further Capability

For some people, this may lead to independent work. Others may continue developing technical expertise, progress to service provision or choose a different learning path altogether.

The essential principle is that responsibility should grow with demonstrated capability. Training prepares people for suitable work; assessment helps establish readiness; and real work, when appropriate and available, creates further opportunities to learn and contribute.

7.9 - Frequently Asked Questions

Getting started

What is the KarmaYoga work pathway?

KarmaYoga connects practical learning with opportunities to develop occupational capability and prepare for meaningful work.

The intended progression is:

Foundation → Certificate → Diploma

Foundation develops the ability to perform defined tasks under appropriate supervision. Certificate develops independent occupational capability within a defined scope. Diploma develops the ability to organize people and resources to deliver a service or production activity.

The pathway is designed to support several possible outcomes, including supervised work, independent assignments, employment and service provision. It does not require everyone to become an entrepreneur.

Who can participate?

The intended learning framework accommodates people with different educational backgrounds, existing skills, work experience and ambitions.

The appropriate entry point depends on the particular course, its prerequisites, the learner’s existing capabilities and any applicable age, safety or occupational requirements. Some pathways may be suitable for beginners, while others may require prior learning or experience.

Specific eligibility criteria must be confirmed for the programme in question.

Do I need previous work experience?

Not necessarily. A Foundation pathway is intended to help learners develop defined occupational capabilities through learning and practice.

People who already have relevant experience may be able to demonstrate some competencies through an appropriate assessment process, where such arrangements are available. Prior experience does not automatically establish that every required competency has been met.

Do I need to complete Foundation before joining Certificate training?

Foundation is the normal starting stage for learners who need to develop the relevant basic occupational capabilities. Certificate training is intended to develop the ability to perform a defined occupation independently.

Whether a learner must complete the entire Foundation pathway first depends on the course requirements and any permitted assessment or recognition of prior learning. The applicable prerequisites should be confirmed before enrolment.

Is Digital Foundation relevant to every occupation?

Digital Foundation is designed as a common capability that supports the different occupational domains. Digital skills can help workers communicate, manage information, maintain records and participate in digital workflows.

The exact digital competencies required will depend on the occupation and the work being performed.

Training and assessment

What will I learn during training?

Each course should define the capabilities a learner is expected to develop, the tasks they must practise and the standards used to assess their performance.

Depending on the occupation, learning may include practical techniques, relevant concepts, safe working practices, quality requirements, communication and workplace readiness.

The specific curriculum and available training facilities depend on the programme being offered.

Is attendance enough to complete a course?

No. Attendance alone does not demonstrate occupational capability.

KarmaYoga’s intended learning model follows:

Learn → Practise → Demonstrate → Verify → Qualify → Work

A learner must meet the applicable course requirements and demonstrate the required competencies. The assessment method and completion criteria should be defined for the particular pathway.

How will my skills be assessed?

Assessment should be based on the competencies and tasks defined for the course. Depending on the occupation, evidence may include practical demonstrations, completed tasks, assessment activities and other appropriate records.

Where independent work is the intended outcome, the assessment should establish whether the learner can perform the specified work independently and responsibly within the defined scope.

Any external assessment or certification requirements must also be satisfied where applicable.

What if I fail to demonstrate a competency?

A gap in assessment indicates that further learning, practice or evidence may be needed. It does not mean that a learner cannot progress in the future.

The next step should be based on the competency that remains to be demonstrated and the reassessment arrangements available for the course.

The specific support, reassessment and completion policies need to be confirmed with the training provider.

Will my previous experience be recognized?

The intended model allows verified prior competencies to inform future learning. This can help experienced learners avoid repeating material they have already mastered, where the relevant recognition and assessment arrangements permit it.

Recognition should be based on suitable evidence and defined requirements, not solely on a person’s claim of experience.

Assignments and work opportunities

Will I receive an assignment after completing training?

Completing training does not guarantee an assignment, job, customer or income.

The purpose of training is to develop and demonstrate useful capability. Suitable work also depends on actual demand, the worker’s verified competencies, availability, location, applicable requirements and the terms of the assignment.

The intended Marketplace is a potential channel for connecting customer demand with suitable workers and service providers, subject to the services and operating arrangements implemented.

Can I work while I am still learning?

Where the programme and work arrangements permit it, a learner may be able to undertake suitable practical work under appropriate guidance or supervision.

The work must match the learner’s demonstrated capability, and the customer must not be misled about the learner’s status. Safety, quality and any applicable occupational requirements must be respected.

Real customer work should not be used to justify assigning tasks beyond the learner’s competence.

What is the difference between supervised and independent work?

Supervised work is performed with the guidance or oversight appropriate to the worker’s current capability. The worker may be responsible for defined tasks without being ready to take responsibility for the entire assignment.

Independent work means that the worker has demonstrated the capability to complete the defined assignment independently within the relevant occupational scope.

Independent does not mean unrestricted. A worker must still follow the agreed requirements, safety procedures, applicable laws and professional boundaries.

How are assignments matched to workers?

A suitable assignment should be matched against the worker’s demonstrated competencies, experience and permitted scope of work.

The assessment should also consider the task requirements, required supervision, safety conditions, equipment, schedule and any mandatory credentials or permissions.

A course title by itself is not enough to establish suitability. The intended Marketplace may use competency and work information to support matching, depending on the system and processes implemented.

Can I refuse an assignment?

A worker should understand the assignment before accepting it, including its scope, expected result, schedule, location, resources, quality requirements and compensation arrangements.

If the worker cannot meet the requirements, lacks the necessary capability or considers the conditions unsuitable, they should raise the concern before accepting the work. A worker should not accept an assignment on the assumption that missing skills, equipment or support will somehow become available later.

The precise acceptance, cancellation and withdrawal rules depend on the applicable assignment terms and operating policies.

Can I work for an employer instead of through the Marketplace?

Yes, the intended occupational pathway does not require every learner to become a Marketplace worker or an entrepreneur.

Depending on their capability and circumstances, a person may seek employment, accept suitable independent assignments, work with a service provider or develop a small independent activity.

Training prepares people for possible work pathways. It does not guarantee that an employer or customer will offer work.

Can I accept work directly from customers?

The Certificate pathway is intended to develop the ability to perform defined occupational work independently. Depending on the occupation, applicable requirements and the worker’s circumstances, this capability may support direct customer work as well as work through an employer, service provider or Marketplace.

Any direct engagement should have clear expectations about scope, price, schedule, quality, payment and responsibilities. Applicable legal and occupational requirements continue to apply.

Payment and work records

How will I be paid for an assignment?

Payment arrangements should be agreed and documented before work begins. They may depend on the nature of the work and could be based on an agreed job, unit of output, project milestone or another lawful arrangement.

The assignment terms should identify the agreed compensation, what constitutes completion or acceptance, and the applicable payment conditions.

There is no single payment deadline or settlement procedure established here for every type of work. The actual terms must be confirmed for the relevant programme or assignment.

Will I have to pay back my training costs from future earnings?

No automatic recovery of training costs from future earnings should be assumed.

Training may be supported through different funding arrangements, including institutional support, sponsorship, philanthropy or eligible skill-development programmes. Any learner contribution or financial obligation must be clearly explained under the applicable programme terms.

The terms of a particular course should be checked before enrolment.

Will my work history be recorded?

The intended model includes maintaining relevant records of verified competencies and, where the necessary Marketplace or work-recording arrangements are implemented, information about assignments and their outcomes.

Useful work-history information may include assignments accepted and completed, quality results, customer acceptance, demonstrated skills and other relevant performance records.

The actual records maintained, who can access them and how long they are retained depend on the implemented system and applicable policies.

Does a certificate guarantee higher earnings?

No. A certificate can document achievement of defined course or occupational requirements, but it does not guarantee a particular wage, fee, customer base or level of demand.

Earnings depend on factors such as the type and quality of work, available opportunities, location, experience, customer requirements and the terms agreed for each engagement.

A verified record of successful work may provide additional evidence of practical experience, but it cannot guarantee future assignments.

Progression and enterprise

What can I do after Foundation?

Foundation is intended to develop the ability to perform defined tasks under appropriate supervision.

After demonstrating the required competencies, a learner may be prepared for suitable supervised work or may continue towards Certificate training, depending on the occupational pathway and available opportunities.

The next step should reflect demonstrated capability rather than course completion alone.

What does Certificate training add?

Certificate training develops independent occupational capability within a defined scope.

The objective is to prepare the learner to accept and complete suitable assignments responsibly without requiring routine supervision for every task.

It is a pathway towards independent work, not a requirement to establish a business.

Do I have to complete Diploma training?

No. Diploma is intended for people who want to develop additional capability in organizing work, managing resources, coordinating people and delivering services.

A person may prefer to remain an independent worker, deepen technical expertise or pursue employment. Those are valid pathways in their own right.

What does it take to become a Service Provider?

A Service Provider must be able to take responsibility for delivering a complete service or order, which may involve coordinating other workers, planning resources, managing schedules, checking quality and communicating with customers.

Technical skill alone may not be sufficient. Further preparation in costing, planning, customer management, record keeping and applicable business responsibilities may be needed.

The Diploma pathway is intended to develop these capabilities. Completing a course does not guarantee a viable business or a supply of customers.

Can a Service Provider engage other workers?

A service provider may need to coordinate or engage other workers to deliver a larger assignment. Any such arrangement must be consistent with the workers' capabilities, the agreed assignment terms and applicable legal requirements.

Where an arrangement constitutes employment or another regulated relationship, the relevant obligations must be observed. The title of Service Provider does not remove those responsibilities.

Certificates and recognition

Is a KarmaYoga certificate nationally recognized?

The status of a certificate depends on the specific programme and the recognition or approval actually established for it.

KarmaYoga’s internal Foundation, Certificate and Diploma stages describe progressive capability and responsibility. They must not automatically be treated as equivalent to an NSQF level, a nationally recognized occupational qualification or an external licence.

Where a suitable national occupational qualification exists, the course’s mapping, approval status, assessment route and certification arrangements should be verified before any claim of formal recognition is made.

Can I use my course completion as proof of competence?

A course completion record can show that the defined course requirements have been met. Its meaning depends on the competencies assessed, the evidence retained and the status of the credential.

For work requiring specific occupational qualifications, licences or external certification, a course completion record is not a substitute unless the relevant authority or requirement explicitly permits it.

Practical participation questions

What should I check before accepting an assignment?

Before accepting, make sure you understand:

• the work to be performed and the expected result;
• the scope and limits of your responsibility;
• the location, schedule and relevant working conditions;
• the tools, equipment, materials and support provided;
• the required quality and safety standards;
• any mandatory qualifications, permissions or credentials;
• the agreed compensation and payment conditions;
• how completion and acceptance will be determined;
• whom to contact if the scope changes or a problem arises.

If a material requirement is unclear, ask for clarification before committing to the work.

What if the assignment changes after I accept it?

A change in scope, schedule, resources or expected result can affect the worker’s ability to complete the assignment.

The change should be raised with the relevant customer, coordinator or contracting party before proceeding where possible. The parties should clarify the revised requirements and any effects on cost, timing, responsibilities or acceptance.

The specific process for approving changes and resolving disagreements depends on the applicable assignment terms and operating arrangements.

What if I discover that I cannot complete the work safely or correctly?

Do not continue with work that exceeds your competence or creates an unacceptable safety risk. Explain the issue to the responsible person and seek appropriate guidance, support or reassignment.

Recognizing a limitation and escalating it responsibly are part of professional work. They are preferable to concealing a problem or delivering work that may harm a person, damage property or fail an essential requirement.

Whom should I contact if I have a question or complaint?

Use the contact or grievance process provided by the relevant training programme, institution or assignment operator, where one has been established.

The applicable contact details and complaint-handling process should be confirmed through the organization managing the programme or work. This page does not establish a universal support channel or response deadline.

Before you participate

The KarmaYoga model is intended to connect learning, demonstrated capability and suitable work through a progressive pathway. Its practical value depends on clearly defined courses, appropriate assessment, transparent assignment terms and responsible operating arrangements.

Before enrolling in a course or accepting work, confirm the relevant programme requirements, assessment criteria, operational status, payment terms and any external occupational requirements.

The guiding principle is simple: develop the capability, demonstrate what you can do, understand the responsibility you are accepting and progress when you are ready.

8 - The Philosophy of the WARA Marketplace

Beyond a marketplace of transactions

A marketplace is often understood as a place where customers discover providers, compare offers, and arrange transactions. This is an important function, but it does not address every challenge involved in getting work done.

Consider an organisation that needs a thousand uniforms, a business that requires recurring digital support, or a community that needs local care services. Meeting such requirements may involve more than finding an available individual. It may require defining the work, identifying suitable capabilities, coordinating multiple contributors, maintaining quality, and establishing clear commercial terms.

At the same time, people may possess useful skills without having reliable access to customers or clearly defined assignments. Local entrepreneurs may be capable of organising delivery but lack access to larger customers or a dependable source of demand.

The central challenge is to connect these two sides and establish a practical way to organise the work between them.

This is the starting point for the WARA Marketplace philosophy.

The big picture

WARA’s intended model connects four elements:

1. Demand: Customers, organisations, and communities identify the products, services, or outcomes they need.
2. Organisation: Requirements become defined orders, service engagements, or assignments with clear responsibilities and expectations.
3. Coordinated delivery: Suitable workers, specialists, and local service providers organise the people and resources needed to perform the work.
4. Value and progression: Accepted work can generate revenue, worker income, practical experience, repeat engagements, and opportunities for further capability development or enterprise.

These elements form a connected operating model rather than four isolated activities.

The marketplace provides the commercial mechanism. Coordination helps turn requirements into deliverable work. Learning and capability development can prepare people for suitable responsibilities. Experience gained through work can support further progression.

The outcomes depend on actual demand, delivery capability, commercial viability, and the arrangements established for each engagement. The model describes the intended direction of the ecosystem, not a claim that every service or process is already operational.

The principles behind the model

Connect demand with capability

Skills are valuable, but skills alone do not guarantee access to customers or meaningful work. People also need a way to identify demand, understand requirements, demonstrate their capabilities, and participate in suitable assignments.

The marketplace is therefore conceived as more than a directory of service providers. It aims to help connect actual requirements with people and organisations capable of meeting them.

Organise work around clear outcomes

Customers need results, not merely a list of activities. A well-defined engagement establishes the expected deliverable or service, quality requirements, responsibilities, and acceptance conditions.

Hours and availability may still matter, particularly for recurring, time-sensitive, or in-person services. They should be considered alongside the outcome the engagement is intended to achieve.

The appropriate arrangement depends on the nature of the work and the agreement between the parties.

Distribute delivery where it makes sense

Some requirements can be fulfilled by one person. Others may need a group of workers, a local coordinator, a specialist, or a distributed production network.

The organisation of delivery should follow the requirements of the work. For example, a local service provider may coordinate a large order by distributing defined tasks among suitable workers without permanently employing every participant.

This approach can create opportunities for independent workers and local enterprises while helping customers access coordinated delivery. It also requires clear responsibilities, appropriate quality controls, and reliable communication.

Connect learning with practical work

Learning should help people develop capabilities that can be demonstrated and applied. As people gain competence and experience, they may become ready for greater responsibility or different kinds of work.

WARA’s intended learning-to-work pathway follows this cycle:

Learn → Practise → Demonstrate → Verify → Qualify → Work

Progression depends on the competencies required for a particular role, the evidence of achievement, and any applicable occupational or regulatory requirements.

Training does not guarantee assignments, income, or enterprise success. Its purpose is to help people develop relevant capabilities and prepare for suitable opportunities.

Make coordination and accountability possible

Distributed delivery requires more than connecting participants. It needs clear scopes, reliable communication, suitable verification, quality controls, and defined responsibilities.

Technology can support these processes by helping organise requirements, assignments, provider information, delivery records, and commercial activities. It cannot replace competent people, sound procedures, or accountability for the work performed.

As the scale and complexity of an engagement increase, the coordination arrangements must be appropriate to its risks and requirements.

Keep social development and commercial activity distinct

Social education, training, and livelihood preparation have a different purpose from commercial service delivery, even though the two can reinforce each other.

Wara KarmaYoga Foundation and its associated educational initiatives focus on capability development, outreach, and preparation for livelihood opportunities. Wara Systems is intended to support commercial marketplace operations, customer relationships, work coordination, service delivery systems, and commercial partnerships.

The distinction allows educational and social initiatives to retain their purposes while commercial activity connects customer demand with suitable services and delivery networks.

Build opportunities through experience

The intended model recognises several possible forms of progression. A person may begin with supervised work, become an independent worker, specialise in a trade, coordinate other workers, or establish a local service enterprise.

These are possible pathways, not mandatory stages. Some people may prefer to remain independent specialists, while others may develop an interest in managing services or organising production.

Progress should reflect demonstrated capability, experience, demand, and the person’s own goals.

Explore the philosophy

The following essays examine the reasoning behind the WARA Marketplace’s intended operating model. Each addresses a different part of the relationship between demand, work, capability, delivery, and economic opportunity.

1. The problem and the opportunity

Why having skills is not enough when people lack access to customers, organised demand, suitable assignments, or reliable delivery mechanisms.

Read: The Problem and Opportunity

2. From demand to livelihood

How customer requirements can become assignments, accepted work, income, and further opportunities for workers and local service providers.

Read: Demand to Livelihood

3. Delivery-based work

Why engagements should define expected outcomes, deliverables, quality, and acceptance criteria rather than hours alone, while recognising when time and availability matter.

Read: Delivery-Based Work

4. Distributed work

How a requirement can be fulfilled by individuals, local teams, villages, towns, and remote contributors through suitable coordination.

Read: Distributed Work

5. The partner model

Why assignment-based participation and service-provider networks can complement permanent employment, and how responsibilities should be established for each engagement.

Read: The Partner Model

6. Learning to work

How learning, practical demonstration, capability verification, eligibility, and occupational progression can connect with suitable assignments.

Read: Learning to Work

7. Quality at scale

How distributed execution can maintain standards, clear responsibilities, appropriate safeguards, and accountability as work becomes more complex.

Read: Quality at Scale

8. Technology and coordination

The intended role of digital marketplace and operating systems in organising customer requirements, assignments, worker and provider networks, delivery information, and commercial processes.

Read: Technology and Coordination

9. Economic and social impact

How commercial activity and capability development can reinforce livelihood creation while retaining distinct institutional purposes and financial responsibilities.

Read: Economic and Social Impact

10. The long-term vision

The intended evolution from individual assignments towards independent workers, local service providers, coordinated teams, and distributed enterprises.

Read: The Long-Term Vision

How the philosophy relates to the operating model

These essays explain the reasoning behind the marketplace. The practical pages explain how that reasoning is intended to translate into participation and delivery.

• How the Marketplace Works: The lifecycle from requirement and scope through execution, verification, acceptance, and settlement.
• The Delivery Model: How engagements can define deliverables, responsibilities, quality requirements, and payment terms.
• For Organisations: How organisations can explore potential service engagements.
• For Work Partners: How workers can understand the intended partnership model and possible progression.
• Learning and Skills: How learning and demonstrated capability can connect with suitable assignments.

The distinction is useful: the philosophy explains why the model is designed this way, while the operating pages explain how participants are expected to engage with it.

What the philosophy requires in practice

The intended model depends on a few practical commitments:

• Demand before expansion: Develop services and training in response to credible needs and delivery capability.
• Capability before responsibility: Match work with demonstrated competence and applicable eligibility requirements.
• Clear terms before execution: Establish scope, responsibilities, quality expectations, and commercial terms before work begins.
• Coordination before scale: Expand distributed delivery only with appropriate processes and accountability.
• Evidence before claims: Distinguish intended capabilities from operational services, and internal learning milestones from externally recognised qualifications.
• Sustainable opportunity: Seek a model in which commercial activity can support recurring economic value while social and educational initiatives retain their own purposes.

These are design principles for the ecosystem. They should guide implementation and evaluation without being presented as proof that every process, service, or feature is already operational.

The underlying belief

A sustainable work ecosystem needs more than customers on one side and workers on the other. It needs a practical way to connect demand with human capability, organise delivery, establish trust, and allow people and organisations to progress.

WARA seeks to build towards that model by connecting commercial requirements with suitable capabilities, supporting coordinated delivery, and creating pathways through which practical experience can lead to further opportunities.

The measure of success is not simply whether a transaction takes place. It is whether the system can reliably serve real needs while creating meaningful, responsible, and sustainable opportunities for people and organisations.

8.1 - The Problem and the Opportunity

The gap between having skills and finding work

A person may know how to stitch garments, repair a computer, teach a subject, provide care, maintain equipment, or support a business. These capabilities can be useful to individuals, households, and organisations.

However, possessing a skill does not automatically lead to work.

A skilled person may not know which customers need the service, how to reach them, how to understand their requirements, or how to agree on the scope and price of an assignment. Even when a customer is found, the work may be irregular, poorly defined, or difficult to deliver independently.

The problem is not necessarily a lack of ability. It may be a lack of connection between that ability and an actual requirement.

Capability creates the potential to perform work. Access to demand creates the possibility of applying that capability commercially.

Turning that possibility into a successful engagement requires additional elements, including clear agreements, suitable delivery arrangements, quality expectations, and accountability.

Why skills alone are not enough

Several barriers can prevent capable people from accessing suitable work.

Limited access to customers

An individual may be able to perform a task well but have few ways to reach people or organisations willing to pay for it.

Finding customers often requires communication, reputation, referrals, negotiation, and the ability to explain what can be delivered. These activities take time and may require capabilities beyond the person’s primary trade.

For people working independently or in smaller communities, access to larger or recurring customers can be particularly difficult.

Unclear or irregular demand

Knowing how to perform a service does not mean knowing when someone will need it.

A tailor may have the ability to produce garments but no confirmed orders. A computer technician may be competent but receive enquiries only occasionally. A tutor may be qualified in a subject but struggle to find enough suitable learners.

Without dependable information about actual requirements, people may find it difficult to plan their time, invest in equipment, or develop their capabilities further.

Organised demand does not mean guaranteeing a continuous supply of work. It means making genuine requirements easier to identify, define, and evaluate.

Difficulty defining the work

A customer may know what they want without knowing how to specify the work clearly.

For example, asking for a large batch of uniforms is not enough to begin production. The parties need to establish quantities, sizes, materials, specifications, delivery dates, acceptable quality, and commercial terms.

Similarly, a request for care assistance needs to clarify the person’s requirements, the nature of the service, scheduling, responsibilities, and relevant safety boundaries.

When expectations remain unclear, misunderstandings can arise even when both the customer and the provider are acting in good faith.

Limited capacity to organise delivery

Some assignments are too large or complex for one person to complete independently.

A production order may require multiple workers and a coordinator. A recurring business service may need several specialised tasks to be performed consistently. A local service may require someone to organise appointments, communicate with customers, and coordinate workers.

A capable individual may not have the resources or experience to organise all these elements alone.

This creates an opportunity for local service providers, coordinators, and distributed networks to organise delivery around a defined requirement.

Difficulty establishing trust

Customers need confidence that the work will meet the agreed requirements. Workers need confidence that the assignment is genuine, the expectations are understandable, and the agreed commercial terms will be respected.

Trust becomes harder to establish when parties have no shared process for defining work, recording agreements, checking results, and resolving issues.

A marketplace that aims to support organised work must therefore consider accountability and delivery quality alongside customer discovery.

The opportunity: organise demand around real requirements

The opportunity is not simply to create another directory where customers can search for providers. It is to establish a practical connection between what customers need and what people and organisations can deliver.

This begins with understanding the requirement.

A customer identifies a need. The requirement is clarified and translated into a suitable service engagement, order, or assignment. The capabilities needed to fulfil it are identified. An appropriate delivery arrangement is established, and the work proceeds under agreed conditions.

The exact process depends on the type and complexity of the work. A small individual assignment may require only a simple agreement. A large production order or recurring service may need coordination across several participants.

The objective is to make genuine demand more actionable.

From individual capability to organised delivery

Consider an illustrative order for 1,000 uniforms.

The requirement is larger than a simple request for stitching. It may involve confirming specifications, sourcing materials, dividing production into manageable tasks, coordinating workers, checking quality, arranging delivery, and agreeing on payment.

A possible delivery arrangement could involve:

1. An organisation defines its uniform requirements and commercial expectations.
2. The marketplace helps clarify the order and identify a suitable delivery arrangement.
3. A local service provider or production coordinator organises the required workers and resources.
4. Workers perform their assigned tasks according to the agreed specifications.
5. Quality checks and delivery arrangements are completed against the order requirements.
6. Acceptance and settlement follow the agreed terms.

This is an illustrative model, not a claim that WARA currently has the capacity to fulfil such an order.

The example shows why organised demand matters. A large requirement can create work for several people, but only if the requirement can be translated into manageable tasks and the delivery process can coordinate them effectively.

The same principle can apply to smaller assignments. The scale changes, but the need to understand the requirement and agree on the work remains.

The role of the marketplace

The WARA Marketplace is intended to help connect customer requirements with suitable workers, service providers, and organisations.

Its potential role extends beyond displaying service listings. Depending on the engagement, the commercial operation may support:

• Customer enquiries and requirement clarification.
• Definition of service scope, deliverables, and expectations.
• Identification of suitable capabilities and delivery partners.
• Coordination of individual assignments or distributed work.
• Quality processes and records of completed work.
• Commercial agreements, payments, and settlements.
• Repeat engagements and longer-term customer relationships.

The specific arrangements will depend on the service, the parties involved, and the capabilities available. These are elements of the intended operating model, not a statement that every function is already available as a live marketplace feature.

The marketplace is intended to be open to organisations and service providers beyond WARA itself. WARA may also participate in coordinating or delivering services where appropriate.

Why local service providers matter

Organised demand can create opportunities not only for individual workers but also for people who can coordinate others.

A local entrepreneur may understand the capabilities available in a village, town, or neighbourhood. That person may be able to organise workers, coordinate schedules, communicate with customers, check progress, and help ensure that an order is completed.

Such a provider does not necessarily need to employ every worker permanently. Depending on the nature of the work and the applicable legal and commercial arrangements, the provider may organise a network of independent contributors for a particular order or service engagement.

This can create a progression from performing a trade to organising delivery, building customer relationships, and potentially establishing a service enterprise.

The progression is not automatic. It depends on competence, demand, resources, commercial viability, and the ability to fulfil responsibilities reliably.

Connecting capability development with demand

Organised demand also matters for education and training.

Training is more useful when it develops capabilities that people can apply to real requirements. Understanding market needs can help identify which skills deserve attention, what practical tasks learners should practise, and what evidence is needed to establish competence.

WARA’s intended learning-to-work approach connects these stages:

Learn → Practise → Demonstrate → Verify → Qualify → Work

The pathway does not mean that every learner will immediately receive an assignment after training. Suitable work depends on actual demand, demonstrated capability, eligibility, and the terms of the engagement.

The purpose is to reduce the distance between developing a capability and being prepared to apply it.

This also helps distinguish the roles of the social and educational initiatives from the commercial marketplace. Training and livelihood preparation can develop capability, while the commercial operation can connect actual requirements with suitable delivery arrangements.

What organised demand cannot solve by itself

Organising demand is necessary, but it is not sufficient for every situation.

A marketplace cannot make an unsuitable service viable simply by listing it. It cannot replace the need for competent workers, appropriate equipment, safe working practices, clear agreements, or compliance with applicable requirements.

Nor does a customer enquiry automatically become a confirmed order. Requirements must be commercially viable, suitable delivery capacity must exist, and the parties must agree on the terms.

For this reason, the model must balance opportunity with evidence and accountability.

It should distinguish between a potential requirement, a confirmed engagement, work in progress, and a completed assignment. It should also distinguish between a capability that someone claims to possess and one that has been appropriately demonstrated or verified.

These distinctions help protect both customers and work partners from expectations that cannot be supported.

From the problem to the wider opportunity

The underlying opportunity is to connect elements that are often treated separately:

• People who possess useful capabilities.
• Customers and organisations with genuine requirements.
• Local providers who can organise resources and delivery.
• Learning programmes that develop relevant practical competence.
• Commercial arrangements that define responsibilities and payment.
• Quality processes that help establish confidence in completed work.

When these elements work together, an individual skill may become part of a defined assignment. Several assignments may support repeat work. Repeat demand may help an independent worker build experience or enable a local provider to develop a service business.

Each step depends on actual results. The model does not assume that every skill will find a customer or that every assignment will lead to long-term livelihood security.

It provides a framework for making those connections more practical and accountable.

The central idea

The problem is not simply that people need skills or that customers need services. It is that capability and demand can remain disconnected.

The WARA Marketplace is intended to help close that gap by organising genuine requirements, connecting them with suitable capabilities, and supporting delivery through clear responsibilities and appropriate coordination.

Skills create capability. Organised demand creates an opportunity to apply it. Reliable delivery turns that opportunity into value.

The next question is how demand can be translated into meaningful livelihood opportunities for workers and local service providers.

Read: Demand to Livelihood

8.2 - From Demand to Livelihood

How demand can create livelihood opportunities

A customer requirement does not automatically create a livelihood. Someone must understand the requirement, organise the work, identify suitable capabilities, agree on the terms, and deliver the expected result.

Consider an organisation that needs garments produced, a business that requires customer support, or a household that needs a suitable care service. Each requirement represents potential demand. It becomes a work opportunity only when the requirement can be matched with capable people, suitable resources, and an arrangement that the parties are willing and able to fulfil.

The WARA Marketplace is intended to help organise this connection.

The objective is not simply to make work visible. It is to help turn genuine requirements into practical assignments and, where conditions permit, create a basis for continuing livelihood opportunities.

The path from demand to income

The process can be understood through six connected stages.

1. Identify genuine demand

An organisation, business, household, or other customer identifies a need for a product or service.

The requirement may be a one-time order, a recurring service, a defined project, or a series of smaller tasks. Its commercial value depends on the customer’s actual need, willingness to pay, and the feasibility of fulfilling it.

A general expression of interest is not the same as a confirmed order. Demand must be understood before it can support a reliable work arrangement.

2. Define the work

The requirement is translated into a clear scope of work.

Depending on the engagement, this may include:

• Expected deliverables or service outcomes.
• Quantity, specifications, and quality requirements.
• Required skills, equipment, and resources.
• Location, schedule, and availability.
• Responsibilities of the customer, coordinator, and worker.
• Payment basis, acceptance conditions, and settlement terms.

Clear requirements help potential work partners decide whether the assignment suits their capabilities and circumstances. They also help customers understand what they can reasonably expect.

3. Identify suitable capabilities

The next step is to identify people or organisations capable of performing the work.

A small assignment may suit one independent worker. A larger requirement may need several workers, a specialist, or a local service provider who can coordinate delivery.

Suitability depends on more than a person’s stated interest. It may depend on demonstrated skills, experience, availability, location, equipment, safety requirements, and any applicable eligibility conditions.

Training can help people develop relevant capabilities, but completing a course does not automatically establish suitability for every assignment.

4. Agree on the engagement

Before work begins, the relevant parties establish the arrangement under which it will be performed.

The agreement should make the scope, responsibilities, deliverables, quality expectations, and commercial terms understandable. Where multiple contributors are involved, their respective tasks and responsibilities must also be clear.

This stage matters because an opportunity becomes meaningful only when the people involved understand what they are accepting and what is expected in return.

An enquiry, proposed assignment, or invitation to participate should not be represented as confirmed paid work until the necessary agreement has been reached.

5. Perform and verify the work

Workers and service providers carry out their agreed responsibilities. A coordinator may organise tasks, communicate with the customer, monitor progress, or arrange quality checks where the engagement requires them.

Completion is assessed against the agreed requirements. Depending on the type of work, verification may involve inspecting a product, checking a deliverable, confirming that a service was performed, or reviewing evidence of completion.

Reliable delivery helps establish trust. It can also provide practical experience that workers and providers may use when considering future assignments.

6. Complete acceptance and settlement

Once the applicable acceptance conditions have been met, payment and settlement follow the agreed terms.

The payment arrangement may be based on a fixed deliverable, units produced, milestones, or a recurring service agreement. The appropriate basis depends on the nature of the work and the agreement between the parties.

A completed assignment can provide income and a record of practical experience. It may also help establish a working relationship that leads to further demand, although repeat work is never guaranteed.

How one requirement can support several livelihoods

Some work opportunities are individual. Others involve a network of people whose contributions combine to fulfil a larger requirement.

Consider an illustrative order for 1,000 uniforms. The organisation placing the order may need a production arrangement involving material sourcing, stitching, finishing, inspection, packaging, and delivery.

A suitable delivery model could involve a local production coordinator and several independent workers. Each contributor performs a defined part of the work, while the coordinator manages the overall process and the customer receives the agreed order.

The possible livelihood effects extend beyond the person who performs the final task. Depending on the actual scope and commercial arrangement, the order may create paid work for multiple contributors and an opportunity for the coordinator to earn revenue by organising delivery.

However, the total value of an order is not the same as the income earned by workers. Materials, equipment, transport, coordination, taxes, rejected work, and other costs must be considered. The work must also be commercially viable.

This example illustrates a possible model. It does not claim that WARA currently has the capacity or confirmed demand to fulfil such an order.

From a single assignment to repeat work

A single assignment can provide immediate experience and income. A continuing livelihood often requires something more: a way to access future demand and deliver reliably over time.

Successful engagements can help build a record of completed work, strengthen customer relationships, and demonstrate the ability to meet agreed requirements. These outcomes may improve a worker’s or provider’s suitability for future opportunities.

Several patterns are possible:

• An independent worker receives further assignments in the same trade.
• A specialist develops a reputation for a particular service.
• A local provider coordinates recurring work for several customers.
• A small team develops the capability to handle larger requirements.
• An experienced worker begins offering services independently or establishes an enterprise.

These are possible pathways rather than a fixed progression. Some people may prefer occasional assignments, while others may seek regular work or business ownership.

The availability of future work depends on customer demand, delivery performance, commercial terms, and other circumstances beyond the marketplace’s control.

The role of local service providers

A local service provider can help bridge the gap between a customer’s requirement and the capabilities available in a particular area.

The provider may understand local skills, organise contributors, coordinate schedules, manage communication, and help maintain delivery standards. This role can be particularly useful when a customer needs a larger quantity of work or a service that requires several people.

The provider’s commercial arrangement may involve managing an order, delivering a service, coordinating contributors, or accepting responsibility for a defined outcome. The actual role and obligations must be established for each engagement.

Workers participating in such a network do not necessarily need to be permanent employees of a central company. Depending on the legal and commercial arrangements, independent contributors may participate in specific assignments.

This approach may create opportunities for local entrepreneurship while allowing delivery networks to expand or contract in response to actual demand.

It also requires clear agreements between the customer, coordinating provider, and contributors. Responsibilities for quality, payment, safety, delays, and unresolved issues should not be left ambiguous.

The connection between learning and livelihood

Demand can also inform which capabilities people should develop.

If organisations regularly need a particular service, that demand can help guide course design, practical exercises, equipment requirements, and assessment criteria. Learners can then practise tasks related to real occupational requirements rather than relying exclusively on theoretical instruction.

WARA’s intended learning-to-work cycle is:

Learn → Practise → Demonstrate → Verify → Qualify → Work

Each stage has a distinct purpose:

• Learn: Understand the knowledge and procedures relevant to a task.
• Practise: Develop the ability to perform the task through guided and independent work.
• Demonstrate: Produce evidence of practical capability.
• Verify: Assess the evidence against defined criteria.
• Qualify: Establish the level of achievement or eligibility supported by the applicable assessment and credential.
• Work: Apply suitable capabilities in an assignment or service engagement.

The term “qualify” must be understood in the context of the particular programme. An internal course completion or capability record is not automatically a nationally recognised occupational qualification or professional licence.

Nor does completing the cycle guarantee a job or paid assignment. Actual opportunities depend on demand, suitability, availability, and the terms of engagement.

The purpose is to create a more practical connection between education, demonstrated capability, and potential work.

The distinct roles of social development and commercial activity

The path from demand to livelihood involves both capability development and commercial delivery. These activities can support each other, but they have different institutional purposes.

Wara KarmaYoga Foundation and its educational initiatives focus on social outreach, learning, practical capability development, and preparation for livelihood opportunities.

Wara Systems is intended to support commercial marketplace activity, including customer acquisition, service engagements, work coordination, production arrangements, quality systems, and commercial partnerships.

The educational side can help people prepare for suitable responsibilities. The commercial side can connect actual customer requirements with appropriate capabilities and delivery arrangements.

This separation helps avoid treating training participation as a commercial assignment or assuming that every person who completes a course will receive work. It also allows the marketplace to serve organisations and providers beyond WARA itself.

What must be in place for the model to work

Demand can create livelihood opportunities only when the surrounding conditions support delivery.

The intended model depends on several practical requirements:

• Real customer demand: The requirement must be genuine and sufficiently defined.
• Suitable capabilities: Workers and providers must be able to meet the relevant requirements.
• Viable commercial terms: The engagement must account for costs, responsibilities, and payment.
• Clear coordination: Participants must understand their tasks and how their work fits into the overall delivery.
• Appropriate quality and safeguards: Work must meet agreed standards and applicable safety or regulatory requirements.
• Reliable acceptance and settlement: The parties need an understandable process for confirming completion and handling payment.
• Access to future demand: Repeat opportunities require customers with continuing needs and satisfactory delivery.

These conditions cannot be replaced by a listing, a training certificate, or a promise of opportunity. They require practical arrangements that work for the specific service and the people involved.

Measuring progress beyond the number of assignments

The number of assignments completed can indicate marketplace activity, but it does not tell the whole story.

A livelihood-oriented model should also consider whether work is completed successfully, whether payment terms are honoured, whether customers return, and whether workers gain useful experience.

Relevant indicators may include:

• First completed paid assignment.
• Value of work completed and accepted.
• Timely settlement against agreed terms.
• Repeat engagements and continuing customer relationships.
• Growth in demonstrated skills and verified work history.
• Progression towards independent service provision.
• Development of local coordinators, service providers, or enterprises.

These are potential measures for evaluating the model. They should not be interpreted as claims about results already achieved.

Income stability, work quality, worker safety, customer satisfaction, and commercial viability also matter. A high volume of assignments is not necessarily a good outcome if the work is unsuitable, poorly paid, unsafe, or commercially unsustainable.

The central idea

Demand becomes a livelihood opportunity through a sequence of practical steps. A customer identifies a genuine need, the work is defined, suitable capabilities are brought together, the parties agree on the engagement, and delivery is completed under clear conditions.

A successful assignment can generate income and experience. Reliable performance may lead to repeat work. Over time, some workers may develop greater independence or build local service enterprises.

None of these outcomes is automatic. Each depends on actual demand, competence, commercial viability, and reliable delivery.

The WARA Marketplace aims to make the connection between demand and capability more organised, so that genuine requirements have a clearer path towards fulfilment and people have a practical way to participate in suitable work.

The next part of the philosophy examines how these engagements should be defined around deliverables, quality, and acceptance rather than relying on hours alone.

Read: Delivery-Based Work

8.3 - Delivery-Based Work

Define the work before deciding how to perform it

When a customer engages someone to perform work, both parties need to understand what is expected.

A customer may need a website updated, a batch of garments produced, a computer repaired, a lesson delivered, or assistance provided to an elderly person. These requirements differ in their nature, complexity, and risks. Each needs an appropriate way to define the work and determine whether it has been completed satisfactorily.

An arrangement based only on hours can leave important questions unanswered. What must be accomplished during those hours? What standard must the work meet? Who decides whether the result is acceptable? What happens if the expected result is not achieved?

An arrangement based on clearly defined outcomes helps answer these questions before work begins.

The central principle is to define the expected result, the responsibilities involved, and the conditions for acceptance before execution starts.

This does not mean that every engagement should use a fixed-price or outcome-only payment model. It means that the parties should understand what they are agreeing to, even when payment depends on time, attendance, or availability.

What delivery-based work means

Delivery-based work begins with a defined requirement and establishes how that requirement will be fulfilled.

Depending on the service, the agreement may specify:

• Scope: What work is included and what is excluded.
• Deliverables: The product, service, task, or outcome expected.
• Quality criteria: The standards the result must meet.
• Responsibilities: What the customer, worker, and any coordinator must do.
• Time and availability: Deadlines, service windows, attendance, or response expectations.
• Acceptance criteria: How completion and satisfactory performance will be confirmed.
• Commercial terms: The payment basis, applicable milestones, and settlement conditions.
• Exceptions: How changes, delays, defects, cancellations, or disputes will be handled.

Not every assignment requires a lengthy contract. A small task may need only a concise written scope and an agreed price. A complex production order or recurring service may require more detailed specifications and controls.

The level of definition should be proportionate to the value, complexity, duration, and risk of the engagement.

Why hours alone are not enough

Time is measurable, but it does not always describe the value or completeness of work.

Consider a customer who asks for a computer to be repaired. Knowing that a technician spent three hours on the task does not establish whether the fault was resolved, whether the machine works correctly, or whether the agreed repair was completed.

Similarly, a customer ordering garments needs the specified quantity and quality, not simply a record of the hours spent sewing.

In other situations, time itself is part of the service. A caregiver may need to be present during agreed hours. A tutor may need to conduct a scheduled lesson. A support operator may need to respond within a defined service window.

The appropriate approach depends on the nature of the work.

Delivery-based work does not eliminate time-based arrangements. It ensures that time is considered in the context of the service being provided.

Different ways to define an engagement

The WARA Marketplace’s intended model can support different commercial arrangements, depending on the requirement and the parties’ agreement.

Fixed deliverable

The parties agree on a defined result for an agreed price.

For example, a provider may agree to produce a specified number of garments that meet documented specifications. Payment depends on the agreed commercial terms and the applicable acceptance conditions.

This approach is useful when the scope can be defined clearly enough to estimate the work and its costs.

Unit-based work

The parties agree on a rate for each accepted unit.

For example, a production arrangement may specify a payment rate for each garment that meets the agreed requirements. The agreement should clarify how quantities, defects, rework, and acceptance will be handled.

Unit-based pricing can help distribute work among several contributors, provided the quality criteria and allocation of responsibilities are clear.

Milestone-based work

A larger engagement is divided into stages, with defined outputs or completion conditions for each stage.

For example, a digital project may have separate milestones for requirements, implementation, testing, and handover.

This can make progress easier to review and help the parties manage larger commitments. Milestones should represent meaningful stages rather than arbitrary dates alone.

Recurring service

The parties agree on an ongoing service with defined responsibilities and performance expectations.

For example, a business may need regular maintenance visits, customer enquiry handling, or scheduled tutoring sessions. The agreement may specify service frequency, availability, expected activities, response times, and quality requirements.

A recurring service can combine time-based commitments with outcome and quality measures.

Time-based engagement

The parties agree to pay for time worked, attendance, or availability.

This may be appropriate when the work cannot be fully specified in advance, when the customer needs dedicated capacity, or when the service itself consists of being available during particular periods.

Even then, the agreement should define the work to be performed, the expected responsibilities, the relevant time records, and the conditions under which the engagement operates.

These arrangements are not mutually exclusive. A single engagement may combine a recurring service fee, defined deliverables, and additional charges for agreed work outside the normal scope.

Acceptance criteria make expectations explicit

A deliverable is not necessarily complete simply because someone reports that the work has finished.

Acceptance criteria establish how the customer and provider will determine whether the agreed requirements have been met.

For a garment order, the criteria might include quantity, measurements, material, stitching, finishing, and packaging. For a computer repair, they might include resolution of the specified fault and successful completion of agreed tests. For a digital project, they might include required functions, test results, documentation, and handover.

Good acceptance criteria should be:

• Relevant: Connected to the actual requirement.
• Understandable: Clear to the people performing and evaluating the work.
• Verifiable: Capable of being checked using suitable evidence.
• Proportionate: Appropriate to the complexity and risk of the engagement.
• Agreed in advance: Established before the work begins, wherever practicable.

The parties should also agree on how defects, incomplete work, requested changes, and disagreements will be handled.

Acceptance criteria should not introduce new expectations after the work has been completed. If the customer changes the requirement, the parties may need to revise the scope, schedule, or commercial terms.

How delivery-based work supports distributed production

Delivery-based work becomes especially useful when an order involves multiple people or locations.

Consider an illustrative order for 1,000 uniforms. A customer may work with a production coordinator who divides the order into manageable tasks and allocates work to suitable contributors.

For the arrangement to work, the participants need a shared understanding of the product specifications, quantities, quality requirements, delivery schedule, and responsibilities. The coordinator also needs a way to monitor progress, identify problems, and ensure that the completed order meets the customer’s requirements.

Individual contributors may be assessed against the work assigned to them, while the overall delivery arrangement must address the complete order.

The allocation of responsibility depends on the agreement. The coordinator, marketplace operator, independent workers, and customer should not be assumed to have identical obligations.

This model can allow local providers to organise production networks without requiring every contributor to be a permanent employee of one central organisation. It also makes coordination, traceability, and quality control important parts of the delivery process.

The example illustrates a possible arrangement, not a claim that WARA currently has confirmed capacity for such an order.

Fairness requires clear responsibilities on both sides

Delivery-based work is not only about measuring the worker’s performance. Customers and coordinating organisations also have responsibilities.

A worker cannot reasonably be expected to deliver against specifications that were never communicated, use materials that were never supplied, or meet a deadline that became impossible because the customer changed the scope without agreement.

Likewise, a customer should not be expected to accept work that fails to meet the agreed requirements simply because the provider has spent time on it.

A sound engagement therefore clarifies both sides’ responsibilities.

The customer may need to provide accurate requirements, necessary materials or access, timely decisions, and payment under the agreed terms. The worker or provider must perform the agreed work, communicate relevant problems, follow applicable safety requirements, and provide evidence of completion where required.

Where a coordinator is involved, the agreement should define the coordinator’s role in communication, task allocation, quality checks, and issue resolution.

Clear responsibilities help distinguish a genuine delivery failure from a problem caused by a change in scope, missing inputs, or circumstances outside a participant’s control.

Quality, payment, and accountability

The commercial arrangement should connect payment with the basis on which the work was agreed.

For a fixed deliverable, payment may depend on the specified completion and acceptance conditions. For unit-based work, it may depend on the number of accepted units. For a recurring service, it may depend on the agreed service period, deliverables, or performance conditions. A time-based engagement may rely on approved time records and agreed responsibilities.

The parties should establish these conditions before execution begins.

The arrangement should also explain how partial completion, rework, rejected items, customer changes, delays, and cancellations will be handled. These details are particularly important when a coordinator distributes work among several independent contributors.

Accountability requires records appropriate to the engagement. These might include the agreed scope, assignment details, progress updates, delivery evidence, inspection results, acceptance confirmation, and settlement records.

The exact records and controls will vary. A simple task should not require the same administrative burden as a high-value or safety-sensitive engagement.

The role of the WARA Marketplace

The WARA Marketplace is intended to help customers and work partners establish clearer arrangements for getting work done.

Depending on the engagement and the capabilities available, its commercial operation may support:

• Clarification of customer requirements.
• Definition of scopes, deliverables, and responsibilities.
• Identification of suitable workers and service providers.
• Coordination of tasks and distributed delivery.
• Quality checks and confirmation of completion.
• Agreement records and commercial processes.
• Payment and settlement arrangements.
• Records that help support repeat engagements.

The marketplace should not assume that every service can use the same contract, payment basis, verification method, or delivery process. The arrangement must fit the work.

These are intended elements of the operating model. They should not be read as confirmation that every process or digital feature is already operational.

Choosing the right balance between outcomes and time

The useful question is not whether work should be outcome-based or time-based in every case. It is which combination of deliverables, time commitments, quality measures, and acceptance conditions best describes the engagement.

A clearly defined product may be suitable for fixed or unit-based pricing. A complex project may require milestones. A recurring service may need both scheduled availability and measurable service expectations. Work that depends on uncertain investigation may be better suited to a time-based arrangement with defined responsibilities and reporting.

The parties should consider the nature of the requirement, the level of uncertainty, the ability to measure completion, the risks involved, and the costs of administering the agreement.

The objective is to make expectations clear without imposing unnecessary complexity.

The central idea

Delivery-based work starts by establishing what needs to be accomplished, who is responsible, what standard the work must meet, and how completion will be confirmed.

Time remains important when the service requires attendance, availability, response windows, or effort-based pricing. It simply should not be treated as a complete description of work when the customer is ultimately paying for a product, service, or result.

For the WARA Marketplace, this principle provides a foundation for clearer assignments, more accountable coordination, and more reliable arrangements between customers, service providers, and workers.

The next essay examines how these defined requirements and responsibilities can support work distributed across individuals, local providers, and multiple locations.

Read: Distributed Work

8.4 - Distributed Work

Work does not always need to happen in one place

Many services are organised around a central workplace, company, or team. This arrangement is appropriate for many kinds of work, but it is not the only way to fulfil a customer requirement.

A garment order may be produced by workers in several locations. Digital services may be delivered remotely. Local maintenance may be performed by people living near the customer. A larger service engagement may combine a central coordinator, local providers, and independent specialists.

In each case, the customer needs a defined result, but the people contributing to that result do not necessarily need to work in the same building, town, or organisation.

Distributed work is the organisation of a defined requirement across suitable people, teams, or locations, with the coordination needed to deliver the agreed result.

The purpose is not to distribute every task. It is to choose a delivery arrangement that fits the work, the available capabilities, the customer’s requirements, and the practical constraints of the engagement.

Why distributed work matters

Useful capabilities are not concentrated in one place. Skilled workers, local entrepreneurs, specialists, and service providers may be spread across villages, towns, cities, and remote locations.

At the same time, customers may need work that exceeds the capacity of one individual or requires services in multiple locations.

A distributed model can help connect these two realities.

Access to wider capabilities

A customer may need a combination of skills that is difficult to find in one person or one local team. Distributed delivery can bring together people with different capabilities, provided their responsibilities and contributions can be coordinated.

For example, a digital service engagement might combine a remote specialist with a local person who gathers information or supports the customer on site.

Opportunities beyond major cities

People do not always need to relocate to a large city to participate in useful work. Depending on the occupation, customer requirements, infrastructure, and delivery arrangements, some tasks can be performed from smaller towns or villages.

Distributed work may help local workers and service providers access requirements originating elsewhere. It can also help customers find capabilities beyond their immediate location.

This does not mean that all occupations can be performed remotely or that location is irrelevant. Many services require physical presence, specialised equipment, local knowledge, or direct interaction with customers.

Better use of local knowledge

Local providers may understand the people, resources, constraints, and practical conditions of their area better than a distant organisation.

A local service provider can coordinate workers, arrange visits, communicate with customers, and help resolve delivery issues. A central marketplace or commercial operator may support customer relationships, technology, and wider coordination.

Combining local knowledge with broader access to demand can create a useful delivery arrangement when responsibilities are clearly defined.

Capacity that can respond to actual demand

Some requirements are small and occasional. Others involve a large order or recurring service. A distributed network can potentially bring together more contributors when a larger requirement arises and use a smaller arrangement when less capacity is needed.

The arrangement must still be commercially viable. Workers need suitable assignments, providers need to cover their costs, and customers need reliable delivery. A larger network alone does not guarantee that these conditions will be met.

Different forms of distributed work

Distributed work can take several forms. The right arrangement depends on what the customer needs and how the work must be performed.

Individual work across locations

An independent worker may accept a defined assignment and complete it from a suitable location.

Examples include preparing digital content, developing software, providing remote learning support, or producing a specific business deliverable.

The assignment still needs a clear scope, agreed terms, suitable communication, and a way to verify completion.

Local service delivery

Some work must be performed where the customer or physical asset is located.

Examples include equipment maintenance, household services, installation work, and certain forms of care assistance. A local provider may organise workers who can reach the customer and perform the required tasks.

The value of distribution in this case comes from local availability and coordination, rather than remote execution.

Village or community-based teams

People in the same area may work together on a shared requirement.

For example, a production order may be divided into tasks that can be performed by several local workers. A local coordinator can organise the work, manage communication, and help ensure that the completed output meets the required specifications.

Such arrangements may create opportunities for people to participate close to home, subject to the availability of suitable work, resources, and market demand.

Multi-location delivery

A customer may need the same service across several locations. Rather than sending one team everywhere, the delivery model may use local providers who follow a common scope, process, and quality standard.

Examples could include maintenance at multiple sites, local installation services, or coordinated support across a network of establishments.

The central challenge is to maintain consistency while allowing each local team to respond to its operating conditions.

Hybrid delivery

Some engagements combine remote and physical work.

A remote specialist might diagnose a problem, while a local technician performs the physical repair. A central team might manage customer enquiries while local providers complete on-site tasks.

Hybrid arrangements can be useful when a requirement combines specialised knowledge with local presence. They depend on clear handoffs, reliable communication, and a shared understanding of responsibility.

From a customer requirement to a distributed assignment

Distributed delivery begins with the requirement, not with a decision to assemble a network.

The process can be organised into the following stages.

1. Understand the requirement

Clarify what the customer needs, the expected result, the quantity or scope of work, the deadline, the location constraints, and the applicable quality or safety requirements.

At this stage, determine whether the work can reasonably be distributed or whether it requires one person or team to retain direct control.

2. Divide the work where appropriate

Identify the tasks that can be performed independently and those that depend on other tasks being completed first.

For example, a production order may be divided by batch or operation. A multi-location service may be divided by site. A digital project may be divided into defined deliverables.

Tasks should not be split merely to increase the number of participants. Poorly designed divisions can create duplication, inconsistent results, and unnecessary coordination costs.

3. Identify suitable contributors

Select workers, specialists, or local providers whose capabilities match the work.

The relevant considerations may include demonstrated competence, availability, location, equipment, experience, safety requirements, and the ability to meet the agreed terms.

Where the work requires specialised authorisation or professional eligibility, those requirements must be addressed before assigning the work.

4. Establish responsibilities and coordination

Define who performs each task, who coordinates the contributors, who communicates with the customer, and who is responsible for checking the result.

The arrangement should also establish how progress will be reported, how changes will be approved, and how problems will be escalated.

For larger engagements, a coordinator may be needed to maintain an overall view of the order while individual contributors focus on their assigned work.

5. Execute and verify

Contributors perform their tasks according to the agreed scope and standards. Appropriate checks confirm that individual outputs and the overall result meet the requirements.

The verification process should reflect the nature and risk of the work. A simple remote deliverable may need a review, while a production order or safety-sensitive service may require more detailed inspection or evidence.

6. Complete acceptance and settlement

The parties confirm completion against the agreed acceptance criteria. Payment and settlement then follow the applicable commercial arrangements.

Where several contributors are involved, the responsibilities and payment terms between the customer, coordinating provider, and workers must be understood in advance.

This process helps make distributed delivery accountable without requiring every participant to be employed by one central organisation.

An illustrative example: distributed garment production

Consider an organisation that needs 1,000 uniforms. The order may exceed the capacity of one tailor or a small workshop.

A possible arrangement could involve a production coordinator who understands the specifications and organises suitable workers across several locations.

The customer establishes the requirements, including quantities, sizes, materials, quality standards, and delivery expectations. The coordinator plans the work and allocates tasks. Workers produce the assigned items, and suitable checks are performed before the completed order is handed over.

The coordinator may need to manage materials, schedules, progress, quality issues, and communication with the customer. Individual workers need to understand their assignments and the standards against which their work will be assessed.

The commercial arrangement must account for production costs, coordination, transport, rejected items, and the agreed payment terms.

This example illustrates how distributed work might be organised. It does not establish that WARA currently has a production network or confirmed capacity to fulfil this order.

The key principle is that a large requirement can be divided among contributors only when the work, coordination, and accountability are designed to support the complete order.

The role of local service providers

Local service providers can play an important role in distributed delivery because they connect broader demand with people and resources available in a particular area.

Depending on the engagement, a local provider may:

• Understand the customer’s local requirements.
• Identify suitable workers and available resources.
• Organise tasks, schedules, and communication.
• Coordinate materials, equipment, or transport where needed.
• Monitor progress and identify delivery problems.
• Support quality checks and completion.
• Maintain the local customer relationship.

The provider’s role should be defined for each engagement. A provider who introduces a worker has different responsibilities from one who accepts responsibility for the overall delivery.

A local provider may organise an assignment-specific network without permanently employing every participant. The appropriate legal and commercial arrangements must be established for the work being performed.

Over time, a person who develops reliable coordination and customer-management capabilities may choose to expand into a service enterprise. This is a possible pathway, not a guaranteed outcome.

Coordination is the foundation of distribution

Distributing work across locations creates opportunities, but it also introduces coordination challenges.

People may use different equipment, work at different times, face different local constraints, or interpret requirements differently. Tasks may depend on one another, and a delay in one location may affect the entire delivery.

A distributed arrangement therefore needs more than a list of participants.

Shared requirements

Everyone involved must understand the relevant specifications, expected outputs, quality criteria, and deadlines. Where a requirement changes, the affected contributors must receive the updated information.

Defined responsibilities

The customer, marketplace operator, local provider, coordinator, and individual workers may have different obligations. These responsibilities should be clear enough to avoid gaps, duplicated effort, and conflicting instructions.

Communication and progress visibility

Participants need suitable ways to ask questions, report progress, raise problems, and communicate delays. The level of reporting should match the complexity of the engagement.

Quality and verification

The delivery model should define how work will be checked and who is responsible for addressing defects or incomplete tasks. Individual contributions may need verification before they are combined into the final result.

Issue resolution

The arrangement should establish how unexpected events, disagreements, scope changes, and missed deadlines will be handled. Problems should be addressed through a known process rather than left to informal assumptions.

These controls make it possible to coordinate contributors who do not share a workplace or report to the same permanent employer.

The role of technology

Technology can help coordinate distributed work by organising requirements, assignments, communication, schedules, progress information, delivery evidence, and commercial records.

For example, a suitable system may help a coordinator track which tasks have been assigned, which remain incomplete, and which outputs require review. It may also help maintain records of agreed terms and completed work.

However, technology is only part of the operating arrangement. People still need to understand the work, make appropriate decisions, perform tasks competently, and take responsibility for their obligations.

Not every assignment needs a complex digital workflow. The tools should be proportionate to the number of contributors, the complexity of the work, the risks involved, and the resources available.

The WARA Marketplace’s intended technology and coordination approach is explored further in Technology and Coordination.

Quality and accountability across locations

A distributed network must give customers a credible basis for expecting consistent results.

This does not necessarily mean every contributor must work in exactly the same way. Some variation may be appropriate because of local conditions, equipment, or the nature of the service.

What matters is that the required outcome and the standards for acceptance remain clear.

For production, this may involve common specifications and inspection criteria. For local services, it may involve defined procedures, role-specific checks, and records of completed work. For remote digital work, it may involve deliverable reviews, testing, or documented acceptance.

The responsibility for quality must follow the actual engagement structure. A central marketplace should not automatically be assumed to perform every task or take responsibility for every outcome. The roles of the customer, provider, coordinator, and worker must be established in the applicable agreement.

The greater the complexity and risk, the more important it becomes to define appropriate controls and accountability.

When distributed work is not the right choice

Distribution is a delivery option, not a universal rule.

Some work requires continuous direct supervision, specialised facilities, strict control over sensitive materials, immediate collaboration, or a single accountable specialist. Dividing such work across multiple locations may introduce more risk or cost than it removes.

Distribution can also be unsuitable when the tasks cannot be separated reliably, communication is inadequate, quality cannot be verified, or the commercial value does not justify the coordination effort.

Before distributing an assignment, the parties should consider:

• Whether the work can be divided without losing coherence.
• Whether suitable contributors are available.
• Whether local conditions and resources support delivery.
• Whether the necessary standards can be maintained.
• Whether coordination and transport costs are reasonable.
• Whether responsibilities and risks can be assigned clearly.

A central team, one local provider, or a single independent worker may be the better option for some requirements.

The objective is to select the most appropriate delivery model, not to maximise distribution for its own sake.

Distributed work and livelihood opportunities

A distributed model can connect people with demand beyond their immediate surroundings and create opportunities for local service providers to organise delivery.

It may allow an individual to contribute a specialised skill remotely, a village-based team to fulfil part of a production order, or a local provider to coordinate a service for customers across an area.

When work is completed successfully, contributors may gain income, practical experience, and a record of completed assignments. Providers may develop stronger customer relationships and learn to coordinate more complex requirements.

These outcomes depend on real demand, suitable capabilities, viable commercial terms, and reliable execution. Distribution does not itself guarantee employment, income, or continuing work.

Its value lies in creating another way to connect customer requirements with capabilities that might otherwise remain disconnected.

The central idea

Distributed work allows a customer requirement to be fulfilled by people across different locations when the work can be organised and coordinated effectively.

Individuals contribute their skills. Local providers connect demand with local capabilities. Coordinators organise the work. Suitable systems support communication, verification, and commercial processes. Clear agreements establish responsibilities and acceptance conditions.

The WARA Marketplace is intended to help make these arrangements possible where they are appropriate, while recognising that different services require different delivery models.

The next essay examines the partner model and how assignment-based participation can connect independent workers, local service providers, and coordinated delivery networks.

Read: The Partner Model

8.5 - The Partner Model

Why the way work is organised matters

A customer needs a service or product delivered. The people capable of fulfilling that requirement may be independent workers, established service providers, local entrepreneurs, specialist teams, or employees of an organisation.

The question is how to organise their participation so that the customer receives the expected result and everyone involved understands their responsibilities.

One approach is to employ a permanent workforce and allocate work internally. This is appropriate when an organisation needs continuing capacity, direct supervision, predictable availability, or sustained control over its operations.

Another approach is to engage independent workers or service providers for defined assignments. This may be appropriate when demand varies, specialised capabilities are needed for particular requirements, or work can be organised through a network of providers.

Neither approach is universally better. The appropriate structure depends on the nature of the work, the continuity required, the risks involved, the commercial arrangement, and applicable law.

The WARA partner model is intended to make assignment-based participation possible without assuming that every person contributing to a delivery network must be a permanent employee of one central organisation.

The limits of a permanent-workforce-only approach

A permanent workforce can provide continuity, shared working practices, and direct organisational control. It is often essential for roles that require sustained availability, ongoing supervision, or continuing operational responsibility.

However, relying exclusively on permanent staffing can create constraints when demand changes significantly or requirements need capabilities that are not used continuously.

Demand may fluctuate

An organisation may receive a large production order one month and a smaller volume the next. A business may need additional customer support during a particular period. A service provider may receive assignments requiring skills that are not needed for every engagement.

Maintaining enough permanent staff for peak demand can increase costs during quieter periods. Maintaining a smaller workforce may make it difficult to fulfil larger requirements when they arise.

Assignment-based participation can provide another way to organise capacity, provided that suitable contributors are available and the work can be allocated reliably.

Requirements may need different capabilities

A single customer engagement may require several trades or specialisations.

For example, a business service may involve technical work, content preparation, customer communication, and local implementation. One permanent team may not need every specialisation for its entire working week.

A network of suitable specialists and service providers may allow the required capabilities to be assembled for a particular engagement.

Work may be distributed across locations

A requirement may involve customers, assets, or production activities in different places. A central organisation may need local providers who understand the area and can coordinate suitable workers.

Employing every contributor centrally is not necessarily the only way to organise this work. Depending on the engagement and applicable legal requirements, a local provider may coordinate independent contributors for a defined order or service.

People may prefer different forms of participation

Not everyone wants the same relationship with work.

Some people prefer stable employment. Others may prefer independent assignments, specialist work, flexible participation, or building a local service business.

An ecosystem that accommodates different legitimate forms of participation can create more ways for people and organisations to work together. The appropriate arrangement must still reflect the actual working relationship, not merely the label used for it.

What the partner model means

In the WARA Marketplace’s intended model, a work partner is an individual or organisation that may participate in suitable work through an agreed commercial or service arrangement.

Participation is connected to the requirements of a particular assignment or engagement. The parties establish what must be delivered, who is responsible, what capabilities are required, and how the work will be evaluated and paid for.

Depending on the service, a partner may:

• Complete a defined task independently.
• Provide a specialist capability for part of a larger engagement.
• Deliver a recurring service under agreed conditions.
• Coordinate other workers or resources for an order.
• Operate as a local service provider or distributor.
• Develop a continuing commercial relationship with customers.

These roles are not interchangeable. A person completing an individual task may have different responsibilities from a provider who accepts responsibility for coordinating an entire order.

The term partner describes the intended participation model. It does not, by itself, establish a person’s legal status, employment relationship, professional eligibility, or authority to perform regulated work. Those matters depend on the actual arrangement and applicable requirements.

An assignment is the basic unit of participation

The partner model begins with defined work rather than a general expectation that someone will be available for any task.

An assignment should establish the information relevant to the engagement.

The level of detail should match the complexity and risk of the work. A simple assignment may require a concise scope and price, while a larger engagement may need detailed specifications, milestones, and quality controls.

Before accepting an assignment, a partner should be able to understand the expected work, the relevant conditions, and the basis on which the engagement will be completed.

How assignment-based participation works

The intended process can be described as a sequence of connected steps.

1. A requirement is identified

A customer or organisation identifies a product, service, or outcome it needs.

The requirement is clarified so that its scope, constraints, quality expectations, and commercial viability can be assessed.

2. A suitable delivery arrangement is identified

The work may suit one independent worker, several specialists, a local service provider, or a larger coordinated network.

The arrangement should reflect the actual requirement rather than assume that every assignment needs the same structure.

3. Suitable partners are identified

Potential participants are considered against the capabilities, availability, experience, and eligibility required for the work.

Where appropriate, practical evidence or role-specific verification may be necessary before a partner is assigned the responsibility.

4. The parties agree on the assignment

The scope, responsibilities, delivery expectations, commercial terms, and acceptance conditions are established before work begins.

Where a coordinating provider is involved, the relationship between that provider, the customer, and the contributing workers must also be clear.

5. The work is performed and checked

Partners carry out their agreed responsibilities. Progress, communication, and quality checks are managed in proportion to the engagement.

The process should identify problems early enough for the parties to address them appropriately.

6. Completion and settlement follow the agreement

The work is reviewed against the agreed requirements. Acceptance, payment, and settlement follow the terms established for the engagement.

A successfully completed assignment may provide practical experience and support future opportunities, but it does not guarantee another assignment or a continuing income stream.

How local providers can organise work

A central company does not always need to engage every worker directly to coordinate a larger requirement.

Consider an illustrative order for 1,000 uniforms. The customer needs a defined quantity, consistent specifications, acceptable quality, and delivery within an agreed period.

A suitable local production provider may organise the work by identifying capable contributors, allocating tasks, coordinating materials, monitoring progress, and arranging quality checks. Individual workers perform their agreed tasks, while the provider manages the responsibilities established for the overall order.

The commercial relationships need to reflect the actual structure. The customer may contract with a provider responsible for the overall delivery, while the provider makes separate arrangements with contributors. Alternatively, a different contractual structure may be appropriate.

The parties must establish who is responsible for quality, delays, payment, defects, and communication. Those responsibilities should not be assumed merely because someone coordinates the work.

The example illustrates a possible delivery arrangement, not a claim that WARA currently has a confirmed production network or capacity for this order.

The role of the marketplace

The WARA Marketplace is intended to help connect customer requirements with suitable workers, specialists, and service providers.

Depending on the engagement, the commercial operation may support:

• Customer acquisition and requirement clarification.
• Definition of assignments and delivery expectations.
• Identification of suitable partners and providers.
• Coordination of work across individuals and locations.
• Quality processes and completion records.
• Commercial agreements, payments, and settlements.
• Repeat engagements and longer-term service relationships.
• Development of local provider and enterprise networks.

The marketplace may also participate in service delivery or coordination where appropriate. It should not be assumed to be merely a directory, nor should every engagement be assumed to involve WARA as the direct employer or service provider.

The intended model is open to other organisations and service providers. Its purpose is to help organise work across a wider ecosystem, with the role of each participant established for the particular engagement.

These are elements of the intended operating model, not confirmation that every function or digital feature is already operational.

The partner model does not exclude employment

Assignment-based participation is not a replacement for every form of employment.

Some roles require a continuing employment relationship, regular working hours, direct supervision, ongoing availability, or responsibilities that cannot reasonably be organised as separate independent assignments.

Other work may be better suited to an independent professional, a specialist service provider, a local enterprise, or a defined project engagement.

The actual relationship must determine the legal and commercial arrangement. Calling someone a partner or contractor does not automatically make the relationship independent if the facts establish otherwise.

Employment, contracting, service provision, and other engagement structures must be assessed against the applicable law and the conditions under which the work is performed.

The intended WARA model is therefore about enabling appropriate participation arrangements, not avoiding employment obligations or imposing one status on every contributor.

Fairness and responsibility

A workable partner model must provide clarity and accountability for everyone involved.

For the customer

The customer should provide accurate requirements, communicate relevant changes, make necessary decisions, and fulfil the obligations established in the agreement.

The customer should also understand who is responsible for delivery and how concerns about quality or completion will be handled.

For the partner

The partner should understand the assignment before accepting it, perform the agreed work competently, communicate relevant problems, and comply with applicable safety and professional requirements.

The partner should also understand the payment basis, acceptance conditions, and process for handling changes or disagreements.

For a coordinating provider

A provider who organises other contributors should understand the responsibilities accepted for the overall engagement. These may include task allocation, communication, quality checks, scheduling, or other delivery obligations.

The provider’s responsibilities should be proportionate to the role and clearly established in the applicable agreements.

For the marketplace operator

Where the marketplace operator coordinates or participates in an engagement, its responsibilities should be defined rather than assumed. The operator should not imply that it directly performs, supervises, guarantees, or employs every contributor unless that is actually the arrangement.

Clear roles help prevent gaps in accountability and make it easier to address problems when they arise.

From completing assignments to developing a livelihood

Assignment-based participation can provide a starting point for people who want to apply their skills, gain practical experience, or develop an independent service.

A person may begin with a small assignment, build a record of completed work, improve a specialist capability, and become suitable for more complex responsibilities. Some may eventually coordinate other workers or establish a local service enterprise.

Learning and practical preparation can support this progression. WARA’s intended learning-to-work cycle is:

Learn → Practise → Demonstrate → Verify → Qualify → Work

Each stage should reflect demonstrated capability and the requirements of the relevant role. Internal course completion does not automatically establish a nationally recognised occupational qualification or guarantee eligibility for a particular assignment.

Progression depends on actual demand, suitable opportunities, performance, resources, and the person’s goals. A partner may choose to remain an independent specialist rather than become a provider or entrepreneur.

The purpose is to allow different forms of participation and growth without assuming that everyone must follow the same path.

When the partner model is appropriate

Assignment-based participation is most useful when the work can be clearly defined, suitable contributors can be identified, and responsibilities can be established for the duration of the engagement.

It may be appropriate for project work, specialist services, defined production tasks, local service delivery, and recurring engagements with clear terms.

It may be less suitable where the organisation needs continuing direct control, uninterrupted availability, or a relationship that legally requires employment. It may also be unsuitable when the work cannot be divided or coordinated safely and effectively.

Before selecting the arrangement, the parties should consider the nature of the work, continuity requirements, legal obligations, risk, commercial viability, and the practical cost of coordination.

The objective is not to maximise the number of partners. It is to establish a reliable arrangement that meets the customer’s needs and treats the people performing the work fairly.

The central idea

The partner model offers a way to organise work around defined requirements and agreed responsibilities without assuming that every contributor must belong to one permanent workforce.

Customers can bring genuine requirements. Independent workers can contribute suitable capabilities. Local providers can organise delivery where needed. The marketplace can help connect and coordinate these participants according to the needs of each engagement.

For this model to work, the arrangement must be clear, commercially viable, legally appropriate, and accountable for the results.

The next essay examines how learning and practical capability development can connect with suitable work opportunities.

Read: Learning to Work

8.6 - Learning to Work

Learning should prepare people to apply their capabilities

Completing a course and being ready to perform a task are related, but they are not the same thing.

A learner may understand the principles of garment construction without being able to produce a garment that meets a customer’s specifications. Someone may study computer networking without yet being able to install and troubleshoot a network independently. A person may learn about customer communication but need practical experience before handling real enquiries reliably.

Learning should therefore develop capabilities that can be demonstrated, assessed, and applied.

For occupational learning, the important question is not simply what a learner has studied. It is what the learner can do, under what conditions, to what standard, and with what level of supervision.

WARA’s intended approach connects learning with practical capability and possible work opportunities. The connection is deliberate, but the outcome depends on the learner’s demonstrated competence, the requirements of the occupation, and the availability of suitable work.

The learning-to-work cycle

The KarmaYoga learning framework follows a common progression:

Learn → Practise → Demonstrate → Verify → Qualify → Work

Each stage serves a different purpose.

Learn

The learner develops the knowledge, concepts, and methods needed to understand a task or solve a problem.

Theory is important because it helps people understand why a method works, recognise unfamiliar situations, and make informed decisions. Learning should introduce concepts in ways that support the capabilities being developed.

Practise

The learner applies the knowledge through guided exercises, repeated practice, and increasingly independent tasks.

Practice helps learners develop accuracy, confidence, judgement, and consistency. The amount of practice required depends on the task, the learner’s starting point, and the standard expected.

Demonstrate

The learner performs a defined task or solves a problem to provide evidence of capability.

Demonstration may involve producing an item, completing a practical exercise, carrying out a procedure, resolving a technical issue, or performing a service under specified conditions.

Attendance or familiarity with the subject is not sufficient evidence that the task can be performed competently.

Verify

The evidence is assessed against the relevant competency criteria.

Verification may involve practical assessment, inspection of an output, observation of performance, questioning, documented evidence, or other methods suitable for the competency.

The assessment method should reflect what the learner is expected to demonstrate. A practical occupation generally requires evidence of practical performance, not theory alone.

Qualify

The learner meets the defined requirements for the relevant course, pathway, or qualification, where applicable.

The meaning of qualification depends on the programme and its recognition arrangements. Completing an internal KarmaYoga course or pathway does not automatically confer a nationally recognised occupational qualification, licence, or professional status.

Where an external qualification is intended, the relevant standards, assessment route, authorisation, and certification arrangements must be established.

Work

The learner applies suitable capabilities in an appropriate real-world setting.

This may involve supervised tasks, an assignment, independent work, service provision, or another arrangement suited to the person’s competence and eligibility.

Moving from learning into work depends on actual demand, suitable opportunities, and the conditions of the engagement. It is a possible next step, not an automatic consequence of course completion.

Competency is the bridge between learning and work

A competency is a clearly defined capability that a learner can demonstrate.

It describes more than a topic that has been covered. It establishes what a person should be able to do and the evidence needed to demonstrate that ability.

For example, a networking course might include a competency requiring the learner to install and test a network connection according to specified requirements. The learner would need to perform the task and provide suitable evidence that it meets the expected standard.

A garment-production pathway might define competencies for interpreting measurements, preparing materials, operating equipment safely, stitching components, and checking finished work.

The exact competencies and assessment criteria must be developed for the particular occupation or subject.

A competency-based approach helps connect course design with practical expectations. It also provides a clearer basis for identifying what a learner has achieved and what further learning or practice is needed.

A common learning architecture for different pathways

KarmaYoga’s learning architecture is intended to support academic education, digital learning, vocational training, tutoring, and continued skill development.

The underlying principle remains the same: define the intended capability, organise learning and practice around it, assess the evidence, and record what has been demonstrated.

The pace, environment, and amount of practice may differ between learners and programmes. The expected capability and the standard for demonstrating it should remain clear.

A course is therefore more than a collection of chapters or lessons. It is a structured programme designed to develop and assess a defined set of competencies.

For occupational learning, the structure can be represented as:

Domain → Occupation → Pathway → Foundation Level → Competency → Task → Lesson Unit

This structure connects the broad field of work to the specific tasks and learning activities through which capability is developed.

Progressive occupational pathways

WARA’s intended occupational learning model uses three principal stages:

Foundation → Certificate → Diploma

These stages represent increasing capability and responsibility. They should not automatically be equated with National Skills Qualifications Framework levels or nationally recognised qualifications.

Foundation: preparation for supervised work

The Foundation pathway develops the initial competencies needed to perform defined tasks under appropriate guidance or supervision.

Within the KarmaYoga framework, Foundation contains three progressive levels:

• L1, Assisted Work: The learner performs defined tasks with guidance.
• L2, Skilled Work: The learner performs a broader range of defined tasks with limited supervision.
• L3, Complete Foundation: The learner has demonstrated the complete Foundation competency set for the defined pathway.

These are progressive levels within Foundation, not separate qualifications. Completion is determined by the competencies demonstrated, rather than by calendar duration alone.

The intended occupational outcome is preparation for work as a Supervised Worker, within the scope of the competencies achieved and the applicable requirements.

Certificate: preparation for independent work

The Certificate pathway builds on the relevant Foundation competencies and develops the capability required to perform defined occupational work independently.

An independent worker must be able to carry out the tasks within the established scope, meet applicable quality requirements, recognise the limits of their competence, and seek assistance when a situation falls outside their responsibilities.

The intended occupational outcome is an Independent Worker who can accept suitable work within their demonstrated capability and eligibility.

The term Certificate refers to the stage in the KarmaYoga learning architecture. It does not, by itself, establish external recognition or authorisation.

Diploma: preparation for service provision

The Diploma pathway develops capabilities associated with organising and managing the delivery of services.

Depending on the occupation and programme, these capabilities may include understanding customer requirements, planning work, coordinating people and resources, maintaining quality, managing commercial responsibilities, and organising service delivery.

The intended occupational outcome is a Service Provider who can take responsibility for an appropriate service or delivery arrangement.

Some learners may choose this pathway to develop a local service business or coordinate a network of independent workers. Others may use it to take on greater responsibility within an existing organisation.

Enterprise development remains optional. Completing a Diploma pathway does not guarantee customers, revenue, business success, or any particular legal or professional status.

Learning must respond to occupational requirements

A course should not be designed only because a subject appears interesting or a training facility is available. For vocational learning, the intended occupation and its actual requirements should inform the competencies, practice activities, assessment criteria, and resources.

Where suitable national occupational standards exist, the course should be designed and reviewed against the relevant standards and assessment requirements. Any intended route to authorised training or recognised certification must be established through the applicable arrangements.

Where no suitable national qualification exists, a competency-based programme may still develop useful practical capabilities. Its scope and recognition status must be stated accurately.

This distinction matters because an internally assessed capability and a nationally recognised occupational qualification are not interchangeable.

The course design should identify the competencies being developed, the evidence required to demonstrate them, the assessment method, and the status of any external qualification or certification route.

From verified capability to suitable work

Demonstrated capability helps establish which tasks a learner may be ready to perform. It does not, by itself, establish that every assignment is suitable.

Before a person undertakes work, the relevant requirements must be considered.

These may include:

• The competencies needed for the assignment.
• Evidence that the person can perform the required tasks.
• The level of supervision appropriate to the work.
• Any required professional registration, licence, or other eligibility.
• Safety, safeguarding, or regulatory conditions.
• The person’s availability, location, and access to necessary equipment.
• The responsibilities and commercial terms of the engagement.

For example, a learner who has demonstrated basic computer maintenance may be suitable for certain supervised tasks but not for every complex repair. A person who has completed introductory care training may be prepared for specified non-clinical duties but not for clinical responsibilities requiring separate qualifications or authorisation.

Work should be matched to the capabilities and eligibility actually established, not simply to the name of a course.

How the marketplace can connect capability with demand

The WARA Marketplace is intended to connect genuine customer requirements with suitable workers, specialists, and service providers.

Learning and capability development can help people prepare for those requirements. The commercial marketplace can help organise suitable assignments and delivery arrangements where demand and capability align.

The connection may involve several steps:

1. A customer or organisation identifies a genuine requirement.
2. The work is defined in terms of scope, deliverables, quality, and responsibilities.
3. Suitable capabilities and any necessary eligibility are identified.
4. Potential workers or providers are considered against those requirements.
5. An appropriate engagement is agreed.
6. The work is performed and assessed against the agreed conditions.
7. Completion and settlement follow the applicable terms.

Not every assignment needs a newly trained worker, and not every learner will immediately find suitable work. The marketplace may also serve experienced workers, established service providers, and organisations that do not participate in KarmaYoga training.

The objective is to make learning one potential route into the wider work ecosystem without making training a condition for every form of participation.

Practical experience can support further progression

Learning does not end when a person completes a course. Actual work may reveal further learning needs, provide opportunities to strengthen existing skills, and help people develop confidence and judgement.

Where the work is appropriate and completed successfully, practical experience can contribute to a record of demonstrated capability. That experience may support applications for future assignments or preparation for more demanding responsibilities.

Possible progression includes:

• A learner moving from guided practice to supervised tasks.
• A supervised worker developing the capability to accept independent assignments.
• An independent worker specialising in a trade or service.
• An experienced worker coordinating other contributors.
• A service provider developing a recurring customer base or local enterprise.

These pathways are neither mandatory nor guaranteed. Progress depends on demonstrated capability, actual opportunities, the person’s goals, and the requirements of the work.

A record of completed assignments can provide useful evidence of experience, but it does not automatically replace formal qualifications, licences, or professional eligibility where those are required.

The distinct roles of learning and commercial operations

The connection between learning and work requires cooperation between educational and commercial activities, while keeping their responsibilities clear.

Wara KarmaYoga Foundation and its educational initiatives focus on social outreach, learning, practical capability development, and preparation for livelihood opportunities.

Wara Systems is intended to support commercial marketplace operations, including customer relationships, service engagements, work coordination, delivery systems, and commercial partnerships.

Training initiatives may help learners develop competencies relevant to market demand. The commercial operation may provide a mechanism for matching suitable capabilities with actual requirements.

Neither activity should be confused with the other. Training participation does not itself create a commercial assignment, and the existence of a marketplace does not guarantee that every trained person will receive work.

This separation allows learning programmes to retain their educational purpose while helping participants prepare for suitable opportunities.

What success should mean

A learning-to-work pathway should be evaluated by more than enrolment numbers, attendance, or certificates issued.

Useful indicators may include:

• Competencies demonstrated against defined criteria.
• Completion of practical assessments.
• Evidence of readiness for specified tasks.
• Appropriate progression between learning stages.
• Successful completion of suitable assignments.
• Development of verified practical experience.
• Further learning or specialisation.
• Progression towards independent work or service provision where desired.

The appropriate measures depend on the programme and its objectives. Not every learning activity is intended to lead directly to paid work. Academic learning, digital literacy, personal development, and everyday capability have value in their own right.

For occupational programmes, however, it is useful to understand whether the intended competencies are being developed and whether learners can apply them in suitable contexts.

Any reported employment, income, or enterprise outcomes should be based on actual evidence rather than inferred from course completion.

The central idea

Learning can create a stronger basis for work when it develops defined competencies, gives learners opportunities to practise, and assesses what they can actually demonstrate.

Verification helps establish capability. Qualification or eligibility depends on the applicable programme and requirements. Suitable work then depends on demand, the person’s readiness, and the terms of the engagement.

WARA’s intended learning-to-work model connects these elements without treating them as automatic steps. It aims to help people understand what they can do, what they need to develop next, and how their capabilities may connect with appropriate opportunities.

The next essay examines how distributed delivery can maintain quality, clear responsibilities, and accountability as work involves more people and locations.

Read: Quality at Scale

8.7 - Quality at Scale

The challenge of quality in distributed work

When work is performed by one person in one location, supervision and communication may be relatively straightforward. As work spreads across independent workers, local service providers, teams, villages, or multiple locations, coordination becomes more complex.

Different contributors may have different experience levels, equipment, working methods, and interpretations of the same requirement. A customer may receive inconsistent results even when every contributor is making a sincere effort.

The challenge is not simply to find capable people. It is to make sure that different people can work towards the same expected result, understand their responsibilities, and know how their work will be checked.

Quality must therefore be part of the way work is organised, rather than an inspection added only at the end.

Define quality before work begins

A contributor cannot reliably meet a requirement that has never been made clear. Before an assignment begins, the parties need a shared understanding of what is required and how completion will be judged.

Depending on the service or product, this may include:

• Scope: What is included in the assignment and what is outside it.
• Specifications: The required dimensions, materials, features, procedures, or service conditions.
• Acceptance criteria: The conditions that must be met for the work to be accepted.
• Responsibilities: Who performs each task, who coordinates the work, and who verifies the result.
• Evidence: What records, demonstrations, samples, photographs, measurements, or other evidence may be needed.
• Exceptions: How delays, defects, changed requirements, and other unexpected situations should be handled.

Not every assignment needs a complicated document. A small local service may require a concise checklist and a clear agreement. A large production order or regulated service may require more detailed specifications, records, and verification.

The amount of control should match the nature, risk, and complexity of the work.

Standardise the result, not every working method

Distributed execution does not require every contributor to work in an identical way. Different locations and teams may need different methods because of their tools, resources, experience, or local circumstances.

The important distinction is between the required result and the method used to achieve it.

Where practical, WARA’s intended approach is to establish common requirements for the result, essential safety and service conditions, completion evidence, and acceptance. Contributors can then use suitable working methods within those boundaries.

For example, a distributed tailoring assignment may specify fabric, measurements, stitching requirements, finishing, labelling, quantity, and delivery conditions. Different local teams may organise their cutting and stitching work differently, provided the agreed requirements are met.

Some activities do require standardised procedures, particularly where safety, legal obligations, technical compatibility, or customer protection depends on following a specific method. In those cases, flexibility must not override the required procedure.

Standardisation should remove avoidable ambiguity while preserving useful local capability.

Build quality into the work process

A final inspection alone cannot prevent every problem. By the time a defect is discovered, materials may have been consumed, deadlines missed, or other contributors affected.

Quality is better supported through checks at appropriate stages of execution.

A work assignment can use the following sequence:

1. Clarify: Confirm the requirement, scope, specifications, responsibilities, and acceptance criteria.
2. Prepare: Check that the people, materials, tools, information, and permissions needed for the work are available.
3. Execute: Carry out the agreed tasks and record relevant progress or evidence.
4. Check: Verify important stages or intermediate outputs where early detection can prevent larger problems.
5. Inspect: Compare the completed work against the agreed requirements.
6. Resolve: Record defects or deviations and agree on the appropriate corrective action.
7. Accept: Confirm whether the work meets the acceptance criteria and document any agreed exceptions.

The sequence is a general operating principle, not a claim that every assignment already follows a deployed WARA quality-management system. The exact checks should depend on the work involved.

Coordinate contributors without losing accountability

Distributed work often involves more than one contributor. A local service provider may organise a team, an independent worker may complete a specialist task, and another contributor may handle finishing or delivery.

Without explicit responsibilities, each participant may assume that someone else is checking the final result.

A coordinated assignment should make the following distinctions clear:

• Execution: Who performs each task.
• Coordination: Who organises dependencies, schedules, materials, and communication.
• Verification: Who checks the work and records the findings.
• Acceptance: Who is authorised to confirm that the agreed requirements have been met.
• Customer responsibility: Which organisation or party is responsible for communicating with the customer and resolving the engagement according to the agreement.

These responsibilities may be held by different people or organisations. In smaller assignments, one person may hold several roles. The essential requirement is that the responsibilities are understood before work begins.

The customer should not have to coordinate every contributor individually when the engagement has been organised through a designated service provider or coordinating organisation.

At the same time, coordination must not become a way to obscure responsibility. Each party should remain accountable for the obligations it has accepted.

Make verification proportionate to the work

Quality verification should be credible and proportionate. Excessive checking can make simple services unnecessarily expensive, while insufficient checking can expose customers and contributors to avoidable risk.

Different assignments call for different methods.

These are examples of possible methods, not a fixed checklist for every WARA engagement.

Verification should answer a specific question: does the delivered work meet the requirements that were agreed for this assignment?

Where a service requires a qualified professional, statutory approval, or a legally prescribed inspection, an internal review cannot substitute for that requirement.

Treat defects and exceptions as part of the process

No distributed system can assume that every assignment will be completed perfectly the first time. What matters is whether problems can be identified, communicated, and resolved fairly.

A workable process should distinguish between different situations:

• A requirement was unclear or changed after the agreement.
• A contributor did not follow the agreed specification.
• Materials, information, or dependencies were unavailable.
• Work was delayed by circumstances outside a contributor’s control.
• The customer identified a genuine defect or an unmet acceptance criterion.
• The parties disagree about whether the work meets the agreed requirements.

These situations do not necessarily have the same cause or remedy. A defect may require correction or replacement. A changed requirement may need a revised scope, timeline, or price. A disagreement may require review of the original agreement and the available evidence.

The response should follow the terms of the engagement, applicable law, and the circumstances of the case. It should not automatically place every cost or failure on the individual worker.

Clear records help all parties understand what was agreed, what happened, what remains unresolved, and who is responsible for the next action.

Protect trust on both sides

Quality and accountability are not only about protecting customers. They also protect workers, service providers, and other partners.

Customers need confidence that the work they purchase will be handled responsibly. Contributors need confidence that requirements will not be changed arbitrarily, that completed work will be evaluated against agreed criteria, and that acceptance and payment decisions will be handled according to the engagement terms.

A fair quality process should therefore provide:

• Requirements that are understandable before execution.
• A consistent basis for reviewing completed work.
• Evidence-based decisions when a result is disputed.
• A reasonable opportunity to correct remediable defects where the agreement allows it.
• Clear communication about acceptance, rejection, and outstanding issues.
• A defined process for resolving disagreements and handling settlement.

A quality system that protects only one side will struggle to sustain a reliable partner network. Trust depends on responsibilities and expectations being clear for everyone involved.

The role of WARA in quality coordination

WARA’s intended Marketplace model provides a framework for connecting customer requirements with suitable organisations, service providers, and workers. Depending on the engagement, the commercial operation may support scope definition, assignment coordination, common work procedures, verification arrangements, customer communication, and settlement processes.

The precise role depends on the agreement. WARA may participate directly in an engagement, coordinate delivery through a service provider, or work with an independent organisation that has its own delivery responsibilities. The Marketplace is not limited to work performed by WARA itself.

A common framework can make distributed work easier to coordinate, but it does not remove the need for competent people, appropriate qualifications, local supervision where required, or clear contractual responsibilities.

Quality also needs feedback. Repeated defects, missed dependencies, customer complaints, and successful delivery patterns can reveal where requirements, training, coordination, or verification need improvement. Such feedback can inform future assignments and learning programmes.

These are principles for organising reliable work. They should not be read as a claim that every verification mechanism, quality process, or performance record described here is already operational.

Quality as a condition for scale

The ability to distribute work is not, by itself, evidence that a model can scale reliably. Growth is sustainable only when the system can maintain an acceptable standard of delivery as the number of assignments, contributors, and locations increases.

That requires more than adding people. It requires repeatable ways to define work, allocate responsibilities, verify results, handle exceptions, and learn from experience.

The objective is not to eliminate every variation or failure. It is to make expectations clear, detect problems early, respond fairly, and prevent avoidable failures from becoming recurring patterns.

When these principles are applied consistently, distributed work can expand participation without making quality dependent on constant personal supervision.

The next question is how information, tools, and coordination systems can support this model across a growing network.

Continue with Technology and Coordination.

8.8 - Technology and Coordination

Technology should serve the work model

A digital marketplace is useful only when it helps people accomplish something that would otherwise be difficult, fragmented, or expensive to coordinate.

For WARA, the central challenge is not simply to publish services or maintain a directory of workers. It is to connect real customer requirements with suitable capability, establish clear engagements, coordinate execution, and make completion and settlement understandable to the parties involved.

Technology can support this process by making information accessible, recording decisions, tracking assignments, and helping different participants coordinate their responsibilities. It cannot, by itself, create genuine demand, guarantee competence, resolve every disagreement, or ensure that work will be available to everyone.

The operating model must therefore determine what the technology does, rather than allowing the features of a software platform to dictate how work is organised.

From customer demand to a managed assignment

The intended work lifecycle provides a foundation for the future Marketplace:

Requirement → Scope → Agreement → Assignment → Execution → Quality Verification → Acceptance → Settlement

Each stage answers a different operational question.

• Requirement: What does the customer need?
• Scope: What exactly must be delivered, under what conditions, and with what acceptance criteria?
• Agreement: What have the relevant parties agreed about responsibilities, price, timing, and other terms?
• Assignment: Which organisation, service provider, team, or worker will perform the work?
• Execution: How will the agreed work be carried out and coordinated?
• Quality verification: What evidence or checks are needed to establish whether the requirements have been met?
• Acceptance: Has the customer or authorised party accepted the agreed deliverable?
• Settlement: What payment or other settlement action follows under the engagement terms?

A digital system can help preserve the connection between these stages. For example, the requirements recorded at the beginning should remain available when the work is assigned and verified. The agreed scope should provide the reference for acceptance, while the recorded outcome should support the appropriate settlement process.

The purpose is to reduce ambiguity and avoid situations in which a customer, coordinator, and worker each hold a different understanding of the same assignment.

Separate demand, offers, and confirmed work

A reliable Marketplace must distinguish between expressions of interest and actual commitments.

A customer enquiry is not necessarily a confirmed order. A published service is not proof that a provider is currently available. A worker’s profile does not establish that the worker has been selected for a particular assignment. Similarly, a proposed assignment should not be treated as accepted work until the relevant parties have confirmed the required terms.

The digital operating model should preserve these distinctions.

It should be possible to understand whether an item represents an enquiry, a proposed scope, an offer, an agreed engagement, an active assignment, completed work, or a settlement awaiting action. The exact statuses and workflows will depend on the services supported.

This distinction matters for both customers and contributors. Customers need to know what has actually been committed. Workers and service providers need to know which assignments they have accepted, what they are expected to deliver, and what conditions govern completion and payment.

A marketplace can improve visibility into potential demand, but it should not present interest, forecasts, or unconfirmed requests as guaranteed work.

Connect organisations, service providers, and workers

WARA’s Marketplace is intended to accommodate different ways of organising delivery. A customer may engage an organisation directly, work through a local service provider, or participate in a coordinated arrangement involving multiple contributors.

The system should not assume that every customer must contract with WARA or that every worker must be directly employed by one central organisation.

A possible network may look like this:

Customer → Marketplace → Local Service Provider or Distributor → Independent Workers and Skilled Contributors

The actual relationship depends on the engagement. Some assignments may involve one individual. Others may require a provider to coordinate a team, organise production across locations, or combine several specialist contributions.

Technology can help represent these relationships, identify the responsible parties, communicate assignment details, and preserve the records needed to coordinate delivery. It should also make the boundaries of responsibility clear.

The Marketplace is intended to be open to organisations beyond WARA. Participating organisations may bring their own customers, capabilities, service networks, and delivery arrangements. The platform’s role is to support appropriate connections and coordination, not to require every participant to operate as part of a single organisation.

Support distributed execution

Distributed execution creates coordination needs that are difficult to manage through informal messages alone as the number of assignments and contributors grows.

A future operating system may need to support activities such as:

• Recording the scope and requirements of an assignment.
• Breaking larger engagements into manageable tasks or stages.
• Identifying dependencies between contributors.
• Communicating instructions, changes, and deadlines.
• Recording progress and exceptions.
• Collecting completion evidence.
• Coordinating quality checks and acceptance.
• Maintaining the records needed for settlement and review.

These capabilities should be introduced according to operational need. A simple service may need only a clear assignment record, communication, and confirmation of completion. A larger production order may require task allocation, intermediate checks, quantity tracking, and coordination across several locations.

The goal is not to force every type of work into the same workflow. It is to provide a consistent underlying structure while allowing different services to use the processes appropriate to their requirements.

Treat information as part of the operating system

Coordination depends on more than storing names and contact details. The system needs reliable information about the work itself.

Relevant information may include:

• Customer requirements and agreed scope.
• Service descriptions and provider capabilities.
• Availability and assignment commitments.
• Responsibilities, dependencies, and deadlines.
• Specifications, instructions, and applicable procedures.
• Progress, exceptions, and completion evidence.
• Verification findings and acceptance decisions.
• Agreed commercial terms and settlement status.

Not every participant needs access to every record. Customers, providers, workers, coordinators, and administrators have different responsibilities and legitimate information needs.

A suitable system should therefore consider access permissions, confidentiality, record integrity, and the handling of personal and commercial information. Records should be retained and shared according to the purpose of the engagement and applicable requirements.

Accurate information also depends on sound operational practices. A system cannot reliably coordinate work if requirements are incomplete, statuses are misleading, or participants do not update important changes.

Use automation where it improves reliability

Automation can reduce repetitive coordination work, especially when similar assignments recur and the required rules are clear.

For example, a future system could support reminders about approaching deadlines, notifications when an assignment changes status, checks for missing information, or prompts for required completion evidence. Repeated workflows could use standard templates so that important requirements are less likely to be overlooked.

Automation should remain proportionate to the risk and complexity of the decision.

A system may identify that a required document is missing, but a qualified person may still need to determine whether the documentation is sufficient. A workflow may flag a delayed assignment, but resolving the delay may require discussion with the customer and provider. A payment process may use recorded acceptance, but disputes and exceptional circumstances may require human review under the engagement terms.

The principle is straightforward: automate repeatable administrative work where the rules are clear, and preserve appropriate human responsibility for decisions that require judgement, professional expertise, or dispute resolution.

Connect learning with operational requirements

The Marketplace and the learning system have different purposes, but they can inform one another.

Learning programmes develop capability through a structured cycle of learning, practice, demonstration, verification, and qualification. The Marketplace organises commercial engagements and connects requirements with available capability.

Where appropriate, information about recurring customer requirements, common defects, skill shortages, or new service needs may help inform future training design. Learning records may also help establish what a participant has demonstrated, subject to the relevant assessment and verification arrangements.

However, completing a course does not automatically guarantee a Marketplace assignment. Nor should an internal learning record be treated as a nationally recognised qualification, professional licence, or statutory approval unless the relevant requirements have been met.

The connection should help people prepare for suitable work while keeping training decisions, competency verification, and commercial assignment decisions distinct.

Measure whether coordination is working

Technology should be evaluated by the operational problems it helps solve, not simply by the number of features it offers.

Depending on the service, useful measures may include:

• Time taken to clarify a requirement and agree on scope.
• Time between confirmation of an assignment and the start of execution.
• On-time completion against agreed commitments.
• First-time acceptance and recurring defect patterns.
• Frequency of scope changes, delays, and unresolved exceptions.
• Time required to resolve a quality or payment dispute.
• Completeness of the records needed for verification and settlement.
• Repeat customer engagements and continued participation by capable providers.

These measures are examples for future operational evaluation, not a claim that WARA currently collects or reports them.

Metrics also require context. A high completion rate may hide poor quality if acceptance criteria are weak. A short delivery time may come at the expense of safety or fair working conditions. A high number of assignments may have little value if the work is unsuitable or commercially unsustainable.

Measurement should help improve the process and reveal problems, rather than encourage participants to optimise a number at the expense of the intended result.

Build the system around clear responsibilities

A digital Marketplace does not remove the need for agreements, appropriate qualifications, competent delivery, or accountability. It makes those responsibilities easier to coordinate only when the underlying operating model is clear.

The future system should support a consistent view of the requirement, the parties involved, the agreed work, the execution status, the verification outcome, and the next required action. The commercial responsibilities of Wara Systems, the social and educational work of the Wara KarmaYoga Foundation, and the responsibilities of independent participating organisations should remain distinct.

Technology can provide shared processes and records without making every organisation part of WARA or transferring every delivery obligation to the platform.

The same principle applies to implementation. The operating model should be tested through real service requirements, refined as evidence becomes available, and expanded according to demonstrated need. A proposed capability should not be treated as operational until it has actually been implemented and adopted.

Technology as coordination infrastructure

The long-term opportunity is to make work easier to define, organise, deliver, verify, and settle across a network of people and organisations.

A future digital Marketplace can provide the shared information and workflows needed to support that coordination. Supporting operating systems can help organisations manage their own delivery responsibilities while participating in a wider network.

But technology is only one part of the model. Sustainable coordination also depends on real demand, capable contributors, fair agreements, appropriate standards, and organisations willing to take responsibility for delivery.

The next question is what this operating model could mean economically and socially when it creates more practical ways for people and organisations to participate in productive work.

Continue with Economic and Social Impact.

8.9 - Economic and Social Impact

Two purposes that can reinforce each other

Education and commercial activity solve different problems.

Education develops knowledge, practical skills, judgement, and the ability to perform useful work. Commercial activity responds to customer requirements by organising people, resources, services, and production to deliver something of value.

Neither is sufficient on its own to create sustainable livelihoods. A person may complete training without finding suitable work. A business may have genuine customer demand but struggle to find people with the required capabilities or organise delivery reliably.

WARA’s broader model seeks to connect these two realities. Capability development can prepare people to participate in productive activity, while commercial operations can reveal what customers need and create opportunities for suitable people and organisations to undertake work.

The relationship is complementary, not interchangeable. Training should not become merely a recruitment mechanism, and a commercial marketplace should not be treated as a substitute for education or social support.

Begin with useful capability

Capability development should help people become able to do something useful and demonstrate that they can do it to an appropriate standard.

The KarmaYoga learning framework follows a common cycle:

Learn → Practise → Demonstrate → Verify → Qualify → Work

Each stage serves a distinct purpose. Learning introduces knowledge and methods. Practice develops the ability to apply them. Demonstration provides evidence of capability. Verification assesses that evidence against defined requirements. Qualification records the outcome of the applicable learning and assessment process. Work provides an opportunity to apply capability in a real setting when a suitable assignment is available.

This progression should be understood as preparation for participation, not a guarantee of employment, income, or commercial success.

The appropriate pathway also depends on the occupation. Some work can be undertaken under supervision after initial preparation. Other assignments require independent competence, additional experience, specialist qualifications, or statutory permissions. Enterprise and service-provider responsibilities may require capabilities beyond performing the technical task itself.

Training should reflect these differences rather than treating course completion as universal eligibility for every kind of work.

Let real demand inform learning

Capability development becomes more relevant when it responds to genuine needs in the economy and community.

Customer enquiries, recurring service requirements, production orders, provider feedback, and patterns of unmet demand can help identify capabilities worth developing. For example, repeated requirements for tailoring, local technical services, hospitality support, or digital business services may indicate a need for appropriately designed learning opportunities.

Such signals should be assessed before new programmes are introduced. An enquiry does not necessarily become an order, and a temporary increase in demand does not establish that a livelihood opportunity will remain available.

The intended relationship is a feedback loop:

1. Customers and organisations express requirements for products or services.
2. Commercial operations assess whether those requirements can support viable engagements.
3. Capability gaps become visible where suitable people or providers are not available.
4. Learning programmes may be designed or adapted to address relevant gaps.
5. Participants develop and demonstrate the required capabilities.
6. Suitable participants may be considered for future assignments when demand, competence, availability, and engagement terms align.
7. Delivery experience informs improvements to both learning and commercial operations.

This approach helps keep learning connected to practical use without allowing short-term market signals to dictate every educational decision.

Preserve the distinction between social and commercial work

The WARA model assigns different responsibilities to its social and commercial activities.

The Wara KarmaYoga Foundation and associated trust activities focus on social education, training, outreach, scholarships, and livelihood preparation. These activities can help people develop useful capabilities and improve their readiness to participate in economic life.

Wara Systems operates the commercial side of the model. Its intended role includes customer acquisition, commercial agreements, work distribution, production coordination, quality systems, technology, provider networks, payments, and commercial partnerships.

These purposes can support one another, but they should remain distinguishable in planning, governance, and reporting.

The table describes the intended division of purpose. The exact arrangements for particular programmes or engagements depend on their implementation and agreements.

Keeping the functions distinct helps prevent several misunderstandings. Participation in a training programme should not be represented as a purchase of guaranteed work. Commercial assignments should not be awarded solely because someone has participated in a social programme. Likewise, a commercial relationship should not be presented as a charitable benefit when it is governed by a business agreement.

Create pathways without promising outcomes

A livelihood pathway is a sequence of possible steps, not a predetermined result.

A learner may begin with foundational preparation, develop trade-specific capability, undertake supervised work, progress towards independent assignments, or eventually establish a service or production operation. Other participants may pursue employment, further education, family enterprises, or opportunities outside the WARA network.

The intended framework recognises different stages of occupational development:

• Foundation: Develop essential and trade-related capabilities, with progression from assisted work towards more complete foundational competence.
• Certificate: Develop the competence expected for more independent occupational work, subject to the requirements of the relevant programme and occupation.
• Diploma: Prepare for broader responsibilities such as providing services, organising delivery, managing a small enterprise, or coordinating other workers, according to the programme’s scope.

These are stages within the KarmaYoga learning framework. They should not automatically be interpreted as nationally recognised qualifications or as substitutes for required licences and professional credentials.

Progression depends on demonstrated capability and the requirements of the intended activity. Access to work additionally depends on actual demand, assignment suitability, availability, commercial terms, and other relevant conditions.

A responsible livelihood model must communicate these limits clearly. It can create pathways and improve access to opportunities without promising that every participant will obtain work or earn a particular income.

Understand how commercial activity can support livelihoods

Commercial work can create opportunities in several ways, depending on the nature of the engagement.

Participation in delivery: Individuals may undertake suitable tasks as independent workers, supervised contributors, or members of a provider’s delivery team.

Local service provision: A capable local provider may organise customer relationships, resources, and workers to deliver services within a community or region.

Distributed production: A larger requirement may be divided into coordinated tasks across several contributors or locations where the work permits this arrangement.

Independent enterprise: With suitable capability and experience, a participant may develop a service business, production unit, distribution operation, or other enterprise.

Repeat work and specialisation: Reliable performance may help a contributor build experience, develop a reputation, and become suitable for more complex or specialised assignments.

These are possible forms of participation, not guaranteed results of joining a programme or marketplace. Each requires an appropriate combination of demand, capability, coordination, fair agreements, and viable economics.

The commercial model must also recognise that useful work does not always require every contributor to become an entrepreneur. Independent work, employment, cooperative activity, service provision, and enterprise can serve different needs and preferences.

Make economic participation more inclusive

Access to economic opportunity is affected by more than technical skill. People may lack customer access, professional networks, reliable information, suitable equipment, working capital, or the ability to coordinate larger assignments.

A marketplace and its associated provider network may help reduce some of these barriers by connecting customer requirements with capable participants and by organising work that would otherwise be difficult to coordinate individually.

For example, an individual may be able to perform a particular production task but lack the resources to find customers, obtain a larger order, coordinate materials, or manage delivery. A suitable service provider or coordinating organisation may help organise those activities, allowing the individual to contribute without having to manage the entire commercial operation.

This does not remove every barrier. Some occupations require substantial equipment, investment, certification, or local infrastructure. Some participants will need additional support before they can take on paid work. Others may not find suitable opportunities in a particular period.

Inclusion should therefore mean improving access to appropriate opportunities and support, not assuming that one commercial arrangement will suit everyone.

Measure social and commercial outcomes separately

A model that combines education with commercial activity needs to understand whether each part is achieving its intended purpose.

Educational outcomes may include demonstrated competencies, course completion, progression between learning stages, and the ability to apply skills in practical settings.

Commercial outcomes may include confirmed assignments, delivery reliability, customer acceptance, repeat engagements, sustainable operating costs, and timely settlement under agreed terms.

Livelihood outcomes require a further view. Depending on the programme and the evidence available, they may include participation in paid work, repeat work, income earned, progression towards independent service provision, or the development of viable enterprises.

These measures should not be confused. A high number of training completions does not establish that participants have obtained work. A high volume of commercial transactions does not establish that the benefits are fairly distributed. A first assignment does not necessarily establish a stable livelihood.

Measurement should also distinguish between activity and impact. Counting enrolments, enquiries, assignments, or transactions can describe what happened, but understanding sustained outcomes requires suitable evidence over time and careful attention to context.

The aim is to improve both capability development and commercial delivery while being honest about what the evidence demonstrates.

Keep the relationship sustainable and fair

Social programmes and commercial operations can reinforce each other over time when each has a clear purpose and the relationship is managed responsibly.

Training should provide meaningful learning rather than depend on the promise of future assignments. Commercial work should be organised around genuine customer requirements, appropriate capability, clear terms, and acceptable delivery standards. Participants should understand the difference between learning opportunities, possible work opportunities, and confirmed commercial commitments.

Where a participant undertakes paid work, the applicable agreement should make responsibilities, compensation, acceptance criteria, and settlement conditions clear. Where a programme provides scholarships or other support, its terms should be communicated separately from any commercial engagement unless an explicit and appropriate arrangement states otherwise.

Sustainability requires attention to both sides of the model. Commercial operations must be viable enough to deliver reliably, while educational and social activities must remain accountable to their own objectives and responsibilities.

The purpose is not to turn every social activity into a commercial transaction. It is to make useful capability more relevant to economic life and to make genuine economic opportunities more accessible to people who can contribute to them.

From livelihood pathways to long-term impact

WARA’s broader proposition is that education, capability, and commercial coordination can work as connected parts of a wider system without losing their individual purposes.

Social education can help people prepare. Learning can establish and demonstrate capability. Commercial operations can connect suitable capability with real requirements. Coordinated delivery can provide practical experience, customer value, and possible opportunities for further work. Experience can then inform future learning and improvements to the way work is organised.

The strength of this model will depend on how well these relationships work in practice, not simply on the existence of a training programme or a digital marketplace.

The long-term question is how these connected activities can develop into a durable network of capable people, responsible organisations, and productive relationships that continues to create value as needs and circumstances change.

Continue with Long-Term Vision.

8.10 - Long-Term Vision

From individual capability to organised work

Productive work often begins at an individual level. A person learns a skill, develops practical competence, and becomes able to perform a useful task. Yet individual capability alone does not always provide access to customers, a steady flow of assignments, the resources needed for larger engagements, or the ability to coordinate delivery.

The next step is not necessarily to make every skilled person start a business. It is to create ways for individual capability to participate in larger and more organised forms of work.

A skilled worker may contribute to an assignment coordinated by a local service provider. Several workers may collaborate on a larger requirement. An experienced provider may organise a team, serve multiple customers, or develop a specialised operation. Organisations in different locations may cooperate to deliver work that no single contributor could reasonably complete alone.

WARA’s long-term vision is to support these possible transitions through the combination of capability development, customer access, assignment coordination, quality practices, and commercial relationships.

A possible progression of participation

The intended model can develop through several forms of participation. These are connected possibilities rather than compulsory stages.

1. Individual assignments

An individual begins by developing and demonstrating a suitable capability. When a relevant requirement becomes available, the person may undertake an assignment independently or under appropriate supervision.

The assignment provides an opportunity to apply learning in a real setting, understand customer expectations, and develop practical experience. Reliable performance may help the person become suitable for further work, subject to demand and the requirements of each engagement.

2. Repeat work and specialisation

With experience, a contributor may become more capable in a particular type of service or task. Repeat assignments can help build familiarity with procedures, improve delivery, and establish a record of performance.

Specialisation may make it easier for customers and coordinating organisations to identify suitable capability. It can also help contributors focus their learning and investment on work they are equipped to perform.

Repeat work is not automatic. It depends on customer demand, delivery quality, commercial viability, and the terms of each engagement.

3. Local service providers

Some contributors may choose to take responsibility for organising services in their own locality. A local provider can connect customer requirements with suitable workers, organise resources, coordinate schedules, and take responsibility for the delivery obligations it accepts.

This role may create opportunities beyond the provider’s own technical work. It can involve customer communication, planning, procurement, team coordination, quality checks, and commercial management.

A local provider does not necessarily need to own every resource or employ every person involved in an assignment. Depending on the work and applicable arrangements, the provider may coordinate independent contributors or collaborate with other organisations.

4. Coordinated teams

Larger or more complex requirements may need multiple people with complementary capabilities.

A coordinated team can divide work into tasks, establish responsibilities, manage dependencies, and bring individual contributions together into an accepted result. The team may operate from one location or across several locations.

Coordination becomes increasingly important as the number of contributors grows. Shared requirements, clear responsibilities, communication, verification, and fair settlement arrangements help ensure that a larger team delivers a coherent result rather than a collection of disconnected tasks.

5. Distributed enterprises

Over time, some providers or organisations may develop networks that coordinate work across multiple locations. Different participants may specialise in production, customer relationships, technical delivery, distribution, or other parts of the service.

A distributed enterprise can combine local knowledge and participation with broader access to customers and coordinated delivery. It may serve larger requirements, cover more locations, or combine capabilities that are not available within a single team.

This model requires dependable coordination, suitable infrastructure, viable commercial arrangements, and clear accountability. Geographic distribution alone does not create an effective enterprise.

How the progression can work

The possible progression can be understood as a widening of responsibility and coordination.

Individual capability → Repeat assignments → Local service provision → Coordinated teams → Distributed enterprise

At each stage, the participant may take on different responsibilities:

This progression is illustrative. People may enter at different points, remain in one form of participation, move between forms, or follow entirely different livelihood pathways.

The objective is to make additional forms of participation possible, not to impose a single career ladder on everyone.

Connect learning with increasing responsibility

As the nature of work changes, the capabilities required to perform it also change.

A person who can complete a technical task may not yet be ready to manage customer agreements, coordinate a team, estimate costs, or resolve delivery exceptions. Similarly, an experienced provider may need additional capabilities to organise work across locations or manage larger commercial commitments.

Learning should therefore support both occupational competence and, where relevant, the wider responsibilities associated with service provision and enterprise.

The KarmaYoga learning framework provides a progression through Foundation, Certificate, and Diploma stages. In its intended occupational model, these relate respectively to foundational capability for supervised work, preparation for more independent work, and preparation for responsibilities such as service provision or enterprise.

These stages support capability development but do not automatically establish eligibility for every occupation, professional role, or commercial engagement. Requirements depend on the work, the applicable programme, and any relevant qualifications, licences, or approvals.

Further learning may be needed when a contributor takes on new responsibilities. Practical experience can also reveal where additional training, mentoring, or assessment would be useful.

Build on local capability rather than replacing it

Local communities contain knowledge, relationships, skills, and resources that may be difficult for a central organisation to reproduce. A sustainable distributed model should make these capabilities easier to connect with suitable demand.

Local providers may understand customer expectations, working conditions, available resources, and the practical constraints of their area. Workers may contribute specialised knowledge or skills developed through local experience. Organisations may already have relationships and infrastructure that can support delivery.

A coordinating network can help these participants reach customers or undertake larger requirements, provided that the commercial arrangement makes sense for all parties.

The aim is not to centralise every activity. It is to combine local capability with the coordination needed to deliver reliably across a wider market.

At the same time, local participation should not be assumed to be automatically viable. Providers need suitable demand, appropriate resources, competent contributors, and workable commercial terms. Some services are better delivered by a single specialist or established organisation than through a distributed network.

The delivery structure should fit the work.

The Marketplace as a connecting layer

The future WARA Marketplace is intended to connect customer requirements with organisations, service providers, and individual contributors. As participation grows, its potential role extends beyond making services visible.

Depending on the services and operating arrangements implemented, the Marketplace may support:

• Recording and clarifying customer requirements.
• Connecting demand with suitable organisations and capabilities.
• Establishing and tracking assignments.
• Coordinating work across contributors and locations.
• Supporting agreed verification and acceptance processes.
• Maintaining records relevant to commercial settlement.
• Helping organisations build and manage service-provider networks.

These are intended capabilities, not a claim that every function is already available.

The Marketplace should remain open to participating organisations beyond WARA. An independent organisation may bring its own customers, delivery capabilities, and provider relationships. The value of the network comes from useful connections and reliable coordination, not from requiring every participant to become part of one company.

Commercial agreements and actual operating responsibilities must continue to determine who is accountable for each engagement.

Keep social purpose and commercial discipline connected

The long-term model depends on both capability development and viable commercial activity, but the two must retain distinct purposes.

The Wara KarmaYoga Foundation and associated trust activities focus on social education, training, outreach, scholarships, and livelihood preparation. Wara Systems is responsible for the commercial Marketplace and its intended operating activities, including customer acquisition, commercial engagements, work coordination, technology, provider networks, and related delivery processes.

The learning system can help people prepare for possible participation in productive work. The commercial system can identify requirements and organise suitable engagements. Experience from delivery may, in turn, inform future learning priorities.

Neither side should make promises that the other cannot fulfil. Training does not guarantee an assignment, and a Marketplace does not guarantee a livelihood. Commercial activity must respond to genuine requirements and viable delivery arrangements, while social and educational programmes remain accountable to their own objectives.

This separation allows the two purposes to reinforce each other without confusing charitable support, educational achievement, commercial participation, and employment.

Grow through evidence, not assumptions

A distributed enterprise should develop as its ability to deliver reliably becomes clearer.

Early assignments can reveal whether requirements are sufficiently defined, whether contributors have the necessary capabilities, and whether the coordination arrangements work in practice. Repeat engagements can provide evidence about service consistency and customer satisfaction. Larger assignments can test whether the provider network can handle additional complexity without weakening quality or accountability.

Expansion should follow evidence of operational readiness rather than an assumption that more participants or locations automatically create more value.

Useful questions include:

• Is there sufficient real demand for the service?
• Can the work be defined and priced in a commercially viable way?
• Are suitable contributors and providers available?
• Can delivery be coordinated without losing quality or accountability?
• Are the agreements and settlement arrangements clear and workable?
• Can the model expand while protecting customers and treating contributors fairly?
• Does the activity create meaningful value for the organisations and people involved?

The answers may differ by trade, region, customer, and type of engagement. Some services may scale through local providers, while others may remain specialised operations. Some networks may develop gradually; others may not prove viable.

Learning from these differences is part of building a durable model.

The long-term objective

WARA’s long-term vision is not simply a larger catalogue of services, a greater number of registered workers, or a marketplace with more transactions.

It is a network in which real customer requirements can be connected with demonstrated capability; individuals can participate in suitable work; local providers can organise services; teams can coordinate larger assignments; and organisations can collaborate across locations when the work supports that arrangement.

Such a network depends on several elements working together: useful learning, genuine demand, fair commercial relationships, reliable delivery, clear accountability, and technology that supports rather than complicates the work.

The progression from individual assignments to distributed enterprises is an intended direction, not a guaranteed outcome for every person or organisation. Its success must be established through actual delivery, sustained customer value, viable operations, and meaningful opportunities for participation.

The guiding principle is simple: make capability useful, make work easier to organise, and enable people and organisations to take on greater responsibility when they are ready and when real demand supports it.

This completes the WARA work philosophy series. The practical pages explain how these principles are intended to translate into the Marketplace, delivery arrangements, organisational responsibilities, and worker participation.