Skip to main content

Overview

Assembly work instructions, first-article inspection sheets, and shop travelers all get built the same tedious way: step through the assembly or drawing by hand, capture a screenshot, write the callout, repeat. The information is already in the model — it just needs to be pulled out and formatted for a different audience. Nexus generates these documents directly from your CAD assembly or drawing: stepping through the build sequence, capturing views at each stage, and writing instructions at the level of detail the audience needs — shop floor, field service, or QA.

What Nexus can help with

  • Assembly work instructions — Step-by-step build documents with an exploded or staged view and a parts callout at each step.
  • Inspection and first-article checklists — A dimension-by-dimension checklist pulled from the drawing’s tolerances and GD&T, with space for measured values.
  • Shop travelers and cut sheets — Quick-reference documents for a machining or fabrication operation, listing setup, tooling, and key dimensions.
  • Field service and maintenance docs — Disassembly/reassembly instructions for service procedures, built from the same assembly data.

Example prompts

Tips for work instruction prompts

  • Name the audience — a shop-floor operator, a field technician, and an engineer need different levels of detail and different assumed vocabulary. State who’s reading it.
  • Specify the format — PDF, Word, or a specific internal template. If you have a template, attach it the same way you would a drawing template.
  • Tell Nexus what’s pre-assembled — if some sub-assemblies ship already built, say so, or the instructions will include steps that don’t apply to your process.
  • Ask for consumables and safety notes explicitly — torque values, adhesives, PPE, and calibration notes aren’t always in the model; state which ones matter and where.
  • Review against the physical process once — a generated instruction reflects the CAD build order, which isn’t always the same as the physical assembly order. Confirm the sequence matches your actual process before releasing it.