Questions, answered

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.