Engineering Workspace / Before the pour
In depth

Before the pour

The pouring plan is the one date on a construction site that does not move. This holds every pour against the approvals that must exist before it, and warns you while there is still time to chase.

The board that watches the dates that cannot slip

Import the pouring plan you already keep — or paste it out of the spreadsheet. Every pour and every watched installation activity is set against the shop drawings and material submittals that must be approved before that date. You choose how many days early you want to be told; from then on the board answers one question, every morning: what is coming, and is the paperwork ready for it.

Import an xlsx pouring plan, or paste the rows straight in — the date column finds itself
You set the lead: flag me 7, 14, 21 days before the pour
States that mean something: ready, watching, at risk, blind — and passed, which is the one you never want to see
The board that watches the dates that cannot slip
How it knows which drawing belongs to which pour

How it knows which drawing belongs to which pour

This is the part that is easy to get wrong and dangerous to fake. Location tokens are read from the pour and from the document by the SAME extractor — L21, B2, Zone A, Podium, Roof — so a match is a real overlap of words, not a guess. Then the kind of event decides what counts: a concrete pour needs the drawings that carry the cast obligation, while an installation needs the material submittals for the systems it names. Every row shows the reasoning that produced it, so you can disagree with it.

One extractor reads both sides — the same token means the same thing everywhere
Cast events demand cast drawings; installation events demand the materials for the systems they name
Documents that merely touch the location are shown dimmed and honestly labelled, never counted as cover

Your judgement outranks the matcher — and survives the next import

An engineer who links a drawing to a pour by hand is stating a fact the software cannot infer. That link is kept. Re-import the revised pouring plan next month and the human decisions ride through it untouched; only the dates and the machine matches are recomputed. The same is true of a dismissal: tell it that a pour needs nothing and it stops asking.

Confirm or dismiss any link by hand — it is remembered against the reference, not the row number
Re-importing a revised plan never erases a person's decision
The daily check rings once per date and per missing document — never a second time for the same news
Your judgement outranks the matcher — and survives the next import
Every capability, declared

The complete list.

Everything the board does, plainly.

Getting the plan in

Import xlsxThe pouring plan as your planner keeps it. Columns are found by content, not by header text, so a renamed sheet still imports.
Paste itNo file needed — paste rows straight from the spreadsheet.
Merged by referenceRe-import updates the pour that already exists rather than creating a twin.
Watch an activityAny programme activity can be watched too, not only concrete — risers, ductwork, anything with a paperwork gate.

What it reads

The deliverables listShop drawings and their approval state, live.
The registersShop-drawing and submittal registers — which matters, because many projects keep the record there and nowhere else.
Approval states, honestly rankedReturned outranks approved outranks in-review outranks pending — a returned drawing is not cover.
Systems vocabularyChilled water, fire fighting, drainage and the rest, so an installation event knows which submittals belong to it.

What it tells you

Countdown per eventThe date, and the days between now and it.
Required list with statesEach document named, with the state it is actually in.
Visible reasoningWhy this document was matched to this pour — always shown, never hidden.
At risk before it is lateThe flag fires at your chosen lead, not on the day.
Blind, and said out loudA pour with nothing linked is reported as unknown rather than quietly reported as fine.

Staying on it

A daily checkRuns each morning by itself; the bell rings once per new gap.
Deep linkThe notification opens this board on the event that caused it.
DismissAn event that genuinely needs nothing stops asking.
Nothing is sent anywhereLike everything else here, it recommends — it never writes to your registers or your mail.
Against the field — the pour gate
Approvals held against the pouring plan, flagged days early
A document register and a programme that never speak
Location and trade matched by the same extractor on both sides
A person remembering which drawing covers which slab
The engineer's manual link outranks the machine and survives re-import
A matching rule you cannot correct, or a spreadsheet you must rebuild

"The field" is the usual toolchain — the per-user construction cloud and the separate applications around it. Good tools; the difference here is one integrated record, on your own server.

See it on a live workspace.

A real account inside a realistic demo project — request it in one minute.
Try the live app →
← Registers & ClaimsSearch & Ask →