How I manage client deliverables in monday.com as a web design agency
Key takeaways
- What do web design deliverables look like in monday.com?
- A mix: exported design comps, optimized web images, a favicon set, brand assets, and PDFs for style guides and documentation — all attached to project items.
- How does a web agency keep the deliverables board lean?
- Compress images and PDFs on upload with a File Compress automation, so comps and documentation never sit on the board at full export size.
- How is the final handoff packaged?
- A status-triggered automation zips the approved deliverables column into a single archive the client downloads once — no account needed if you share the link.
- Should production-ready web assets be compressed too?
- The assets that go live on the client's site should already be optimized for the web. The board copy can be compressed further for review without affecting what ships.
Web design projects end with a handoff: the client needs the comps they approved, the optimized assets, the documentation, and often a favicon and social-image set. Doing that by hand — collecting, shrinking, zipping, uploading — is the kind of task that gets rushed at 6pm on a Friday. I automated it. Here is how.
The deliverables board structure
| Column | Contents | Treatment |
|---|---|---|
| Working | In-progress comps and exports | Manual compression per phase |
| Deliverables | Approved comps, assets, docs | Compress-on-upload automation |
| Delivery | Compressed copies for handoff | Automation output |
| Client Download | One ZIP | Automation output |
The client only ever sees Client Download.
Why separate Deliverables and Delivery?
So revisions do not lose the source. Deliverables keeps the approved originals for the next round; Delivery is a disposable compressed copy that gets zipped. If the client comes back for changes, the originals are right there.
The automations
Two File Compress recipes on a status column value of Ready to deliver:
- Compress images and PDFs from Deliverables into Delivery (medium).
- Zip Delivery into Client Download.
Move the item to Ready to deliver and the package assembles itself.
The client experience
The client gets one file in Client Download, or a shareable view of their project. One click, everything inside, original filenames preserved. No "can you resend the logo" emails.
The short version
Structure the board so approved deliverables and their compressed handoff copies are separate columns. Trigger a compress automation and a zip automation off a single project status. The client downloads one archive. Production web assets stay in your build pipeline. See the setup guide and how I automatically compress client deliverables in monday.com.
Frequently asked questions
- Can I automate the client handoff in monday.com?
- Yes. Chain two File Compress automations to a status like "Ready to deliver": one compresses the deliverables column, the second zips it into a client-download column.
- What compression level for web design comps?
- Medium for review. The comps a client signs off on do not need to be full-resolution PNGs on the board; the design source stays in your storage.
- Does compressing a style guide PDF change it?
- No. File Compress optimizes PDF structure and removes metadata losslessly — every page renders identically.
- How do clients access the deliverables?
- Share the ZIP file link directly, or give them a filtered shareable view of their project so they can self-serve the download.
- What about keeping originals for revisions?
- Compress into a separate Delivery column and zip that, leaving the working column with the originals for future revision rounds.
Zack
File Compress Developer at ColumnMate. Writes about file management, storage, and automation inside monday.com.
Related reading
Compress and zip files without leaving monday.com
File Compress runs on your board. 14-day free trial, no credit card required.
