PDFs from Inventor that the shop floor can actually read

On a monitor every drawing is sharp. You zoom in to the smallest fillet, colors keep views and revision clouds apart and even a hair-thin line stays visible. The shop floor does not look at a monitor. There, a printed A3 sheet lies next to the saw, handled with gloves, read at arm's length under strip lighting, and after the break there is a coffee ring on it.

Between those two worlds sits one moment: the export. To export a PDF from Inventor takes two clicks, and that is exactly why it goes slightly wrong so often: colored lines that come out of the printer pale gray, hatching that clogs into a gray patch, sixty sheets in one file where the sawyer needs just one. In this article we walk through the choices you set right once, so that every PDF arrives readable from then on. With a toolbox like Thundercad you then apply those fixed choices the same way at every export.

We stick to the PDF itself: how it looks, what it is called and how it is packaged. What else belongs in a delivery to the shop floor besides the PDF is a story of its own; you can read it in The complete production package: what do you deliver, and to whom.

Paper is the benchmark, not your monitor

Almost every PDF that goes to the shop floor ends up on paper or on a dusty screen in a metal enclosure. Printing is usually done in black and white, on a laser printer that turns every color into a shade of gray. Reading is done standing up, at a distance, often with the sheet flat on the workbench next to the workpiece. Whatever looks fine on your calibrated monitor has to survive a reduced black and white print on a greasy workbench.

That is the test to judge every export choice by. Not "does it look good on my screen", but "can the sawyer still read this three weeks from now with the sheet next to the machine". Put on those glasses and most of the choices below fall into place by themselves.

Black and white is a choice, not a shortcoming

In the CAD system colors have a job: keeping layers apart, marking changes, dimming references. On a black and white print that same color becomes a gray value, and a yellow or light blue line comes out as a barely visible trace. The dimension you wanted to emphasize with color is the first thing to vanish on paper.

So export the shop floor PDF in black and white by default, so every line prints at full density and the distinction comes from line weight and line type instead of color. If you do want color on screen, for a review round for example, make that a separate agreement. More important than the choice itself is that there is one: one fixed preference for everything heading to the shop floor, not a different result per colleague.

Line weights and hatching that survive the printer

The difference between thick and thin lines is the grammar of a drawing: contours thick, dimension lines and hatching thin. That ratio has to survive the print. Put everything on nearly the same pen and the sheet becomes a spiderweb; print an A1 reduced onto A3 and the thinnest lines drop below what the printer can still render and simply disappear.

Hatching has the same problem in reverse: a fine hatch that looks elegant on screen clogs into a gray patch on a reduced print, with no dimension value left readable inside it. So check at least these four points on a test print:

• Does the difference between thick and thin lines stay visible, even in the smallest views?
• Can hatching still be recognized as separate lines, or does it form a gray patch?
• Are the smallest dimension values readable at arm's length?
• Do any lines vanish that were still visible on screen?

One drawing per file, or a set after all

Then the packaging. One thick PDF with all the drawings of an order browses nicely in the office, but at the saw stands someone who needs exactly one sheet and has to scroll through dozens of pages to find it. For execution the opposite works better: one PDF per drawing, so every file is exactly one part and the file name tells you which.

Choose deliberately, and preferably both from the same source: individual PDFs per drawing for the people at the machine, plus one document to leaf through for work meetings or checks if you want it. For the one-off case there is Export PDF: the drawing you are working in comes out in a single click. At the end of an order Batch Publish takes over: it exports all drawings in one run to PDF, with the same preferences every time, and it works together with Vault if your files live there.

The file name is part of the drawing

A PDF travels further than you think: from your export folder to the work planner's email, to a network share, to the folder next to the saw. Along the way the file name is often the only thing left that says what is inside. "Drw_final_v2 (copy).pdf" is a riddle at that point; a name like "4715-118 platform frame.pdf" states order, part and content at a glance, even for whoever digs the file up three weeks later.

So agree on one build-up, for example drawing number, description and revision, in a fixed order and without creative variations. The data for it is already in your model; how to build such names automatically from your iProperties instead of retyping them at every export is covered in Building file names automatically from iProperties.

Frequently asked questions

Why do my colored lines come out of the printer so faint?

Black and white printers translate every color into a shade of gray, and light colors such as yellow or cyan come out nearly white. On screen those lines stand out, on paper they fall away. Export the shop floor PDF in black and white and every line prints at full density.

Should I go for one PDF per drawing or everything in one file?

For the shop floor: one PDF per drawing, with the drawing number in the name, so everyone at the machine grabs exactly the right sheet. A collected document to leaf through is fine as a second form for meetings and checks, but not as the only delivery.

How do I keep the whole team's export choices identical?

Pin the choices down once and have everyone export along the same route, instead of each through their own dialogs. With Export PDF and Batch Publish from Thundercad every export follows the same fixed preferences, and the free trial month lets you test that on your own drawings.