






What actually goes in a Manufacturing Record Book
Whatever your customer’s book specification says goes in it. That’s the real answer, and it’s worth saying first because the…
Read NowManufacturing record books, dispatch dossiers, quality dossiers, technical dossiers and mud books, compiled from the documents already approved on your project. Bookmarked, hyperlinked, paginated and structured to your customer’s specification, generated rather than assembled.
Set your rules, generate polished dossiers automatically, and re-sync without starting over.
Payment
Final payment hinges on book approval, but project wrap-up is when your team has already moved on to the next order. DocBoss automatically compiles approved files into complete dossiers so your money isn’t left waiting on paperwork.
Assembly
Skip the manual scavenger hunt of digging through scattered folders, finding the right version, formatting hyperlinks, and hand-building tables of contents.
Every current file, tag, and cover page compiles automatically into the exact sequence demanded by the specification.
Compliance
Pass customer review on the first try. Table of contents depth, numbering, section structure, and file naming are fully configurable to match your customer’s exact spec. Set up the layout once in your project template to deliver perfectly formatted books every time.
Change
Structural customer requests, like changing the entire layout or adding tags to every bookmark, should not mean starting over from scratch. Use DocBoss to quickly update your settings and regenerate a brand-new version of the book.
Reuse
A book structure can be saved and reused rather than rebuilt from the specification each time. Expect to adjust it per job; expect not to start from nothing.
See how easy it is to generate multi-volume, tag-split dossiers directly from your live project files, without a single hour spent on manual PDF stitching.
Set your cover sheets, section layouts, and TOC specs once. DocBoss handles the auto-filing, split-book logic, and final PDF generation.
Approve layout and TOCs at project start. Generate the full contents with real documents, numbers, and tags before a single file is produced. Settle structure arguments in week one instead of handover week.
Every document links to equipment, so DocBoss pulls files automatically instead of manual file-by-file sorting. On forty-book orders, this eliminates closeout errors like drawings filed to the wrong vessel.
Apply cover pages to all files, returned files, or none. Book-level covers stay part of the structure so running footers and pagination stay accurate, avoiding the broken page numbers of merged files.
Save book layouts against customer document code lists for future orders. Set business-wide defaults with instance presets, tweaking job-specific details instead of rebuilding from scratch.
Generate books per tag, skid, or shipment from one defined structure. Documents route automatically. The split is a simple setting, and changes only require regenerating the affected book.
Set contents levels, numbering depth, starting points, and PDF bookmark trees. Entry text follows your defined patterns, with page numbers appearing on contents and estimated before files exist.
Include unapplied or merged document codes on the contents list with the exact suffix your customer expects. The table of contents answers strict contract specifications without looking incomplete.
Attach the book to a document code to manage its revisions, queues, and transmittals like any other file. Books hold out of the queue until documents are complete, with early release options available.
Get answers to questions about DocBoss’s Final Databooks
No. Regenerate and the book rebuilds against the current approved documents, with contents, bookmarks and pagination recalculated. Where several books came from one structure you can regenerate only the ones affected.
No. Both are groupings in your equipment list, so the same structure produces either set. Shipment is usually a grouping you define; a vessel or skid is normally already there as a major tag.
Yes, and it is one of the better reasons to set the book up early. The document list usually exists at kickoff, so the contents can be generated in full with the real documents, numbers and tags in it. You can also generate the structure with no files in it where that is what they asked for.
Get answers to questions about DocBoss’s Final Databooks
No. Regenerate and the book rebuilds against the current approved documents, with contents, bookmarks and pagination recalculated. Where several books came from one structure you can regenerate only the ones affected.
No. Both are groupings in your equipment list, so the same structure produces either set. Shipment is usually a grouping you define; a vessel or skid is normally already there as a major tag.
Yes, and it is one of the better reasons to set the book up early. The document list usually exists at kickoff, so the contents can be generated in full with the real documents, numbers and tags in it. You can also generate the structure with no files in it where that is what they asked for.
Guides to book structure, contents configuration and closeout package assembly.
Whatever your customer’s book specification says goes in it. That’s the real answer, and it’s worth saying first because the…
Read NowThey’re all names for the same kind of deliverable: a compiled book of project documents your customer wants at handover,…
Read NowYou can build a compliant databook in Acrobat. Suppliers do it all the time: combine the files, add bookmarks, build…
Read Now