Client and supplier indicators
Clients → Indicators and Suppliers → Indicators measure service quality: satisfaction, delivery punctuality (OTD), delivery quality (OQD), and the progress of the projects linked to each partner. Where the dashboard follows the money — contracted, invoiced, committed — this screen follows what is delivered, when, and how it is received.
The indicators
| Indicator | Client side | Supplier side |
|---|---|---|
| Satisfaction | Average of the scores clients give us, from 1 to 5 | Average of our supplier ratings, from 1 to 5 |
| OTD (On-Time Delivery) | Share of delivery milestones delivered on or before the contractual date | Share of installments received on or before the planned date |
| OQD (On-Quality Delivery) | Share of deliveries accepted as compliant | Share of receipts accepted as compliant |
| Delivered projects | Projects with the Closed status, out of all linked projects | Same |
| Late deliveries | Delivery milestones past due and not yet delivered | Installments past due and not yet received |
Three rules keep one figure from being read as another:
- Delivering on the planned day is delivering on time. OTD compares two calendar days, never hours.
- A rate with no basis shows "—", not "0%". As long as nothing is delivered or assessed, there is nothing to measure; 0% would mean everything is late.
- OTD only judges what has been delivered. An awaited, overdue delivery is not in it yet: it is counted separately, under Late deliveries, until it is delivered.
Under each value the screen recalls its basis: "8 on time out of 10 delivered", "3 surveys".
Scope and year
The scope is that of the banner: the partner selected in Client mode, or in Portfolio mode all the partners you can see or those of a portfolio. As on the dashboard, only firm contracts count: no framework agreement, no quote or price request, no cancelled contract.
The year selector bounds the dated measures — a satisfaction survey by its survey date, a delivery by its delivery date. Projects, however, are always a snapshot of the present: the state a project had last year is not kept on the project.
Projects by state and by status
A project is linked to a client or a supplier by the breakdown of one of its contracts or orders. The screen gives:
- the distribution by state (the workspace state list: draft, approved…) and by status (Open, Pending, Ongoing, Closed), as two charts;
- the Indicators by client (or by supplier) table: one row per partner with its satisfaction, OTD, OQD and late deliveries, then its projects counted state by state and status by status;
- the Project state and status list, project by project.
A project shared by two clients appears under both, but counts only once in the total. A deleted project leaves the count; an archived project stays, flagged as such.
Billing and delivery milestones
On the client side, a contract schedule now distinguishes the type of each milestone:
| Type | What the milestone carries | Feeds |
|---|---|---|
| Billing | A percentage, an amount, a status (Waiting → To invoice → Invoiced → Paid) | The schedule and the pro forma invoice |
| Delivery | An actual delivery date and an acceptance result | OTD and OQD |
| Billing and delivery | Both: accepting the work package triggers its invoice | Both |
A pure delivery milestone carries neither an amount nor a billing status: it appears neither in the remaining amount to invoice nor in the pro forma invoice. Installments entered before this change remain what they were, billing milestones.
A time and materials contract carries milestones too: its days are invoiced through the consumed amount, but deliverables are still handed over on a date. A milestone added to such a contract is therefore a delivery by default — you remain free to make it a billing milestone, for a down payment for instance.
On a delivery milestone, fill in from the contract panel:
- the contractual date — the promised date;
- Delivered on — the actual delivery date;
- the Acceptance — Compliant, With reservations or Rejected.
The badge on the row immediately tells where the milestone stands: Due in 12 d, On time, Delivered 3 d late, Not delivered, 5 d late.
Linking a milestone to the planning
Each line of the schedule has a Milestone list: it links the contractual milestone to a planning milestone, whatever the billing type (fixed price, time and materials, subscription). It only offers the milestones of the projects in the contract's allocation — with no allocated project, the panel says so and the list stays empty; if the allocated projects have no milestone, it says so too.
The link moves no date: the contractual date remains the one you enter. Below the line, the milestone date and its deadline are shown, each with a → button that copies it into the contractual date. The Contract milestones screen shows the three dates side by side.
The Clients → Contract milestones screen (formerly "Billing milestones") lists every milestone of the active client with its type, delivery date, punctuality and acceptance — filterable and exportable like the other columns.
Milestones that do not comply with the contract
The screen flags every deviation from the contract, in the Contract compliance column and by tinting the row:
| Deviation | Severity | When |
|---|---|---|
| Not delivered | Alert (red) | Delivery milestone whose contractual date has passed, with no delivery |
| Not invoiced | Alert (red) | Billing milestone whose contractual date has passed, neither invoiced nor paid |
| Acceptance rejected | Alert (red) | Delivery rejected at acceptance |
| Delivered late | Watch (orange) | Delivered after the contractual date |
| Accepted with reservations | Watch (orange) | Delivery accepted with reservations |
| Planning beyond contract | Watch (orange) | The linked planning milestone (its date, otherwise its deadline) falls after the contractual date while it is still to be delivered or invoiced |
Above the grid, one counter per type of deviation gives its number; clicking a counter shows only those milestones, a second click (or Show all) removes the filter. When nothing deviates, the screen says so — unless some open milestones have no contractual date: their compliance cannot be checked, so the screen counts them separately and marks them "Contractual date missing".
Supplier side
Every instalment of an order is already a receipt: there is no type to choose. OTD is read from the receipt date, which the Installments screen already knew. Only the Acceptance is added, in the order panel and in the Installments screen, next to the new Punctuality column.
An instalment moved to the received status without a receipt date cannot be measured: it is counted neither on time nor late.
The Installments screen also flags deviations from the contract, with the same column, row tint and counters as client milestones: receipt expected and not done, late receipt, acceptance rejected or with reservations, planning milestone scheduled after the due date. The due date stands for the contractual date; an installment received without a date counts as delivered.
Satisfaction surveys
The Satisfaction survey (or Supplier rating) button records a score from 1 to 5, its date, a comment and, when the survey is about a specific project, that project. Without a project, it stands for the whole relationship.
The average shown is that of the surveys, not of the per-partner averages: a client surveyed ten times weighs ten times. Each survey can still be edited and deleted from the list, by those who can edit the partner.