Mapping Credit Early: A One-Page Authorship Agreement for New Lab Collaborators

Authorship conversations tend to arrive late. A project begins with a promising question, a shared bench, and an unwritten assumption that credit will sort itself out. Months later, when a manuscript takes shape, the same team must decide who is first author, who is corresponding, and whose contribution merits acknowledgment rather than authorship. At that point, incentives are sharpest and memories are least reliable. A short conversation held before the first experiment cannot eliminate disagreement, but it can make the terms of credit explicit while the work is still easy to discuss.

At NI Lab, we treat this conversation as a lab practice rather than a legal instrument. It is a planning meeting about contribution and communication, not a binding contract. The goal is not to fix an author list forever. The goal is to establish a shared vocabulary, a written record, and a clear point at which the team will revisit the question.

Why the First Week Is the Right Time

New lab teams are often assembled quickly. A principal investigator brings on a postdoctoral researcher, a graduate student joins a rotation, a technician is assigned to a method, and an external collaborator offers a reagent or a dataset. Each person arrives with a different model of authorship. Some assume that bench work determines order. Others assume that conceptual leadership does. Still others have been taught that the last author is always the senior person, regardless of field or institution.

Waiting until drafting to discuss these models is a recipe for avoidable conflict. Before data arrive, the team can talk about expectations without implying that anyone has already earned a position. The conversation is prospective. It asks what kinds of work will count and how the team will decide when the contribution picture changes.

The timing also matters for inclusion. A student who joins in week one can ask about credit without appearing presumptuous. A technician can clarify whether method development is expected to lead to authorship. An external collaborator can state whether they expect co-authorship or acknowledgment. These questions are harder to raise after a paper is nearly finished.

Four Categories, Not a Ranking

The most useful starting point is a set of contribution categories broad enough to cover most laboratory work. The categories should be discussed separately before they are translated into order.

• Conceptual contribution: framing the question, designing the study, selecting the theoretical framework.
• Execution: performing experiments, developing methods, managing data collection, maintaining protocols.
• Analysis and interpretation: statistical analysis, coding, modeling, interpreting results, preparing figures.
• Writing and communication: drafting, revising, responding to reviewers, presenting the work publicly.

A team can then ask which categories are essential for authorship in this project and which are better recognized through acknowledgment. This distinction is especially important in interdisciplinary work, where a collaborator may provide a critical dataset without participating in interpretation or writing. The conversation should also identify the evidence the team will use to document contributions: lab notebook entries, meeting notes, authorship contribution statements, and drafts with tracked changes.

Order Expectations and Decision Rights

Order expectations are the most delicate part of the conversation. It helps to separate three questions. First, what order does the team currently expect, and why? Second, who has decision rights if expectations diverge? Third, what process will the team use to resolve a disagreement?

A useful practice is to record expectations as provisional and reasoned, not as promises. For example, a team might note that a graduate student is expected to be first author because they are leading the experimental design and analysis, while a postdoc is expected to be corresponding author because they are overseeing the project and handling submission. The record should also state that order will be reviewed when the manuscript outline is drafted and again before submission.

Decision rights should be explicit. In many US labs, the principal investigator holds final responsibility for the author list, but that authority should be exercised through a documented process. The team should know who convenes the review, who is consulted, and where the record is stored.

A One-Page Worksheet

A single page is enough to make the conversation concrete. The worksheet can be kept in a shared lab folder and updated at milestones.

Project title and working question. One or two sentences.

Named contributors. Include role, start date, and expected duration.

Contribution categories. For each contributor, note the categories they expect to lead, support, or observe.

Order expectations. Record the current expectation, the reasoning, and the date of the conversation.

Authorship versus acknowledgment. Note any contributions that the team expects to recognize through acknowledgment rather than authorship.

Decision rights. Identify who holds final responsibility and who must be consulted.

Renegotiation triggers. List events that require a review: a new method, a new collaborator, a change in scope, a departure, a funding requirement, or a delay of more than six months.

Review dates. Set at least two: when the manuscript outline is drafted and before submission.

The worksheet is not a substitute for institutional policy. It is a record of a conversation that can be revisited.

Sample Scripts

For a principal investigator opening the meeting:

'I want us to spend twenty minutes on credit before we start experiments. This is not a final author list. It is a chance to say what kinds of contributions we expect and how we will revisit the question. I will take notes and put them in the shared folder.'

For a student raising the topic:

'I would like to understand how authorship will be discussed on this project. Could we set a time to talk about contribution categories and when the order will be reviewed? I am not asking for a promise, just a process.'

For an external collaborator:

'Before we begin, I would like to clarify how our teams will handle authorship and acknowledgment. Could we agree on the contribution categories and a review point before the first dataset is transferred?'

These scripts are deliberately modest. They do not demand a particular outcome. They establish that credit is a topic the team can discuss.

Common Objections

The most common objection is that the conversation is premature. In practice, it is easier to discuss credit before results exist. A second objection is that written expectations create rigidity. The remedy is to build renegotiation into the document. A third objection is that power differences make it hard for students to speak. That is why the PI should open the conversation and why the worksheet should include a review date that does not depend on a student's request.

A Routine, Not a Contract

The value of this practice lies in repetition. A credit conversation held once and never revisited becomes another document that no one reads. A conversation held at the start, at the outline stage, and before submission becomes a routine. It gives new lab members a way to ask questions, gives senior members a way to explain expectations, and gives the team a record to consult when memory and incentive diverge.

For new collaborations, the first experiment is a better time to discuss authorship than the final draft. The work is still open, the roles are still forming, and the team can agree on a process before it needs to agree on an outcome.