Lesson 3 of 6
After the Call: Notes, an Action Log and a Same-Day Follow-Up
Turn a call into notes somebody else can use, keep every action in one log with an owner and a date, read that log as it stood on any day with a short script, and send the follow-up before the day ends.
7 minForward Deployed Engineering
After this lesson you will be able to write up a call so that it is useful to someone who was not there, and keep a list of actions that shows at any moment who owes what to whom.
The discovery call with Larchmont Vets ended at 10:45 on Tuesday 2 June. What you do in the next few hours decides how much of it survives. By tomorrow each of the five people on the call will remember it a little differently.
Notes somebody else can use
Notes are not a record of who said what in which order. They are for a reader who was not there, or for you in three weeks. Sort what you heard under a few fixed headings.
Discovery call, Larchmont Vets, Tue 2 June, 10:00 to 10:45
Present: operations director; practice manager and head nurse
(Ashby Road); IT manager; FDE
Decided
- Pilot at Ashby Road and Mill Lane, four weeks from Mon 22 June.
- Success: fewer emergency orders than in May, and the weekly
order takes less of the head nurse's time.
Heard
- Ashby Road orders on Thursday afternoon, Mill Lane on Wednesday.
The order takes the head nurse about two hours.
- Ashby Road ran out of a common item twice in May.
- Controlled drugs are ordered under a separate procedure and
must never appear on a suggested order.
Not known yet
- How long the supplier takes to issue a read-only key.
"About a week" (IT manager, from memory).
- Whether Mill Lane orders in the same way as Ashby Road.
Actions: see the action log.The headings do the work. "Decided" holds what everyone agreed and can be held to. "Heard" holds what one person told you and nobody has checked. "Not known yet" holds the open questions, so that they are not forgotten and nobody mistakes a guess for a fact. The supplier's "about a week" sits there on purpose.
The action log
Actions agreed on a call are scattered through people's memories and inboxes within a day. Keep them in one place. A spreadsheet is enough. So is a plain file, which is what this course uses, because a file can be read by a script.
Make a new folder for the course and save this as actions.csv.
id,raised,side,owner,action,due,done,blocks
A01,2026-06-02,us,FDE,Send notes and actions from the discovery call,2026-06-02,2026-06-02,
A02,2026-06-02,customer,Practice manager,Send May's order history for the two pilot practices,2026-06-05,2026-06-04,
A03,2026-06-02,customer,Head nurse,List the items that must never be suggested for reorder,2026-06-08,,
A04,2026-06-02,customer,IT manager,Get a read-only key for the practice system from its supplier,2026-06-10,,Pilot start
A05,2026-06-02,us,FDE,Demo reorder suggestions on May's order history,2026-06-11,,
A06,2026-06-04,customer,Operations director,Confirm the start date with both practice managers,2026-06-09,,Each row is one action. The columns are these.
idis a short reference you can quote in a message.raisedis the day the action was agreed.sidesays whether it is the customer's or yours. Your own actions go in the same log. A log that lists only what the customer owes reads as a list of accusations.owneris one person, never "the team".dueis one date, agreed with the owner.doneis empty until the action is finished, and then holds the date it was finished.blocksnames anything that cannot happen until this action is done. Only one row has it so far: without the key, the pilot cannot start.
The first two rows already have a date in done. You sent the notes on the day of the call, and the practice manager sent the order history on Thursday, a day early. Row A06 was added on Thursday as well, when the operations director offered to confirm the start date with both practice managers. A log grows between meetings, not only during them.
Read the log as it stood on a day
A list of rows does not answer the questions you will be asked: what is open, what is late, and whose it is. Save this as actions.py.
"""Show the action log as it stood at the end of one day.
Usage: python actions.py YYYY-MM-DD
"""
import csv
import sys
from datetime import date
SIDES = (("customer", "With Larchmont"), ("us", "With us"))
def load(path="actions.csv"):
with open(path, newline="", encoding="utf-8") as handle:
rows = list(csv.DictReader(handle))
for row in rows:
for field in ("raised", "due", "done"):
row[field] = date.fromisoformat(row[field]) if row[field] else None
return rows
def as_of(rows, day):
"""Split the log into what was done and what was still open at the end of `day`."""
known = [row for row in rows if row["raised"] <= day]
done = [row for row in known if row["done"] and row["done"] <= day]
still_open = [row for row in known if not (row["done"] and row["done"] <= day)]
return done, sorted(still_open, key=lambda row: row["due"])
def days_late(row, day):
"""Days past the due date: up to the day it was done, or up to `day` if it is still open."""
end = row["done"] if row["done"] and row["done"] <= day else day
return max((end - row["due"]).days, 0)
def main(day):
done, still_open = as_of(load(), day)
late = [row for row in still_open if days_late(row, day)]
print(f"Action log at the end of {day:%a %d %b %Y}: {len(done)} done, {len(still_open)} open, {len(late)} late")
for side, title in SIDES:
print(title)
for row in still_open:
if row["side"] == side:
flag = f"LATE {days_late(row, day)}d" if days_late(row, day) else ""
blocks = f" [blocks: {row['blocks']}]" if row["blocks"] else ""
print(f" {row['id']} due {row['due']:%a %d %b} {flag:<8} {row['owner']}: {row['action']}{blocks}")
if __name__ == "__main__":
if len(sys.argv) != 2:
sys.exit(__doc__)
main(date.fromisoformat(sys.argv[1]))The script takes a date and shows the log as it stood at the end of that day. It leaves out actions raised later, and it treats an action finished later as still open. That is why done holds a date and not a tick: you can ask what was true on any day, including days in the past.
Run it for Friday 5 June.
python actions.py 2026-06-05Action log at the end of Fri 05 Jun 2026: 2 done, 4 open, 0 late
With Larchmont
A03 due Mon 08 Jun Head nurse: List the items that must never be suggested for reorder
A06 due Tue 09 Jun Operations director: Confirm the start date with both practice managers
A04 due Wed 10 Jun IT manager: Get a read-only key for the practice system from its supplier [blocks: Pilot start]
With us
A05 due Thu 11 Jun FDE: Demo reorder suggestions on May's order historyTwo actions are done, four are open and none is late. The open actions are grouped by side and sorted by due date, so the next thing due is at the top of each group. The words in square brackets mark the one action that can stop the pilot from starting.
Send the follow-up the same day
You promised notes and actions by the end of the day. Keep that promise to the hour. It is the first promise you have made to this customer, and they will notice whether you keep it.
Subject: Notes and actions from today's call
Thank you all for your time this morning. My notes are attached.
Decided: the pilot runs at Ashby Road and Mill Lane for four
weeks from Mon 22 June.
Actions
- Practice manager: May's order history for both practices,
by Fri 5 June.
- Head nurse: the items that must never be suggested,
by Mon 8 June.
- IT manager: a read-only key from the supplier, by Wed 10 June.
The pilot cannot start without it.
- Me: a demo on May's orders, Thu 11 June.
If I have misheard anything, please correct me by reply.
Next written update: Fri 5 June.The message is short because the detail is in the attachment. The decision comes first. Each action names a person and a date. The one action that can hold up the pilot says so in plain words. And the last two lines invite correction and say when the reader will hear from you next.
Chase before it is late
An action log is only useful if somebody looks at it. Look at yours every morning. When an action is due tomorrow and you have heard nothing, write to its owner today.
The tone matters. "Your action is due tomorrow" is a reminder from a system. "Is there anything you need from me to get the list done by Monday?" is an offer from a colleague, and it gets the same result with less friction. Sometimes the answer shows a real obstacle, such as an owner who is on leave or who is waiting for somebody else, and you learn about it while there is still time.
When an action does go late, the log should show it plainly and without comment. The exercise shows what that looks like.
Key takeaways
- Notes separate what was decided, what was heard and what is not yet known.
- Every action lives in one log, with one owner, one due date and a note of anything it blocks.
- Record the date an action was done. The log is then a history as well as a to-do list.
- Send the notes and actions on the day of the call, and ask to be corrected.
- Chase an action before it is late, by asking whether the owner needs anything from you.
Try it
Run python actions.py 2026-06-09 and read what it prints. A good result shows 2 done, 4 open and 1 late: the head nurse's list, due on Monday 8 June, is one day late. That afternoon she sends it. Record this by putting 2026-06-09 in the done column of row A03 in actions.csv, between the last two commas, and run the same command again. A good result now shows 3 done, 3 open and 0 late. Then write the one-line message you would have sent her on Monday morning, before the action was late.
Official documentation
Written with AI and checked automatically. Nobody has run these steps by hand, and tools change, so a command may behave differently in the version you install. Spotted a mistake? Tell us.