Approval and Billing Readiness Checklist for Solo Operators

Use this checklist before treating a project as approved, before issuing an invoice, before marking payment as tracked, or before beginning closeout. It is a stage-transition gate, not a workflow design guide.

This page is not legal, accounting, or contract advice. Use it as a practical operating checkpoint to reduce ambiguous stage transitions.

If a readiness item is missing, fix the gap before proceeding. Moving to the next stage on an incomplete signal is where most billing and closeout problems begin.

Start upstream first if…

• the whole delivery or approval process still feels unclear — start with Milestone Delivery Workflow for Solo Service Businesses before using this checklist,
• you are not yet sure what counts as approval — read FAQ: What Counts as Client Approval? first,
• invoice timing or payment-status location is still unclear — read Invoice and Payment Workflow Setup before checking billing readiness here,
• the whole client lifecycle order is still fuzzy — start with Freelance Client Workflow System: Inquiry to Final Payment before narrowing to a stage transition.

This checklist is most useful when the process rules are already set and you want to confirm that a specific project is ready to move forward.

Readiness checklist

Check every item that is true before moving to the next stage. Missing items are the gap to fix first.

Delivery

• All work in scope for this milestone or stage has been completed.
• Deliverables have been sent through the agreed delivery channel — not through a side message, comment, or informal drop.
• The acceptance criteria or deliverable definition for this milestone is documented and was shared with the client before delivery.

Approval

• The approval owner is named — one person whose acceptance formally closes this milestone.
• The approval channel is confirmed — the client knows where to send confirmation.
• A decision deadline or review window was stated when the deliverable was sent.
• Any “looks good” or informal positive comment has been confirmed as formal acceptance, not assumed to be approval.
• Change requests have been separated from approval — any new scope has been documented and handled before the approval gate closes.

Invoicing

• Explicit approval has been received — billing is not triggered by delivery alone or by informal positive comments.
• The invoice amount, billing period, and payment terms match the agreed proposal or contract.
• The invoice is ready to send to the correct contact and billing address.

Payment status

• Payment status for this invoice has been entered into the correct system of record — not tracked only inside the invoicing tool, or only in memory.
• A follow-up trigger is scheduled if payment has not arrived by the due date.

Closeout

• All milestones are complete and all invoices are paid or formally resolved.
• The client has been informed that the project is closing — closeout is not assumed from the final delivery alone.
• Any final handoff materials, account accesses, or documentation have been sent or confirmed complete.

Approval readiness

A project milestone is ready for approval when:

• the deliverable has been sent through the agreed channel,
• the acceptance criteria were shared before delivery,
• the approval owner is named and has been given a clear decision window,
• no unresolved change requests are open that would alter what is being approved.

An informal “looks good” or a positive reply is not approval unless it explicitly closes the milestone. If the client’s intent is unclear, ask a direct closing question: “Does this confirm your acceptance of [milestone name]?” Do not issue an invoice until that confirmation is in hand.

For more on what counts as approval and how to handle ambiguous signals, see FAQ: What Counts as Client Approval?.

Billing readiness

A project is ready to invoice when:

• explicit milestone approval has been received — not just delivery sent,
• the invoice amount, contact, and terms are confirmed and correct,
• the invoice will go to the right billing contact, not just the project contact.

Billing readiness does not depend on how long the delivery has been sitting with the client, on a positive-sounding email, or on a soft agreement that “we’re all good.” The trigger is explicit approval.

Once invoiced, payment status must be entered into one system of record immediately — not tracked in the inbox, the invoicing tool alone, or a separate spreadsheet. If it is unclear where payment status should live, see Best Home for Billing Status: Invoicing Tool vs System of Record.

For the full billing process and follow-up cadence, see Invoice and Payment Workflow Setup.

Closeout readiness

A project is ready to close when:

• all milestones are complete and confirmed approved,
• all invoices are paid, waived, or formally resolved — no open billing items remain,
• the client has been explicitly informed that the project is closing,
• any handoff materials, credentials, or documentation are sent and confirmed received.

Closeout does not happen because the final delivery went out. It happens when all of the above conditions are true and acknowledged. If the client has not responded to a closeout message, do not assume the project is done — see FAQ: Client Does Not Respond to Project Closeout.

For the full offboarding and testimonial process, see Client Offboarding Workflow for Freelancers and Solo Service Businesses.

If one item is missing

Do not skip a readiness condition or move forward assuming it will resolve itself. Address the gap first.

If the problem is broader than one missing readiness condition, return to Freelance Client Workflow System: Inquiry to Final Payment before treating this checklist as the starting point.

Fix the missing condition first

A stage transition that happens before all readiness conditions are met tends to create the problems that appear later — billing disputes, stalled closeout, unclear payment status, and repeated approval questions on work already delivered.

Fix the weakest item on this checklist before moving the project forward. The upstream pages listed above are the fastest route to resolving each specific gap.