The research plan your whole team can read.
Map questions, experiments, evidence, and decisions on one shared canvas, then plan the timeline and team capacity around it. Sauriq works beside your ELN.
Access is invite-only · we follow up with a walkthrough.
“Where is this at?” shouldn’t need a meeting.
-
The plan lives in someone’s head.
Which question a run answers, and what happens after it, is known to one or two people.
-
Status lives in a spreadsheet.
The tracker drifts out of date the week it is made, so nobody trusts it.
-
Decisions happen in a weekly meeting.
The reasons behind a branch are said once, then lost before the next experiment.
The graph is the plan.
Follow the work from the incoming plasma shipper through intake, plate maps, and reader QC to the handoff decision and the date it has to meet, on the map the team already shares.
-
Objective
State the question the work has to answer, with the success criteria beside it.
-
Activity
Plan each experiment as an activity with its protocol, tasks, and owner.
-
Material
Keep the samples and files each step depends on attached to it.
-
Decision
Write the go/no-go down before the result is in, with each option the team can take.
The method stays attached to the experiment.
Write each method once in the protocol library, then link it from the activities that use it, so whoever runs the experiment opens the method from the card.
-
One shared library
Shared protocols belong to your institution, filed in folders the whole lab can open.
-
Linked from the activity
Each link holds the revision it was made with, so saving a new revision does not change the method an activity already follows.
Switch the view, not the tool.
The tasks on the canvas are the same tasks in every plan view.
Table
Keep owners, priorities, dates, planned hours, and status together, with blocked work visible before you scan the rows.
Kanban
See planned, in-progress, blocked, and completed work, with each task's owner and work package in sight.
Gantt
Place intake, bench, and QC tasks on dated bars and see the dependencies that decide when the next run can start.
Calendar
Lay the same tasks on a month grid to see which days the bench is already booked.
Who is free, what changed, and where the hours went.
-
Team capacity
Compare allocated hours and time off week by week before assigning the next run.
-
Activity log
Every canvas change and comment with who made it and when, so the reasons behind a branch stay findable.
-
Logged hours by work package
Time is logged against the plan's work packages, so the hours each phase took are one report away, ready to export as CSV for a grant or budget review.
Answer “where is this at?” with a link, not a meeting.
Request access to the private preview. We reply by email to set up a walkthrough.