Template

Team roles, RACI & research org design template

Ready-to-use role cards, a sample RACI matrix for common research tasks, recommended spans of control, and governance forum templates to clarify responsibilities and speed execution in research teams.

Purpose (what this template helps you solve)

This template helps research teams define clear roles, decision rights, and handoffs so discovery work is coordinated, efficient, and reproducible. Use it to reduce delays, eliminate duplicated effort, and make responsibilities explicit across projects, labs, and cross-functional programs.

How to use this template

  1. Copy the role-card table and adapt each card to your local job titles and responsibilities.
  2. Pick the common research tasks in the sample RACI matrix and tailor rows to your workflow (experiment design, protocol approval, data collection, analysis, publication, IP, procurement, etc.).
  3. Assign R/A/C/I letters collaboratively in a short working session (30–60 minutes) with project leads and key stakeholders to resolve conflicts and ambiguities.
  4. Publish the agreed roles, RACI matrix, and governance cadence where the team can find them (project wiki, lab handbook, or this platform).

Role-card template (copy & adapt)

Use one card per role. Keep cards concise so they are usable in meetings and onboarding.

Field Example / Guidance
Role name e.g., Principal Investigator (PI)
Purpose One sentence that explains why this role exists
Key responsibilities 3–6 bullet points of primary tasks and outputs
Decision rights Which decisions this role makes (e.g., approve protocols, hire staff, sign off on publications)
Typical skills / competencies Short list of skills required
Typical span of control Suggested direct-report range or workload guidance
Handoffs / upstream Who hands work to this role and what they expect
Handoffs / downstream Who receives outputs and what they need

Sample role cards (starter set — adapt as needed)

Principal Investigator (PI)

  • Purpose: Sets scientific direction, secures funding, and is ultimately accountable for research integrity and outputs.
  • Responsibilities: Research strategy, funding & sponsor relationships, final approval of publications, personnel decisions.
  • Decision rights: Approves protocols, budgets, hires above a threshold, publication submissions.
  • Span of control: Typically 3–12 direct reports depending on seniority and administrative support.

Lab/Group Lead or Project Lead

  • Purpose: Day-to-day leader for a project or subgroup; translates PI strategy into execution.
  • Responsibilities: Plan experiments, assign tasks, monitor progress, mentor staff.
  • Decision rights: Tactical decisions about resource allocation within the project, experiment go/no-go.

Research Scientist / Postdoc

  • Purpose: Design and run experiments, analyze data, and contribute to manuscripts.
  • Responsibilities: Experimental design, data collection, primary analysis, method development.

Research Technician

  • Purpose: Perform routine lab procedures, maintain equipment, support experiments.

Data Manager / Research Data Steward

  • Purpose: Ensure data quality, metadata standards, storage, and reproducibility.
  • Responsibilities: Data pipelines, access controls, backups, documentation.

Statistician / Analyst

  • Purpose: Design analysis plans, support experimental design, and validate results.

Research Software Engineer (RSE)

  • Purpose: Build and maintain analysis pipelines, automation, and reproducible codebases.

Lab Manager / Operations Coordinator

  • Purpose: Manage procurement, equipment maintenance, training, health & safety compliance.

Quality / Compliance Officer

  • Purpose: Ensure adherence to protocols, regulatory requirements, and QA processes.

Sample RACI matrix (starter)

Map common tasks (rows) to roles (columns). R = Responsible (does the work), A = Accountable (final sign-off), C = Consulted (two-way), I = Informed (one-way).

Task / Activity PI Project Lead Scientist / Postdoc Technician Data Manager Statistician Lab Manager
Define research question & hypothesis A C R I I C I
Design experiment / protocol C A R C C C I
Ethics / regulatory approval A R I I I I C
Data collection I C R R C I I
Data cleaning & storage I C C I R / A C I
Analysis & interpretation C C R I C A I
Manuscript / reporting A R R I I C I
Intellectual property / tech transfer A C I I I I C

Guidance for filling RACI effectively

  • Keep one and only one accountable (A) per deliverable to avoid confusion.
  • Use R for the people who actually do the work. If multiple people share doing the work, mark them R and clarify how they divide tasks in supporting docs.
  • Use C to collect input early — these are the people you consult when making decisions.
  • Use I for stakeholders who must be kept informed (sponsors, compliance officers, collaborators).
  • Resolve conflicts in a short meeting and record any exceptions or conditional rules (e.g., PI is A for safety-critical approvals only).

Recommended spans of control (practical guidance)

Suggested ranges — adapt to your context, funding, and administrative support:

  • Principal Investigator: 3–12 direct reports (depends on administrative support and size of portfolio)
  • Project / Lab Lead: 3–8 direct contributors per project
  • Data Manager / RSE / Statistician: typically shared across projects; aim for predictable workload caps (e.g., 2–4 active projects)
  • Technician / Lab Manager: span determined by equipment and operational complexity

Governance forums (who meets, why, frequency, outcomes)

Forum Frequency Participants Primary purpose Outputs
Project huddle Weekly Project lead, active scientists, data steward Synchronize short-term tasks and unblock experiments Action list, experiment schedule updates
Steering / PI check-in Monthly PIs, project leads, major stakeholders Strategic alignment, resourcing, major decisions Decision log, priority changes
Protocol / methods review Ad hoc (before key experiments) Scientists, QA, Ethics rep, Statistician Approve critical protocols and ensure reproducibility Approved protocol, checklist
Data governance Quarterly Data manager, PI reps, IT, Compliance Agree on standards, access, retention Data standards, access rules

Common pitfalls and how to avoid them

  • Ambiguous A: If more than one person is 'A', hold a quick escalation meeting to assign single accountability.
  • Too many Cs: Limit consulted parties to those who materially affect the decision to avoid delay.
  • No published RACI: If the matrix lives only in people's heads, update project docs and require a short sign-off during onboarding.
  • Unclear handoffs: Document inputs/outputs between roles and include examples (data files, protocol versions, sign-offs).

Tailoring checklist (quick)

  1. Replace sample role names with your local titles.
  2. Add any regulatory or sponsor roles (e.g., Clinical Operations, Institutional Review Board) relevant to you.
  3. Map in collaborators or external partners as roles (C or I) and define communication channels.
  4. Publish and review RACI at project milestones (proposal, start of data collection, before publication).

Next steps and suggested experiments

Run a 60-minute RACI workshop with the core team to adapt this matrix. After two sprints, review whether decisions are happening faster and whether handoffs are clearer. Iterate role-cards where confusion persists.

Templates included: role-card table, starter role-cards, sample RACI matrix, governance forum templates, tailoring checklist.

Discuss Ask the Librarian

Discussion

Comments and conversation will live here.