How should a marketplace allocate work across providers?

Separate a possible match from committed capacity

A provider profile can show relevant capability without confirming availability for a particular request. Define how availability is established, how long it remains current and what action confirms acceptance. Make the customer-facing status reflect the stage the request has actually reached.

Before ranking providers, identify the conditions an assignment must satisfy: suitable expertise, location where relevant, timing and the scope of the job. Let providers communicate constraints the platform cannot infer reliably. An offer should contain enough information for them to judge whether they can fulfill it.

Decide what happens when an offer expires or is declined. Avoid promising a start time based solely on a historical response pattern. A marketplace can use that pattern to plan its next contact while still requiring a current commitment before presenting the work as assigned.

State which allocation outcomes matter

Choose measures for customers and providers together. Matching speed, completed service, opportunities received and time spent waiting for work describe different aspects of the system. Define the eligible provider group and relevant time window before comparing the distribution of offers.

When a platform also operates a provider or sells services to providers, map those roles separately. Identify who controls eligibility, ranking, participant data and exception review. The European Commission’s published Amazon commitments distinguish data use, offer selection and logistics access. Those are useful, separate questions for an allocation review; affiliation alone does not establish preferential treatment.

Compare the documented rule with actual treatment of otherwise comparable requests. Record any differences in eligibility, placement or required services and investigate their basis. Amazon describes equal offer-selection criteria in its own account of its European changes. A published commitment is something to verify in operation, with a clear route for participants to raise unresolved concerns.

Research by Alkhatib and colleagues identified allocation and customer expectations as important design concerns through fieldwork in several work marketplaces. Their findings invite provider involvement in the design process, with limits on transfer across industries. Ask how a proposed rule would affect providers with different availability and capabilities.

Raman and colleagues studied fairness objectives in a ride-pooling model using taxi data. Such research shows how explicit objectives can be examined under stated assumptions. It does not select one universally appropriate rule. Compare plausible rules for the particular market and examine who gains or loses opportunities under each.

Evaluate allocation through completed service

Test an assignment change against downstream outcomes. A quicker offer may still lead to a decline, reassignment or incomplete job. Follow the request through acceptance and delivery, and check whether an apparent gain comes with additional coordination for either participant.

Make the service responsibilities clear when something changes after the match. Identify who handles an incorrect brief, a provider's loss of availability or a request for a replacement. Provide an accessible route for a person to review a case the normal workflow cannot resolve.

Use provider feedback to form hypotheses about unclear rules or avoidable friction, then check those hypotheses against relevant behavior and service records. Keep expectations about future work tied to actual demand. Review the allocation design as the mix of requests and available providers changes, so the rule continues to serve the market it is operating in.