Skip to main content
KEY ORGANIZATION / FIELD NOTESISSUE 01 · 2026
MENU
THE METHOD
← The field guide collection

Key Organization ·

Keep the promise behind every contact

A name in an address book tells you who someone is. A useful follow-up record also tells you why you met, what you promised and what should happen next.

A contact moves from meeting context to an agreed promise, a named next step and a review. No promise means no automatic follow-up.
Original Key Organization workflow, adapted from the 2004 article. This is an editorial procedure, not a measured sales funnel.

A contact moves from meeting context to an agreed promise, a named next step and a review. No promise means no automatic follow-up.

1. Capture the reason, not just the business card

Lisa Ray’s 2004 article asked a practical question: can you remember where you met a person and why you kept their card? Denise Landers recommended recording that context in a consistent contact system. The article also discussed CardScan, PDAs and applications of that period. They are historical examples, not today’s software recommendations.

Use a tool your authorised team can maintain. Start with the person’s name and organisation, the date and context of the conversation, the agreed purpose of further contact, and a link to the relevant work record. Add only information needed for that purpose. A networking conversation is not permission to add someone to a marketing list.

2. Separate a promise from a possible opportunity

“Interesting person” is not an action. “Send the accessibility checklist we discussed” is. Record the actual agreement, a responsible person and a date. If there was no request or agreement, do not invent one to keep a pipeline busy. A referral may also require checking that the other person wants the introduction before sharing their details.

Keep the contact record separate from confidential case notes, passwords and payment information. Use the access controls of the system you already have. This worksheet does not ask you to upload a contact list to this website.

3. Work through one complete example

Fictional situation: Alex from Studio A meets Morgan from Team B at a supplier workshop on 19 October 2026. Morgan asks for a blank project checklist, but does not ask for a proposal or newsletter.

Context
Supplier workshop; discussed missing approval steps.
Promise
Alex will send the blank checklist, with no client information.
Next action
Alex sends the agreed document on 20 October.
Review
On 23 October, check only whether the promised document was sent. If Morgan has not requested further contact, close the action rather than scheduling repeated reminders.
Evidence of completion
A link to the sent message and document version; no claim that a sale resulted.

If the message cannot be delivered, record that fact. Verify the address through an appropriate existing channel if there is a reason to do so. Do not keep sending the same message or silently substitute a different recipient.

4. Review and hand over the record

  1. Look at due promises, not every name in the address book.
  2. Check whether the next action is still wanted and whether the owner is available.
  3. Mark completed actions with evidence. Separate “sent” from “received” and “agreed”.
  4. When a colleague takes over, transfer the context and promise together, subject to the original purpose and access permissions.
  5. Review obsolete contact details under your organisation’s retention rules. Do not keep information indefinitely simply because storage is cheap.

For the message itself, use the decision email format. For a repeated team process, add the ownership rule to your one-page operating manual.

Make your own record

Download the blank CSV and fill it on your own device. Completed records are not sent to this website. You can also copy the headings onto paper.

Download the blank CSV worksheet
Open the completed example record
Context
Workshop; approval steps
Purpose
Send requested blank checklist
Owner
Alex
Next step and date
Send checklist / 20 October 2026
Completion evidence
Sent message and document version
Review or close
23 October; close when promise fulfilled

Sources and reading limits

Keeping Track of Your Clients · Lisa Ray · 8 November 2004. The original document and the new editorial exercise are distinct. An archive capture date is not a publication date.

No new expert review or measured outcome is claimed.

Inspect the original page facsimile
Keeping Track of Your Clients · Lisa Ray · 8 November 2004
Original 2004 Daily Court Review article preserved by Key Organization. This facsimile identifies the source; its software recommendations describe that period.

Return to the field guide collection →