This is a refreshingly honest problem because it reveals something most automation advocates overlook: a team's actual workflow. The user, LibraryTechBeard, has a circulation team that receives a daily CSV of room bookings. They want to print a formatted table, with a handwritten Notes column, for information desks that prefer paper. The instinct to reach for a macro is understandable, but the real insight here is that the team's resistance to digital tools isn't a failure, it's a signal. And the solution should honor that signal, not override it.
The macro approach the user proposed is workable, but it carries hidden friction. A macro in Excel or Google Sheets can convert the CSV to a table, set row heights, and adjust print margins for landscape letter paper. Adding a Notes column to the export source is a smart workaround. But macros require maintenance. If the CSV format changes, if columns shift, or if someone runs the macro on the wrong file, the process breaks. The team will eventually call IT, and the automation becomes a dependency rather than a liberation. What the team really needs is a system that treats the printed table as a first-class output, not a post-processing afterthought.
A more resilient method would be to use a dedicated data tool that separates the source CSV from the formatting logic. For example, a simple script (Python with Pandas and ReportLab, or even a low-code platform like Power Automate) can ingest the CSV, generate a PDF with the exact row heights and Notes column, and save it to a shared folder each morning. The team prints the PDF. No macros, no fragile spreadsheet dependencies, no risk of accidental edits corrupting the source data. The handwritten Notes column stays physical, but the automation stays invisible. This approach respects the team's preference for paper while removing the manual formatting burden entirely.
The lesson here is that automation should adapt to people, not the other way around. The circulation team doesn't need to be dragged into a digital dashboard they don't want. They need a reliable bridge between the digital report and their analog workflow. A print-ready table, generated automatically, that leaves room for pencil marks is not a compromise, it is a precise solution to a specific human need. The user should build that bridge, test it with the team, and then walk away. The best automation is the one your team stops noticing because it just works.