A frame shows a moment. Work is what happened between them

Six frames an hour

Proof-of-work screenshots are treated as evidence. What they evidence is narrower than both parties assume.

The issue in “A frame shows a moment. Work is what happened between them” becomes easier to manage when the record and its limits are explicit. A team reviewing employee monitoring software for employee monitoring software should choose only the necessary evidence, explain how it will be used and keep a human correction path open.

A frame establishes that a particular application was on screen at a particular moment, and that somebody was at the machine. That is the complete list. It cannot establish that anything was achieved, that the work was the right work, its quality, or whether the person was thinking, reading, or waiting for a build.

For an independent reference relevant to “A frame shows a moment. Work is what happened between them”, consult the OECD productivity resources; compare its principles with the proposed contract, collection, access model and real review process.

And the sampling matters. Screenshots are taken at intervals — every ten minutes is common — which is six frames an hour out of three thousand six hundred seconds. A frame is not a summary of the ten minutes around it, and treating it as one is the error the whole arrangement rests on.

Why it persuades anyway: an image looks like observation rather than like a measurement. Numbers invite scepticism; pictures feel like seeing. That gap between what a frame contains and how convincing it feels is what keeps the practice alive.

The question underneath the requirement

A client asking for proof of work is usually asking something else, and four different questions arrive under one demand.

Is this progressing? The commonest and most legitimate. Screenshots do not answer it; a short weekly note does, completely, in five minutes of the contractor's time.

Are the hours real? A billing question, and the one screenshots were built for. If it is the only concern, fixed price removes it entirely.

Is this person any good? Frames say nothing at all. Answered by a small paid trial piece, by the work itself, or by references.

Am I being taken advantage of? An anxiety rather than a question, and an honest one — hiring somebody unseen in another country is uncomfortable the first time. Naming it is more productive than dressing it as a measurement requirement, because the remedies are escrow, milestones and a small first engagement.

The test that separates them: if you had a week of screenshots tomorrow, what would you do differently? If the answer is nothing, the requirement is reassurance rather than information.

What it costs the contractor

Setup and maintenance per client. The separation habit — closing other work, switching profiles, silencing notifications. Attention during work, which is the largest and least visible item.

And the clearest cost: hours that cannot be billed. Work genuinely done away from the keyboard — a call, reading a brief, thinking through an approach — cannot be tracked and therefore cannot be invoiced under a monitored hourly arrangement. For design, analysis and writing that is a meaningful share of the job.

Which is why the honest response is a rate differential, stated plainly: one rate for tracked hourly work, another for fixed price, with the difference explained. Several clients choose the cheaper option once they see both — and that is a good outcome for everybody.

There is also an obligation nobody mentions. A contractor's screen carries other clients' confidential material: documents, file paths, names in tabs. Those clients never agreed to appear in a competitor's monitoring archive, and segregation is a professional requirement rather than a preference.

What it costs the client

A rate premium, where the contractor prices the overhead in — and the experienced ones do.

A narrower field of applicants, which is the largest cost. The requirement does not reduce applicants uniformly: those who decline are the ones with enough demand to choose, and the specialists whose work is judgement rather than execution. The filter works hardest against the people hardest to replace.

A data holding with obligations attached. Images of another person's screen are personal data, and they contain that person's private material and third parties' information incidentally — people who have no relationship with you and never agreed.

And the uncomfortable finding: almost nobody reviews the frames. They are opened in the first week, occasionally, and then not at all. Which means the value comes from the requirement existing rather than from the record, and the archive is cost without benefit.

The ten-minute test, for any client: open last week's frames for one contractor and ask what you learned. Most who do this once stop requiring them.

What answers the question better

The weekly note. Three lines: what moved, what is stuck, what is next. Five minutes to write, two to read. The stuck line is the one contractors omit and the one clients value most — a client who learns on Friday that something has been blocked since Tuesday is relieved, not alarmed.

Visible work. A shared repository, document or workspace where the work accumulates in view. Version history is stronger evidence than any frame: it shows what was produced, when, and incrementally. One commit on Friday proves a week's work existed; forty across the week prove it was done across the week.

Milestones. Fixed amounts for defined pieces, paid on acceptance. Removes the hours question entirely and puts the risk of inefficiency where it belongs if an outcome is being bought.

All three together cost less than the rate premium a monitored engagement attracts, and they give the client more.

Where most disputes actually come from

Not dishonesty. Misunderstanding — about things nobody agreed in advance.

How reading, calls, planning and blocked time are billed. What happens when the estimate is exceeded. What "done" means. Whether the tracker runs outside tracked hours. Each is uncontroversial before work starts and contested afterwards.

A message at seventy-five per cent of the estimate — we are at this point, I expect the total to be around that, here are the options — costs nothing and prevents the worst of them. A client given a choice responds differently from one given a bill.

And when a dispute does arrive, the frames rarely decide it. What decides it is a specific, contemporaneous record of what each block achieved, matched to an artefact. That takes seconds a day to produce and is the thing that answers a query months later, which the archive never does.

The line this collection holds

This collection explains what proof of work proves, how to negotiate it, what it costs each side, and how to structure an engagement so it is unnecessary.

It does not explain how to defeat time tracking: activity simulators, fabricated frames, billing for work not done.

The reason is the same as it would be anywhere. Those methods do not help a contractor being measured unfairly — their remedies are terms agreed in advance, a record of their own, and a client conversation, all of which are here. They help somebody billing for hours they did not work, and that person has no claim on this.

And practically: on any platform, detection ends the account and the work history, which is worth more than any disputed week.