A customer's requested date is useful planning input, but it is not automatically a promise. Record requested, quoted, and confirmed dates in separate fields.
Make each date mean one thing
The requested date captures the customer's need. The quoted date reflects the shop's current estimate. The confirmed date is the commitment accepted after artwork, material, and workload questions are resolved. If any of these change, keep the earlier value in the order history.
This distinction prevents a note such as “needed Friday” from being copied into customer communication as an approved completion date. It also makes rush requests visible before they disrupt other work.
Review dependencies before confirming
Check personalization approval, blank availability, test needs, and collection or delivery arrangements before confirming. Do not use a general machine claim as a substitute for a job-specific schedule.
Explore more small-shop workflow notes in /updates/.
See the current AntBelt G1 project information on Kickstarter: