68/100

Moderate evidence

ProblemPublished recordLaborProblem Space

A Better Matchmaker? The Impact of GenAI on Matching Effectiveness in Online Labor Markets

Truvace record
TRV-2026-2554raw data (JSON)
Version
v2Revised
First published
Evidence type
Controlled or validated comparison
Sources
1 sourcePeer-reviewed
sha256
3dc9a582e2e5…check it

Generative Artificial Intelligence (GenAI) is rapidly transforming online labor markets. However, its impact on matching effectiveness—the ability of platforms to efficiently pair mutually satisfactory relationships between employers and workers—remains underexplored. This study investigates how GenAI-assisted proposals affects the matching process. While access to GenAI may improve proposal clarity and increase the likelihood of a successful match, it can also obscure workers' unique attributes, potentially hin…

The problem

In early lab experiments on creative tasks, workers' AI-assisted proposals converged in writing style and content, which makes them less differentiating for employers choosing among them.

What this doesn’t fix

The findings are preliminary results from controlled lab experiments on creative-intensive tasks, so they do not yet show how GenAI affects matching on real platforms.

Sources

1 on file
  1. Peer-reviewed2026-07-05

Cite this record

v2

Truvace Impact Record TRV-2026-2554, v2: “A Better Matchmaker? The Impact of GenAI on Matching Effectiveness in Online Labor Markets.” Truvace, 2026-11-12. /record/TRV-2026-2554 (accessed on the day you copy it). sha256 3dc9a582e2e50227…

Change history

2 versions

Every change made to this record since it was first published, and why.

  1. Revisedv23dc9a582e2e5…

    Reworded the problem so it stands on its own and repaired the source title; no facts changed.

  2. Publishedv1f12c98ada13a…

    Certified into the record

Check this record hasn’t been altered

Check this record hasn’t been altered
How to check it yourself, without trusting this page

Download any version from /api/record/TRV-2026-2554 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.