These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Risk Management
- Features
- Project context
Project context
Read risk beside project dates, work packages and assigned tasks.
OverviewMy project checkpoints×
Risk Management · Project context
New
My project checkpoints
Review checkpoints
| Checkpoint name | Project | Due date | Status | |
|---|---|---|---|---|
| Checkpoint 579 | PRJ-9900 | 14 Oct | Pending | |
| Checkpoint 795 | PRJ-2071 | 16 Oct | Met | |
| Checkpoint 197 | PRJ-9288 | 23 Oct | Missed | |
| Checkpoint 490 | PRJ-1063 | 25 Oct | Pending | |
| Checkpoint 573 | PRJ-5954 | 10 Oct | Met |
6 of 6 records
Checkpoint 579Review checkpoints · RC-27700
PendingProjectPRJ-9900
Due date14 Oct
What you can do
Put exposure in the delivery picture
A risk assessment becomes more useful when the Project Manager can see the project it affects. The project record holds its organization, owner, dates, budget and delivery status. Work packages group delivery activity, and tasks carry individual assignments. The manager can compare an Open risk with an approaching end date, a blocked task or a project already marked at risk.
How the work is organized
- Project. Keep the project name, organization, owner, planned dates and status current.
- Work package. Group related work under its project with an owner and schedule.
- Task. Assign the next action, record priority and follow its working status.
Project, work package and task are separate levels of responsibility. A work package is not a risk treatment by itself, and a task marked Done does not automatically lower risk. The manager reads their combined state at the review checkpoint and asks the Risk Owner whether the mitigation is still credible.
What to agree during setup
Choose how project owners use Planned, Active, on hold, at risk, Completed and Cancelled. Agree when a delivery concern should move the project to at risk. A high risk rating can prompt that conversation, but the status remains a project decision. Define the naming and ownership rules for work packages so that a person seeing a task can trace it to the intended engagement.
Set a practical rhythm for updating task due dates, priority and status. An assignment that remains in progress after its due date belongs in the project review. Decide how the team will record a change to planned end date while keeping the risk and checkpoint discussion understandable.
Check the handoff on an actual case
A project is Active with an end date next month. A Resource risk threatens an important work package. The Delivery Lead assigns a task to find an alternate specialist and sets a due date before the next checkpoint. The Project Manager sees the task, the risk and the project schedule together when preparing the review.
If the task is Blocked, the team can change the assignment or delivery plan while the Risk Owner updates the mitigation. If the date becomes unachievable, the manager can mark the project at risk. That status informs the team about the project; the risk still retains its own assessment and owner. The manager can explain the decision from the linked records instead of treating the project’s rollup counts as the whole story.
What your team sees
- Active Projects — Start the review from current engagements and their owners.
- Task Board by Status — Check the work that may affect the project dates.
- Task Board by Status — See the current distribution of assigned work.
Follow the work through
Use delivery response and risk review to bring work back to the next decision.
What it keeps track of
Data model- Projects
- Engagements delivered for an organization, with budget and schedule.
- Organizations
- Client and internal business organizations that projects are delivered for.
- Work packages
- Groupings of work inside a project.
- Tasks
- Individual pieces of work assigned to a delivery team member.
- Team members
- Delivery staff with role, practice and weekly capacity.
- Risk register
- Project risks with likelihood, impact, owner and mitigation.
- Review checkpoints
- Dated checkpoints a project must meet.
Who uses it
Permissions- Project Manager
- Owns the project decision; Delivery Lead coordinates work; Team Member updates assigned tasks; Risk Owner explains remaining exposure.
Set up Risk Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.