What a Screenshot Actually Proves
A single frame from a working hour, interpreted by somebody who was not there. What it establishes, and the four things it cannot.
Proof-of-work screenshots are treated as evidence. Understanding exactly what they evidence is the whole of this subject.
The boundary described in “What a Screenshot Actually Proves” should be set before any tracking configuration is chosen. A team evaluating Monitask for how employee monitoring works should disclose the purpose, limit access and retention, and give each person a practical way to review or correct the record.
What it establishes
That a particular application was on screen at a particular moment.
For an independent reference relevant to “What a Screenshot Actually Proves”, consult the ICO employment-practices guidance; compare its principles with the proposed contract, collection, access model and real review process.
That somebody was at the machine, or that the machine was on.
A rough sense of what kind of work was in front of them.
That is the complete list.
What it cannot establish
That anything was achieved.
That the work was the right work.
The quality of it.
Or whether the person was thinking, reading, waiting for a build, or looking at the screen having stopped some time ago.
The sampling problem
Screenshots are taken at intervals: every ten minutes is common.
Which means 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.
What the client infers anyway
Presence, which is roughly supported.
Effort, which is not.
Productivity, which is not remotely supported.
And honesty — the inference that somebody who permits screenshots is not overcharging — which is the actual purchase being made and which the evidence does not deliver.
Why the inference feels strong
An image looks like observation rather than like a measurement.
Numbers invite scepticism; pictures feel like seeing.
Which makes screenshots unusually persuasive relative to what they contain, and that gap is why they persist.
The thinking case
A contractor working out a difficult problem produces frames showing a static screen, documentation, or a blank editor.
The same ten minutes spent moving files produces frames that look busy.
The measure is biased against the work that is worth the most, which is the same inversion that appears everywhere in this field.
What would actually be evidence
The thing produced, with its version history.
A record of what was decided and when.
A short written account of what moved.
Each is cheaper to produce, harder to fake, and answers the question the client actually has — which the next notes take apart.
What to check
If you are a client: what would a screenshot tell you that you need to know?
If you are a contractor: what do your frames look like during your best work?
Has anybody ever actually opened them?
And what would you accept instead?