- Closed orders that went wrong
- The handover sheet is shaped by where past orders broke: a missed promise, a changed drawing, a late detail. Bring the ones your teams remember, even as rough notes. Without them, the sheet covers fields that look sensible but miss your real failures.
- A named acceptor in operations
- Acceptance means someone in operations can say yes or send the order back. Name that person or a deputy. Where nobody holds that authority, the acceptance step becomes a formality and the wrong-promise check never runs.
- Your current order or job sheet
- The new sheet is built around what operations already uses, so teams do not keep two records. A spreadsheet, paper form or CRM screen is acceptable. Without it, GullySales designs from nothing and adoption by the plant suffers.
- A list of what sales may promise
- The wrong-promise review needs a clear line between what a salesperson can commit to and what needs operations first. A short written list from your operations head is acceptable. Without it, every promise is argued case by case.
- The point at which an order is final
- Changes after handover need a cut-off your teams accept, such as acceptance by operations. Agree it before the work starts. If it stays vague, the change rule is ignored and buyers keep amending orders in conversation.