How to Document Special-Order Requirements Clearly Before Final Approval
Special-order conditions create problems most often when everyone involved thinks the requirement has already been understood, but it has not actually been written clearly enough for the next person reviewing the order.
Special-order planning should not stop at verbal clarity. The requirement should be written clearly enough for quoting, ordering, approval, and installation.
Common Special-Order Conditions
In this product category, special-order conditions can include:
- 220V
- Hydronic Jeeves
- Left-electrical special-order options
- Special-order finishes on eligible collections
- Specific configuration conditions that should not be treated as standard assumptions
Before final approval, the requirement should be stated in a way that is specific enough to survive review. That means documenting the exact collection, the exact special-order condition, and whether the condition is standard for that collection or requires exception handling.
What Should Be Written Explicitly
Voltage
If 220V is required, that should be stated directly rather than implied through a broader electrical note.
Hydronic
If the selection is hydronic Jeeves, that should be written as a defined system requirement, not as a vague variation request.
Left-Side Electrical
If the requirement is left-side or left-electrical, the documentation should clearly identify whether the order uses:
- A true left-electrical model
- A special-order left-electrical setup
- A rotation option on an eligible model
Finish
If the finish is special order, the collection eligibility should be confirmed and the finish should be written without ambiguity.
Product And Customer Context
This is about more than administrative neatness.
Clear documentation helps prevent:
- Wrong-order assumptions
- Drawing mismatches
- Field confusion
- Approval language that sounds clear but is not specific enough
Questions To Resolve Before Final Approval
Has the exact special-order condition been named clearly
Does the selected collection actually support that condition
Do the drawing, spec notes, and order language all point to the same requirement
Is anything still being left to assumption
Common Mistakes
Referring to a Requirement Indirectly
That often creates false confidence.
Treating a Special-Order Condition as Though It Were a Standard Catalog Assumption
That usually causes drift later.
Leaving the Requirement Only in Email or Conversation
If it matters, it should be in the actual approval-facing documentation.
The safest approach is simple: if the project depends on a special-order condition, that condition should be written explicitly enough that it remains clear through review, specification, quoting, ordering, and installation without anyone needing to infer what was meant.