Co-writing with partners whose first language is not English

The most common way authorship becomes inequitable in these collaborations is not a dispute over name order. It is the division of labour where one side collects data and the other writes.

It usually happens for a defensible reason — your English is stronger, the deadline is close. But whoever drafts the paper decides what it argues, what it emphasises, and how the results are interpreted.

Divide by section, not by language ability

Build the outline together, before anyone writes prose. One call: what the paper argues, the main message, section order, what each figure shows. This is where the intellectual control sits.

Let the team that did the work write methods and context. Your description of fieldwork you did not attend will contain errors, and reviewers who know the setting will find them.

Draft discussion jointly, or have your partner produce the first version. Interpretation is the part that matters most, and it is the part most often taken over by default.

Treat language editing as a separate final step. If the English needs work, fix it at the end — do not resolve it by taking over the content.

This costs you more time than writing it yourself. That is the actual trade-off, and it is worth naming honestly rather than concluding that the faster route is the only workable one.

The context section

Your partner should have the final say here, and you should read their version as information rather than as prose to be tidied.

Where you have suggestions, frame them as questions: "would a reader outside Vietnam understand what this means?" rather than rewriting the description itself.

And when you find yourself explaining the Vietnamese setting in your own words in the discussion, check that with your partner. Confident generalisations about a country by someone who has spent three field visits there are a recognisable failure mode in the literature.

Giving feedback on a draft

Rewriting a paragraph wholesale teaches nothing and can remove meaning the author intended. Three practices that work better:

Comment on structure first, sentences last. If the paragraph order is wrong, sentence-level edits are wasted work for both of you.

Explain the rule, not just the fix. "This paragraph's main point should come first — English academic prose usually front-loads the claim" teaches something that transfers. A silent edit does not.

Say what is working. Specifically, so they know what to keep. This is information, not politeness.

Use tracked changes or comments rather than a clean rewritten file. A clean file removes your partner's ability to see, and disagree with, what you changed.

Workflow that avoids wasted effort

Agree three things: who holds the master file, the deadline for each review round, and who decides when two co-authors disagree.

The first prevents the worst case — three divergent drafts that cost more to merge than to write.

Give realistic round times. A partner carrying a heavy teaching load cannot turn around a full chapter in two days, and a deadline that ignores this produces a superficial review rather than a fast one.

Approval is not a formality

Every co-author has the right to approve the final version. If your partner raises an objection to a claim, resolve it before submission rather than proceeding and noting the disagreement.

Watch for the pattern where a partner approves everything immediately. Given the power asymmetry, that often means review did not really happen. Ask a direct question about a specific claim to find out.

Building capacity deliberately

If you want a partnership that lasts, your partner writing better serves you directly — it is what makes them able to lead the next paper.

Two things that help, at low cost: keep a short note of the recurring edit types you make, and send it to them once rather than making the same edit across three papers; and where the journal allows, share a reviewer report and your response with them so they see how that exchange works.

Hand over the lead

At some point in a productive collaboration, a paper should be led by your partner as first and corresponding author — most naturally one drawing chiefly on work their team did.

Support it properly: review their draft as substantively as you would review your own student's, and let them handle the correspondence with the journal.

This is the point where a collaboration stops being a service arrangement. It also produces something you cannot get otherwise: a partner group with an independent publication record, which is what makes them fundable as a co-investigator on the next grant.