1. Research Projects PM
  2. Features
  3. Projects and organizations
Feature · Projects and organizations

Projects and organizations

Keep each funded project, research organization and staff membership tied to the work they own.

OverviewPackages Awaiting Review
Research Projects PM · Projects and organizations

Packages Awaiting Review

Acceptance waits for the research coordinator

New
Record numberSubjectStatusRevisionOwnerDue at
WP-87949Review wp-805Review36021 Oct
WP-17304Review wp-288Review80009 Oct
WP-82383Review wp-700Review9017 Oct
WP-13077Review wp-191Review10003 Oct
WP-82149Review wp-513Review46020 Oct
6 of 6 records
Review wp-805Work packages · WP-87949
Review
Revision360
Due at21 Oct
Example screen with sample data

What you can do

Establish the research context

An organization owns the research work. Admin records its name, code, time zone, currency and active state before a coordinator opens work against it. A funded project belongs to that organization and acts as the counterparty for each work package. Its contact name, address and eligibility note give the team a common place to check which project a package belongs to. A project can be marked active while work continues under it.

Team membership links a person to an organization and a platform user. The member record carries a role name, time zone and active state. Keep that membership current before assigning a package owner or reviewer. The relationship matters when work crosses organizational boundaries: the package, milestone and member must point to the intended research organization.

How the work is organized

  • Organization. Admin keeps the identity and operating context for the research unit that owns the records.
  • Funded project. Research Coordinator selects the project that will be the package’s counterparty and checks the eligibility note with the grant team.
  • Membership. Admin maintains the member linked to a platform user, so assignments and reviewer records identify a person.

What to agree during setup

Agree which organization owns each funded project and how the team uses project codes. Decide who updates the project contact and eligibility note when funding terms change. Set the organization’s time zone before staff compare due dates or review decisions across locations. The currency selection belongs to the organization; task hours remain effort, not an amount of money. Make an explicit access plan for staff who work with more than one organization.

Decide how an inactive project or team member should be handled in the operating routine. Existing records still need a readable owner and counterparty, while new assignments need a current member. Research Coordinator and Admin should rehearse a project correction before the first operating cycle, including the effect on already planned packages.

Check the handoff on an actual case

Suppose a team starts a funded materials study at a second research organization. Admin records that organization’s code and time zone, then adds the project and its contact. The Package Owner is linked to the new organization through Team Members. Research Coordinator opens the package and checks that its organization and counterparty resolve to the same research unit. If the project was selected from the old organization, correct that relationship before tasks or evidence are added.

Then ask an Independent Reviewer to find the owner and project from the package. The reviewer should be able to tell which project funded the work and which organization is responsible for it without relying on the package subject alone. That is the useful test of the handoff.

What your team sees

  • Active Work Packages — Current package work with owner, funded project and due date in one list.
  • My Work Packages — Assigned packages a person can take into their daily planning review.

Follow the work through

Continue with package planning and use the data model when preparing project and member records.

What it keeps track of

Data model
Organizations
Research organizations that own projects, work packages and research milestones.
Projects
Funded research projects acting as the counterparty for work packages.
Team members
Staff membership linking a platform user to an organization and role name.
Users
Users
Work packages
Baseline and accepted units of research work with budgeted hours and revisions.

Who uses it

Permissions
Admin
Maintains the organization and memberships; Research Coordinator checks project scope; Package Owner accepts an assignment; Independent Reviewer uses those links when checking a decision.

Set up Research Projects PM your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started