My team went fully remote in 2020. We moved everything to Google Workspace — Docs, Sheets, Slides, Drive, the whole suite. It worked beautifully for about 90% of our document workflow. The other 10%? PDFs. And that 10% consumed a wildly disproportionate amount of our time.
The problem wasn’t storing PDFs — Drive handles that fine. The problem was what happened when someone needed to do something with a PDF. Sign it. Fill in a form field. Redact a social security number before sharing. Add a comment for a colleague.
Every one of those tasks broke our workflow. Someone would download the PDF, open it in whatever app they had locally, make the edit, save it with a slightly different filename, and re-upload it to Drive. Now we had two versions. Which one was current? Did they overwrite the original or create a duplicate? Did the person on the other end even see the update?
This is the story of how we fixed it.
The Old Workflow (Don’t Do This)
- Receive PDF in Google Drive
- Download to desktop
- Open in Preview / Adobe / whatever’s installed
- Make edits
- Save as new file
- Upload back to Drive
- Delete (or forget to delete) the local copy
- Notify the team that the file was updated
- Hope nobody edited the old version in the meantime
Steps 2-8 took anywhere from 5 to 15 minutes per PDF. Multiply that by the 20-30 PDFs our team handles per week and we were burning 2-5 hours weekly on file management theater.
The New Workflow
- Receive PDF in Google Drive
- Right-click → Open with → Super PDF Editor
- Make edits directly in the browser
- Save (overwrites the same Drive file)
- Done
Steps 2-4 take about 90 seconds. The file never leaves Drive. There’s no download, no local copy, no re-upload, no version confusion. The same file link that was shared with the team still points to the updated version.
What Changed For Us
Version control stopped being an issue. When the PDF is edited in place, there’s only ever one version. The Drive file’s version history tracks what changed and when, just like it does for Docs.
We stopped emailing PDFs. Previously, the download-edit-upload friction meant people would often just email the edited PDF instead of putting it back in Drive. Now that editing happens in Drive, the file stays in Drive.
IT stopped fielding “how do I edit a PDF” questions. This was a surprisingly frequent helpdesk ticket. Different team members had different local PDF tools (or no tools at all). Standardizing on a Drive-native add-on meant everyone had the same capability regardless of their OS or what was installed locally.
Onboarding got simpler. New hires get a Google Workspace account and they’re set. No need to install Adobe Acrobat, no license to provision, no IT ticket to open.
The Specific Use Cases That Improved
-
Contracts and agreements: Edit terms, add signatures, initial clauses — all in Drive. Share the Drive link with the other party. One file, one source of truth.
-
Client deliverables: Consultants on our team were spending 10+ minutes per deliverable on the download-edit-upload cycle. Now they edit the PDF in Drive, click “Share,” and move on.
-
HR documents: Onboarding packets, tax forms, NDAs — all PDFs, all need occasional updates. Editing in Drive means HR doesn’t need to maintain a separate folder of “editable versions.”
-
Compliance and legal: Redacting PII before sharing documents externally. This used to require Adobe Acrobat on a specific machine. Now anyone on the team can redact properly from their browser.
Why This Matters More Than It Sounds
I know “we improved our PDF workflow” doesn’t sound transformative. But death-by-a-thousand-paper-cuts is how remote teams actually lose productivity. It’s not one big bottleneck — it’s fifty small ones, each costing 5-10 minutes, adding up to hours per week per person.
The best productivity improvements aren’t dramatic. They’re the ones that remove a small friction point from something you do every day. For Google Workspace teams, PDF editing is one of the biggest remaining friction points. Fix it once and you stop thinking about it forever.