Lifecycle ยท Article 2.12
Status: Amendment in progress
You've created a change-order amendment and sent it to the client. The original proposal stays in its existing state; the amendment has its own lifecycle. Once the client signs the amendment, the proposal updates and moves on. This article is a brief pointer โ Section 7 covers amendments in depth.
This status is a transient marker. It's not really a separate state of the proposal โ it's a flag that says "an amendment is in flight on this proposal". The proposal's underlying status (In work, Paid, etc.) is preserved underneath. When the amendment resolves (signed, declined, expired, cancelled), the proposal returns to its underlying status with the amendment's effects applied.
Keep reading
Proposals & Invoices
Creating an amendment (the 4-step wizard)
The amendment wizard at `/proposals/{id}/amend` walks you through line items, reason, preview, and email โ in that order. Five minutes for a simple change, ten minutes for a complex one. The client doesn't see anything until you click Send on Step 4.
Proposals & Invoices
The 4 delta branches: ฮ+, ฮโ, ฮ=0, ฮ_REFUND
Every signed amendment falls into one of four branches based on (a) the sign of the cost change and (b) whether the proposal was already paid. Each branch fires a different document chain. This is the central conceptual map for the entire amendment system.