The current tree planner lists removal, pruning and stump grinding as possible primary jobs. A later multi-item brief might allow tree removal with separate decisions on stump work and cart-away. A boolean defaulted to false would erase the difference between a deliberate exclusion and a service nobody discussed.
Use an explicit lifecycle for each choice
Represent the three meaningful decisions and keep unasked separate. Then downstream readers can distinguish a service the homeowner wants included from an item that requires a conversation. A missing value in a historical draft should stay missing until someone makes a choice or the interface asks again.
type Decision = 'include' | 'exclude' | 'discuss'; type AddOns = { stump?: Decision; debris?: Decision }; const updateStump = (addOns: AddOns, stump: Decision): AddOns => ({ ...addOns, stump }); Test migration and summary wording together
In a future implementation, load a saved draft with no stump field and confirm it reads as unanswered. Change it to discuss, save and reload. Confirm the summary prints the exact intended meaning and that no estimation code treats discuss as a priced exclusion. Repeat with explicit exclude and verify the two values remain distinct across serialisation.
The existing flow has one project choice, count, access and timing, with no multi-item editor. The proposed type is for a richer scope if one is introduced. Its role is capturing user intent and outstanding choices. Approval and the tree assessment are decisions handled outside this interface.
If the public form later converts an unanswered item to a suggestion, keep it out of saved decisions. Test that reaching a suggested screen and abandoning it leaves the underlying field absent.
Perth Quotes tree work planner is the live preview. Online enquiries are closed.


