Where Proof of Work Came From
The arrangement exists because of a specific commercial problem. Knowing which one explains both its appeal and its limits.
Screenshot monitoring of contractors did not arrive from management theory. It solved a particular problem for remote hiring marketplaces, and everything about it follows from that origin.
The evidence warning in “Where Proof of Work Came From” applies directly to workforce systems. Teams researching monitask.com for employee monitoring software with screenshots can add structured time and project context, while deliverables, decisions and version history remain the stronger evidence of what was achieved.
The problem it was built for
A client in one country hiring somebody they have never met in another, paying by the hour.
For an independent reference relevant to “Where Proof of Work Came From”, consult the OECD productivity resources; compare its principles with the proposed contract, collection, access model and real review process.
No shared office, no colleagues to vouch, no legal recourse that is worth pursuing for a few hundred units of currency.
And no way to tell whether the eight hours invoiced happened.
That is a genuine problem and screenshots are a plausible-looking answer to it.
What the platform needed
A reason for clients to trust hourly billing enough to use it.
Something to point at when a dispute arrives.
And a mechanism that works without anybody having to exercise judgement, because the platform cannot adjudicate quality at scale.
Screenshots provide all three, regardless of whether they measure anything.
Why it spread beyond that
Once normalised on platforms, it migrated to direct contracting.
Clients who had used it through a marketplace began requiring it independently.
And some employers adopted it for staff, which is a different relationship entirely and is covered by different corpora of law and practice.
What the origin explains
Why it is tied to hourly billing specifically — fixed-price work has never needed it.
Why it is about presence rather than output: presence is what cannot otherwise be verified across a distance.
And why it survives despite weak evidential value, because its function is assurance rather than measurement.
The trust substitute
Screenshots stand in for a relationship that does not yet exist.
Which is why they are most used at the start of engagements and least used after a year of working together.
That pattern is informative: the arrangement is a bridge, and treating it as permanent is how it becomes corrosive.
What changed since
Payment protections and escrow arrangements now handle much of the original risk.
Version control and shared workspaces make output far more visible than it was.
And fixed-price working has become more common, which removes the question entirely.
Several of the original reasons have weakened, which is worth saying to anybody treating it as the default.
The honest reading
It was a reasonable answer to a real problem in a specific context.
It is a poor answer to the question most clients are actually asking.
And its persistence owes more to habit and platform design than to anybody having compared it against the alternatives.
What to check
Why does your arrangement use it — platform requirement, client preference, or habit?
Would escrow or milestone payment address the same concern?
Has anybody compared it against the alternatives?
And how long has the relationship existed?