Guide · updated 2026-10-28T00:00:00.000Z
How to Assemble an Engineering Handover Pack
Handover is when drawings, test sheets, and operating notes stop being a project folder and become the file an operator will use next year. They need bookmarks and page numbers more than they need another zip. The engineering template in InHousePDF starts with scope, drawings, test records, and operations. Change the titles to match the asset. A cover page with the asset tag and the handover date stops two revisions being confused.
Drawings and test sheets
Save drawings to PDF from the tool that owns them. Add those PDFs. Do not expect InHousePDF to interpret layers or to redline. It copies pages, turns them if you say so, and stamps a label. Mixed page sizes are normal: an A3 drawing beside an A4 test sheet. Both stay their own size. If a drawing was exported on its side, rotate that page and look at the thumbnail before you trust the download.
Continuous numbering with a prefix such as ENG- lets a snag list say ENG-0142 instead of “the third PDF, somewhere near the end”. Divider pages mark the change from drawings to test records. Bookmarks let someone in a plant room jump to operations. The contents page is the same map, with links. The CSV is there if the asset register wants a table rather than a PDF outline.
Keep the pack with the asset, not on a random site
Test results and as-built drawings can describe how a building fails. Do not merge them by uploading the folder. The browser already has the files. The proof panel is the check that assembly did not open a connection. After you download, store the pack in the document control system the contract names. InHousePDF does not file it for you and does not claim compliance with a particular engineering standard.
If the operator also needs a smaller extract, use split by page range and say in the cover of that extract which pages of the master it came from. Re-stamp if the extract should have its own sequence.
Check the file before you send it
Download the pack and open it on the same device. Read the cover, the contents page, and the first page of each section. Confirm the stamped numbers match the contents. Open the CSV beside it if a colleague needs the index in a spreadsheet. Only then send the pack by the route your process already uses: the company portal, the client’s secure room, or the email address in the instructions. Sending it there is a choice. Assembling it did not require a copy on someone else’s server.
If the proof panel lists a network request while the pack is built, stop and treat that as a fault. The expected count is zero. You can also switch the network off after the page has loaded and run the same steps. The worker does not need a connection to stamp numbers or write bookmarks.
InHousePDF is not a professional adviser and is not affiliated with a regulator or a professional body. The same buttons can prepare documents for a review, an audit, a submission, or a handover. The product does not decide which papers a process requires. You still follow the instructions you were given.
Naming and revisions
Give the download a name that includes the asset and the revision, for example handover-asset-14-rev-c.pdf. The tool will not invent that name. If a drawing is superseded, remove it before you download rather than leaving both and hoping the bookmark order is enough. Two copies of the same drawing with different clouds are a common cause of a wrong installation. The contents page will list both if you leave both in. That is useful only when the later drawing is clearly the one after the earlier one.
Agree with the contractor which file is the master before you stamp ENG- numbers. If they already issued a numbered pack, continue the sequence by setting the start number, or use a new prefix for your volume. Do not renumber their contractual pages inside your head and forget to stamp the file. The CSV is the record of what you actually produced.