Why Your Agent Should Read the Project Board Before Answering a Client

A client emails asking when the second phase lands. An agent drafts a helpful reply quoting the date from the proposal. The date changed three weeks ago and the board says so.

The rule is that an agent should read the project board before answering a client, and read it first, before anything else it might use. A confident answer that contradicts the plan of record does more damage than a slow one, because the client now has two versions of the truth from the same firm and has to work out which to believe.

The trust maths

Clients tolerate slow. They plan around slow. What they do not tolerate is being told two different things, because it makes every other thing they were told suspect.

One contradicted answer costs more than a week of delayed ones. The client stops treating your updates as facts and starts checking them, which means more meetings, more emails asking for confirmation, and a working relationship that runs on suspicion.

The cruel part is that the agent that produced the wrong date was doing exactly what it was asked. It found a relevant document and used it. The document was simply not the current one.

Why agents pick stale sources

Left to search broadly, an agent finds the most relevant looking thing, not the most current thing. And documents are usually more relevant looking than boards.

A proposal is written in full sentences, explains the reasoning, and states dates in a form that reads like an answer. A project board is terse. It says a status and an owner and a date field. To a retrieval step scoring by similarity to a question phrased in prose, the proposal wins nearly every time.

Meanwhile the proposal is frozen at the moment it was sent, and the board is what people actually update. So the more readable source is the more wrong one, systematically.

Email threads are worse again. They contain decisions, reversals of decisions, and speculation, all in the same tone. An agent reading a thread cannot always tell a proposal from a conclusion.

Ordering the retrieval

The fix is to stop treating all sources as equal candidates and give them a sequence.

• First, the plan of record. Current status, dates, owners, open items. Whatever your team treats as the thing they update. Availability belongs in the same tier, which is why an agent should see the leave calendar before booking a meeting.
• Second, recent decisions. Approved changes since the last baseline.
• Third, the client's own last few messages. What they were told, so the reply is consistent with it.
• Last, background documents. Proposal, statement of work, older reports. These provide context and history. They do not provide current facts.

The distinction to encode is between sources that supply facts and sources that supply background. A background source should never be the origin of a date, a status or a commitment in an outgoing message.

Handling the conflict

Sometimes the board and the document genuinely disagree and neither is obviously stale. The right behaviour then is not to pick.

An agent that finds a conflict on a fact it is about to state should stop and escalate, with both versions shown. That is a better outcome than either answer, because a conflict between the plan and the paperwork is usually a real problem someone needs to know about.

Teams that skip this end up with agents quietly resolving contradictions by preference, which hides exactly the information a project manager most wants.

When the board itself is stale

All of this assumes the board reflects reality. Often it does not, because updating it is somebody's least favourite task. Stale records are what managers usually mean when they say an agent forgot.

Pointing agents at the board has a useful side effect: it raises the cost of a stale board from mild confusion to a wrong client answer. That tends to concentrate attention. But it is worth saying to the team in advance rather than after the first incident, because "the agent was wrong" is a more comfortable story than "we had not updated the board since April".

A reasonable guard is a freshness check. If the record backing a fact has not been touched in longer than the work's normal cadence, the agent flags it rather than quoting it as current.

The shared record advantage

This is much easier when the board and the agent are not two systems held together by an integration. SicherOne puts project management, HR and AI agents on the same set of records, so an agent asked about a delivery date reads the same row a project manager reads, and there is no sync lag between them to reason about. A human approves output before it ships, which catches what the ordering misses.

The general principle stands whatever you use, though it gets easier when project boards, leave calendars and agents share one set of records. Decide which source is the plan of record, tell the agent to read it first, and never let a document written months ago be the origin of a fact you send to a client today.