Lifecycle ยท Article 2.10
Status: Declined โ the client said no
The client clicked `Decline` on the public page, optionally wrote a reason. Status moves to `Declined`. No invoice is issued, no money changes hands, and the proposal is over.
Where this fits in the lifecycle
Draft
Only you can see this. Edit anything.
Sent
Email landed in the client's inbox.
Viewed
Client opened the link โ awaiting decision.
Signed
Legally binding. Audit trail captured.
Deposit paid
Money in escrow. You can start work.
In work
Project running. Final invoice ready when you're done.
Paid
Final invoice settled. Just one click left.
Completed
Closed. Archived. You did the thing.
A decline is the cleanest possible negative outcome โ no money has moved, no contract was signed, no legal entanglement. The most useful thing the client can do is leave a one-line reason so you understand why; about half the time, a decline is recoverable with a tweaked offer.
Step by step
The client clicks Decline.
Public page shows a "Decline this proposal" link below the Sign button. They're prompted for an optional reason.
Status flips to
Declined.Timeline event recorded with timestamp and reason text.
Email goes out to you.
Subject: "Proposal declined: [project title]". Body includes the client's reason (if provided) and a "Reach out" prompt (we don't auto-email the client further; that's your call).
(Optional) Reach out to the client.
The decline reason is on the proposal detail page; consider a short personal email exploring whether something specific can be adjusted.
(Optional) Duplicate and revise.
From Actions โ
Duplicate as draft. New PRO number assigned only when you re-send. Ideal for revised pricing or scope.
Red Declined badge. Banner on detail page shows the decline reason in italics. Action panel offers: Duplicate as draft, Archive, Send follow-up note.
Why this works this way
We don't auto-suggest a "revise and resend" workflow when a client declines, because most decline reasons aren't fixable by tweaking the proposal โ they're about budget, timing, scope, or chemistry. We do show the decline reason prominently on the proposal detail page so you have it in front of you when deciding next steps. If the reason is fixable (e.g., "price too high" โ revise pricing) the duplicate-as-draft workflow is one click.
If the decline happens after deposit was paid (rare โ usually the client signs before paying), the deposit is held and the refund flow can be triggered manually. This is mostly a theoretical case; in practice, declines happen pre-signing.
Troubleshooting
Keep reading
Lifecycle
Status: Sent โ the proposal is in your client's inbox
You've clicked `Send`. The PDF is rendered, the email is on its way, the proposal number is assigned, and the audit trail starts here. Now you wait โ until the client opens it (`Viewed`) or signs (`Signed`).
Refunds & Notifications
When refunds happen: the ฮ_REFUND amendment branches
A refund in Clozo is always tied to a ฮ_REFUND amendment branch โ partial (revised total smaller than deposit paid) or full (revised total at zero). The amendment is the legal trigger; the refund is the cash consequence.