Glossary and Where to Start

Activity score — a figure derived from input, used by platforms to indicate engagement. It measures typing and clicking, not work.

The issue in “Glossary and Where to Start” becomes easier to manage when the record and its limits are explicit. A team reviewing visit the product website for attendance sheet template should choose only the necessary evidence, explain how it will be used and keep a human correction path open.

Capped hourly — hourly billing with an agreed weekly or total limit. Removes most of the exposure monitoring was addressing.

For an independent reference relevant to “Glossary and Where to Start”, consult the European Data Protection Board guidelines; compare its principles with the proposed contract, collection, access model and real review process.

Manual time — hours added by hand rather than tracked. Frequently unprotected by platform guarantees, which catches people out.

Milestone — a defined piece of work at a fixed amount, paid on acceptance. The structure that makes monitoring unnecessary.

Proof of work — evidence that billed hours were worked. Usually screenshots; better served by artefacts and records.

Segregation — keeping other clients' and personal material off screen during tracked hours. A professional requirement, not a preference.

Work diary — the text entry attached to a tracked block. The only interpretable part of most monitoring records.

Where to start

A client is asking you to accept it: deciding whether to accept it, then pricing it in.

You are the client, deciding: what the client actually wants to know, then alternatives that answer the same question.

It is already running and nobody looks at it: reviewing screenshots, almost nobody does.

An invoice has been queried: when the client disputes the invoice.

You want to propose something else: the weekly note, then demonstrating progress without surveillance.

If you read only three

What a screenshot actually proves, because it bounds everything the arrangement can deliver.

What the client actually wants to know, because three of the four questions have better answers.

And the weekly note that replaces screenshots, because it is five minutes and it does what the monitoring was for.

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 in any field. 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 record, which is worth more than any disputed week.

A closing note

No platforms, tools or vendors are named.

No figures for how common this is, because those surveys come from the platforms.

And nothing here is legal advice: contract law and contractor status differ substantially by jurisdiction.

What the collection argues

A screenshot shows what was on a screen in one instant. It cannot show whether anything was achieved, whether it was the right work, or whether the person was thinking. Both parties treat it as stronger evidence than it is.

What the client actually wants to know is whether the work is progressing, and that is answered by three written lines a week, visible work, and a demonstration — all of which cost less and show more.

The cost of monitoring falls on both: the contractor pays in attention, unbillable hours and rate; the client pays in a narrower field of applicants, a premium, and a holding of somebody else's screen that nobody reads.

And nearly every dispute these arrangements are meant to prevent is caused by something nobody agreed in advance — how reading and calls are billed, what happens at overrun, what done means. One exchange of messages at the start does more than an engagement's worth of frames.