A typical workflow has been based on PCB design tools as they appeared first in the product development. So it was natural to use the tool for all documentation.
During last decade or two, the environment has changed radically. The computers are used all over the design/manufacturing chain. The workflow for documentation is still the same.
So it is time to think over. A better approach is to split the documentation to primary and secondary documentation. The primary documentation covers the traditional files needed for pcb fabrication, the secondary is for assembly and test. Splitting the documentation means that a change in the assembly documentation does not require a change in the original pcb files – less revisions. Documentation is easier to manage.
The BluePrint is the tool for the secondary documentation. It can replace a physical product folder by building a digital equivalent to the drawings. Most likely the pcb designer would create the initial BluePrint document, but later on it can be maintained by other people in the assembly and test.
But this is not all. BluePrint has been developed natively for pcb documentation. It means that the document set is based on (user definable) template set, the entire pcb database is imported to the tool once and all the pages are filled automatically, minimizing the interactive work. All can be done inside BluePrint, no copy/paste, no multiple tools.
When a new revision of the pcb is released, just import the CAD data again. All documentation is updated automatically, minimizing the rework.
So if you have been using multiple tools for documentation (Word, Excel, Designer, AutoCad etc.), take a look at BluePrint.
BluePrint is independent of the CAD system, the data can be imported in ODB++ or native PADS Ascii.