Events tab
Sync reads new documents, and the review queue holds every proposed change until the project lead approves or dismisses it.
The Events tab is where new information enters the project. Sync reads documents into proposed changes, and the review queue holds those changes, and any change someone stages, until the project lead decides. The tab's number is the count of rows waiting for review.
Sync
The Sync bar sits at the top of the tab.
- Beside the button it says how many documents are new since the last sync (for example "2 documents new since last sync"), or Up to date.
- Click Sync to read every document the project has not read yet, or that changed since.
- While it runs, a list shows each document as Queued, Reading, Read (with what it changed) or Failed (with why). Stop ends the run; the next Sync reads what is left.
- When it finishes, one line sums it up. What each document changed lists each document's effect, for example "answers DEC-015; adds 2 tasks; 1 conflict".
Sync keeps running if you switch tabs. Running it twice never reads a document twice. Sync calls an AI model for each document, so it is not free; read a document again on purpose only when you need to (Read again, on the Knowledge tab).
A project created from a scoping handoff can show Import from scoping once. It copies discovery, estimate and contract dates into Events without AI.
The review queue
Project and Config
The queue has two sub-tabs, each with its count:
- Project: tasks, questions, decisions, milestones, deliverables, RAID, agreements, people and baseline changes.
- Config: changes to the system build (plans, components, interfaces, build objects, test cases).
Grouped by document
Rows are grouped under the document they came from. The Documents list on the left filters to one document, or All documents. You can also filter by Source.
Each document's header sums up what it holds, for example "Scope 1 in, 3 out · Commercial 7 · Plan 3 milestones, 7 deliverables · Risks 2".
Within a document, rows sit under their area: Scope & terms, People, Plan, Work, Risks, Requirements, Build and Needs a look.
What a row shows
A row reads: a coloured dot, the type, the item's reference and title, then what changes. For example "120% → 115%", "+ new" or "+ 2 options". A red dot means the change contradicts the plan. An amber dot means a date or a decision moves. A row that changes a signed document is tagged SOW or BRD.
Needs a look
Needs a look holds rows Infra could not place on its own:
- A Which item? row: Sync found something but is not sure which existing item it is about. Open the row and pick the item in the pane. It then comes back as a normal change to approve or dismiss.
- Rows from the weekly data check (see Management).
Review a row
Only the project lead or an admin can approve or dismiss. Others see "Only the project lead can approve or dismiss."
- Click a row. The item pane opens beside the list with the Change (each field before and after), its Source quote, History and Related items.
- To fix a detail first, use Edit before approving in the pane. Your edits are approved with the row.
- Click Approve or Dismiss.
Approving a row applies everything that travels with it in one step. The row leaves the list and the next one is selected.
Keyboard: ↑ and ↓ move between rows, A approves, D dismisses. Clicking the open row again, ✕ or Esc closes the pane.
Review many rows at once
- Approve group and Dismiss group review every row in one area of a document.
- Approve all and Dismiss all review every row shown.
Each asks you to confirm with a second click first ("Approve all 12?"). A "Which item?" row is approved only after you pick its item.
Stage a change by hand
Stage a change adds one change through the same queue. Use it when you learn something that is not in a document yet.
- Click Stage a change.
- Under What, pick the type: requirement, deliverable, milestone, decision, test case, meeting, RAID item, agreement, a system build item, a link between two items, or the project's dates.
- Under Change, pick Add, Update or Retire, and fill in the fields. An update sends only the fields that changed.
- Add Why: one sentence a reviewer can check.
- Optionally pick a Source document and paste a Quote from it, word for word. Infra finds the quote in the document so the change carries a real citation.
- Click Applies now (you are the lead) or Stage for review (anyone else).
Project status and progress follow the milestones, so you cannot set them here.
Where else changes come from
Suggest filing on the Items tab, the plan follow-ups of a decision, a phase template, the project agent and outside agents all put their changes in this same queue. See Changes and review.