My Event Recaps

My Event Recaps is where a recap lead writes and submits the recaps they own, and where a current squad leader reads the recaps for the campuses they lead. You reach it from the sidebar when the reports module is on for your organization.

What You’ll Find

The page is split into two lists:

• To write — Recaps you are the recorded lead of that are still in DRAFT. These are the ones waiting on you.
• Campus recaps — If you currently lead a squad, every recap on a campus of a squad you lead (plus org-wide recaps with no campus). You can read these even when someone else is the lead.

Each row links to the recap’s detail page, where you write your narrative and submit. A coordinator links the events to the recap before it can be submitted; you can read the linked events there but cannot change them. The workflow — DRAFT → SUBMITTED → APPROVED — is the same one described under Admin → Event Recaps.

How Drafts Reach You

Most recaps do not need to be created by hand. The platform drafts them for you and tells you they’re waiting.

Who the lead is

The recap lead is resolved the same way for every automatically drafted recap:

1. The leader of the squad that staffed the event — the squad leader on the earliest assigned event, as of that event’s start.
2. If there is no squad leader, an Oversight member of your organization.
3. If there is no oversight member, an Organization Admin.
4. If nobody qualifies, no draft is created for that group and the skip is logged.

A coordinator is a lead only by leading the squad in step 1 — coordinators are never chosen as a fallback. Applicants and platform admins are never chosen.

When the draft appears

Once a day at 06:00 UTC (overnight in US time zones), the daily job creates a draft for every program or special event with no recap that ended at least two hours earlier and within the last seven days. It notifies the lead by bell and push notification.

• The seven-day look-back makes the job self-healing: a missed run is caught by the next one. Events older than seven days when the feature first ships get nothing — the job does not back-fill history.
• A quiet event with no incidents and no patrol logs still produces a draft to be submitted.

One recap per day and campus (program events)

Event type	One recap per
Special event	The single event
Program event	Your organization, the campus, and the org-local calendar day of the event’s start

A program event that turns up after its day’s recap already exists — created late, or moved onto that day — is added to that recap while it is still a draft. If the recap has already been submitted or approved, the event gets its own new draft instead. A submitted recap is never reopened.

Weekend services keep their existing grouping: one recap per campus per weekend.

The one reminder

If a job-created recap is still a draft three days after it was created, the lead gets one reminder by bell and push. After that it stays silent — there are no further reminders. Recaps you create by hand are never reminded.

If the event is removed before you write

Events can be deleted (there is no separate “cancelled” state). When every event linked to an automatically drafted recap is removed:

• A draft nobody has written in — no narrative, no notes, and the title unchanged from what the job generated — is deleted automatically. It had nothing to report on.
• A draft you have started — any narrative, off-duty officer info, coordinator notes, or a retitled draft — is kept. Its detail page shows an “Event removed” notice explaining that the event was removed and asking a coordinator to link an event or delete the recap.

Recaps created by hand are never deleted by the job.

The “Recaps to Write” Card

When you lead one or more open draft recaps, a “Recaps to write” card appears on your home page and mobile dashboard. It shows how many drafts are waiting, oldest first, with each row linking straight to that recap’s detail page. Members with no open drafts see no card.

Next Steps

• Admin → Event Recaps — The admin recap builder, workflow, and which recaps are created automatically.