T140 Conference follow-up action list
Conference follow-up action list
Every follow-up action from the regional conference, with an owner and a date, so Basalt Creek Industries' training coordinator and the association's education staff can see what is done, what is open and what is still waiting on attendance hours. Prepared by the events coordinator at the Workplace Safety Coordinators Association from the program register as it stood on Monday, September 28, 2026. Twenty-seven Basalt Creek members attended.
Sample template: the firm, people, clients and figures are fictional.
How fast the actions were closed
The count of completed actions climbed every day from the conference. Six were done by September 17 and 44 by September 28. The pace slowed after September 24, when the easy actions were gone and the remaining ones depended on a person or a record outside the program team.
Live example from the Dashboards app, shown with Basalt Creek Industries' demo data. Block dates move forward each week, so they can differ from the sample dates on this page.
What the actions were about
Resource requests are the largest group at 18. Credential record questions follow with 14, and session feedback follow-ups with 11. The three smallest groups are course enrolments (8), community introductions (6) and receipts and invoices (4).
Live example from the Dashboards app, shown with Basalt Creek Industries' demo data.
The 12 open actions
Each open action has one owner and a due date of October 9. The breakdown below is sample detail for this page: it shows how the 12 open actions split by group.
| Group | Open | Owner | Due | What closes it |
|---|---|---|---|---|
| Credential record questions | 5 | Marisol Thackeray | Oct 9 | The attendance hours for the member's sessions are confirmed |
| Resource requests | 3 | Callum Breckenridge | Oct 9 | The approved resource is in the member space and the member has the link |
| Session feedback follow-ups | 2 | Callum Breckenridge | Oct 9 | The member has an answer to the comment sent after the session |
| Course enrolments | 1 | Callum Breckenridge | Oct 9 | The member is enrolled and has confirmed access |
| Community introductions | 1 | Callum Breckenridge | Oct 9 | The introduction is made and both members are told |
Callum Breckenridge, member services lead, owns the action list as a whole. An action is complete only when the member has what they asked for, not when staff finish their part.
The same slide deck was requested five times
Five members asked for the same slide deck in the week after the conference. Each request was logged as its own action, and each could have taken staff time to answer on its own. Callum Breckenridge published the approved resources to the member space once and pointed all five members to that copy. Owner: Callum. Status: resolved. The five requests are counted separately from the 44 complete and the 12 open.
Rule from now on. When a second member asks for the same resource, the answer is the published link, and the repeat is counted. Nothing is attached to an email twice.
19 attendees are waiting for their credential records
Attendance was scanned in only 2 of the 5 conference rooms, so the hours for three sessions are not on the scan. They come from the paper sign-in sheets. Marisol Thackeray, the credentialing lead, decides each attendance record from the sheets, and 19 credential records are waiting for that decision. Members see no hours until she confirms them. Due: October 9. Nobody else, including the events team, enters or changes an hour.
Plan to October 12
The credential records are the longest item. The remaining open actions close alongside them.
%%{init: {"gantt": {"useWidth": 920}}}%%
gantt
dateFormat YYYY-MM-DD
axisFormat %b %d
section Credential records
Collect sign-in sheets for three sessions :active, c1, 2026-09-28, 2026-10-02
Marisol Thackeray decides 19 attendance records :active, c2, 2026-10-01, 2026-10-09
Tell each member the record status :c3, 2026-10-09, 2026-10-12
section Open actions
Close 5 credential questions :a1, 2026-10-05, 2026-10-09
Close resource, feedback, course and community actions :a2, 2026-09-29, 2026-10-09
Live example from the Dashboards app, shown with Basalt Creek Industries' demo data.
Publication checklist
I will not guess an hour. Where the scan is missing, the sign-in sheet decides, and the record says which one I used.
How to use this template
List every action created after the event, give each one an owner and a due date, and update the counts after each working session. Publish an approved resource once and count repeat requests instead of answering each one again.
| Variable | Meaning | Required |
|---|---|---|
{{event.name}} | Event the follow-up covers | Required |
{{action.counts}} | Actions created, complete, open and repeated | Required |
{{action.open_rows}} | Open actions with group, owner and due date | Required |
{{resource.published_list}} | Approved resources published to the member space | Required |
{{credential.waiting_count}} | Credential records waiting for attendance hours | Required |
{{credential.hour_source}} | Source used for each attendance record, scan or sign-in sheet | Optional |
{{action.type_counts}} | Actions by type | Optional |
If a required value is missing, show Needs review in its place and hold the list; never fill it with a guess. If the program register cannot be read, show Unavailable instead of the counts.
The live Dashboards blocks on this page show the Basalt Creek Industries demo profile. Point each block at your own client's profile, or remove it, before you share the page.