Connects to the tools you use
Set up connections through ERP.AI and Proto workflows, with every change logged.
- Research Projects PM
- Grant authority
- External operation source
- Identity
Research project management here centers on a work package owned by a research organization and linked to a funded project. A package carries a record number, subject, due date, budgeted hours, owner, revision and lifecycle status.
Work packages in one list
An Independent Reviewer decides on the package revision and supporting evidence.
Every feature works on the same records. Pick one to see the screen your team works in.
Keep each funded project, research organization and staff membership tied to the work they own.
Acceptance waits for the research coordinator
| Record number | Subject | Status | Revision | Owner | Due at | |
|---|---|---|---|---|---|---|
| WP-87949 | Participant recruitment protocol | Review | 360 | Leo Fischer | 29 Oct | |
| WP-17304 | Baseline survey development | Review | 800 | Priya Nair | 17 Oct | |
| WP-82383 | Water sample field collection | Review | 90 | Mina Varga | 25 Oct | |
| WP-13077 | Laboratory assay validation | Review | 100 | Tomas Silva | 11 Oct | |
| WP-82149 | Interview coding framework | Review | 460 | Sofia Haddad | 28 Oct |
Plan and follow the bounded unit of research work through review and acceptance.
Work packages
| Record number | Subject | Owner | Status | Due at | Budget hours | |
|---|---|---|---|---|---|---|
| WP-13195 | Participant recruitment protocol | Amara Diallo | Draft | 15 Oct | 6 | |
| WP-75464 | Baseline survey development | Priya Nair | Planned | 17 Oct | 9 | |
| WP-78095 | Water sample field collection | Nadia Rahman | Active | 27 Oct | 12 | |
| WP-94056 | Laboratory assay validation | Sofia Haddad | Review | 12 Oct | 16 | |
| WP-55172 | Interview coding framework | Tomas Silva | Accepted | 12 Oct | 8 |
Keep dependent task lines and planned versus actual hours under the right work package.
Tasks
| Parent | Line number | Task name | Planned hours | Actual hours | Due at | |
|---|---|---|---|---|---|---|
| Interim data analysis | 270 | Finalize consent language | 1 | 2 | 29 Oct | |
| Interim data analysis | 390 | Pilot baseline questionnaire | 7 | 10 | 19 Oct | |
| Baseline survey development | 750 | Collect estuary site samples | 11 | 11 | 11 Oct | |
| Laboratory assay validation | 910 | Run assay control batch | 5 | 5 | 03 Nov | |
| Interview coding framework | 380 | Code first interview set | 3 | 1 | 26 Oct |
Tie grant milestone submissions and completion evidence to the work package revision.
Approval waits for the independent reviewer
| Status | Grant reference | Due at | Completed studies | Approval reference | Parent | |
|---|---|---|---|---|---|---|
| Submitted | GRANT-2026-041 | 04 Nov | 120 | IRB-2026-114 | Laboratory assay validation | |
| Submitted | GRANT-2026-052 | 19 Oct | 230 | IRB-2026-127 | Participant recruitment protocol | |
| Submitted | GRANT-2026-063 | 11 Oct | 80 | ETH-2026-038 | Laboratory assay validation | |
| Submitted | GRANT-2026-074 | 02 Nov | 140 | ETH-2026-044 | Water sample field collection | |
| Submitted | GRANT-2026-085 | 27 Oct | 70 | IRB-2026-152 | Laboratory assay validation |
Keep scoped attachments and independent decisions tied to a package revision.
Record attachments
| Parent | Title | Evidence type | Visibility | Uploaded at | Uploaded by | |
|---|---|---|---|---|---|---|
| Baseline survey development | Approved study protocol | Ethics approval | Shared | 18 Oct | Mina Varga | |
| Baseline survey development | Consent form, version 3 | Consent form | Shared | 03 Nov | Leo Fischer | |
| Laboratory assay validation | Field sampling log | Field log | Shared | 13 Oct | Leo Fischer | |
| Community findings workshop | Assay validation report | Lab report | Shared | 14 Oct | Priya Nair | |
| Interview coding framework | Interview codebook | Analysis memo | Shared | 26 Oct | Nadia Rahman |
See work package progress, task effort, reviews and operation exceptions across organizations.
Operation receipts
| Parent | Action | Expected revision | Result state | Occurred at | Failure reason | |
|---|---|---|---|---|---|---|
| Interview coding framework | Submit ethics packet | 750 | Failed | 02 Nov | Ethics approval has expired | |
| Water sample field collection | Approve field protocol | 280 | Needs review | 17 Oct | Consent form version is outdated | |
| Interim data analysis | Request data correction | 390 | Failed | 03 Nov | Field log is incomplete | |
| Participant recruitment protocol | Accept milestone evidence | 310 | Needs review | 21 Oct | Assay controls are missing | |
| Participant recruitment protocol | Record grant decision | 260 | Failed | 11 Oct | Reviewer conflict is unresolved |
Work package to reviewed milestone ships ready to use. 2 steps need a named approval before the work moves on: Evidence review (Independent Reviewer) and Milestone approval (Independent Reviewer).
Link each package to its research organization and funded project.
Set the owner, due date, hours and task sequence.
Record completed work and actual effort against the plan.
Bring the package revision and supporting files to an independent reviewer.
Submit grant details against the supporting package.
Record the reviewer decision before completion.
Open any work package to see its operation receipts, the roles that work on it, its process stages and its approvals on one page.
Owner, Counterparty, Due at and Budget hours.
Each line is linked to this work package.
Admin, Research Coordinator and Package Owner, each with their own permissions.
Project scope and Package plan, with the role that acts.
Evidence review and Milestone approval, with who decides.
Wetland restoration monitoring · Planned
| Parent | Action | Expected revision |
|---|---|---|
| Interview coding framework | Submit ethics packet | 750 |
| Water sample field collection | Approve field protocol | 280 |
| Interim data analysis | Request data correction | 390 |
Signed in as Independent Reviewer
| Decision | Approver | |
|---|---|---|
| Evidence reviewBring the package revision and supporting files to an independent reviewer. | Independent Reviewer | |
| Milestone approvalRecord the reviewer decision before completion. | Independent Reviewer | |
| Approve work packages, research milestones | Independent Reviewer |
Everyone opens Research Projects PM to the work that is theirs. Pick a role to see what it starts with.
Maintains organization membership and access to research records.
Coordinates package plans, progress and review handoffs across a research organization.
This is the first screen this role sees.
Work packages · Research Coordinator
Owns the work package plan, task progress and evidence for assigned work.
This is the first screen this role sees.
Work packages · Package Owner
Decides whether a package revision and its supporting evidence can proceed.
This is the first screen this role sees.
Research milestones · Independent Reviewer
| Status | Grant reference | Due at | Completed studies | Approval reference | Parent | |
|---|---|---|---|---|---|---|
| Submitted | GRANT-2026-041 | 04 Nov | 120 | IRB-2026-114 | Laboratory assay validation | |
| Submitted | GRANT-2026-052 | 19 Oct | 230 | IRB-2026-127 | Participant recruitment protocol | |
| Submitted | GRANT-2026-063 | 11 Oct | 80 | ETH-2026-038 | Laboratory assay validation | |
| Submitted | GRANT-2026-074 | 02 Nov | 140 | ETH-2026-044 | Water sample field collection | |
| Submitted | GRANT-2026-085 | 27 Oct | 70 | IRB-2026-152 | Laboratory assay validation |
Owns grant milestone submission and follows its decision trail.
This is the first screen this role sees.
Research milestones · Grant Manager
| Status | Grant reference | Due at | Completed studies | Approval reference | Parent | |
|---|---|---|---|---|---|---|
| Submitted | GRANT-2026-041 | 04 Nov | 120 | IRB-2026-114 | Laboratory assay validation | |
| Submitted | GRANT-2026-052 | 19 Oct | 230 | IRB-2026-127 | Participant recruitment protocol | |
| Submitted | GRANT-2026-063 | 11 Oct | 80 | ETH-2026-038 | Laboratory assay validation | |
| Submitted | GRANT-2026-074 | 02 Nov | 140 | ETH-2026-044 | Water sample field collection | |
| Submitted | GRANT-2026-085 | 27 Oct | 70 | IRB-2026-152 | Laboratory assay validation |
Examines package progress, task effort, receipts and exception records.
This is the first screen this role sees.
Work packages · Operations Analyst
Ask concrete questions about package progress, task effort, milestones and exceptions.
This quarter
How far records got this quarter
| Stage | Reached | Step | |
|---|---|---|---|
| Draft | 45 | ||
| Planned | 18 | 40% | |
| Active | 5 | 28% | |
| Review | 1 | 20% |
Sample totals per stage
Which packages are planned, active, in review or accepted for each owner and funded project?
Show due dates and current status for each work package.
Where does recorded effort differ from the plan within a package?
Which submitted grant milestones need an independent decision before their due date?
Show grant references, completed studies and milestone status.
Which package revision was approved, rejected or returned, and why?
Show attached evidence by package and visibility.
Which receipts need investigation and what parent package do they affect?
See how Research Projects PM fits your kind of team.
Coordinate funded study work across research groups and independent review.
Follow multi-team research work from package plan to evidence decision.
Keep participating organizations and funded work packages distinct in a shared operating view.
Each stage of work package to reviewed milestone names the role that acts and the status it records, so a change is never anonymous.
Each stage, the role that acts and the status it records
Use Proto to prepare research project records and bring decisions to the right people.
Set up connections through ERP.AI and Proto workflows, with every change logged.
Every record lives in a table you can see, extend and export. Add fields or whole tables in Proto.
Browse all 10 tablesStart with one team and one process, then add the rest once the basics are running.
Create the active research organization, funded project and team members linked to platform users. Confirm time zones and ownership.
Enter a package with a record number, subject, due date, budgeted hours and responsible member. Add task lines and inspect dependencies.
Record task progress, attach evidence with deliberate visibility and have an independent reviewer decide on the current package revision.
Add a milestone under the package with its grant reference, due date, completed studies and approval reference. Rehearse submission and decision.
Open Operations Overview and investigate a review backlog item and an operation exception using the linked records.
$0per user
The base account and everyday work in the ERP.AI app are free, for every user.
| Usage | Per $1 |
|---|---|
| Record reads (list, filter, get) | 20,000 |
| Search or aggregate queries | 4,000 |
| Record writes | 4,000 |
| Imported or synced records | 200,000 |
| Workflow runs | 2,000 |
| AI agent runs | 2,000 |
| Scheduled jobs or webhooks | 20,000 |
| File uploads (MB) | 2,000 |
| CSV or PDF exports | 100 |
Click Get started, then use Proto to configure PM for Research Projects for your business. Begin with one research organization, one funded project, a work package with dependent tasks, and an independent review of its evidence.
A work package identifies a bounded piece of research work with an owner, funded project, due date, budgeted hours, revision and lifecycle status. Tasks, milestones, attachments and decisions connect back to it.
Link the package to its research organization and funded project, then assign an active team member from the correct organization. Use the package record number when discussing the work.
Yes. Task lines record planned and actual hours under a work package. Review the line details when the comparison changes a scope or acceptance discussion.
Each task can record predecessor information along with its line number and revision. The owner and coordinator should inspect the sequence before work begins and after a scope change.
An independent reviewer records an Approve, Reject or Return decision with a reason against a package revision. The coordinator checks completed task progress before package acceptance.
The grant manager submits a milestone linked to its parent package. The reviewer checks the grant reference, due date, completed studies, approval reference and supporting package revision before a decision.
Attachments carry Internal or Shared visibility. Decide who can make that choice and review the setting when files are added or corrected.
An operation receipt keeps its action, expected revision, result state and references. The analyst compares its linked effects and any agreed external source, then keeps a discrepancy visible for review.
Operations Overview shows the package lifecycle, review backlog, recorded operations, planned versus actual task hours and exception queue across organizations.
Start free, then use Proto to change fields, steps and approvals before your team goes live.