Engine chains
Engines feed each other. There are 51 automated chain connections between the 19 engines — some carry data forward automatically, others just suggest the next step.
What a chain is
A chain is a pre-defined relationship between two engines that says "after running A, the natural next step is B." Some chains are just suggestions — they open engine B with you picking the inputs. Others carry data forward — engine A's output auto-populates engine B's input, so you don't have to re-upload.
Where they appear
- Bottom of every engine result: the most common chain destinations as clickable buttons.
- Platform Atlas graph: /how-trueleveler-works shows all 51 edges as an interactive graph. Solid lines = suggestions; dashed lines = data carries forward.
- Engine docs pages: every engine's page has a "Chains" section listing its inbound + outbound connections.
The two types
Clicking opens the target engine with a blank slate. You pick the inputs. The chain is just "this is a logical next step."
Clicking opens the target engine with input pre-loaded from the source engine's output. E.g., Contract Review → COI Tracker carries the contract's insurance requirements forward so you can compare COIs against them.
Common chain paths
A few high-value flows:
- Pre-Award: RFQ Generator → Bid Leveling → Contract Review → PM Handoff
- Pay app audit: Contract Review → Pay App Review → Owner Report
- CO management: Contract Review → Change Order Review → Negotiation
- Submittal management: Submittal Extractor → Submittal Tracker → Procurement Tracker
- Insurance: Contract Review → COI Tracker (carries requirements)
Interactive graph
The Platform Atlas interactive chain graph is the best way to explore. Click any engine node to see its inbound + outbound connections highlighted, with the solid/dashed distinction rendered.