Designer Traveling for Client Work: A 3-Week Handoff Playbook for Brand Designers on the Road

Day-shape of a 3-week client trip

You don't need a literal Gantt chart. You need to know which week is heavy, which week is recovery, and which week is the one where revisions land hardest.

A few notes from doing this. Week 1 is when you set the rules;file names, review windows, the shared folder structure,and clients will quietly absorb them if you set them on day one and forget them if you don't. Week 2 is when the rhythm pays you back, because every revision lands inside the structure rather than against it. Week 3 is when you stop creating new work and start finishing, exporting, and archiving,and that is the week where reliable data matters most.

A file-naming convention worth committing to

Why do designers hate file-naming conventions? Because at home they feel like bureaucracy. On the road, with three projects in flight and a client who calls everything "the new one," they are the only thing standing between you and a 2 am rebuild.

Here is what I run:

• • Client_Project_Asset_v01_yyyymmdd_aqh.fig

Six fields, underscore-separated, no spaces, no special characters, lowercase initials. Examples from last autumn's trip:

• • acme_rebrand_logo-lockup_v03_20251104_aqh.fig
• • acme_rebrand_brand-kit_v02_20251108_aqh.pdf
• • northbird_landing_hero-mockup_v01_20251119_aqh.png

The asset slug uses a single hyphen for multi-word assets and never bleeds into the version field. The version is two digits, always, because v10 sorts before v2 in every operating system if you don't pad. The date is yyyymmdd because it sorts alphabetically and chronologically at the same time, which is the kind of small win that compounds over twenty-one days.

Commit the convention to a one-pager and pin it inside the project's shared folder. If a client renames a file, you rename it back, and you do it gently the first time.

One source of truth per asset type

Pick one tool per asset class and let the others wither.

• • Vectors and editable design: Figma (browser-based, version-history baked in, comments live next to the artwork).
• • Raster exports, brand-kit PDFs, fonts, and decks: Google Drive or Dropbox — pick one, never both.
• • Code-adjacent assets (SVG, JSON for Lottie, icon libraries): Git or whichever repo your developer client already uses.
• • Email and Slack: communication only. Never source-of-truth. Files in Slack expire from your memory faster than from the platform.

The single biggest version-control failure on the road is sending a v04 PNG over email, the client editing on top of v03 they still have open, and you reconciling at midnight. The fix is dull: every asset has one canonical location and one canonical filename, and the email contains a link, not an attachment.

Timezone math for review windows

Here is the part nobody writes down.

If you are in Lisbon (UTC+0 in winter, +1 in summer) and your three clients are in San Francisco (-8 from Lisbon winter time), Berlin (+1), and Sydney (+10), you have exactly two hours per day when at least two of them are reachable at the same time. Those two hours are 17:00-19:00 Lisbon. That is your synchronous review window. Everything else is async.

Build the trip around that.

• • Morning Lisbon: deep work, no calls, exports queued for upload.
• • Afternoon Lisbon: revisions you can ship before the synchronous window.
• • 17:00-19:00 Lisbon: live calls, screen-shares, revision approvals.
• • After 19:00 Lisbon: Sydney is awake, San Francisco is finishing lunch. One last asynchronous round of comments, then close the laptop.

The trap is letting Sydney creep into the morning. Don't. They can wait twelve hours; you cannot do good design at 06:30 after a 23:00 revision call.

Staying online across the route

Hotel Wi-Fi is fine for email and bad for everything else you do. The day you have to upload a 1.2 GB packaged InDesign archive to a client server is the day the hotel router decides to throttle uploads. This is a known thing. Plan for it.

What worked, leg by leg

In Portugal, MEO has the strongest 4G/5G coverage in both Lisbon and Porto and reaches into the small coastal towns I detoured through on a weekend. NOS is a close second in the city centers. I picked up a local prepaid MEO SIM at the Humberto Delgado airport arrivals counter for €15 with 15 GB included, and that carried me through the upload-heavy afternoons in week one and most of week two. In Spain, Movistar is the workhorse,its coverage in Madrid is full 5G, and it reaches into Toledo and Segovia on the day trips. Vodafone España is the secondary option if your apartment building has a quirk.

For the in-between days;airports, trains, the one afternoon I worked from a vineyard outside Porto because the client meeting overran,I ran HelloRoam, the travel-data service as my backup data plan. It rode whichever local network was strongest at the time (MEO in Portugal, Movistar in Spain) and meant I didn't have to swap physical SIMs at every border or wait at a kiosk on a 90-minute connection. One travel-data setup, two local SIMs, and a hotel router that I trusted for nothing heavier than Slack.

When to use mobile data and when not to

Use it for one job: the upload that absolutely has to go out before the synchronous window opens. Tether the laptop to your phone, kill the cloud-sync clients on every other folder, push the file, and switch back. Off-duty, leave it alone. Mobile data is for unblocking shipments, not for being constantly reachable. You will work better if your phone is not the second monitor.

Gear and battery (a short primer)

You do not need a redundant laptop. You do need a small redundant ecosystem.

• • One laptop, one external SSD (1 TB minimum), one 65W GaN charger, one short braided USB-C cable. That is the desk.
• • A power bank that can charge the laptop at 45W — not the phone-only kind. Anker and UGREEN both make versions that fit in a jacket pocket.
• • A small wired mouse, because hotel desks have wood you do not want to mouse on, and Bluetooth dies right before your synchronous window.
• • An e-ink notebook or paper for the morning review pass. Screen fatigue on day fourteen is not a vibe.
• • One sturdy laptop sleeve, because checked-bag treatment is a different sport.

What to do when the system breaks

It will. You'll lose a Figma version because someone overwrote your branch, or the hotel Wi-Fi will drop in the middle of an export, or a client will rename the file to logo_FINAL_FINAL_v2_use-this-one.png and you'll feel your soul leave.

Three rules.

One,Figma's version history is your friend; right-click, restore, breathe. Two,if the upload drops, do not retry on the same network; tether and re-push. Three;when a client renames a file, fix it once, send a one-line note explaining the convention, and move on. You are not the file-naming police. You are the person who knows the difference between v03 and v04.