Engine chains
An engine chain is a link from one engine's result to the next step. A chain is a button under an engine result that opens the next engine or tracker, and no engine runs until you press Run. Of the 89 chain connections, 19 also pass something on, such as the result's text. The other 70 only open it.
Updated
What is an engine chain?
A chain is a pre-defined link between two engines, or from an engine to a tracker, that says "after running A, the natural next step is B." Clicking it opens B, and an engine runs only when you press Run. Some chains are only that: B opens empty and you pick the inputs. Others pass something on: A's result text is copied into B, so you do not have to upload it again.
Where do chains appear in the app?
Chains appear in three places: after an engine result, in the Platform Atlas graph, and in the Chains section of many engines' help pages. Nine chains start at the Submittal Tracker or the Procurement Tracker; those two open as workspaces and show no next-step buttons, so these nine are on the atlas and in the help pages but have no button in the app today.
- After an engine result: the most common next steps as buttons. Some engines show them as a banner, the others as a row of "What to try next" chips.
- Platform Atlas graph: /how-trueleveler-works draws the chain connections. Solid lines only open the next step; dashed lines also pass something on.
- Engine help pages: many engine pages have a "Chains" section that lists the chains into and out of that engine, with a "Data" mark on the ones that pass something on.
The two types
Clicking opens the next engine or tracker with nothing carried over. You pick the inputs. The chain only says "this is a logical next step."
Clicking opens the next engine with something from the result already in place. Most copy the result's text into the next engine's input, which uses it when you run it there. E.g., Contract Review → COI Tracker carries the contract's insurance requirements so you can check certificates against them. Two work differently: Bid Leveling → Contract Review passes only the winning vendor's name, and Submittal Extractor → Submittal Tracker opens a review list and adds only the rows you tick.
Which chain paths work end to end?
These paths work today. Each step says what it passes on.
- Scope to purchase order: Scope Builder → RFQ Generator (the drafted scopes fill the RFQ's scope box) → Bid Leveling (the RFQ text carries) → Create PO on a vendor card, which opens a purchase order with that vendor's lines filled in.
- From the contract: Contract Review → Contract Summary, Notice Builder, Change Order Review, Owner Report, PO vs Quote or the COI Tracker page. Each click copies the contract's text into that engine.
- Pre-award: RFQ Generator → Bid Leveling carries the RFQ text. Bid Leveling → Contract Review passes only the winning vendor's name, so you upload the contract yourself. There is no chain from Contract Review to PM Handoff: PM Handoff reads the project's latest saved Contract Review, Bid Scope Compliance and Contract Summary when you run it.
- Change orders: Contract Review → Change Order Review carries the contract's text. A Change Order Review run saves the change order in the Change Orders tracker, where Negotiate opens a negotiation session with the amounts filled in and Push to Schedule adds an activity for the delay to the Schedule.
- Submittals: Submittal Extractor → Submittal Tracker opens a review list, and the rows you tick are added to the register. In the tracker, a row's Push to Procurement button fills the procurement item form for you to complete and save.
- Insurance: Contract Review → COI Tracker carries the contract's insurance requirements. Upload the certificates there, then add them to the COI tracker.
Some engines need no chain at all. When you run PM Handoff, Owner Report, Pay App Review, Daily Log Synthesizer, Closeout Builder, Warranty Compiler, Bid vs Actual or Schedule Risk, they read the project's trackers and earlier saved results themselves.
Interactive graph
The Platform Atlas interactive chain graph is the best way to explore. Click any engine node to see its inbound and outbound connections highlighted, with solid lines for links that only open the next step and dashed lines for links that also pass something on.