After signature, give each open question its own line. A useful working record says what you have read, what that item establishes and what evidence would justify changing the entry. Otherwise, a new document can make the whole file feel further along without answering the question you actually needed resolved.
At announcement
MIND supplies telecom billing, communications analytics and messaging. Shareholder approval and other conditions remained. One holder pledged her votes unless the board changed its recommendation. Enghouse’s closing obligation had no financing condition. MIND’s November 10 release
Terms included US$1.30 cash per share, about US$25.4 million equity value. MIND could solicit competing proposals until December 10. Accepting a superior proposal could trigger a US$1m fee. Enghouse release
For operating context, Enghouse’s September 10, 2026 quarterly report, issued from Markham, Ontario, reported C$117.6 million in revenue for the quarter ended July 31. Its recurring revenue category, which includes SaaS and maintenance, contributed C$81.7 million, or 69.5%. The report also discusses software licence and hardware demand. That gives the reader a business description involving software delivery and ongoing services. These are dated operating figures; they do not identify the funding for an acquisition.
Build the record around the question
Start each entry with a question precise enough to answer from an identified item. “Where are we?” is too broad for a document register. “Which version was reviewed?” or “What outcome does this notice report?” gives the person maintaining it something observable to record.
Use six fields: document and version, date, observed state, open question, next evidence and responsible person. Keep a copy of the item behind each entry. When someone supplies a replacement, preserve the earlier version and record which entry changed. This is a working method for organising a discussion, not a way to determine legal rights.
1. Locate the wording
For a contract question, identify the executed version and the passage to be reviewed. Give the adviser a specific question and retain the answer with its date and scope. If a financial statement is also in the folder, give it a separate entry. Ask what it measures and at what date. Do not make one document carry an answer that the reviewer has not established from it.
2. Record the approach
For an incoming message, retain the actual text, sender and receipt date. Describe what arrived before deciding how to respond. “Asked for a meeting” is a usable observation. Put the question about a permitted next step in a separate field for review against the operative documents. This keeps receipt of information separate from a decision to act on it.
3. Locate the outcome
For an approval question, specify the result being sought and the record that would establish it. Keep notices, expressions of support and reported outcomes as distinct entries. Assign someone to obtain the relevant result. Until it arrives and is reviewed, leave that outcome field open; a fuller folder is not a reason to complete an unanswered field.
A different stage from an extension request
Our guide to review a buyer exclusivity extension addresses an earlier decision: whether the progress and remaining work support discussing more exclusive time before signing. It organises dated observations and unresolved tasks around that request. Here, the proposed working record starts with a signed file and asks what each subsequent item establishes. The shared discipline is preserving dated evidence. The decision differs: assessing a requested period and tracking an observed development are separate jobs. Use the guide for the extension discussion; keep the record below tied to its own documents.
A fictional file, opened June 3
Maya Chen, the owner of Orchard Meter Systems, opens a signed-deal file involving Linden Lab Services. The companies, people, dates and documents in this exercise are invented. They do not describe the reported transaction. Maya creates Record v1 on June 3 and sets a June 7 follow-up. The file contains three items; no other evidence is assumed.
Entry A: the financial statement
Document and date: Financial Statement v1, dated March 31, reviewed June 3. Observed state: the statement shows available cash at its reporting date, subject to its accounting basis. Maya records that date alongside the observation.
Open question: what evidence answers the financing question in the signed file? Next evidence: the operative financing-condition wording and the separately applicable, dated financial evidence for the status being claimed. Responsible person: finance lead Joel Martin will locate the relevant items for adviser review by June 7. Record v1 contains no conclusion that those missing items have been obtained or reviewed.
Entry B: the incoming email
Document and date: Incoming Email 01, received June 2, reviewed June 3. Observed state: an unsolicited sender asks for a meeting. The record contains an approach, with its wording preserved; it supplies neither an offer nor an accepted alternative.
Open question: what, if anything, may Maya do next? Next evidence: the current agreement terms and an adviser’s assessment of the proposed response. Responsible person: Maya will send the exact message and current document version to her adviser for the June 7 review. The record does not treat the meeting request as permission to arrange one.
Entry C: the support message
Document and date: Holder Email 02, received June 3. Observed state: one holder states support. Maya records the statement as that person’s position at that time. No vote result is supplied in the exercise.
Open question: what required approval remains to be evidenced? Next evidence: identification of the applicable approval mechanism and its official outcome, or separately verified evidence supporting the particular status claimed. Responsible person: company secretary Asha Patel will identify the required record and report at the June 7 follow-up. The outcome entry remains open.
Change one field when one fact changes
On June 6, Asha receives Meeting Notice v1, scheduling a meeting for June 18. Maya adds it to the file and creates Record v2. Entry C now includes the meeting date and the notice that supplies it. Its outcome field still reads “open”. The notice supplies no result in this fictional file.
Asha is assigned to obtain the official result when available and identify the document and date supporting any update. At the June 7 review, she can report the scheduled meeting without reporting an approval. Entries A and B retain their open questions because the exercise supplies no new evidence for either. Record v1 remains available, so a reader can see exactly what changed.
For your own working record, write the next update rule before the next email arrives: name the item needed, who will locate it and which field it could change. That makes the follow-up specific and keeps an unanswered question visible.
For general information and education, not legal, tax, investment or valuation advice. Examples are illustrative and do not predict your business’s value, financing terms or sale outcome. Consult qualified advisers about your situation.
Subscribe to Deal Flow Canada for practical owner guides and Canadian deal updates.