Work orders

The shape of one

A work order names what is being done, for whom, by when, by whom, and what state it is in. It carries the messages exchanged about it and the files produced. That is deliberately less structure than a project — the client is looking at it, and a client does not want a work breakdown.

Awaiting client

The most useful state in the module. Work blocked on the client is invisible in most systems, which means it silently becomes your delay in the client's memory. Making it an explicit state, visible to both sides, changes that conversation entirely — and the list of work orders awaiting client input is the single most valuable report here.

• Use it whenever you genuinely cannot proceed, and be specific about what you need.
• Use a form when what you need is structured — it collects the answer rather than starting a thread.
• Review the list weekly. A work order awaiting client for a month is a commercial conversation, not a delivery one.

What the client sees

The client sees their own work orders with the state, the due date, the messages and the delivered files. They do not see your internal notes, your costs, or anybody else's work.

What this does not do

Questions

Related