Finish a meeting with a usable handoff
Use this tool after the group has agreed on decisions and actions. Write a clear task, one owner label and an optional due date for each action. Build a shared decision brief for the group and owner checklists that can be printed or passed on as HTML files. A separate facilitator copy also includes the notes that you choose to keep out of the shared handoff.
The app does not listen to a meeting, transcribe audio, infer decisions or assign people automatically. You enter the agreed wording. It does not send messages, create calendar reminders or synchronize with a project-management account. The output is a dated snapshot you can review and distribute through your usual process.
Three downloads with different contents
Shared brief: meeting title, optional meeting date, shared decisions and the complete action table. Shared owner checklists: meeting title, optional date and action checklists grouped by owner. General decision text is left out of these compact checklists. Neither shared file includes the facilitator-only notes.
Facilitator copy: the brief, all owner checklists and the separately labelled facilitator-only notes. This copy deliberately contains those notes. Check the download label and file contents before distributing it. The on-page result previews shared actions and checklists, so facilitator notes are not copied into the shared preview, hidden markup or shared file comments.
Use the example
The example records three actions for two owners. Alex has an open keyboard-navigation review due on 2026-11-04 and a completed archive task with no due date. Dev has an open launch-checklist action due on 2026-11-05. The shared brief records the decision to wait for the accessibility review. The staffing reminder appears only in the facilitator copy.
Action identifiers A1, A2 and so on follow the current form order at build time. Removing an action and rebuilding renumbers the snapshot. The same identifiers appear in the shared table and owner checklists, making it easier to discuss an item without retyping the full description.
Owners, dates and status
Owner labels are trimmed and grouped by exact text. Use the same spelling and capitalization for the same person or team. Alex and alex are separate groups; the tool does not infer that two labels refer to one person. A label can identify a team if the group has explicitly agreed who is accountable for that action.
Dates must use YYYY-MM-DD and be real calendar dates. A blank due date is displayed as No date assigned. Dates are printed as supplied, without timezone conversion or an automatic overdue judgment. Open and Done are the only statuses. The printed checklist marks completed tasks and leaves an empty box for open tasks; checking a box on paper does not update a saved system.
Review and keep the right version
Read every action before sharing the files. The tool checks required fields, date validity and size limits; it cannot decide whether a task is clear, realistic, authorized or actually agreed. Shared decisions are visible to the group, so put information there only when you intend it to be included in the shared brief.
Changing a field, adding a row or removing an action clears the previous result and download links. Rebuild after edits. Downloaded files are independent snapshots and do not update when this page changes. Use the browser’s print command to print a saved HTML file, checking its print preview, scale and page breaks. No specific email-client layout or physical printer has been certified.
Temporary inputs and limits
The tool accepts 1–30 actions. A meeting title can contain up to 100 characters, each action up to 200, each owner label up to 60, and each of the two note fields up to 3,000. These are interface bounds to keep a handoff manageable. Multiline notes and Unicode text are supported; task and owner fields stay on one logical line.
Inputs and outputs remain in the current page’s memory. There are no accounts, uploads, hidden network requests or browser-storage history in the tool. Clear or reload removes the page state. Files you deliberately download remain on your device and can include names, decisions and, in the facilitator copy, your private notes. Keep a separate working record if you need to revise the meeting later; this app does not import its exported snapshots.
Reference: Atlassian’s task-report documentation illustrates owner and task reporting in a connected system. This tool instead prepares standalone handoff files from the actions you type.