Author order gets negotiated more than once. A team agrees on a running order at kickoff, then a co-author’s contribution grows, a planned contributor drops out, or new data changes whose analysis carries the paper — and the order that made sense in month one no longer reflects what actually happened by month six. That renegotiation is normal. What causes problems later is not the change itself but the absence of a clear record of who agreed to what, and when.
This guide covers the practical, document-management side of that problem: how to change author order mid-draft — while the manuscript is still being actively written and before it has been submitted anywhere — without losing the paper trail of the decision. It is a different topic from what happens after a manuscript has been submitted or published. Formal correction and consent requirements for authorship changes at those later stages are governed by publisher and COPE process, covered in CASRAI’s comparison of COPE’s before- and after-publication authorship-change flowcharts. Here, the manuscript hasn’t left the authoring team yet, and the question is purely operational: how do you make the change, document it, and keep everyone’s agreement traceable inside the same drafting workflow you’re already using.
Why an author-order change needs its own record, separate from text edits
Most collaborative-writing discipline is built around tracking changes to prose — who edited which sentence, when a paragraph was rewritten, which draft is current. CASRAI’s guides on manuscript version control across co-authors and track-changes etiquette for co-authored manuscripts cover that mechanic well, but a change to the byline order itself is a different kind of edit. It isn’t a wording change any reviewer can see by comparing two paragraphs; it’s a decision about credit, and per the ICMJE authorship criteria, every listed author is expected to have approved the final version of the manuscript, which includes the byline as it will actually appear. An author-order change that happened in a chat message, a hallway conversation, or an email thread that later got deleted leaves no evidence that everyone actually consented — and “I don’t remember agreeing to that” is exactly the kind of dispute a research-integrity office or a journal editor has no good way to resolve after the fact, because there’s nothing to check it against.
A text edit that turns out to be wrong is usually recoverable from ordinary version history. A silent, undocumented author-order change is not recoverable in the same way, because the “before” state that mattered was an agreement between people, not a state of a file. That’s why it needs an explicit record, not just reliance on whatever your word processor happens to log automatically.
Keep an explicit author-order decision log
The single most effective practice is a short, dated log — separate from the manuscript text itself — that records every author-order decision and change across the life of the draft. It doesn’t need to be elaborate. A simple shared document or a pinned entry in whatever collaboration tool the team already uses (a shared drive folder, a project wiki page, a pinned Slack/Teams message) is enough, provided it is:
- Dated at every entry. “Author order: A, B, C, D (agreed 2026-03-04)” followed later by “Author order changed to A, C, B, D (agreed 2026-06-18, per B’s request after taking on the revised statistical analysis)” gives anyone reading it later a clear timeline, not just a final state.
- Explicit about the reason. A one-line rationale — a contribution grew, a co-author’s role changed, someone withdrew — matters more later than it seems like it should at the time. If a dispute does surface, the reason is often what makes a change look reasonable or not; the order alone doesn’t tell that story.
- Confirmed by name, not inferred from silence. Record who explicitly agreed, not just who didn’t object. A change proposed in a group email that nobody replied to is not the same as a change every co-author affirmatively confirmed — and only the latter satisfies the spirit of ICMJE’s final-approval expectation.
- Kept alongside the manuscript, not buried in email. The log should live somewhere every current and former co-author can find it later, ideally the same shared workspace as the manuscript itself — a shared drive folder or the same Overleaf/Git project — not a single person’s inbox.
If the team already put together a written authorship agreement at kickoff, the decision log is simply the living update mechanism for that agreement: the kickoff document establishes the starting order and the criteria for earning a place on it, and the log records every point at which that starting position changed and why.
Use your existing version-history tools deliberately — don’t rely on them by default
Most collaborative writing tools already retain some form of change history, but none of them were built to flag “this revision changed the author list” as a distinct, findable event. Used deliberately, though, each can supplement the decision log:
- Google Docs version history. Google Docs automatically saves incremental versions, but the named-version feature is the part worth using intentionally: use File > Version history > Name current version whenever the author order changes, with a version name that says so directly (e.g., “Author order updated – see decision log”). An unnamed autosave is easy to scroll past; a named version is not. Named versions are also exempt from Google’s automatic cleanup of older revisions, so they stay retrievable long after ordinary autosaves age out.
- Microsoft Word with tracked changes and version numbering. Word’s native version history is weaker once a file leaves OneDrive/SharePoint sync, so pair it with the file-naming discipline covered in CASRAI’s manuscript version-control guide: increment the version number in the filename specifically at the point of an author-order change, and note the change in the covering email or message that circulates the new version, rather than leaving it to be discovered by comparing bylines.
- Git repositories and Overleaf projects. For LaTeX manuscripts kept under version control, an author-order change should be its own isolated commit with a commit message that says exactly what changed and why — not folded into a larger commit that also touches the results section. This is the cleanest record of the group covered here: the commit history is timestamped, immutable once pushed, and typically already visible to every collaborator with repository access.
In every case, the tool’s built-in history is a supplement to the decision log, not a replacement for it. A Git commit or a named Google Docs version tells you a change happened and when; it doesn’t reliably tell you that every co-author agreed to it, which is the part that actually prevents a later dispute.
Communicate the change to every co-author explicitly, not just the ones directly affected
An author-order change often starts as a conversation between two people — the two authors whose positions are swapping, for instance — but it affects everyone on the byline, because every author’s position is defined relative to the others. Practices worth following every time an order change is proposed:
- Circulate the proposed new order to every current co-author, not only the ones whose position is changing, and ask for explicit confirmation rather than assuming no news is good news.
- State the reason for the change in that same message, using the same language that goes into the decision log — consistency between what people were told and what’s recorded matters if the record is ever revisited.
- Give a real deadline for objections and say plainly what happens if none arrive (e.g., “the order below becomes final as of [date] unless I hear otherwise”) — an open-ended proposal that never gets formally closed out is a common way author-order questions stay unresolved for months.
- Where a co-author has left the project entirely or become unreachable, don’t simply drop them from the log silently — record the attempt to reach them and the basis for how their status was resolved (this is also where CASRAI’s guidance on formal mediation for authorship disputes becomes relevant if agreement can’t be reached directly).
What this practice is protecting against
None of this is paperwork for its own sake. A clean, dated, consented record of every author-order change protects the team in three concrete ways:
- It answers the “who agreed to what” question if a dispute surfaces later — whether that’s an informal disagreement between co-authors, a question from a supervisor or research-integrity office, or, in the more procedural sense, part of what a journal or COPE-guided process will want to see if an authorship dispute is ever formally raised after submission.
- It satisfies the spirit of ICMJE’s final-approval expectation in a way that’s actually demonstrable, not just asserted: every author’s documented, dated agreement to the version being submitted, byline included, rather than a byline nobody can confirm anyone signed off on.
- It separates a legitimate, negotiated change from an unexplained one — the same information that protects the team from a later dispute is also what distinguishes an ordinary, well-documented order change (contributions evolved, which is normal) from the kind of undisclosed, unagreed change that research-integrity offices and journals treat as a red flag.
The mechanics here are lightweight on purpose: a dated log, a deliberately named version or isolated commit, and an explicit round of confirmation from every co-author. The habit is what matters — treating an author-order change as an event worth documenting in the moment, rather than something to reconstruct later from memory and old email threads once it’s already in dispute.
Frequently asked questions
Does an author-order change mid-draft need to be formally reported to anyone?
Not while the manuscript is still pre-submission and hasn’t gone to a journal. Formal reporting obligations, consent forms, and correction mechanisms apply once a manuscript has been submitted or published — see CASRAI’s comparison of COPE’s before- and after-publication authorship-change flowcharts for that stage. Before submission, the obligation is internal: keep a clear, consented record so that if the change is ever questioned, the team can show exactly what happened.
What’s the difference between this and general manuscript version control?
General version control (covered in CASRAI’s guide to managing manuscript versions across co-authors) is about knowing which draft of the text is current. An author-order decision log is narrower and more specific: it exists to record consent to a change in credit, not just to track which file is newest. A manuscript can have perfect text version control and still have no record of who agreed to a byline change — the two problems need separate solutions.
Who should own the author-order decision log?
In practice, whoever already owns version control for the manuscript — typically the corresponding author, per CASRAI’s guide on corresponding author responsibilities under ICMJE — is the natural person to also maintain the decision log, for the same reason: they’re already the point of contact producing the version that goes to the journal, and confirming every author approved that version’s byline falls to them by default.
What if co-authors can’t agree on a proposed order change?
Try to resolve it directly first, with the reasoning for the proposed change stated explicitly and in writing. If direct discussion doesn’t resolve it, CASRAI’s guide to formal mediation for authorship disputes covers how to bring in a neutral party — typically a departmental or institutional research-integrity contact — before the disagreement escalates further or the manuscript is submitted with the disagreement unresolved.
Does CRediT (contributor roles) replace the need to track author order?
No — they answer different questions. The CRediT taxonomy (ANSI/NISO Z39.104-2022) records what each author contributed, independent of byline position. Author order still separately signals relative contribution and role by convention (see CASRAI’s comparisons of first vs. second author and middle vs. last author), and many teams use CRediT statements alongside an author-order decision log rather than as a substitute for one, since a change in someone’s CRediT roles is often exactly the trigger for renegotiating order in the first place.
