For approval · Rev A
Your engineers make the decisions.
Decklog runs the paperwork.
Every comment, query, approval and revision on a newbuild — extracted, filed and traceable. Ship design correspondence becomes a searchable record instead of fourteen inboxes.
01 · The gap
Everything is documented.
Nothing is findable.
2,847
Comments per newbuild
14
Inboxes holding pieces of the record
0
Systems of record
“Three hours to find who approved this change.”
“The yard says we never answered this comment.”
“The client thinks we missed a requirement.”
Class comments, owner remarks, yard queries — a newbuild's technical dialogue lives in email threads, Excel logs and scanned PDFs. When a decision is questioned two years later, finding out who agreed to what, and why, is archaeology. And it's the design office that answers for it.
02 · The unit of work
Every comment. Accounted for.
Six clerical steps an engineer does by hand today. Decklog does five of them. The sixth — sign-off — stays human.
Ingest
Comment sheets, emails, scans. Decklog reads what arrives, as it arrives.
Extract
Every comment becomes a structured record. Quoted, referenced, numbered.
Classify
Discipline, severity, deadline. Filed before a human opens it.
Link
Wired to the drawing, the revision, the rule it cites and the decisions it touches.
Draft
A response is prepared, with citations. Confidence stated, sources shown.
Sign-off
A named engineer approves. One click for the routine. Judgment for the exceptions.
03 · The demo
Watch it clear a comment sheet.
Scripted run · curated data · no live calls
Watch Decklog process an incoming class comment sheet — extraction to sign-off — in about a minute.
04 · Method
AI first. Human by exception.
One comment sheet, start to finish — what Decklog does, and where your engineer comes in.
A comment sheet lands in the project inbox. Thirty-eight comments on the stability booklet, Rev C.
Read and extracted. Every comment quoted, numbered and filed by discipline, severity and deadline.
Linked — to the drawing, the revision, the rule it cites and the earlier decisions it touches.
Thirty-one routine responses drafted, citations attached. Seven flagged for engineering judgment.
Your engineer works the seven, edits two drafts, signs all thirty-eight. A name on every answer.
Twenty-nine minutes after arrival, every comment is closed out and traceable — who raised it, who answered it, what it changed.
Attention, not authority
People are interrupted only when something genuinely needs judgment. The exception applies to attention, never to authority.
Every decision carries a name
Nothing ships on model output alone. Sign-off is human, recorded and permanent.
Provenance on everything
Every extraction cites its source — sheet, page, line. The audit trail is the product.
05 · Next
Ask the project.
Every comment, decision and revision forms a graph. Phase two lets you query it — "why did the WT bulkhead stay at Fr.60?" — and trace the answer, citation by citation.
06 · Who it's for
Built for the design office.
Everyone joins the record.
Design offices
Twenty to two hundred engineers answering to a yard, an owner and class at once. Every comment lands on your desk and every answer carries your name. Decklog makes your office the keeper of the record — without an engineer spending Fridays filing it.
Yards
Technical queries answered in days cost weeks at the block stage. When the yard joins the shared record, the answer is findable before the steel is cut.
Owners & class
Supervision runs on trust in the record. Audit any decision back to its origin — who raised it, who closed it, what it touched.
07 · Where we are
In development. Pilot forming.
Scripted demo
The clearance console above runs on curated data. Every output shown was generated by AI, then checked by people.
One live project
One design office, one newbuild, real comment sheets. The pilot.
The whole table
The yard, the owner and class join the same record.
What the pilot measures
Three numbers: engineer-hours spent on correspondence, days from comment raised to comment closed, and comments answered late or lost. If those numbers don't move, Decklog isn't working.
Decklog is pre-product. We're building it in the open, with the people who'll use it.