This Action Items Template is designed to bring clarity and accountability to technical discussions, ensuring that critical decisions and follow-ups are never lost. It helps software engineers, DevOps, and data engineers standardize how they capture tasks from standups, architecture reviews, and incident post-mortems. By providing a structured format, it reduces miscommunication, accelerates onboarding, and keeps teams aligned on project progress.
Meeting Context
e.g., Architecture Review, Incident Post-Mortem, Daily Standup
Select or specify the type of meeting where the action item originated.YYYY-MM-DD
Enter the date the meeting took place.John Doe, Jane Smith, Alex Chen
List the key participants present during the discussion.Decision to migrate Kafka clusters to new hardware; Investigation of high latency in API Gateway.
Briefly summarize the main topic or decision that led to the action item.Action Item Details
Investigate root cause of intermittent 5xx errors in `auth-service`.
Clearly state the specific task to be performed.Identify the faulty component and propose a fix; Document the new deployment strategy for `frontend-app`.
Describe the expected result or deliverable upon completion of the action.https://github.com/org/repo/pull/123, https://confluence.company.com/pages/viewpage.action?pageId=456
Include links to related code, documentation, or discussion threads.Requires access to production logs; Blocked by `PR #456` approval.
Note any prerequisites or obstacles preventing immediate progress.Assignment & Timeline
@john.doe
Assign the individual or team responsible for completing the action.YYYY-MM-DD (e.g., 2024-07-15)
Specify the target date for completion.Small (2 hours), Medium (1 day), Large (3 days), 5 Story Points
Provide an estimate of the time or complexity involved.Status & Priority
Open, In Progress, Blocked, Done, Deferred
Update the current state of the action item.Critical, High, Medium, Low
Indicate the importance and urgency of the action.2024-07-01: Started investigating; encountered permission issue.
Add a brief note on the latest progress or challenges.Follow-up & Tracking
JIRA-1234, GH-Issue-567
Link to the corresponding issue tracker ticket.Discussed in subsequent standup; confirmed fix deployed to staging.
Record any subsequent discussions or decisions related to this action.Verify `login-service` response time < 100ms in production; Check `feature-flag-X` is enabled.
Outline steps to confirm the action item has been successfully completed and validated.How to Use This Template
- Open CraftNote and select "New Note" from your dashboard or project space to begin capturing.
- Choose the "Action Items Template" from your saved templates or import it directly into your new note.
- Populate the fields for Meeting Context, Action Item Details, Assignment, and Status with information from your technical discussion.
- Utilize CraftNote's collaboration features to assign owners, set due dates, and update statuses, notifying relevant team members of changes.
- Regularly review your action items list in CraftNote, using the "Last Update" and "Follow-up Notes" fields to log progress and ensure timely completion.
Customization Tips
- Integrate with Workflow: Add custom fields for specific internal IDs (e.g., `Service_ID`, `Deployment_Ticket`) or link directly to your CI/CD pipeline statuses for comprehensive tracking.
- Scenario-Specific Sections: Create separate template variations for different meeting types, such as a 'Retrospective Actions' section with fields for 'Learnings' or 'Preventative Measures'.
- Automate Reminders: Configure CraftNote to automatically send reminders to action item owners a day before the due date, reducing manual follow-ups and improving accountability.