Skip to content
Klargantt

Klargantt on one page

A tool that opens a schedule file, recalculates it, checks it and renders it. It does not manage the project, and it never will.

Open a schedule What does not leave

The problem

A schedule travels as a file. The supervisor writes it in Microsoft Project, the contractor in Primavera P6, the subcontractor in a spreadsheet. Everyone receives a format they cannot open, and the software costs more than the need.

The usual answer is an online service: you upload the file, you wait, you download. A schedule carries contractual deadlines, penalties, the names of people on the job and sometimes costs. Uploading it to a third party in order to read it is a decision, and it is rarely taken knowingly.

What Klargantt does

  • Open. A Microsoft Project XML, a Primavera P6 XER, a GanttProject .gan. An .mpp is recognised and inventoried.
  • Recalculate. Early and late dates, float, critical path, using the file's calendars, constraints, deadlines and progress.
  • Check. The 14 points of the DCMA assessment, plus three checks of our own, with the number and the threshold.
  • Compare. Two versions of the same schedule, and what moved between them.
  • Render. A Gantt chart as a PDF paginated up to A0, as a PNG, as an SVG, a workbook, a CSV, an XML that Project opens, the milestones in a calendar, and a mermaid chart.

What Klargantt is not

  • It is not a project management tool. No account, no server, no sharing, no task assigned to anyone, no notification.
  • It is not a replacement for Microsoft Project. It is a way to read what Project wrote, and to hand it back a file it opens.
  • It is not a judge. The check gives numbers and thresholds; it does not conclude that the schedule is compliant.
  • It is not a delay analyst. The comparison gives differences; attributing them is expert work.

How it is built

Everything runs in the tab. The format readers, the calendar engine, the scheduling, the checks, the comparison and the renderers are written for this product, with no production dependency. The PDF is written byte by byte, and so is the .xlsx workbook.

Each page's content security policy forbids the browser from opening a connection to another site. That is not a marketing promise: it is a line the browser enforces, and you can read it in the page source.