How Assignments Work
A work assignment is a defined piece of work with an agreed scope, expected result, completion conditions and applicable payment terms. The worker should understand the commitment before accepting it, complete the work responsibly, and submit it for the required quality checks and acceptance.
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:
- Confirm their understanding of the task and any unresolved details.
- Check the tools, materials, access and other resources required.
- Plan the work within the agreed schedule.
- Follow the relevant procedures, specifications and safety precautions.
- Check the quality of the work as it progresses.
- Inform the customer or coordinator promptly about delays, unexpected conditions or changes that may affect delivery.
- 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.