Client-side project management — sign-off, stakeholders and risk

DESIGN

The rules went into the contract, not into goodwill

Most contracting disputes aren't caused by the delivery. They're caused by nobody defining what counts as done, what counts as late, and how it ends.

Billing unit

Four-week stages, five in total Aligned to the actual working rhythm rather than calendar months, which split work in half at month end.

Sign-off

A dated checkpoint per stage: contractor submits progress, client confirms, stage closes Makes acceptance an event with a date on it, rather than a feeling.

Scope
control

Client may reprioritise freely; resulting slippage is not the contractor's delay Requirements changing is normal. Who carries the cost of the change is what needs writing down.

Exit

30 days' notice either way, with completed work settled An engagement needs a dignified way out, agreed at the start rather than improvised at the end.

THE TEST

Stage one went unpaid for three months

This is where project management is actually tested. In this order:

Stop the loss before raising the issue

Invoked the payment-linkage clause and halted work rather than continuing to invest in unpaid stages. The instinct is to go and talk about it first; stopping the bleeding is what creates room to negotiate.

Hold the price

Restarted at the original fee and absorbed the cost of the stall myself. What that bought was the moral position in the negotiation — every rule I then changed became difficult to argue against.

Change the structure, not the tone

The restart proposal moved billing from arrears to prepayment. Apologies and assurances don't change the next outcome. Terms do.

Reframe the process change as the client's interest

The client didn't read documents in advance, so every meeting restarted from zero and cost half a day. I proposed moving to video calls as a requirement of hitting their peak season — not as my preference.

Put everything in writing

Built a client-facing progress page where every deliverable carried a timestamp and a confirmation. Anything that could be a document wasn't a conversation. This matters most when both sides are busy and both are certain they remember it differently.

OUTCOME

The project survived

Payment

Stage one settled in fullPayment resumed after work stopped.

Structure

Stage two restarted on prepayment, on scheduleFunds arriving counted as acceptance of the revised terms.

Efficiency

Three design directions approved in a single callDecisions that previously took several rounds closed in one, after the meeting format changed.

Discipline

Directions confirmed at one stage are not reopened at the nextLater stages refine within the agreed line instead of relitigating it — which is what stops a project burning itself on the same decision.

TAKEAWAY

A problem left inside the feeling stays a problem

The hard part of project management isn't the schedule.
It's adjusting the structure, instead of absorbing the frustration,
when the other side doesn't move at your pace.

For those three months I was circling two questions: whether to chase it, and whether chasing it would damage the relationship. Nothing shipped in that time.

What eventually restarted the project wasn't finding the nerve to have the conversation. It was reclassifying "this client pays late" from something upsetting into a design problem for the next version of the contract. Once it was a clause, it had a solution.

That habit carries into everything I've built since: when a problem keeps recurring, change the structure that produces it instead of trying to be more careful.