How creative actually ships · 6 min read
Why file-request forms kill creative timelines
Every agency we talk to has the same sequence.
Monday: email the client.
Wednesday: chase the client.
Friday: Dropbox link arrives. Files are named FINAL_v3_REAL_final.jpg.
Monday next week: half the files don't match the spec. Back to the client.
Friday next week: three weeks in, still not started.
The tool that created this pattern was Dropbox File Request. Then WeTransfer Pro copied it. Then Google Forms got a file upload field. Then Typeform. They all converged on the same three moves:
1. A bare dropzone 2. A filename field 3. A "done" screen
That's it. No spec validation. No branding. No audit log. No follow-up. The partner uploads whatever they have, hopes it's right, and waits.
What's missing
- The spec. A "5MB JPG" isn't enough. Real specs have dimensions, DPI, bleed, color space, duration caps, quantity. The partner should see them before they upload, and the platform should check them in the partner's browser before the file ever leaves their machine.
- The shape. When you ask for a square album cover, show a square. When you ask for an LED banner, show ultrawide. Partners who see the shape upload the right thing on the first try. Partners who see a generic dropzone guess.
- The trust. Your partner is trusting you with unreleased creative. Tell them what you're going to do with it. "No AI training. No tracking pixels. Deleted 30 days after close. 24-hour pullback window." These aren't legal hedges; they're the only honest answer to the anxiety every partner has.
- The receipts. Every open, every upload, every approval should be logged. The sender should be able to prove "yes, Elena downloaded the embargoed press kit on April 18 at 10:02am." The partner should be able to verify the same.
- The loop. After approval, the asset should flow. Printer gets the print file, AV team gets the LED loop, library gets the sourced original, everyone gets what they need.
A file-request form is a feature. What partners actually need is a brief: a spec-declared, verified, logged, two-party exchange that closes a workflow instead of starting one.
We built GoBrief because the form was never enough.