Eduth

Client-facing project governance

Milestone and schedule tracking that answers whether a project is on track — for both supplier and client, from one shared source of truth.

Not the supplier’s optimism. Not the client’s anxiety. The record both sides can check — for engineering, manufacturing, construction, fit-out and software delivery.

In build. Next in the Kinara Consulting portfolio — the client-visible layer above shop-floor tools like Iddan.

How it works

Charter. Schedule. Milestones. One answer.

A project is set up once, between supplier and client. From then on, every question about it has one place to be answered.

01
Charter
Plant upgrade · Phase 2
Scope · 4 objectives · 6 stakeholders · 5 milestones
Supplier signedClient signed

Set up the charter

Scope, objectives, who is who, and what counts as done — agreed by both sides before execution starts. That agreement is the record everything else checks against.

02
Design
Procure
Fabricate
Project
BufferBuffer being eaten

Schedule with buffers, not padding

One project buffer at the end and feeding buffers where chains join — not a safety margin hidden in every task. Watch the buffers, not the tasks, and you see trouble while there is still time.

03
GA drawings rev C approved4 d
Vendor data sheets · awaiting client9 d
Milestone 2 reached → invoice raisedR

Milestones that mean something

Drawings and vendor documents logged as sent, received, approved — with how long each side took. A milestone reached is an invoicing event. The paper trail and the money trail are the same trail.

04
The client asks
“Are we still on track for December?”
Yes. Handover 2 Dec. One milestone at risk, buffer holding.
From the record — not from a phone call.

One honest answer

The client logs in and asks the only question that matters. The answer comes from the shared record, the same for both sides — and it says at risk before it has to say late.

Two views of one truth

The supplier sees the reason. The client sees the status.

Too much internal insight is not good for the relationship; too little breaks trust. Eduth is the deliberate translation between the two — the same project, the same data, two views built for who is looking.

Supplier view
Plant upgrade · Phase 2
Buffer consumption vs chain complete
Project
62%
Fabrication
80%
Procurement
35%
Why Fabrication is at risk
Vendor data sheets have sat with the client for 9 days; cutting cannot start without them. Welding capacity is booked from the 14th.
Fed by Iddan · stage times live from the floor
Transmittals
Sent 24 · Received 19 · Approved 163 outstanding
Client view
The same project, the same minute
Are we on track?
Yes — one milestone at risk.
Handover still 2 December.
Design freeze12 Sep
Long-lead orders placed3 Oct
Fabrication completeAt risk · 24 Oct
Site installation18 Nov
Handover2 Dec
Waiting on you
Vendor data sheets — approval outstanding 9 days. Approving them protects the 24 October date.

Status, not process

The client gets on track / at risk / late per milestone and the next date. Never the internal bottleneck. That is a design rule, not a permissions setting.

The client’s part, visible to the client

Approvals and documents the project is waiting on appear on the client’s own page, with the date they protect. Delays stop being an argument.

Fed by the floor, when you want it

If your production runs on Iddan, stage times update the buffers on their own. If it doesn’t, you update them by hand. Either way the client sees the same picture.

Why Eduth

The name, and the space between.

Every Kinara product’s mark carries its own story. Eduth’s is told in two arcs that turn to face each other, and what appears between them.

01 · Two accounts

The supplier’s version, and the client’s

Every project has two stories: what the supplier believes is happening, and what the client fears is. Each is closed, each is complete, and they do not agree.

02 · They turn to face each other

Each one opens toward the other

Eduth brings the two together and opens them — not into one merged account, but toward a shared point that neither side owns.

03 · One record both can check

The testimony lives in the space between

Eduth is the Hebrew word for testimony — the record kept in the Ark of what two parties had agreed, consulted whenever they disagreed about who promised what. When a client asks “are we on track?”, the product is the eduth.

Not one side’s account. The record both sides can check.
An eduth records what happened, not why. That is the product’s design rule too: the client sees milestone status, never the supplier’s internal process.

Built for how projects actually go.

For suppliers who deliver projects to clients — engineering, manufacturing, construction, fit-out, software — and for the clients who need to know. Kinara Analytics is built into every paid Kinara and Qlaim product; in Eduth it is what turns buffer data into a forecast.

Buffers, not padding

Safety lives in one project buffer and a few feeding buffers, where you can watch it being spent — not hidden inside every task estimate where nobody can.

Milestones tied to money

A deliverable accepted is an invoicing event. The schedule and the cash flow stop being two documents maintained by two people.

The document trail eats buffer

Drawings sent, received, approved, outstanding — with response times. A client’s slow approval shows up as what it is: time taken off the buffer, visible to the client too.

Fed by the floor, optionally

Iddan can update buffer status from live stage times, so delivery problems surface before anyone discovers them late. It is not required — Eduth stands on its own.

The client sees the status, never the reason

On track, at risk, late, next date — and the approvals the project is waiting on from them. Not your bottleneck, not your staffing, not your margin.

Agreed first, argued never

The charter both sides signed is the reference for every status that follows. When the question is “who promised what?”, the answer is already written down.

For suppliers

Stop answering the same question by phone.

Run the project on buffers, log the paper, and let the client see exactly as much as they should. The “are we on track?” call stops coming.

Charter, schedule and buffers in one place
Transmittals with response times, both directions
Milestones that raise the invoice
For clients

One page that tells you the truth about your project.

On track or not, which milestone is at risk, what the next date is — and what the project is waiting on from you. No chasing, no reading between the lines.

Status per milestone, updated from the record
Approvals you owe, with the date they protect
At risk before it is late
Your supplier invites you. Nothing to set up.

Ready to answer “are we on track?” once?

Eduth is in build. Tell us about the projects you deliver and we will show you what your clients would see.