Meeting Input is the central data entry point. Paste any raw text - meeting minutes, status emails, site visit reports, change request documents - and an AI engine reads it and populates the relevant sections automatically. You review everything before it touches your data.
| Category | Trigger phrases (examples) | Goes into |
|---|---|---|
| Decisions | Any clear statement of a decision made | Decision Log (09) |
| Actions | Owner + task + deadline combinations | Decision Log - standalone |
| Risks | "risk", "might", "concern", "exposure" | Risk Register (08) |
| Budget - allocated | "budget of", "approved at", "cost plan" | Budget (04) - Allocated |
| Budget - spent | "we have spent", "actual to date", "invoiced" | Budget (04) - Spent |
| Budget - forecast | "expecting to spend", "projected cost" | Budget (04) - Forecast |
| Schedule impacts | Date slippage, revised date, new deliverable | Schedule (05) & Timeline (07) |
| Issues | "problem", "issue", "defect", "blocker" | Issue Tracker (11) |
| Change requests | CR number, variation order, scope change | Change Log (10) |
| Assumptions | "assuming", "we assume", "if X happens" | Assumptions Log (03) |
| Dependencies | "blocked by", "can't start until", "waiting for" | Dependency Tracker (12) |
"3 weekends of validation starting 5 July" produces three separate Schedule entries with individual dates - not one collapsed line.
After extraction, every item is shown with a checkbox. All are selected by default. Deselect anything that isn't relevant before committing. Toggle all on or off at once with the header checkbox.
Every extraction is tagged with a batch ID. The Undo button removes all items added in the most recent extraction - and only those. Items added manually, or from earlier extractions, are untouched.
If a field isn't present in the notes, it's left blank. The extraction only produces items actually supported by the text.
The top-level view across all your projects simultaneously. Pulls live data from every project and presents it in one place - no project-switching needed.
The command centre switches context and takes you to the Project RAG Summary for that project.
The at-a-glance health check for the current project. Set the overall Quality (Green / Amber / Red) using the colour buttons in the top-right corner of the card - this is a manual judgement call, not auto-calculated.
See How Meeting Input works above for the full breakdown. Supported input: meeting minutes, status emails, change request documents, site visit reports, or any plain text.
"Next Friday" or "end of next week" are converted to absolute dates based on today's date at the time of extraction.
A register of things the project is assuming to be true. Assumptions that turn out to be wrong are a common source of unmanaged risk - this log makes them visible and actionable.
| Field | Description |
|---|---|
| Text | The assumption itself, stated plainly |
| Impact if wrong | What breaks - cost, schedule, scope - if the assumption turns out false |
| Owner | Who is responsible for validating this assumption |
| Last validated | When it was last confirmed to still hold |
| Status | Unknown · Valid · At Risk · Broken |
Click the status label to cycle. Items are grouped by status with Broken at the top.
Any assumption at At Risk or Broken status shows a ⚠ button. Clicking it creates a new High priority risk using the assumption text and impact - no re-typing required.
Trigger phrases: "assuming", "we assume", "this depends on", "if X happens", "assuming the vendor", "assuming we get approval".
Track budget by line item - typically one line per supplier, contract, or cost centre. Three amounts per line give a clear picture of where money stands.
| Field | Meaning |
|---|---|
| Allocated | What has been budgeted, approved, or contracted for this line |
| Spent | What has actually been paid or invoiced to date |
| Forecast | What is projected to be spent by completion |
Total rows at the bottom sum all three columns. Variance = Forecast minus Allocated. Edit any line with the ✏ button alongside the delete button.
The AI distinguishes amounts by language: "we have spent £1.6M" → Spent. "Budget approved at £2M" → Allocated. "Expecting to spend £500k" → Forecast. Only the relevant field is populated; others stay at zero.
The milestone list view - the same data that powers the Gantt, in table form. Use this to scan dates quickly or add a new milestone with full detail.
| Field | Description |
|---|---|
| Name | Milestone or deliverable name |
| Planned date | The original baseline date |
| Forecast date | Current expected completion date |
| Actual date | Date completed (if done); triggers Completed status on the Gantt |
| Owner | Person or team responsible |
| Status | On Track · Slipping · At Risk · Completed · Blocked - or blank to auto-calculate |
| Blocker | What is preventing completion |
| Notes | Context, references, caveats |
A monthly calendar that aggregates key dates from across the project automatically. Navigate months using Prev / Next buttons.
Dates are read live from the source sections - no duplication needed.
A scrollable horizontal Gantt chart built from the same milestone data as the Schedule. The visual layer makes slippage and patterns immediately legible in a way a list cannot.
| Element | Meaning |
|---|---|
| Grey tick mark | Planned (baseline) date |
| Coloured bar | The span between planned and forecast, coloured by status |
| Coloured tick mark | Forecast date (right end of bar) |
| Gold diamond ◆ | Actual completion date (if recorded) |
| Variance label | e.g. "+12d", "3d early", "on time" |
| Status label | Right-aligned, coloured to match bar |
| Gold vertical line | Today |
Leave the Status field blank and the Gantt calculates it:
Manually set Completed or Blocked always overrides the calculation.
Click any milestone row to open a detail panel beneath the chart showing the full milestone details plus three live summaries from the rest of the project: open actions (not Done), open risks (not Closed), and at-risk dependencies (At Risk or Blocked). Click the row again or ✕ to close.
Use ← Prev and Next → to shift the view by one month. ⊙ Show all resets to an auto-fitted view covering the full data range.
A standard risk log with lifecycle tracking. Risks are listed in order of entry. Closed risks remain for audit purposes but are visually separated.
| Field | Description |
|---|---|
| Title | Short name for the risk |
| Impact | What happens if the risk materialises |
| Likelihood | High / Medium / Low |
| Owner | Who is managing mitigation |
| Mitigation | What is being done to reduce the risk |
| Deadline | When mitigation must be in place |
| Status | Open · In Progress · Closed |
Click the status text to cycle. The ✓ button jumps directly to Closed. Status text is colour-coded: blue for Open, amber for In Progress, green for Closed.
The AI populates Title, Impact, Likelihood, Owner, Mitigation, and Deadline where stated. Status defaults to Open.
A record of project decisions with accountability built in. Decisions can have actions attached directly to them, keeping who-does-what-by-when linked to the reasoning behind it.
| Field | Description |
|---|---|
| Decision text | What was decided |
| Approved by | Who made or approved the decision |
| Date | When the decision was made |
| Cost impact (£) | Financial implication if any |
| Schedule impact | Time implication if any (e.g. "2 weeks") |
Each decision card has a + Action button. Actions added this way are linked to that decision. Fields: action text, owner, deadline, status (Not Started / In Progress / Done), % complete, blocker.
Actions from Meeting Input that aren't linked to a decision appear in a Standalone actions section at the bottom. Each has a Move button to link it to a decision and optionally update the owner and deadline at the same time.
When any action is past its deadline and not Done, a red banner appears at the top. When actions are due within 5 days, an amber banner appears. Both also surface on Section 01 (Project RAG Summary) and Section 00 (Portfolio Dashboard).
A formal register for change requests and variation orders. Keeps scope control visible and auditable throughout the project.
| Field | Description |
|---|---|
| CR ID | Change request number or reference (e.g. CR-012) |
| Title | Short description of the change |
| Category | Type of change - scope, design, regulatory, etc. |
| Description | What has changed and why |
| Cost impact (£) | Additional or reduced cost |
| Schedule impact | Time effect on the programme |
| Drawing refs | Specification or drawing numbers affected |
| Status | Pending · Approved · Rejected |
If notes include a CR number, variation order reference, or formal scope change, Meeting Input extracts all available fields including cost impact, schedule impact, and drawing references.
A running log of operational problems that need resolution. Distinct from risks (potential events) - issues are things that have already happened and need addressing.
| Field | Description |
|---|---|
| Title | Short name for the issue |
| Impact | What it is affecting - schedule, quality, cost, safety |
| Owner | Who is resolving it |
| Deadline | When it must be resolved |
| Blocking | Flag: checked if this issue is stopping other work cold |
| Status | Blocking · Open · Closed |
Tracks cross-workstream dependencies - where one piece of work cannot proceed until something else is delivered. Particularly important on multi-supplier or multi-team projects.
| Field | Description |
|---|---|
| Dependent | The work or workstream that is waiting |
| Blocker | What it is waiting on |
| Blocker owner | Who controls or is responsible for the blocker |
| Impact | What happens to the dependent work if the blocker is late |
| Resolution date | When the blocker is expected to be resolved |
| Workaround | Any interim approach if the blocker can't be resolved in time |
| Status | On Track · At Risk · Blocked |
Any dependency at At Risk or Blocked status appears in the Gantt drill-down panel (Section 07), giving a cross-section view of what is constraining each milestone.
Trigger phrases: "blocked by", "can't start until", "depends on", "waiting for", "critical path", "prerequisite".
On the Project RAG Summary page, the ⬇ PowerPoint button builds a branded status report: a title slide with the overall RAG, the four RAG lamps with key figures and top risks, recent decisions and overdue actions, a milestones table, and a drawn Gantt timeline with status-coloured bars.
On the Portfolio Dashboard, the ⬇ PowerPoint button exports the leadership view: a Portfolio RAG Summary (health, combined budget, open risks, needs attention, plus a colour-coded RAG grid for every project), the portfolio overview table, and the highest-priority risks and pending approvals across all projects.
On the Project RAG Summary page, the ⬇ Excel button downloads one workbook with a sheet per register: Risks, Decisions, Actions (with their linked decision), Issues, Changes, Assumptions, Dependencies, Milestones and Budget. Opens in Excel or Google Sheets; save any sheet as CSV from there if needed.
On the Meeting Input page, after you extract a set of notes, a ⬇ Weekly Meeting Report button appears. It produces a branded, client-ready Word document: meeting date and times (or the time you generated it if none are stated), an attendees table with a blank Role column to complete by hand, a discussion summary, a plain-English meeting summary, an action items table with owners and status (Not Started / In Progress / Completed), the key discussion points and notes, and a conclusion.
Unlike the PowerPoint and Excel exports (which are built instantly from data you already have), the meeting report re-reads your notes as a meeting to draft the summaries and narrative. It counts as one against your extraction allowance, and takes a few seconds longer. It is written in British English. Always review it before sharing with a client.
Your data is stored in this browser by default, so protect it. On the Portfolio Dashboard, ⬇ Download backup saves every project as a single file. ⬆ Restore from backup loads that file on any device: projects with a matching ID are replaced by the backup version, everything else is added alongside.
Cloud sync (optional): the Enable cloud sync button on the same card keys your projects to your login, encrypted, so they follow you automatically between laptop and phone. It is off unless you switch it on, you can disable it anytime, and a one-click control deletes the cloud copy entirely. Documents you upload to the chat are never stored or synced either way.
With sync off there is no copy on any server, so download a backup regularly, the same way you would save an important spreadsheet. With sync on, your cloud copy has you covered.
All exports and backups are generated entirely in your browser.
During the beta period, usage is capped per browser. The limits are generous for normal use.
| Limit | Value |
|---|---|
| AI chat messages | 500 per session |
| Document uploads | 20 per session |
| Maximum file size | 10 MB per file |
The platform uses Clerk authentication. Your account must be on the approved list to access the Command Centre. If you see an "Access Denied" page, contact the team to check your account status.