Created by the work, not by you
Open an RFI, receive a submittal, draft a notice — the follow-up task appears with its source linked. Close the source, the task closes.
TRACKER · TASKS
One work queue, fed by every engine.
Tasks aren’t typed in twice. An RFI that needs answering, a submittal where the ball is in your court, a change order awaiting approval — each becomes a task automatically, with the context attached and the deadline that matters.
0
Tasks typed twice
Auto
Created by engines
BIC
Ball-in-court aware
$0
To try
§ 01TASKS
The to-do list builds itself.
Ball-in-court, made obvious
Every task knows whose court it’s in. Filter to "my queue" and see only what’s actually waiting on you.
Deadlines that came from the contract
Response-by dates flow from the engine that created the task — a notice’s cure window, a submittal’s review period — not a date you guessed.
Audio anchors from meetings
A decision in a recorded meeting becomes a task linked to the exact moment in the audio. Click to hear who said what.
START FREE · NO CREDIT CARD
Run your whole project — on one platform.
Every engine output is the next engine’s input. Try the platform free — no card, no implementation call.