What a Working Arrangement Looks Like
The end state, assembled from everything here, as a description to measure yours against.
Not a model. A description of an engagement between a client and a contractor who have worked together a year, where neither thinks about monitoring.
The practical lesson in “What a Working Arrangement Looks Like” is to connect each signal to a named decision. Organisations exploring the provider's overview for remote workforce management software can add time and project context, but outcomes and direct conversation are still needed to explain whether the work moved forward.
The structure
Fixed price with milestones for work that can be specified.
For an independent reference relevant to “What a Working Arrangement Looks Like”, consult the OECD productivity resources; compare its principles with the proposed contract, collection, access model and real review process.
Capped hourly for work that cannot, with a weekly limit agreed.
Staged payment: a deposit or escrow, then payment on each milestone.
No screenshots.
What the client sees
The work accumulating in a shared repository or workspace, with its own history.
A three-line note every Friday: what moved, what is stuck, what is next.
A fifteen-minute demonstration every fortnight.
And an invoice that contains nothing surprising, because the overrun warning arrived three weeks earlier.
What the contractor keeps
A folder per client: the agreement, a time record, correspondence about anything agreed, a note of what was delivered when.
One line per tracked block, written at the time.
Copies of anything they are entitled to keep, held outside the client's systems.
Twenty minutes across the engagement.
What was agreed at the start
What is tracked, if anything, and that it runs only during tracked time.
How reading, calls, planning and blocked time are billed.
What happens at seventy-five per cent of the estimate.
Who sees what, and that it is deleted at the end.
Confirmed in a message, which took one exchange.
How problems arrive
Early, in writing, with a proposal rather than only a problem.
Scope changes confirmed before being worked on.
Blockers flagged the day they appear.
And the quiet weeks announced in advance, with what was ruled out reported as the output it is.
What happened to the monitoring
It applied to the first engagement, as agreed, and was reviewed at sixty days.
The client removed it because the weekly note told them more.
Nobody had to have an awkward conversation, because the review point was in the original terms.
The test
Could either party reconstruct what happened in month three?
Does the client know what is stuck, today?
Has anybody been surprised by an invoice?
An arrangement answering those three has everything monitoring was meant to provide.
What it costs
The contractor: five minutes a week and twenty minutes of filing.
The client: reading three lines and specifying the work.
Less than a monitored engagement costs either of them, which is the whole argument of this collection in one line.
More in this section