Delivery-Based Work
Work is easier to understand and evaluate when the parties agree on what must be delivered, what constitutes acceptable quality, and how completion will be confirmed. The WARA Marketplace’s intended model emphasises defined outcomes and deliverables while recognising that time, availability, and attendance remain important for many services.
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.
| Type of work | What should be defined | Role of time |
|---|---|---|
| Garment production | Quantity, specifications, quality, and delivery | Production schedule and deadline |
| Computer repair | Agreed diagnosis or repair scope and verification of the result | Time may inform pricing or estimates |
| Tutoring | Subject, learning objectives, session arrangements, and expected activities | Scheduled teaching time may be central |
| Care assistance | Care scope, agreed duties, schedule, safety boundaries, and continuity | Presence and availability may be essential |
| Digital business service | Tasks, outputs, response expectations, and quality standards | Deadlines and service windows may matter |
| Maintenance | Equipment or area covered, tasks, inspection criteria, and reporting | Planned visits and response times may be required |
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.