Long Projects and Slow Weeks
Work that produces nothing visible for a stretch is where monitored arrangements become most uncomfortable for both sides.
Some weeks produce no deliverable. Under hourly monitored billing those weeks look identical to weeks of nothing, and both parties feel it.
The practical lesson in “Long Projects and Slow Weeks” is to connect each signal to a named decision. Organisations exploring the software website for task switching cost can add time and project context, but outcomes and direct conversation are still needed to explain whether the work moved forward.
Where this arises
Research and investigation before anything can be built.
For an independent reference relevant to “Long Projects and Slow Weeks”, consult the European Data Protection Board guidelines; compare its principles with the proposed contract, collection, access model and real review process.
A difficult fault whose cause takes days to find.
Design exploration where several directions are tried and discarded.
Dependencies: waiting for access, information, a decision.
All legitimate, all invisible in both frames and deliverables.
What the client experiences
Hours accumulating with nothing to see.
Which produces exactly the anxiety the monitoring was meant to settle, and the frames make it worse rather than better — a week of screenshots of documentation and a blank editor reads as nothing happening.
What actually helps
Say in advance that the week will look like this and why.
Report what was ruled out, which is real progress and is invisible otherwise.
Show the intermediate artefact: notes, a comparison, a decision record.
And give a date for the next visible thing.
Four sentences, sent before the quiet week rather than after it.
Ruling things out is progress
"I have eliminated three of the five possible causes" is a week's work described accurately.
It sounds like failure and is the opposite.
Saying it plainly, repeatedly, is how a client learns to read investigative work, and most have never had it explained.
The waiting problem
Time blocked on a dependency is not billable in most arrangements and is still consumed.
Flag it immediately, name what is needed and from whom.
A client who learns on Friday that you were blocked since Monday has lost a week that they caused, which is a conversation worth having early.
Billing a quiet week
Honestly, with the diary entries that explain it.
Not padded, and not absorbed either — absorbing it teaches the client that investigation is free.
And a brief covering note with the invoice, which converts a surprising line into an expected one.
The structural answer
Fixed price for the investigation phase, with a defined output: a report, a recommendation, a decision.
Removes the question entirely and prices the uncertainty where it belongs.
For exploratory work this is frequently the better arrangement for both, and it is rarely proposed.
What to check
Does your client know when a quiet week is coming?
Do you report what was ruled out?
Is blocked time flagged the day it starts?
And could the exploratory phase be priced separately?