Due date register
Follow the artifacts that impact your schedule
Terminal Nord, cruise wharfRegister1 overdue1 due this week1 in progress
Letter, Port AuthorityCP
330Shelter, foundations and slabCPEmployerOverdue 5 dAccepted
RFI-022, response340Aluminium gangway and railingsEmployerDue 11-255 dAccepted
A-301, rev. C350Canopy glazingEmployerDue 11-277 dIn progressObservation, Barge B240Rock armour, zone 2ContractorNoneRejectedEmail, safety walkNo taskUnattributedNoneRejected
DC-07CP330Shelter, foundations and slabCPEmployerSent 09-22ND-03AcceptedDR-03, under reviewCP330Shelter, foundations and slabCPEmployerSent 09-22ND-03SupersededSD-014, approved320Fender units, installationEmployerSent 06-12ND-02AcceptedReads your sources, never writes to them
Overruns are the changes nobody logged
Every document tied to the task it touches in your schedule, and whether it hits the critical path. Koredoc logs each one before it becomes an overrun
See the platformof megaprojects suffer cost overruns of more than 30%
of megaprojects are at least 40% late
Source: McKinsey, The construction productivity imperative, 2015
A call from the field becomes an artifact in the register
Koredoc listens to the call, recognizes who is speaking and logs the change event straight into the register
Integrate your current technology with Koredoc
Koredoc plugs into the tools your teams already use: email, voice, documents, and field software
Automated reminders to cut cognitive load and costly oversights
Build, reuse, and follow effortlessly
Reminders you generate once and can forget about, until Koredoc brings them back to you
- 1.✦ ASK due_date + What is the contractual deadline?
- 2.RUN Read the contract
- 3.RUN Check the schedule
- 4.✦ SEND Reminder RAP-018 sent to the Owner and the PM, three days before the deadline
- 5.DEPLOY Escalation auto if no answer at the deadline, the delay notice goes out on its own
Move past scattered emails, shared drives and spreadsheets that bury the documents that change your contract
Document ingestion lets Koredoc read the spec, the estimate and every directive as it arrives, pull out the dates and milestones and tie each one to the task it hits
