Most product descriptions list features. This one follows a single fact through Verian for three days, on the fictional Northgate Terminal project we use for every example: a supplier's letter saying the gate valves will be two weeks late. Everything below is what the platform does with it, in order, and what it leaves to people.
Day 1, 09:14 · The letter is read, and tied to the work it affects
The letter lands in the procurement mailbox that Verian reads. Within the minute it is in the pipeline: the document reader extracts the fact (V-12 gate valves, now week 41, previously week 39), and the matcher ties it to the three things in the record it concerns: activity A-1205 Valve delivery V-12 on the live schedule, clause 14.2 of the supply contract, and milestone M4, mechanical completion, which sits eight days of float downstream.
This is the part people underestimate. Reading the letter is easy. Knowing that it is this activity, that clause and that milestone, on a schedule of 1,284 activities and 2,960 links, is the work, and it is done before anyone has opened their inbox.
Day 1, 09:15 · A risk is proposed, not created
Verian does not add a risk to the register. It proposes one: R-0231, late gate valves, with the letter attached, the activity and clause linked, and its first assessment of the impact (two weeks late on a path with eight days of float, so M4 moves unless something changes). The proposal goes to the person who owns risk on the project, M. Chen, and waits in her queue. Until she accepts it, it is visible, but it is not a risk.
| What Verian did | What it did not do |
|---|---|
| Read the letter and extracted the date change | Change any date on the schedule |
| Linked it to A-1205, clause 14.2 and M4 | Create a risk in the register |
| Proposed R-0231 with an impact assessment | Send anything to the supplier |
| Put the proposal in M. Chen's queue | Decide anything |
Day 2, 10:23 · The question in the review
The weekly progress review runs in Microsoft Teams. Verian is in it as a participant, listening through the live captions and saying nothing. Twenty minutes in, the planner asks: “Verian, what’s driving the risk on mechanical completion?”
L. Ferreira asked, in the weekly review
“Verian, what’s driving the risk on mechanical completion?”
M4 depends on the T-102 hook-up, which has eight days of float. Risk R-0231, late gate valves, sits on that path. The forecast for M4 is 23 November.
Answered with L. Ferreira’s access · figures computed from the record
Sources used
- Rev 13Schedule
- R-0231Risk register
- SUP-0877Supplier letter
Three things happen inside that answer that are worth naming. The float, the path and the forecast are computed by the schedule engine, not written by the language model. The answer is given with the planner's access, which is why it can name the risk and the letter. And it names its sources, so anyone in the room can open Rev 13, R-0231 and SUP-0877 afterwards and see the same thing.
Day 3, 14:02 · Three ways to protect M4
After the review, the planner asks for options. Verian copies the live schedule three times, tries one change on each copy, and re-runs the whole schedule on each: a second crew on the hook-up, prefabricating the spools, and erecting bents 5–8 ahead of T-103. Then it ranks the three by days saved on M4, and says what it did not assess: cost, crews and the contract.
- 1S-3 Erect bents 5–8 before T-103−6 d
- 2S-1 Second crew on the T-102 hook-up−4 d
- 3S-2 Prefabricate T-102 spools off-site−3 d
Copies are sandboxes. Putting one on the live schedule takes a person’s approval.
Day 3, 14:12 · Approval, and a name on the change
The planner picks S-3. The project manager, S. Okafor, sees the proposed change against the current schedule: two activities swap order, M4 moves from 23 November to 15 November. He presses Approve. The change is written as Rev 14, the previous order is kept beside it, and the approval carries his name and the time.
| Time | Event | By |
|---|---|---|
| Day 1 · 09:14 | Letter SUP-0877 read and linked | Verian |
| Day 1 · 09:15 | Risk R-0231 proposed | Verian |
| Day 1 · 11:40 | R-0231 accepted | M. Chen |
| Day 2 · 10:23 | Question answered in the review, 3 sources | Verian, with L. Ferreira's access |
| Day 3 · 14:02 | Three recoveries tried and ranked | Verian |
| Day 3 · 14:12 | S-3 approved · Rev 14 | S. Okafor |
What this took from the team
- One acceptance of a proposed risk, from the person who owns risk.
- One question, asked out loud in a meeting that was happening anyway.
- One request for options, in a sentence.
- One approval, by the person with the authority to give it.
Four decisions, each made by the right person with the figures in front of them, and none of them waiting for a report. The rest of the series looks at the two things that make this possible: how Verian computes figures, and how the 3D model follows the same rule.