NovMeeting notes should separate agreement from the next action
Why transaction minutes should distinguish what the parties actually agreed from the documents, checks and confirmations that still have to happen afterwards.
This article reflects the named expert’s practical perspective. See NovAsia’s editorial policy for how material is prepared and reviewed.
The phrase “we agreed” is surprisingly imprecise after a complicated property meeting. It may mean that everyone accepted a principle, that a buyer liked a proposed commercial term, that one party promised to draft new wording, or that a specialist was asked to investigate a problem. Those are very different states, yet weak meeting notes often collapse them into the same sentence.
I do not need minutes to reproduce everything people said. I need them to preserve the transaction state accurately enough that the next meeting does not begin with an argument about the previous one. The core distinction is simple: an agreement changes the shared position of the parties; a next action is work that may produce a later agreement, fact or document.
The word “agreed” should be earned by the record
Imagine a hypothetical meeting about handover timing. The seller’s representative says a revised date can be proposed. The buyer says that date would work. The representative will prepare an amended draft. If the minutes record “handover date agreed,” they may have moved one step too far.
The buyer’s commercial position is clear. The seller side has indicated a willingness to revise. But the actual wording has not yet been produced, and the person who can formally confirm the change may still need to do so. New drafting might also introduce a different trigger, exception or definition.
A more useful record keeps those elements separate. It captures what the buyer accepted in principle, what the seller side said it would prepare, and what still requires confirmation. This is not bureaucratic caution. It is a way of stopping a future document from borrowing an agreement that belonged to an earlier conversation.
The same discipline applies to price, included assets, access arrangements, works before handover and any other material term. A statement should identify the subject and its boundary. “Price agreed” can be inadequate if the contents of the sale, tax treatment or payment timetable remain unsettled. “Furniture included” means little if nobody knows which inventory was being discussed.
Authority matters as much as wording. A helpful participant may be able to gather documents but not amend the deal. A lawyer may explain the effect of a clause but not choose the commercial compromise for the buyer. A coordinator can maintain the issue list without becoming a party. Meeting notes should not manufacture authority by assigning a stronger verb to a person than the documents support.
Version control is another reason to be precise. A meeting may refer to a contract draft, a term sheet and a presentation in the same hour. One document is updated the next day while another continues circulating. If the record does not identify what the discussion concerned, later readers can attach the old agreement to the wrong version. A short reference to the relevant document or section can prevent a large misunderstanding.
A next action needs a route, not the appearance of agreement
Actions are valuable because they move the transaction forward. Their weakness is that people often treat the assignment itself as progress sufficient to close the issue. “Lawyer to review,” “seller to confirm,” or “engineer to inspect” says who is next, but not what outcome will return to the transaction.
I prefer to think of an action as a small route. Someone has a task, the task produces a document, answer or decision, and that output changes the status of a defined issue. If the lawyer reviews a clause, the next useful event is not merely that time was spent on it. The useful event is a clear conclusion about the question that was referred. If a representative requests an approval, the next useful event is the approval or refusal from the appropriate party, not a message saying the request was sent.
This structure also makes handovers between participants much easier. A seller representative may supply a document, counsel may evaluate it, and the buyer may then decide whether to accept the remaining risk. Those are three separate actions with three different responsibilities. Recording them as one vague “pending” line hides the transaction logic.
Good notes therefore do not need to sound confident. They can contain unresolved items, conditions and dependencies. That makes them more useful, not less. The goal is not to make the meeting look successful; it is to make the next decision easier to take with the same set of facts.
The best test comes a week later. A person who did not attend should be able to read the notes and distinguish three things without guessing: what the parties actually settled, what still requires substantive confirmation, and what concrete action is supposed to move each open point forward. When those lines remain separate, the record supports the transaction instead of rewriting it.