I drafted a 20-point checklist for editing user manuals in Word Track Changes and Oxygen XML 26.1, focusing on imperative steps, consistent UI strings, and callout numbering. I can upload a DOCX and a DITA-friendly version; before I do, what must-have checks are we missing for hardware install guides?
One thing I always check is a step-to-BOM/kit crosswalk: every ‘M4x10 screw’, tool, and connector called out ships, matches the label in photos/diagrams, and has a unique ID the warehouse recognizes. Small caveat: on pilot runs the fastener finish/part code often changes, so I ask for a production-sample photo before freezing callouts and add that as a pre-release gate.
I add a torque/unit sanity check: any step that says “tighten” or “torque” includes a numeric value and units (N·m or in‑lb) that match the spec sheet and the figure label. In Oxygen XML 26.1 I use a simple Schematron to flag missing values and then confirm the numbers survive into the Word Track Changes version; want me to share the rule? If torque doesn’t apply, the step explicitly says “hand-tighten” to avoid ambiguity.