Work Lifecycle & Closeout System

What this guide covers

• Status stages from inquiry through closeout
• Qualifying, proposing, approval, and scheduling gates
• Active work, waiting states, and revisions
• Delivery, quality review, and customer acceptance
• Invoicing, payment or refund, and formal closeout
• Evidence, guarantees, follow-ups, and archive
• Why finished work is not the same as a closed engagement

The full lifecycle in order

A lifecycle is a shared map of where work stands, no matter what you call the unit of work — a client engagement, an order, a booking, a service request, a project, a campaign, a repair, a production run, or a subscription setup. Without it, every person on your team defines “almost done” differently, and customers hear conflicting answers. The stages below fit most service, product, and project-based businesses; adapt the labels but keep the sequence logic.

1. Inquiry — someone expressed interest; contact info and source captured.
2. Qualified — you confirmed fit: scope, budget band, timeline. Poor fits exit politely.
3. Proposed or ordered — a written proposal or quote is issued, or an order placed, with clear terms.
4. Approved — the customer signed, replied “approved,” clicked accept, or paid a deposit; a verbal agreement alone doesn’t count.
5. Scheduled or queued — a start date and slot are assigned; the customer knows what they must provide.
6. Active or processing — work is underway: on site, in the studio, in the shop, or in the pipeline.
7. Waiting — paused for a decision, approval, or dependency. Note why and who owns the next action.
8. Revised — scope or price changed after approval; documented and, where money or deadlines shift, approved in writing.
9. Delivered or completed — the primary deliverable is in the customer’s hands, even if small items remain.
10. Accepted — the customer confirms the work meets the agreement, in writing or an equivalent action.
11. Invoiced — the final or remaining invoice is issued, referencing the agreement and any revisions.
12. Paid or refunded — the balance is collected, or a refund or credit issued per your terms.
13. Closed — accepted, paid or refunded, documented, and any guarantee clock started.
14. Archived — records filed, team released, ready for future reference.

Skipping stages is how disputes start. Scheduling before approval, invoicing before acceptance, or archiving before payment each creates a hole someone falls into later.

Inquiry through scheduled: gates that protect margin

Inquiries are cheap; bad engagements are expensive. Qualification filters out work you cannot perform legally, safely, or profitably — a consulting firm declining a project outside its expertise, a boutique turning down a rush order it cannot staff. Minimum questions: what is the goal, the timing, and the budget band? “I don’t know” on budget isn’t disqualifying, but it means the proposal needs clear options, not open-ended time-and-materials.

Proposals and orders should reference specifics and assumptions, not vague promises. “Redesign the checkout flow — excludes payment-gateway integration” or “Twelve units, standard finish, ships in three weeks” is auditable. Vague proposals become scope-change fights later.

Approval means a signature, an emailed “approved as written,” a clicked acceptance, or a deposit — not a verbal “sounds good” you cannot produce later. Tie approval to a deposit policy: no slot held without commitment when your terms require it.

Scheduled or queued means the work appears on a calendar or fulfillment queue with an owner, a duration, and a point of contact for day-of issues. Send a confirmation with the date and what the customer must provide. One missed confirmation causes delays that look like your fault.

Active or processing, waiting, and revisions

Active engagements get regular notes: what was done, what blocked progress, anything discovered that changes the picture. Waiting is a legitimate status, not a failure — but undocumented waiting looks like neglect. Log “Waiting — customer choosing finish option, follow up Thursday” with an owner for the follow-up.

Revisions exist because real engagements deviate from the original plan: a designer gets a request for a different layout, a retailer processes a purchase-order change, a subscription customer upgrades mid-cycle, or — in construction, as one clearly specialized example — a client wants a wall moved after the estimate was signed. Any change affecting price, timeline, or core scope gets documented before more work proceeds. A verbal “sure, go ahead” works until it doesn’t, usually at final invoice.

Minor courtesy adjustments — swapping a color the customer already paid for — may not need a formal revision if your terms define a threshold. Everything else goes in writing. Your team should pause and confirm before doing work outside the approved scope.

Delivery, quality review, and acceptance

Delivered or completed means the primary deliverable is done, even if small items remain — a website launched with a minor copy edit pending, an order shipped with one backordered accessory. Define what “delivered” means in your terms so customers don’t expect perfection before final touches wrap up.

A quality review before the customer sees the work catches problems early — an internal proofread, a QA pass, a final walkthrough. In some specialized fields this step has a formal name and legal weight, such as a construction final inspection. Know whether your industry treats this as informal quality control or a documented requirement, and note deficiencies with an owner and a target fix date either way.

Acceptance is written confirmation that the delivered work meets the agreement — a signed form, an email confirmation, or an approved milestone. For some engagements it triggers a guarantee period and final payment. Do not skip it because the customer “seemed happy.” Happiness without confirmation is not a closeout record.

Invoiced, paid or refunded, and closed

Invoice timing belongs in your terms: due on delivery, on acceptance, or net terms for business clients. The invoice references the original agreement and any approved revisions and shows prior payments applied. See Invoice, Payment & Collections for billing detail.

Payment collected triggers a receipt — same day when possible. A refund or credit follows the same discipline: documented reason, amount, and method. Closed is administrative completion: confirm zero open balance or a documented payment plan, file final records, store the acceptance confirmation, and record any guarantee start date.

Closed also means internal release: the engagement comes off the active board, team time is closed out, and profitability is noted if you track it. An engagement still sitting “active” months after everyone stopped working on it pollutes scheduling and distorts revenue reporting.

Evidence, guarantees, and follow-ups

Evidence protects both sides when memory gets fuzzy. What counts varies by business: dated photos of before-and-after conditions, a signed acceptance form, a QA checklist, a screenshot of published content, a completed service ticket. Physical-work fields — construction, repair, installation — often rely on site photos as a specialized example; digital or service work more often uses logs, timestamps, and confirmations. Store whichever applies in the engagement folder per Records, Files & Document Control.

Guarantee terms belong in your agreement, whatever you call them: warranty, satisfaction guarantee, return window, or service-level credit. State duration, coverage, exclusions, and how to report issues. Record the start date at closeout — usually acceptance or final payment.

Follow-ups are post-close contact for defects or goodwill fixes — a warranty callback on a repair job, a reopened support ticket, a repeat visit for a personal-service customer. Log these separately from the original engagement so you know true cost. A spike tied to one team member or supplier is a training or sourcing signal, not bad luck.

Lessons learned need one paragraph, not a ceremony: what assumption was wrong, what step failed, what communication prevented or caused delay. Future you reads this when a similar inquiry appears.

Done ≠ closed

The person doing the work says “done” when they stop touching it. Finance says “done” when payment clears. Operations says “done” when the record is complete and archived. Those are different moments.

Complete but unpaid is not closed — it is receivables risk. Paid but missing acceptance is not closed — it is dispute risk. Accepted but missing evidence is not closed — it is guarantee risk. Define closed as ALL of: accepted, paid or refunded, receipt sent, records complete, guarantee clock started, archived.

Weekly review: list engagements marked active or waiting longer than expected, and anything marked done by the team but not closed in the system. That single habit catches most lifecycle leaks.

Minimum viable status system

You do not need enterprise software on day one. You need one list — whiteboard, spreadsheet, or app — where every open engagement shows: customer, reference ID, current status, next action, owner, and date. Update status when it changes, not at week’s end from memory.

Minimum fields: reference ID, customer, what was ordered or engaged, status, amount quoted, invoiced, and paid, target date, notes. Filter or color-code Waiting items so they don’t disappear. One person owns status accuracy — usually the owner, not everyone editing randomly.

Common mistakes

• Starting work on verbal approval without any deposit or commitment
• No Waiting status — paused work looks abandoned or still active
• Team performs scope creep without anyone documenting a revision
• Final invoice sent before customer sign-off; disputes become chargebacks
• Marking something complete in your head but leaving it open on the board
• No before/after evidence; guarantee arguments become word against word
• Skipping lessons learned; the same estimating error repeats every quarter
• Treating payment or refund as optional after physical completion

When professional guidance may be needed

Consult a contract attorney when acceptance, retainage, or payment rights are disputed on a large engagement — construction, creative services, and consulting each have their own norms worth checking. Use a qualified contract review when guarantee or revision language exposes you to open-ended liability. Mediation or legal help early beats arguing lifecycle facts without documentation.

Related Business & Systems resources

• Invoice, Payment & Collections
• Records, Files & Document Control
• Cashflow Calendar for Operators
• Profit Reserve System
• Delaware LLC Literacy
• Business & Systems hub