> For the complete documentation index, see [llms.txt](https://docs.diracinc.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.diracinc.com/videos/tutorials/structure-and-organization/creating-phantoms.md). # Creating Phantoms {% embed url="" %} {% hint style="info" %} This video was recorded before BuildOS renamed these groupings. What the video calls a subassembly is now called a **phantom**. A **subassembly** is now a phantom which has been given its own work instruction. See [Phantoms and Subassemblies](https://dirac-inc.gitbook.io/dirac/how-to-be-successful-in-buildos/concepts/phantoms-and-subassemblies) for the full picture. {% endhint %} ### What this allows you to do Define logical build stages by grouping components that are assembled together before being installed into the main assembly. ### When to Use Phantoms Use phantoms when: * A group of parts is built together before being brought to the main assembly * You want instructions to show a sub-build first, then the installation of that sub-build Phantoms are typically defined in Model View early in the workflow to establish hierarchy before instruction steps and sequence are created. ### What Phantom Steps Do When a set of components is identified as a phantom: * BuildOS first shows the instructions for assembling that phantom * The completed phantom is then shown being installed into the main assembly ### Creating Phantoms #### Create a Phantom in Model View * Multi-select the components you want to group with Ctrl-click * Right-click and choose **Create Phantom** #### Working with Design Phantoms * Groupings defined in the original CAD file are automatically pulled into BuildOS as phantoms * You can **dissolve design phantoms** or reorganize them as needed, allowing you to create manufacturing-specific groupings directly inside BuildOS This allows you to adapt design structure to match manufacturing reality. #### Adding Components to an Existing Phantom * Drag and drop components into the phantom using the part tree * Changes are reflected immediately in the model and instructions ### Giving a Phantom Its Own Instruction If a phantom should be built, reviewed, and approved separately, convert it to a subassembly: * Right-click the phantom and choose **Convert to** -> **Subassembly** * Its steps move into their own instruction, which can be reassigned to another member of your team * To bring it back into the surrounding instruction, right-click it and choose **Unlock to Phantom** ### Key Tips * Create phantoms based on how parts are physically built, not how CAD is authored * Phantoms can be refined iteratively as instructions take shape * Clean phantom structure simplifies downstream instruction authoring * Convert a phantom to a subassembly when the sub-build needs its own owner, review, and approval