APRD 3004 · Account Management · Fall 2026 · Znerold Reading · for Week 6

a conference report, annotated

A working report, sanded for teaching. The numbered notes explain why each section reads the way it does.
assignedWeek 5 · Wednesday, Sep 23
read byMonday, Sep 28
checkedRC5, first five minutes, with Account service standard operating procedures (Levitan)

The client below appears as 'Alpenglow,' which is not a real brand: the name is sanded off, people are reduced to initials, and the numbers are rounded. Everything else reads exactly the way reports like this ship every day, assembled from ones that actually shipped. The format is the course template you already have. A proper report records, at minimum: what was decided, who owes what by when, what is still open, and what could surprise somebody later. Watch how each shows up, then read the numbered notes.

client / project'Alpenglow' · summer campaign
date of meetingThursday, March 5
prepared byJ.K., account executive
attendees (client)M.O. (VP marketing), D.R. (brand manager)
attendees (agency)S.B. (account director), J.K. (AE), T.M. (creative director) [1]

decisions made [2]

actions and owners [4]

actionownerdue
Updated budget tracker showing the radio-to-social moveS.B. (agency)Mon, Mar 9
Revised media plan reflecting the same moveJ.K. (agency)Tue, Mar 10
Summer Pass promotion: legal read on the offer languageD.R. (client) [5]Thu, Mar 12
Photography shot list approvedM.O. (client)Wed, Mar 11
Second cut of the :15 hero videoT.M. (agency)Fri, Mar 13

open questions [6]

risks or flags [7]

Sent Friday, March 6, 9:41 a.m., about 18 hours after the meeting ended. Please reply with corrections by end of day Monday; after that we will treat this as the record. [8]

the annotations

  1. Who was in the room is evidence. When a decision gets disputed in April, the first question is who agreed to it in March, and this line answers it.
  2. Only decisions. The section refuses discussion on purpose: memories of discussion drift within days, and a report that records vibes invites relitigation. If nothing was decided, a good report says so plainly, which is itself information.
  3. The rejected option is written next to the decision. A choice recorded together with its alternative cannot quietly reopen next month as if the conversation never happened.
  4. Every action has one owner and one date. 'The team' is not an owner; a name is. Vague ownership is how deadlines die politely.
  5. Client actions get the same discipline as agency actions. The report is the politest possible way to hand your client homework in writing, and clients respect it.
  6. Open questions are logged so they cannot ripen into surprises. An unwritten question quietly becomes an assumption, and assumptions send invoices later.
  7. The risk section says the uncomfortable thing early, in writing, so the client hears it from the agency first. Candor logged today is trust you can spend later.
  8. The clock is the whole trick. The report ships within 24 hours because memory softens fast: the longer a decision stays unwritten, the softer it gets, until it is relitigated from scratch. Sent while the meeting is still warm, the report invites correction; uncorrected, silence is sign-off and it becomes the official record. Which means the person who writes it is, politely, steering the project.
the standard
Accurate enough that someone who missed the meeting could act on it. Short enough that everyone reads it. Sent while the meeting is still warm. Fifteen minutes to write, or you are writing too much.