Changes and review
How a project's plan changes in Infra. Sync, agents and people propose; the project lead decides.
A project's plan is what was agreed: its requirements, deliverables, milestones, decisions, RAID, agreements, test cases and system build. Infra keeps the plan trustworthy with one rule: the plan changes only through changes that someone reviewed.
Where changes come from
A change can come from:
- Sync, which reads new or changed documents and proposes what they change. See Events.
- A person, through Stage a change, an edit in the item pane, or a dialog such as Decide or Move to RAID.
- The project agent, which stages changes when you ask it to. See The project agent.
- A plan follow-up, proposed automatically when someone decides a question. See Questions and decisions.
- An outside agent using an API key or connector. See Connecting agents.
Each change carries its source when it has one: the document and, where possible, the exact quote it came from.
Applied now, or waiting for review
What happens to a change depends on who made it and how:
| Who made the change | What happens |
|---|---|
| The project lead or an admin, by hand | It applies now and is logged. |
| A team member, by hand | It waits for the lead on Events, unless the project uses Team writes directly. |
| Sync, the project agent, a plan follow-up, or an API key | It always waits for review. |
Buttons tell you which will happen. Stage a change says Applies now or Stage for review. A property in the item pane that waits for review shows Waits for lead review.
Tasks are the exception: you edit your own tasks directly on Items, and the edit is logged.
The review setting
On Management, the project lead or an admin chooses who applies a team member's own hand edits:
- Lead reviews (the default): a team member's own edits wait for the lead on Events.
- Team writes directly: a team member's own edits apply at once and are logged.
Sync, the project agent and API keys always wait for review, whatever this setting says. Changes to the setting are logged in History and restore.
Reviewing
Only the project lead or an admin approves or dismisses changes. They do it on the Events tab, row by row or in groups. Approving a row applies every change that travels with it in one step. See Events.
Undoing a change
Every applied change is in Management › History and restore. The lead can revert one change or restore the project to a point in time. Both show a preview first and stop if they hit a conflict. See Management.
What the baseline protects
Some items come from signed documents and are locked:
- Milestones and deliverables from a signed SOW change only through a signed change order. For a later date, the lead pins a forecast instead (Pin forecast in the item pane).
- Requirements in a signed BRD change through BRD amendments, listed on Plan.
A locked field shows a lock in the item pane, with the reason.