> For the complete documentation index, see [llms.txt](https://portavi.gitbook.io/portavi-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://portavi.gitbook.io/portavi-docs/governance/assumptions.md).
# Assumptions
What the plan takes for granted, how sure you are, and when you will check.
An assumption is something the plan takes to be true without proof: that a vendor will deliver in March, that a team will be free in November, that a price will hold. Writing it down, with a date to check it, turns a hidden risk into one you can watch.
## Where assumptions live
An assumption belongs to exactly one **project** or one **programme**, and is never shared between them. You manage them from that entity's **RAID** tab, on **Assumptions**, and see every assumption in the workspace in **Governance → Assumptions Register**.
## Logging an assumption
From **RAID → Assumptions**, select **Log an assumption**:
* **Assumption**: the statement, in a sentence
* **Why we assume it**: what it rests on
* **Confidence**: low, medium or high. Low confidence is the one to check first
* **Check by**: the date by which you will know whether it holds
* **Status**: unvalidated, valid or invalid
* **Category** (optional): schedule, budget, technical, scope, resource or external, the same six as risks
* **What the check found**: the evidence, once you have it
Whoever logs an assumption **owns** it.
## Checking an assumption
Open an assumption and use the status pill at the top to mark it **valid** or **invalid**. Note what the check found, so the record shows why. Marking it unvalidated again puts it back on the list to check.
An assumption is **due a check** while it is unvalidated and its check-by date is today or past. It then:
* shows its check-by date in red on the card
* puts a dot on the RAID tab and on the **Assumptions** toggle
* appears under **Assumptions to check** on its owner's [My Focus](/portavi-docs/tracking-delivery/my-focus.md), where **Validate** and **Invalidate** settle it without leaving the page
* appears in its owner's weekly briefing email
* is counted on Governance's [RAID dashboard](/portavi-docs/governance/raid-log.md#the-raid-dashboard)
## When an assumption proves invalid
If the plan rested on something untrue, something now has to change. An invalid assumption that has not raised anything yet offers two buttons in its preview:
* **Raise a risk**, if it might now cause trouble
* **Raise an issue**, if it already is
Either opens that register's form in the same project or programme, filled in from the assumption: its statement as the title, what the check found as the description, and its category. Edit it and save. The assumption then names the risk or issue it raised, and the offer goes away. Deleting that risk or issue keeps the assumption.
Until it raises something, an invalid assumption stays on the [RAID dashboard](/portavi-docs/governance/raid-log.md#needs-attention).
## Who can edit
The owner of the project or programme it sits in. Executives read assumptions on Governance, not on a project's or programme's page.
## The Assumptions Register
**Governance → Assumptions Register** lists every assumption in the workspace, read-only. Search it, group it by project or programme, confidence, status or category, and sort it by check-by date, confidence or when it was logged. Unvalidated assumptions come first.
On the timeline, an unvalidated assumption shows **Assumption check due** on its check-by date, and an invalid one **Assumption proved invalid** on the day it was marked so.
