Client Client approval of project minutes
The client's approval of the project minutes is the most discreet and the most decisive act of the follow-up. Without it, you have a document that you wrote alone and sent to someone whose handling of it you do not know. With it, you have a trace that both parties established, on a date. The whole difference lies there.
What an unanswered email establishes.
Nothing, and that is precisely the problem, because we believe the opposite until the day we need it.
You know what you wrote
That is all. You do not know whether it was read, by whom, or whether a point in it was disputed without being said.
Silence is not agreement
It is most often a lack of time. Holding it against them six months later produces a tense discussion, not a finding.
The version is debated
An attachment gets corrected, resent, split into three copies. No one knows which one was authoritative.
The disagreement stays tacit
The client disagrees on a point, and does not say so because answering would mean rereading everything. They will say it at invoicing.
A dated act, rather than an absence of reaction.
Getting approval is not one more formality imposed on the client: it is what turns your follow-up into shared information. As long as the minutes go out with no reply expected, they remain a one-sided statement, however well written.
Two things change when approval becomes an act. The first is rejection: a client who can refuse with a reason will voice their disagreement at the moment it arises, rather than keeping it for the end-of-project discussion. Disagreement becomes a piece of project data instead of remaining an awkwardness.
The second is immutability. A document that freezes after approval proves something; a document that can be touched up afterwards proves nothing, even when no one has touched it up. This is what we call operational commitment management.
Four states, and each transition is dated.
This is the complete mechanism, as it applies to committee minutes.
Submitted
The document goes out for review with the client, on a date. From that moment, the supplier can no longer modify it.
Approved
The client signs off. The document freezes and joins the history, with the state of the project at that date.
Rejected with a reason
The client challenges it and says on what. The point of disagreement is recorded, dated, and treated as a topic.
Corrected
Through a new cycle, never by rewriting. You can see that a correction took place, when, and what it covered.
The structure of the document itself is covered on steering committee minutes, and the access that lets the client approve on the project client portal.
"My client will never approve."
It is the most frequent objection, and it deserves a frank answer rather than an argument. Many clients will not approve, at least at first, and the mechanism is designed so that this is not blocking.
What you get without approval remains better than an email: the submission is dated, the content is frozen, and you can establish what was presented and when. What you do not have is the explicit agreement; but you did not have it with the attachment either.
Two things help, in practice. The first is that client access is free, so the request does not run into a question of cost. The second is that approval takes a gesture, not a full reread: it applies to a document that the client was able to follow along the way rather than discover all at once.
What we are asked about approval.
How do you get minutes approved by the client?
By submitting them in the tool where they already follow the project, rather than as an attachment. They approve, or reject with a reason, and the act is dated. Access costs them nothing.
What is the value of an approval in the tool?
We speak of dated proof and of a trace that both sides can rely on, not of a legal qualification: the applicable framework is that of your contract. What we observe is simpler, and it can be verified: a document submitted, read and approved on a date establishes what both parties knew at that moment. See the terms and conditions.
What happens if the client rejects?
They state the reason, and the disagreement becomes a dated point of the project. The document is corrected through a new cycle rather than touched up, which shows that there was a discussion and what it covered.
And if the client never answers?
The minutes are submitted to them on a date, and that submission is traced. With no reply within the deadline agreed between the parties, they move to the approved state in pylotik, with a note that no reply came. This is a state of the product, not a legal acceptance: the applicable framework remains that of your contract.
Does the client also approve interventions?
Yes, when you use intervention management: they sign off the acceptance on the technician's phone, from their client access, or by a physical signature, or refuse it with a reason. The principle is the same as for the minutes. See field intervention management.
Can minutes be modified after approval?
No, and that is the point. Once approved, they are immutable. A correction goes through a new cycle. A history that gets rewritten proves nothing.
The client disputes it six months later, what should you do?
Reopen the meeting concerned: what was presented, what they approved, on what date. The discussion goes back to being a finding. Without a frozen history, it stays a clash of memories.
Does it work with an internal client?
Yes. An IT department reporting to its business units has the same need to establish what was presented and accepted, with no contract or penalty.
Going further.
- Steering committee minutes: the structure of the approved document.
- The project client portal: where the client approves, and what they see.
- Operational commitment management: the definition of the category.
- The product tour: committees, history, client access.