LTkr — Last Tracker

1. Mode d'emploi — what LTkr synthesises

LTkr (Last Tracker) is the collaborative layer that keeps industrial promises visible: who owns what, this week’s meeting frame, what was decided, and — when delivery slips — a calm, non-blame explanation.

• Shared task board — actions with owners, due dates, categories (HSE, C&P, logistics…), status and notes.
• Meeting agenda — timed weekly structure (Last Planner results, supply chain, JV, milestones…).
• Meeting minutes (MoM) — decisions, issues, attendance, actions reviewed.
• Variance explanations — simple, non-conflictual reasons why a resolution plan did not hold (not a court case).
• Priority colours — so the room sees critical vs base work at a glance (see §2).

How to use on this site: open the live workspace (editable in the browser), or the Kapuni read-only demo; present the DFKPS deck in the room; export agenda / minutes / progress; send reminders with mailto (your mail client).

2. Task classification · colours

Four levels — red · orange · blue · gray (critical · important · base · simple info).

• Simple info — lilac · FYI, closed items, context only — no pressure on the room.
• Base — blue · standard work to execute this week.
• Important — orange · medium priority, in progress or near due.
• Critical — red · blocked, safety, JV decision, or path-critical package.

3. Why the resolution plan did not hold (10–12 calm reasons)

Variances are written as simple, non-conflictual explanations — facts, not accusations. Typical catalogue (Last Planner / industrial practice):

1. Prerequisite not ready (upstream deliverable late)
2. Underestimated effort or complexity
3. Incomplete or poor-quality input data
4. External decision pending (JV / client / authority)
5. Resource not available (people / equipment)
6. Priority re-sequenced by the team
7. Scope clarification needed
8. Contractor / supply-chain delay
9. Weather or site access constraint
10. Safety hold / permit not yet in place
11. Interface misalignment between disciplines
12. Plan optimistic vs real site conditions

In the Kapuni demo, each variance links an action, an owner, a date and a category code (e.g. lack_of_decision, poor_data_quality, underestimated_effort).