# Partner event follow-up worksheet

Companion guide:
https://www.overskill.com/learn/plan-partner-event-follow-up

Use this editable record to turn one event into owned follow-up work. The filled
Harbor Fabrication example is fictional. Its evidence descriptions are practice
inputs, not existing attachments, real messages, customer results or proof of app
behavior. Keep the observation column Unverified until you test your own copy.

## 1. Name the event and review time

Event ID and name:
Business partner / host:
Event date, start and end:
Business timezone:
Event coordinator:
Current event status:
Review date and time:

Filled example: EV-01, Harbor Fabrication lunch workshop. October 8, 2026,
noon–1:00 PM, America/Chicago. Coordinator Maya; event support Alex; host Jordan.
The workshop is marked Completed. First follow-up review: October 9 at 9:30 AM.

| Milestone | Sample date | Evidence to record for your event |
| --- | --- | --- |
| Plan created | October 6 | Named event and initial plan |
| Host/room confirmed | October 7 | Actual agreed time and place |
| Workshop held | October 8, 1:00 PM | Event completion note |
| Commitments reviewed | October 9, 9:30 AM | Open commitments, owners and next due times |

An event's Completed status does not close its follow-up work.

## 2. Capture each commitment

Use one row per independently finishable promise. Every open row needs exactly
one responsible person, one next action and one due time, including waiting work.

| ID | Event | Owner | Next action | Current due, America/Chicago | State |
| --- | --- | --- | --- | --- | --- |
| F-01 | EV-01 | Maya | Send promised recap to Jordan | Oct 9, 2026, 10:00 AM | Open |
| F-02 | EV-01 | Alex | Prepare two tentative dates for internal review | Oct 8, 2026, 4:00 PM | Open |
| F-03 | EV-01 | Maya | Review any direct attendee follow-up requests; record permitted scope or keep contact on hold | Oct 9, 2026, noon | Waiting for permission review |
| F-04 | EV-01 | Alex | File room-close checklist | Oct 8, 2026, 3:00 PM | Completed Oct 8, 1:45 PM |
| Your ID | | | | | |

States for this exercise: Open; Waiting; Completed; Cancelled.
Overdue and Rescheduled after a missed deadline are labels/history, not completion.
For a cancellation, retain who decided, when and why; do not invent completed work.

## 3. Record permission and channel

| ID | Who requested what / restriction | Source and date | Channel for next action |
| --- | --- | --- | --- |
| F-01 | Jordan requested one workshop recap | Fictional closing-conversation note, Oct 8 at 1:00 PM | Jordan's agreed business email |
| F-02 | Internal draft only; no dates offered | Fictional event planning note, Oct 8 | Internal planning record; no message |
| F-03 | No direct attendee contact permission recorded | Fictional permission-review task, Oct 8 | Internal review only; external contact on hold |
| F-04 | Internal event documentation | Fictional event plan | Internal event record; no message |
| Your ID | | | |

For your real record:
Exact purpose and scope:
Who requested it:
Where and when the request was recorded:
Permitted channel:
Unknowns / restrictions:
Withdrawal or change, person and time:
Internal next step when external contact is on hold:

Do not infer a request from attendance or the host's separate request. Use only
necessary business information. This exercise needs no patient information,
clinical notes, attendee health information or real contact-list import.

## 4. Review the open work at a stated time

Filled review: October 9, 2026, 9:30 AM, America/Chicago.
Open count: 3 (F-01, F-02, F-03).
Currently overdue: 1 (F-02, due October 8 at 4:00 PM; 17 hours 30 minutes late).
F-01 is due in 30 minutes. F-03's internal review is due at noon.
F-04 is complete with fictional checklist v1 recorded by Alex October 8 at 1:45 PM.

Your review time and timezone:
Open count and IDs:
Overdue count and IDs:
Next-due work:
Waiting work and next internal review:
Unassigned rows to resolve:

## 5. Reassign one commitment without losing the miss

Filled handoff: F-02, October 9 at 9:40 AM. Alex is unexpectedly unavailable.
Maya accepts responsibility for the same internal draft. Original due remains
October 8 at 4:00 PM. Current due becomes October 9 at 11:30 AM. State stays Open;
record Rescheduled after a missed deadline. No external communication is enabled.

Commitment ID:
Previous owner:
Proposed new owner:
New owner's acceptance and time:
Next action:
Original due:
Revised due and timezone:
Reason for change:
Who recorded the change and when:
Evidence/history reference:

Keep the existing owner responsible until the new owner accepts. Preserve the
original deadline and the missed-deadline history after setting a new due time.

## 6. Complete only what the evidence supports

Filled F-02 completion: Maya files internal date-options draft v1 on October 9 at
11:10 AM. It lists October 20 and October 22 as unconfirmed options. The draft
finishes the internal preparation task. No date is reserved, offered or confirmed;
no message was sent. This is a fictional evidence description, not a real file.

Commitment ID:
Exact action completed:
Completed by / completed at / timezone:
Actual evidence file or record and version:
Authorized teammate who could open it:
What this evidence does NOT establish:
New commitment created by the result, if any:

At 11:10 AM, the sample still has 2 open commitments: F-01 and F-03.
F-01 is overdue by 1 hour 10 minutes; F-03 remains due at noon.
F-02 and F-04 are complete. None of these sample states establishes a real send.

## 7. Rehearse in your test copy

| Check | Expected | Observed / evidence |
| --- | --- | --- |
| Event and work stay separate | Completing EV-01 does not close F-01 through F-03 | Unverified |
| Every open record is actionable | One owner, next action, permission/channel and due time per open row | Unverified |
| Initial review | At Oct 9, 9:30 AM: 3 open, 1 overdue; F-02 is 17 hours 30 minutes late | Unverified |
| Accepted handoff | F-02 changes Alex to Maya at 9:40 AM; original due retained, new due 11:30 AM | Unverified |
| Permission remains scoped | F-02 handoff does not authorize external contact; F-03 remains on hold | Unverified |
| Evidence closes the right action | F-02 draft closes preparation only; no booking or send appears | Unverified |
| Final review | At 11:10 AM: F-01 and F-03 open; F-01 1 hour 10 minutes overdue | Unverified |
| Save and return | Authorized teammates reopen the same owners, dates, history and evidence | Unverified |

Use fixed sample times for the rehearsal, not the computer's current date.
Reviewer:
Remaining work / owner / next due:
Next review:

Use https://www.overskill.com/learn/verify-private-record-access for a separate
access review and https://www.overskill.com/learn/ai-app-launch-checklist for launch
checks. Keep external sending disabled during this planning exercise.