.png)
The mounting hole on bracket 104-A moves 2 mm. Engineering releases an ECO.
What happens next?
STEP 1: Find which documents are affected
SOLIDWORKS Composer
Search your folders for every file you think uses bracket 104-A.
Quarter20
Documents are organized by CAD, so the impact is clear right away. You can also search for part 104-A to see every doc that references it.
STEP 2: Start updating the CAD views
SOLIDWORKS Composer
Open each Composer file. Push the update from CAD. Check that every view, callout and label landed where it should. Repeat for every file.
Quarter20
Push the change from the SOLIDWORKS plug-in. Views in every connected document update automatically.
STEP 3: Update the images in the document
SOLIDWORKS Composer
Re-export every affected view, including views in later assembly stages that also show the mounting hole and bracket.
Quarter20
Images are already updated on every page, across every operation step.
STEP 4: Update the text in the document
SOLIDWORKS Composer
Ctrl-F “104-A” in your documents (Word, PowerPoint, etc.) to find every reference to the bracket. Make sure the data is still accurate: part name, number, rev, torque values and more.
Quarter20
Quarter20 flags the affected pages. Accept, tweak or reject each suggested edit.
STEP 5: Log the new revision
SOLIDWORKS Composer
Rename the file and add the version to every page. Use your company’s convention, or make one up.
Quarter20
Every change is versioned automatically. See what changed, when and why.
STEP 6: Resend to downstream teams
SOLIDWORKS Composer
Export a new PDF and email it. Make sure everyone knows the old version can no longer be used.
Quarter20
The link you already shared now shows the updated document.
Summary
For years, Composer has been a go-to tool for turning CAD into illustrated manuals, exploded views and technical illustrations. When one person owns the document and the design rarely changes, it does the job well.
But in fast-moving engineering environments, every change ripples across the organization, and each one means hours of manual rework for every team that touches the documents. Composer wasn’t built for that kind of cross-functional, always-changing workflow. Quarter20 was.
In this example, one hole moved. How many ECOs did your team release last quarter? Multiply those six steps by every one. With Quarter20, each change is a review, not a redo.
.png)
