The community center wanted one PDF before they would confirm us the room for another season. The handbook had started, in September, as a friendly packet for new volunteers: how to greet a visitor, how to log a toaster, how to say no when a repair was unsafe. By March it had absorbed a year of photographs, a floor plan, a loan-sheet for the tool library, and an annual report I had promised the board in a moment of optimism. It looked, on my laptop, like a complete account of a project I love. It looked, to the center's upload form and to half our volunteers' inboxes, like a file that had no intention of arriving.

This is a list of what I learned while trying to make that packet travel, written down so I will not have to learn it again next season, at the same table, under the same fluorescent lights, with another toaster waiting on a towel.

The handbook that grew like a junk drawer

Useful documents in community work do not stay slim. They collect the same way a repair table collects screws: honestly, gradually, and with a confidence that later becomes a problem.

Things that quietly made the file enormous

  • Photographs of the Saturday hall, taken so a new volunteer could see where the electrical station sits in relation to the tea kettle, and taken again in winter when we moved the tables to avoid a draft. The second set was the one I needed, and also the one that pushed the export into a size I could no longer pretend was modest.
  • Close-ups of tool-library inventory tags, because we had lost a soldering iron the honest way, by lending it, and I wanted the next person to be able to read a handwritten number on a worn label. Close-ups of worn labels are heavier than a paragraph explaining the same system.
  • A floor plan I had redrawn after a volunteer with a cane pointed out that our "intuitive" layout was only intuitive to people who could weave. The new plan was better and, once scanned, not cheap.
  • The annual report itself, which included a year of before-and-after photographs: a lamp that lit, a coat that could be worn again, a radio that found a station. Those pictures are the argument for the room. They are also why a board packet stops fitting through a ten-megabyte door.
  • A scanned insurance certificate and a copy of the center's own room-use rules, both already PDFs, both already larger than their sentences required, both necessary if we wanted the key to the storage closet.

Doors that were narrower than the work

  • The community center's upload form, which asked for a single PDF, announced its size limit only after I had filled in the season dates, the contact phone, and the names of two coordinators who already have enough emails.
  • Volunteer inboxes, including one person who still reads messages on a machine that treats a large attachment as a personal affront, and another who asked, reasonably, that I not send her to a shared folder she would forget to check before Saturday.
  • The board's preference for one document rather than a zip of images, which I agreed with, because a board member looking at five community projects in an evening should not have to reconstruct our year from a pile of loose photographs.
  • My own habit of calling a file finished when the pages looked right on my screen, as if a handbook were done when I was done looking at it, rather than when another person could actually open it.

What I almost did, and why I stopped

When a form says no, the mind starts bargaining with the wrong objects. I made a list of those bargains too, because they are tempting, and because they would have made a worse packet.

Temptations that would have made a worse handbook

  • Pulling out the before-and-after photographs, which would have lightened the annual report and emptied it of the only evidence the board actually wants. A year of toasters repaired, told only in numbers, is a thinner story than we earned.
  • Splitting the handbook into a welcome packet, a floor plan, a tool-library sheet, and a report, then hoping people would open all four. I have been that volunteer. I have opened the first file, told myself I would read the rest after dinner, and arrived on Saturday only half briefed, smiling at a kettle I had not been told had moved.
  • Photographing fewer repairs next year, as if the problem were our pride in the work rather than a door that was too narrow for ordinary documentation.
  • Asking the center, in a slightly frantic email, to make an exception "just this once," which is a request they would then have to remember at the desk, on a busy afternoon, while someone else is asking about yoga.

Tools I refused to install on a volunteer night

  • A desktop program I would use once, leave on a shared laptop, and then have to explain to the next coordinator, who did not sign up to inherit software.
  • Any site that wanted a new account before it would touch a file that already contained volunteer phone numbers and a floor plan of a building we do not own.
  • Any suite that, once it had the handbook, would offer to edit pages, merge packets, split the report into chapters, or convert the PDF into another format the center had not asked for. We already had a PDF. We needed a lighter one. That is a smaller job than those suites like to admit.

The traveling copy, and the settings that actually mattered

I looked for a browser page that would do one job and then get out of the way. I found PDFCompress, a free online PDF compressor that runs in the tab I already had open, and I uploaded the handbook without installing a program or creating an account. What follows is not a feature list so much as a record of what I actually used, on a weeknight, with a room confirmation still outstanding.

Choices I made without turning the evening into a project

  • I started with a medium setting, because I still cared whether a worn inventory tag could be read. In typical cases a low setting trims something like twenty to thirty percent, a medium setting often lands around forty to sixty percent smaller, and a high setting can take off more still, sometimes around sixty to eighty percent, especially when a file is full of photographs. Those ranges are typical, not guaranteed, and I trusted the page more because it did not pretend every repair-café packet would shrink in the same way.
  • The medium copy was lighter and not quite light enough for the center's number. I opened it and checked the floor plan, the lamp that lit, and the insurance certificate. It was not lossless, which I had expected. The pictures were a little softer and still useful as proof and as training. I made a high-compression version for the upload, and I kept the medium one for the printed binder we leave on the tea table.
  • I used the grayscale option on pages where color was not information: the room-use rules, the welcome script, the loan sheet. I left color in the before-and-after photographs, because a lamp that returns to life is easier to believe when you can still see the shade.
  • Once the handbook was behaving, I lightened four companions in the same tab: the one-page Saturday checklist, a shorter flyer for visitors, a copy of the tool-library rules, and a sign-in sheet we had been treating as a separate stubborn file. The page let me upload up to five PDFs at a time, each allowed to be as large as 1GB, which was more room than a toaster report required and exactly the kind of headroom a messy weeknight needs.
  • I hesitated before I uploaded, because the packet includes phone numbers, a building plan, and photographs of volunteers who had not agreed to live forever on a stranger's server. The page said files were encrypted in transit and during processing, and that originals and results were deleted within twenty-four hours. A day is a unit I can live with. It is long enough to download the lighter copy and short enough that I could close the laptop and go home.

What changed after the file finally arrived

  • The center's form accepted the handbook on the next try, with a confirmation so plain I almost missed it, and the room was reserved for the season before I had finished washing the mug I had been drinking from.
  • Two volunteers who had never opened the shared folder wrote back from the attachment, one with a correction to the floor plan, one with an offer to bring a better lamp for the fine-repair table. The packet had started to do its real work, which is not to impress a form, but to let people arrive already knowing where the kettle is.
  • I kept two versions on purpose and stopped treating that as a failure: a clearer copy for the binder, a lighter copy for every door we have to walk through. The work is the same. The container changes.
  • I added a last step to the coordinator checklist, in ordinary language, before the line about bringing extension cords: check the file size. A handbook that cannot pass through the door is not a handbook, no matter how many toasters it remembers.
  • I did not keep a new permanent tool on the shared laptop. I kept a note, and the habit of making the traveling copy before I tell anyone, including myself, that the packet is finished.

The repair café will still be a room full of small crises and small recoveries, which is why I show up. I cannot compress a soldering iron, a drafty hall, or the moment when a radio finds a station again. I can, at least, stop letting the documentation of that room become a second, quieter failure, sitting in an upload form while a season waits to be confirmed. Since that week I have been treating file size as part of hospitality. If we want people to come, the pages have to get there first.

nov 17 2026 ∞
nov 17 2026 +