Features · Documentation
Jobsite documentation
Turning messages, photos, and spreadsheets into a contemporaneous, citable record
A document written late is worth less when a claim is reviewed. Kolang logs the event as it happens, so claims and financial control rest on jobsite reality, not on reconstructing events weeks later.
The input is the same messages, photos, spreadsheets, and reports already exchanged on site today. The output is a shared record for the owner, construction manager, and contractor.
One shared record, three parties
Every project party sees one version of jobsite reality — no parallel channels or conflicting records.
Linked to contract context
Every record can be linked to its contract clause, work package, and responsible party, ready when a claim is reviewed.
Timestamped and immutable
Once confirmed, a record isn't simply deleted or rewritten; the change history stays visible.
Legal and financial citability
The construction manager can review the output and the owner can decide based on it. Every item is traceable back to the source document.
The documentation path in Kolang
-
01
Raw data comes in
Messages, photos, spreadsheets, and handwritten reports enter the system exactly as they're produced on site.
-
02
The event is structured
Kolang's Persian-language engine extracts the time, subject, location, and responsible party and assembles them into a record.
-
03
Human confirmation
The technical office or supervisor reviews and confirms the record; no number is ever generated without a source.
-
04
A citable record
The record stays in the shared log, ready for reporting, claims handling, and financial control.