How to Work with International Freelancers (Without Losing Anything in Translation)

If you shoot destination weddings or run a studio that books international projects, you’ve probably already noticed that the best freelancers for the job don’t always speak fluent English. The colorist in Madrid is brilliant but his English is rusty. The Polish editor turns around 4-minute highlights in 36 hours but writes you in broken English. The Brazilian second shooter you hired for a Sicilian wedding sends voice notes in Portuguese.

This is fine. It’s actually how a good destination crew gets built — you hire for craft first, language second. But it changes how you brief, review, and communicate. Studios that figure this out early scale into international work cleanly. Studios that don’t end up either bottlenecking on English-only freelancers or burning hours fixing miscommunication.

Here’s the playbook.

Brief in writing, not on calls

The single biggest mistake studio owners make with international crews is running the kickoff on a Zoom call. You’ll spend 20 minutes saying things you think are clear, the freelancer nods, the deliverable comes back wrong because they were nodding to be polite, not because they understood.

Replace the kickoff call with a written brief. Three sections:

1. What we’re shooting. Date, venue, couple’s names, language(s) of the couple, expected hours.
2. What I need from you. Specific deliverables. “Highlight reel, 4 minutes, color graded for Instagram.” Not “the usual.”
3. Reference. Two or three short example clips or galleries — show, don’t describe. Visual references travel across languages much better than words.

Send it as a PDF or shared doc. Let them read on their own time, in their own language if they want to translate it. They come back with questions in writing, you answer in writing. Everything is logged.

Use freelancers’ first language for feedback

Once they’re working, the trap is to insist on English-only feedback. You think you’re “keeping the team aligned.” What you’re actually doing is asking your colorist to spend 10 extra minutes per comment translating what they want to say into approximate English. The comment loses precision in the process — and you, who don’t speak Spanish, can’t tell that something was lost.

Better: let everyone write in their own language and translate at the read time, not the write time.

A good chat tool does this automatically. The colorist writes “un po’ più caldo qui” on a chat thread, and on your screen it shows up in English. You reply “warmer at 0:15”, and on her screen it shows up in Italian. Both sides see their own language, both sides see the original preserved, and nobody’s translating anything by hand.

If your tool doesn’t have built-in translation, you can DIY it with a translator in another browser tab — but it’s friction every comment, every time. 20 comments per project × 30 seconds per paste = 10 minutes of translation per project, every project.

This is one of the few places where it’s worth picking a tool that supports per-comment translation natively.

Pay in the freelancer’s currency, not yours

This one’s small but it adds up. If you pay a Polish editor in USD, she loses 1.5–2.5% on the FX conversion every time. Across 20 projects a year that’s $300–$500 of money you “paid” that she never received.

Pay in EUR (or her local currency if it’s not EUR-zone) directly. Wise and Revolut Business both let you hold balances in 30+ currencies and pay out at the mid-market rate. The setup is a one-time afternoon. The freelancer notices on the first invoice — and you immediately stand out from every other studio that just sends USD via PayPal.

If your invoicing tool lets the freelancer pick her preferred currency on the payment request itself, even better. Make it her decision, not yours.

Don’t make them learn your tool stack

Every studio has its own ops stack. Asking each freelancer to learn HoneyBook + Frame.io + Slack + Notion + Pixieset + your custom Google Drive convention before they can deliver one cut is a hidden cost you’re charging them for free. The good ones won’t accept it; the desperate ones will accept it and then be slower.

The bare minimum a freelancer needs to deliver work is:

1. One link to where the project lives — not five
2. One inbox where their assignments show up
3. One way to send the invoice when the work is done

If you can’t give them that, your stack is too complicated for the international freelance market. The international freelance market is where the best craft people are — so simplifying the stack pays for itself in talent access.

A real workflow

Here’s how a Polish editor gets onboarded onto a Sicilian wedding cut in a typical FlowShot setup:

1. Day 0 — Owner writes the project brief in English, drops it in the project folder, sends one link to the editor.
2. Day 1 — Editor opens the project, sees her assignment, downloads the RAW from the same Drive link the brief points to. She writes a short clarifying question in Polish in the project chat. The owner sees it in English (auto-translated), replies in English. She sees his reply in Polish.
3. Day 5 — Editor uploads v1. The owner leaves timestamped notes on the cut in English; the editor reads them in Polish (DeepL on video review comments). Longer discussion happens in chat with the same translation layer.
4. Day 7 — V2 uploaded. Approved. Editor clicks “request payment” on her project, picks EUR, fills in line items, sends. The owner’s financial inbox shows the request, he approves, she gets paid in her local bank within 48 hours.

Total moments where language was an obstacle: zero. Total tools she had to learn: one.

The cost of not doing this

If you keep a “must speak fluent English” filter on your freelance hiring, you’re paying a 30–40% premium and accessing maybe 20% of the available talent pool. The other 80% — the Polish editor who turns around 36-hour highlights, the Italian colorist whose grade is on another level, the Brazilian second shooter who knows light better than anyone you’ve worked with — they’re all working for studios who figured out how to brief and review across languages.

For destination studios, this is now the baseline. Studios that hire internationally get better talent at the same rate.

---

FlowShot’s project chat, photo review, and video review (studio-side) support per-user language preferences with per-comment translation that happens at read time — the studio team sees their own language, the original always kept alongside. Translation runs on every paid plan (Starter $25/mo, Pro $49/mo, Business $89/mo) across 30 languages. The cross-organisation freelancer inbox shows your assignments from every studio in one list, so the freelancers you hire don’t have to learn your tool — they just see the work.