Jakten Risk User Guide

Document ID: M17-CERT-001-D12

Audience: Risk analysts, estimators, project managers, and reviewers

Last updated: 2026-08-12

Applies to: Jakten Platform 2.0

1. What Risk does

Jakten Risk turns an Estimate Version into decision support for uncertainty and contingency. The integrated workbench combines estimate uncertainty, dependencies, line risks, discrete risk events, Monte Carlo simulation, comparisons, and executive reporting.

Risk does not replace the estimate source. It analyzes the selected Platform Estimate Version and preserves saved analytical results as the basis for reports and cross-version comparison.

2. Open the correct workspace

Before opening Risk, confirm:

• Jakten Risk is enabled for the company and assigned to the project.
• You hold a Risk seat and have project access.
• The project Overview has the intended working Estimate Version selected.

Open the project, then select Risk. Risk opens on the last workbench tab used in the current session, or Settings on first integrated launch. Use Back to Platform to return to the project.

The Risk workbench tabs are Settings, Estimate, Dependencies, Register, Events, and Results. Save and Run remain available across the workbench.

3. Recommended workflow

1. Review simulation and project defaults in Settings.
2. Load or review the estimate basis in Estimate.
3. Model relationships in Dependencies.
4. Enter line-level uncertainty in Register.
5. Add discrete project risks and opportunities in Events.
6. Run a quick scan or full analysis.
7. Review funding, exposure, sensitivity, and comparison results in Results.
8. Save and export the appropriate report.

You can revisit any step. When a change invalidates saved analysis, Risk shows that a rerun is required rather than presenting old results as current.

4. Settings

Use Settings to confirm simulation behavior and project defaults before the first run. Project defaults include the risk-potential bands and dependency strengths used by editing tools.

Change defaults deliberately: they affect how new or updated modeling inputs are interpreted. Existing saved results remain evidence of the settings used when they were created.

5. Estimate

The Estimate tab is the cost basis for the simulation.

Available actions include:

• Add Row for manual estimate input
• Bulk Edit for repeated changes
• Import Estimate for spreadsheet or CSV input
• Export Estimate for a working extract
• Clear Filters to return to the full grid

In an integrated project, prefer the Platform/Estimate publication offered in the workspace. Review mapped columns, row identity, WBS, cost type, and uncertainty values before accepting an import. A completed Risk simulation is tied to its estimate basis; material estimate changes require a new run.

6. Dependencies

Use Dependencies to model correlation among estimate packages or groups.

Select Apply Dependencies after review. Resolve diagnostics before relying on a full simulation. A dependence matrix that is incomplete or invalid can materially change the distribution.

7. Register and Events

Use Register for uncertainty or risk treatment attached to estimate lines. You can bulk edit, import, export, and filter the register.

Use Events for discrete project risks and opportunities that are not represented adequately as line uncertainty. Select Add Event, enter probability and impact information, and keep the event description specific enough for a reviewer to understand the modeled basis.

Avoid counting the same exposure in both the line register and an event unless the two entries intentionally represent different effects.

8. Run analysis

Use the global Run command or the actions on Results.

Risk performs readiness checks before analysis. If the review panel identifies blocking inputs, open the first affected tab, correct the issue, save, and run again. Do not treat a quick scan as the final report basis.

9. Read the Results workspace

Results can include:

• Cost distribution and cumulative confidence curves
• Selected funding position and exceedance probability
• Contingency bridge and source attribution
• Sensitivity and major uncertainty drivers
• Dependency, register, event, and schedule exposure
• Scenario comparisons
• Estimate-Version evolution and changed-line drivers

When a result or comparison says Unavailable, the required saved analytical basis is missing. Run and save the necessary analysis; do not interpret unavailable as zero.

10. Export and share

From Result Actions, choose:

Wait for the export to finish before closing Platform. Review the project name, Estimate Version, scenario, target confidence, and analysis date before distributing a PDF.

11. Common problems

Related documentation