Before the work: qualify, propose, and agree
Confirm the client, decision-maker, problem, budget range, desired timing, and constraints before preparing a detailed offer. A clear no is cheaper than an engagement built on incompatible expectations.
Send a bounded proposal, preserve acceptance, and complete the appropriate agreement before delivery begins. Collect only the identity, billing, and project information necessary for the work.
- Client identity, authority, billing contact, and decision path are known
- Proposal states scope, exclusions, dependencies, price, currency, and expiry
- Agreement is signed and any deposit or start condition is satisfied
During the work: control scope and decisions
Create the project from the accepted commercial record. Give milestones observable completion conditions and record client dependencies beside the date they affect.
Capture material decisions and change requests chronologically. Use AI to draft or summarise only after checking the source record, and keep a human responsible for anything sent to the client.
- Milestones, dates, owners, dependencies, and review windows are visible
- Scope changes receive explicit approval and commercial treatment
- AI-generated text remains a draft until a person verifies and sends it
After delivery: accept, invoice, follow up, and hand over
Attach concise delivery evidence, request acceptance through the agreed method, and create the invoice from the correct milestone or fee. Verify its currency, tax treatment, due date, and instructions before sending.
Run reminders against the live balance, record verified payment, then complete the access and documentation handover. Export the records your accountant needs and apply an appropriate retention schedule.
- Delivery, review, acceptance, invoice, reminder, and payment events are connected
- Reminder automation stops when payment or cancellation makes it inappropriate
- Handover and accountant exports are complete before the project is archived
Decision check
Ask these questions before you commit
- 01Does every stage end with a clear decision, record, or next owner?
- 02Can a failed payment or delayed review resume safely without duplicate actions?
- 03Would the full engagement still make sense six months later?
- 04Can I reuse this workflow without forcing every client into the same project shape?
Put the guide into practice
Related free resources
Continue reading
From advice to a connected record
Run the workflow in FreelanceOS
Start on the Free plan and keep password sign-in available alongside Google.