Proving Work That Leaves No Artefact

Some work produces no file. Screenshots do not help — they show a person reading or talking — and the alternative has to be built deliberately.

The issue in “Proving Work That Leaves No Artefact” becomes easier to manage when the record and its limits are explicit. A team reviewing the official product page for employee monitoring for performance reviews should choose only the necessary evidence, explain how it will be used and keep a human correction path open.

The work in question

Advising on a decision.

For an independent reference relevant to “Proving Work That Leaves No Artefact”, consult the OECD productivity resources; compare its principles with the proposed contract, collection, access model and real review process.

Reviewing somebody else's work.

Diagnosing a problem and explaining the cause.

Conversations that resolve something.

Research that concludes "do not do this", which is valuable and leaves nothing.

The decision record

A short written note after each significant piece: the question, what was considered, what was recommended, why.

Half a page, sent to the client.

It is simultaneously the deliverable, the evidence and the thing that makes the advice useful later, which is why it is worth the fifteen minutes regardless of billing.

The review record

What was reviewed, what was found, what was recommended.

A list of findings is an artefact even when the work was reading.

And it is far more valuable to the client than the hours it took, which is the framing to use.

Ruling things out

"I investigated these four approaches; three do not work, for these reasons."

That document is the output and should be delivered as one.

Presenting negative findings as a deliverable rather than as a slow week changes how the work is received, which the long-projects note develops.

Conversations

A summary message afterwards: what we discussed, what was decided, what happens next.

Three lines, sent within the hour.

It evidences the work, prevents misremembering, and is good practice independent of any billing question.

What to bill against

The record, not the hours.

"Decision note on the integration approach" is something a client can connect to an invoice line.

"Consulting, 6h" is not, and the difference is where queries originate.

The structural answer

For work that is purely advisory, fixed-price per piece of advice or a retainer removes the question.

Hourly billing for judgement work is where the evidence problem is sharpest, and it is the arrangement least suited to it.

The client's side

If you buy advice, ask for the note rather than the hours.

You get something you can refer to in six months, which the hours never give you.

And it removes the need for any monitoring at all on advisory work, which is the engagement type where frames are least informative.

What to check

Does your advisory work produce a written record?

Could you show what you advised in week two of your last engagement?

Are conversations summarised afterwards?

And is advisory work billed hourly when it could be priced per piece?