Choose a Template
- General Meeting Notes
- Standard Meeting Minutes
- Formal / Board-Style Minutes
- 1:1 Meeting Notes
- Team Sync / Weekly Meeting
- Daily Standup
- Sales Call
- Client Meeting
- Project Review / Status
- Project Kickoff
- Interview Notes
- Leadership / Executive Meeting
- Decision Log
- Action Items
- Retrospective
- Brainstorm / Workshop
1. General Meeting Notes Template
Blank Template
Meeting: [Meeting name]
Date: [YYYY-MM-DD]
Time: [Start - End]
Location / Link: [Room or meeting link]
Facilitator: [Name]
Note Taker: [Name]
Attendees: [Names]
Objective
[What this meeting needs to accomplish]
Agenda
1. [Topic]
2. [Topic]
3. [Topic]
Discussion Notes
- [Topic]: [Key facts, context, concerns, and viewpoints]
- [Topic]: [Key facts, context, concerns, and viewpoints]
Key Takeaways
- [Takeaway]
- [Takeaway]
Decisions
- [Decision] - Decision owner: [Name]
Action Items
- [Task] - Owner: [Name] - Due: [Date] - Status: [Not started / In progress / Done]
Risks / Blockers
- [Risk or blocker]
Open Questions
- [Question]
Parking Lot
- [Topic deferred for later]
Next Meeting / Follow-Up
Date: [Date]
Purpose: [What needs to happen next]
Date: [YYYY-MM-DD]
Time: [Start - End]
Location / Link: [Room or meeting link]
Facilitator: [Name]
Note Taker: [Name]
Attendees: [Names]
Objective
[What this meeting needs to accomplish]
Agenda
1. [Topic]
2. [Topic]
3. [Topic]
Discussion Notes
- [Topic]: [Key facts, context, concerns, and viewpoints]
- [Topic]: [Key facts, context, concerns, and viewpoints]
Key Takeaways
- [Takeaway]
- [Takeaway]
Decisions
- [Decision] - Decision owner: [Name]
Action Items
- [Task] - Owner: [Name] - Due: [Date] - Status: [Not started / In progress / Done]
Risks / Blockers
- [Risk or blocker]
Open Questions
- [Question]
Parking Lot
- [Topic deferred for later]
Next Meeting / Follow-Up
Date: [Date]
Purpose: [What needs to happen next]
Filled Example
Meeting: Q4 Product Launch Readiness
Date: 2026-09-10
Time: 10:00 AM - 10:45 AM PT
Location / Link: Zoom
Facilitator: Maya Chen
Note Taker: Daniel Ruiz
Attendees: Maya Chen, Daniel Ruiz, Priya Shah, Leo Martin, Erin Cole
Objective
Confirm whether the October 6 launch date is still realistic and assign work for the remaining launch risks.
Agenda
1. Product readiness
2. Website and email assets
3. Support coverage
4. Launch risks
Discussion Notes
- Product readiness: QA has closed 38 of 41 launch-blocking issues. Two remaining issues affect account migration; one affects the Android onboarding flow.
- Website and email assets: Final product screenshots are approved. The pricing page still needs legal review before publication.
- Support coverage: Weekend support coverage is not yet confirmed. Erin proposed a rotating two-person schedule for launch weekend.
- Launch risks: The Android onboarding bug is the only issue the group considered capable of moving the launch date.
Key Takeaways
- October 6 remains the working launch date.
- The Android onboarding issue requires a go/no-go update by September 18.
- Legal review is the critical dependency for the pricing page.
Decisions
- Keep October 6 as the working launch date - Decision owner: Maya Chen
- Use a two-person rotating support schedule for launch weekend - Decision owner: Erin Cole
Action Items
- Resolve Android onboarding bug - Owner: Priya Shah - Due: 2026-09-18 - Status: In progress
- Send pricing page to legal - Owner: Daniel Ruiz - Due: 2026-09-12 - Status: Not started
- Publish launch-weekend support rota - Owner: Erin Cole - Due: 2026-09-22 - Status: Not started
Risks / Blockers
- Android onboarding bug may affect launch readiness.
- Pricing page cannot publish before legal approval.
Open Questions
- Will account migration testing require a second full regression pass?
Parking Lot
- Post-launch customer survey design.
Next Meeting / Follow-Up
Date: 2026-09-18
Purpose: Go/no-go review for Android onboarding and pricing-page approval.
Date: 2026-09-10
Time: 10:00 AM - 10:45 AM PT
Location / Link: Zoom
Facilitator: Maya Chen
Note Taker: Daniel Ruiz
Attendees: Maya Chen, Daniel Ruiz, Priya Shah, Leo Martin, Erin Cole
Objective
Confirm whether the October 6 launch date is still realistic and assign work for the remaining launch risks.
Agenda
1. Product readiness
2. Website and email assets
3. Support coverage
4. Launch risks
Discussion Notes
- Product readiness: QA has closed 38 of 41 launch-blocking issues. Two remaining issues affect account migration; one affects the Android onboarding flow.
- Website and email assets: Final product screenshots are approved. The pricing page still needs legal review before publication.
- Support coverage: Weekend support coverage is not yet confirmed. Erin proposed a rotating two-person schedule for launch weekend.
- Launch risks: The Android onboarding bug is the only issue the group considered capable of moving the launch date.
Key Takeaways
- October 6 remains the working launch date.
- The Android onboarding issue requires a go/no-go update by September 18.
- Legal review is the critical dependency for the pricing page.
Decisions
- Keep October 6 as the working launch date - Decision owner: Maya Chen
- Use a two-person rotating support schedule for launch weekend - Decision owner: Erin Cole
Action Items
- Resolve Android onboarding bug - Owner: Priya Shah - Due: 2026-09-18 - Status: In progress
- Send pricing page to legal - Owner: Daniel Ruiz - Due: 2026-09-12 - Status: Not started
- Publish launch-weekend support rota - Owner: Erin Cole - Due: 2026-09-22 - Status: Not started
Risks / Blockers
- Android onboarding bug may affect launch readiness.
- Pricing page cannot publish before legal approval.
Open Questions
- Will account migration testing require a second full regression pass?
Parking Lot
- Post-launch customer survey design.
Next Meeting / Follow-Up
Date: 2026-09-18
Purpose: Go/no-go review for Android onboarding and pricing-page approval.
AI-Ready Template
TASK
Convert the transcript or raw notes into the template below.
SOURCE RULES
- Use only information explicitly contained in the source.
- Do not invent names, dates, owners, decisions, commitments, deadlines, metrics, reasons, votes, or outcomes.
- Do not treat a suggestion as a decision.
- Do not treat a discussion point as an action item.
- Do not infer an owner or due date.
- Use "Not specified" for a required field that is missing.
- Use "Unresolved" for a question that was raised but not answered.
- Keep discussion, decisions, action items, and open questions separate.
- Preserve uncertainty and disagreement when they exist.
OUTPUT FORMAT
Meeting: [ ]
Date: [ ]
Time: [ ]
Location / Link: [ ]
Facilitator: [ ]
Note Taker: [ ]
Attendees: [ ]
Objective
[ ]
Agenda
1. [ ]
Discussion Notes
- [Topic]: [ ]
Key Takeaways
- [ ]
Decisions
- [Decision] - Decision owner: [ ]
Action Items
- [Task] - Owner: [ ] - Due: [ ] - Status: [ ]
Risks / Blockers
- [ ]
Open Questions
- [ ]
Parking Lot
- [ ]
Next Meeting / Follow-Up
Date: [ ]
Purpose: [ ]
Return only the completed template.
Convert the transcript or raw notes into the template below.
SOURCE RULES
- Use only information explicitly contained in the source.
- Do not invent names, dates, owners, decisions, commitments, deadlines, metrics, reasons, votes, or outcomes.
- Do not treat a suggestion as a decision.
- Do not treat a discussion point as an action item.
- Do not infer an owner or due date.
- Use "Not specified" for a required field that is missing.
- Use "Unresolved" for a question that was raised but not answered.
- Keep discussion, decisions, action items, and open questions separate.
- Preserve uncertainty and disagreement when they exist.
OUTPUT FORMAT
Meeting: [ ]
Date: [ ]
Time: [ ]
Location / Link: [ ]
Facilitator: [ ]
Note Taker: [ ]
Attendees: [ ]
Objective
[ ]
Agenda
1. [ ]
Discussion Notes
- [Topic]: [ ]
Key Takeaways
- [ ]
Decisions
- [Decision] - Decision owner: [ ]
Action Items
- [Task] - Owner: [ ] - Due: [ ] - Status: [ ]
Risks / Blockers
- [ ]
Open Questions
- [ ]
Parking Lot
- [ ]
Next Meeting / Follow-Up
Date: [ ]
Purpose: [ ]
Return only the completed template.
2. Standard Meeting Minutes Template
Blank Template
Meeting Name: [ ]
Date: [YYYY-MM-DD]
Time: [Start - End]
Location: [ ]
Chair / Facilitator: [ ]
Minute Taker: [ ]
Attendees: [ ]
Absent: [ ]
Meeting Purpose
[ ]
Agenda Item 1: [Title]
Discussion Summary:
[Concise factual summary]
Decision:
[Decision or None]
Action:
[Task - Owner - Due date]
Agenda Item 2: [Title]
Discussion Summary:
[ ]
Decision:
[ ]
Action:
[ ]
Other Business
[ ]
Decisions Summary
- [Decision]
Action Items Summary
- [Task] - Owner: [ ] - Due: [ ]
Next Meeting
Date: [ ]
Adjournment
Time: [ ]
Minutes Prepared By: [ ]
Date: [YYYY-MM-DD]
Time: [Start - End]
Location: [ ]
Chair / Facilitator: [ ]
Minute Taker: [ ]
Attendees: [ ]
Absent: [ ]
Meeting Purpose
[ ]
Agenda Item 1: [Title]
Discussion Summary:
[Concise factual summary]
Decision:
[Decision or None]
Action:
[Task - Owner - Due date]
Agenda Item 2: [Title]
Discussion Summary:
[ ]
Decision:
[ ]
Action:
[ ]
Other Business
[ ]
Decisions Summary
- [Decision]
Action Items Summary
- [Task] - Owner: [ ] - Due: [ ]
Next Meeting
Date: [ ]
Adjournment
Time: [ ]
Minutes Prepared By: [ ]
Filled Example
Meeting Name: Operations Weekly Review
Date: 2026-09-08
Time: 2:00 PM - 2:50 PM ET
Location: Conference Room B / Teams
Chair / Facilitator: Jordan Lee
Minute Taker: Sofia Patel
Attendees: Jordan Lee, Sofia Patel, Marcus Green, Hana Kim, Alex Reed
Absent: None
Meeting Purpose
Review fulfillment performance, open staffing gaps, and the September inventory count.
Agenda Item 1: Fulfillment performance
Discussion Summary:
Average order processing time increased from 7.8 hours to 9.1 hours last week. Marcus attributed most of the increase to two late inbound shipments and a temporary packing-station outage.
Decision:
Keep the current service-level target and review again after two normal shipment cycles.
Action:
Marcus Green to provide a two-week processing-time comparison by 2026-09-22.
Agenda Item 2: Weekend staffing
Discussion Summary:
The Saturday shift is short by two people for the next three weekends. Hana confirmed that four part-time staff members have availability.
Decision:
Offer the open Saturday shifts to trained part-time staff before requesting overtime.
Action:
Hana Kim to finalize the September weekend roster by 2026-09-11.
Agenda Item 3: Inventory count
Discussion Summary:
The full inventory count remains scheduled for September 26. Finance requested that damaged stock be separated before counting begins.
Decision:
No date change. Damaged stock will be tagged by September 24.
Action:
Alex Reed to coordinate damaged-stock tagging by 2026-09-24.
Other Business
Sofia requested that October holiday coverage be added to the next agenda.
Decisions Summary
- Keep the existing fulfillment service-level target.
- Fill Saturday gaps with trained part-time staff before approving overtime.
- Keep the September 26 inventory count date.
Action Items Summary
- Two-week processing-time comparison - Owner: Marcus Green - Due: 2026-09-22
- September weekend roster - Owner: Hana Kim - Due: 2026-09-11
- Damaged-stock tagging - Owner: Alex Reed - Due: 2026-09-24
Next Meeting
Date: 2026-09-15
Adjournment
Time: 2:50 PM ET
Minutes Prepared By: Sofia Patel
Date: 2026-09-08
Time: 2:00 PM - 2:50 PM ET
Location: Conference Room B / Teams
Chair / Facilitator: Jordan Lee
Minute Taker: Sofia Patel
Attendees: Jordan Lee, Sofia Patel, Marcus Green, Hana Kim, Alex Reed
Absent: None
Meeting Purpose
Review fulfillment performance, open staffing gaps, and the September inventory count.
Agenda Item 1: Fulfillment performance
Discussion Summary:
Average order processing time increased from 7.8 hours to 9.1 hours last week. Marcus attributed most of the increase to two late inbound shipments and a temporary packing-station outage.
Decision:
Keep the current service-level target and review again after two normal shipment cycles.
Action:
Marcus Green to provide a two-week processing-time comparison by 2026-09-22.
Agenda Item 2: Weekend staffing
Discussion Summary:
The Saturday shift is short by two people for the next three weekends. Hana confirmed that four part-time staff members have availability.
Decision:
Offer the open Saturday shifts to trained part-time staff before requesting overtime.
Action:
Hana Kim to finalize the September weekend roster by 2026-09-11.
Agenda Item 3: Inventory count
Discussion Summary:
The full inventory count remains scheduled for September 26. Finance requested that damaged stock be separated before counting begins.
Decision:
No date change. Damaged stock will be tagged by September 24.
Action:
Alex Reed to coordinate damaged-stock tagging by 2026-09-24.
Other Business
Sofia requested that October holiday coverage be added to the next agenda.
Decisions Summary
- Keep the existing fulfillment service-level target.
- Fill Saturday gaps with trained part-time staff before approving overtime.
- Keep the September 26 inventory count date.
Action Items Summary
- Two-week processing-time comparison - Owner: Marcus Green - Due: 2026-09-22
- September weekend roster - Owner: Hana Kim - Due: 2026-09-11
- Damaged-stock tagging - Owner: Alex Reed - Due: 2026-09-24
Next Meeting
Date: 2026-09-15
Adjournment
Time: 2:50 PM ET
Minutes Prepared By: Sofia Patel
AI-Ready Template
TASK
Convert the transcript or raw notes into the template below.
SOURCE RULES
- Use only information explicitly contained in the source.
- Do not invent names, dates, owners, decisions, commitments, deadlines, metrics, reasons, votes, or outcomes.
- Do not treat a suggestion as a decision.
- Do not treat a discussion point as an action item.
- Do not infer an owner or due date.
- Use "Not specified" for a required field that is missing.
- Use "Unresolved" for a question that was raised but not answered.
- Keep discussion, decisions, action items, and open questions separate.
- Preserve uncertainty and disagreement when they exist.
OUTPUT FORMAT
Meeting Name: [ ]
Date: [ ]
Time: [ ]
Location: [ ]
Chair / Facilitator: [ ]
Minute Taker: [ ]
Attendees: [ ]
Absent: [ ]
Meeting Purpose
[ ]
Agenda Item 1: [ ]
Discussion Summary:
[ ]
Decision:
[ ]
Action:
[ ]
Other Business
[ ]
Decisions Summary
- [ ]
Action Items Summary
- [Task] - Owner: [ ] - Due: [ ]
Next Meeting
Date: [ ]
Adjournment
Time: [ ]
Minutes Prepared By: [ ]
Return only the completed template.
Convert the transcript or raw notes into the template below.
SOURCE RULES
- Use only information explicitly contained in the source.
- Do not invent names, dates, owners, decisions, commitments, deadlines, metrics, reasons, votes, or outcomes.
- Do not treat a suggestion as a decision.
- Do not treat a discussion point as an action item.
- Do not infer an owner or due date.
- Use "Not specified" for a required field that is missing.
- Use "Unresolved" for a question that was raised but not answered.
- Keep discussion, decisions, action items, and open questions separate.
- Preserve uncertainty and disagreement when they exist.
OUTPUT FORMAT
Meeting Name: [ ]
Date: [ ]
Time: [ ]
Location: [ ]
Chair / Facilitator: [ ]
Minute Taker: [ ]
Attendees: [ ]
Absent: [ ]
Meeting Purpose
[ ]
Agenda Item 1: [ ]
Discussion Summary:
[ ]
Decision:
[ ]
Action:
[ ]
Other Business
[ ]
Decisions Summary
- [ ]
Action Items Summary
- [Task] - Owner: [ ] - Due: [ ]
Next Meeting
Date: [ ]
Adjournment
Time: [ ]
Minutes Prepared By: [ ]
Return only the completed template.
3. Formal / Board-Style Meeting Minutes Template
Blank Template
Organization: [ ]
Meeting Type: [Board / Committee / Annual / Special]
Date: [YYYY-MM-DD]
Time: [Start - End]
Location: [ ]
Chair: [ ]
Secretary / Minute Taker: [ ]
Directors / Members Present: [ ]
Directors / Members Absent: [ ]
Guests: [ ]
1. Call to Order
The meeting was called to order at [time] by [name].
2. Quorum
[Quorum confirmed / Not confirmed / Not specified]
3. Approval of Previous Minutes
Motion / action: [ ]
Outcome: [ ]
4. Reports
Report: [ ]
Summary: [ ]
Action / Decision: [ ]
5. Unfinished Business
Topic: [ ]
Discussion: [ ]
Motion / Decision: [ ]
Vote / Outcome: [ ]
6. New Business
Topic: [ ]
Discussion: [ ]
Motion: [Exact motion, if stated]
Proposed By: [ ]
Seconded By: [ ]
Vote: [ ]
Outcome: [Passed / Failed / Tabled / Not specified]
7. Resolutions / Decisions
- [Resolution or decision exactly as approved]
8. Action Items
- [Task] - Owner: [ ] - Due: [ ]
9. Next Meeting
Date: [ ]
10. Adjournment
The meeting was adjourned at [time].
Prepared By: [ ]
Approved By: [ ]
Approval Date: [ ]
Meeting Type: [Board / Committee / Annual / Special]
Date: [YYYY-MM-DD]
Time: [Start - End]
Location: [ ]
Chair: [ ]
Secretary / Minute Taker: [ ]
Directors / Members Present: [ ]
Directors / Members Absent: [ ]
Guests: [ ]
1. Call to Order
The meeting was called to order at [time] by [name].
2. Quorum
[Quorum confirmed / Not confirmed / Not specified]
3. Approval of Previous Minutes
Motion / action: [ ]
Outcome: [ ]
4. Reports
Report: [ ]
Summary: [ ]
Action / Decision: [ ]
5. Unfinished Business
Topic: [ ]
Discussion: [ ]
Motion / Decision: [ ]
Vote / Outcome: [ ]
6. New Business
Topic: [ ]
Discussion: [ ]
Motion: [Exact motion, if stated]
Proposed By: [ ]
Seconded By: [ ]
Vote: [ ]
Outcome: [Passed / Failed / Tabled / Not specified]
7. Resolutions / Decisions
- [Resolution or decision exactly as approved]
8. Action Items
- [Task] - Owner: [ ] - Due: [ ]
9. Next Meeting
Date: [ ]
10. Adjournment
The meeting was adjourned at [time].
Prepared By: [ ]
Approved By: [ ]
Approval Date: [ ]
Filled Example
Organization: Harborview Community Arts Foundation
Meeting Type: Board Meeting
Date: 2026-09-03
Time: 6:00 PM - 7:18 PM
Location: Harborview Arts Center, Room 204
Chair: Elaine Brooks
Secretary / Minute Taker: Noah Bennett
Directors / Members Present: Elaine Brooks, Noah Bennett, Carla Nguyen, Thomas Reed, Priya Nair
Directors / Members Absent: Javier Ortiz
Guests: Morgan Ellis, Executive Director
1. Call to Order
The meeting was called to order at 6:00 PM by Elaine Brooks.
2. Quorum
Quorum confirmed.
3. Approval of Previous Minutes
Motion / action: Carla Nguyen moved to approve the August 6, 2026 minutes as circulated. Thomas Reed seconded the motion.
Outcome: Motion passed unanimously.
4. Reports
Report: Executive Director report
Summary: Morgan Ellis reported that summer-program enrollment reached 412 participants and that two fall workshops remain below enrollment targets.
Action / Decision: Staff will consolidate the two under-enrolled workshops if combined enrollment remains below 18 by September 15.
5. Unfinished Business
Topic: Roof repair contract
Discussion: The board reviewed two revised bids. The finance committee recommended the $42,800 proposal from Cedar Construction because it included drainage repair and a five-year workmanship warranty.
Motion / Decision: Approve the Cedar Construction proposal for $42,800, subject to final insurance verification.
Vote / Outcome: 5 in favor, 0 opposed. Motion passed.
6. New Business
Topic: 2027 fundraising gala date
Discussion: The board discussed venue availability for April 17 and April 24.
Motion: Reserve April 24, 2027 as the gala date and authorize a venue deposit up to $5,000.
Proposed By: Priya Nair
Seconded By: Noah Bennett
Vote: 5 in favor, 0 opposed
Outcome: Passed
7. Resolutions / Decisions
- Approve the Cedar Construction roof repair proposal for $42,800, subject to final insurance verification.
- Reserve April 24, 2027 for the fundraising gala and authorize a venue deposit up to $5,000.
8. Action Items
- Verify Cedar Construction insurance documentation - Owner: Morgan Ellis - Due: 2026-09-10
- Place gala venue hold and confirm deposit terms - Owner: Priya Nair - Due: 2026-09-18
9. Next Meeting
Date: 2026-10-01
10. Adjournment
The meeting was adjourned at 7:18 PM.
Prepared By: Noah Bennett
Approved By: Not specified
Approval Date: Not specified
Meeting Type: Board Meeting
Date: 2026-09-03
Time: 6:00 PM - 7:18 PM
Location: Harborview Arts Center, Room 204
Chair: Elaine Brooks
Secretary / Minute Taker: Noah Bennett
Directors / Members Present: Elaine Brooks, Noah Bennett, Carla Nguyen, Thomas Reed, Priya Nair
Directors / Members Absent: Javier Ortiz
Guests: Morgan Ellis, Executive Director
1. Call to Order
The meeting was called to order at 6:00 PM by Elaine Brooks.
2. Quorum
Quorum confirmed.
3. Approval of Previous Minutes
Motion / action: Carla Nguyen moved to approve the August 6, 2026 minutes as circulated. Thomas Reed seconded the motion.
Outcome: Motion passed unanimously.
4. Reports
Report: Executive Director report
Summary: Morgan Ellis reported that summer-program enrollment reached 412 participants and that two fall workshops remain below enrollment targets.
Action / Decision: Staff will consolidate the two under-enrolled workshops if combined enrollment remains below 18 by September 15.
5. Unfinished Business
Topic: Roof repair contract
Discussion: The board reviewed two revised bids. The finance committee recommended the $42,800 proposal from Cedar Construction because it included drainage repair and a five-year workmanship warranty.
Motion / Decision: Approve the Cedar Construction proposal for $42,800, subject to final insurance verification.
Vote / Outcome: 5 in favor, 0 opposed. Motion passed.
6. New Business
Topic: 2027 fundraising gala date
Discussion: The board discussed venue availability for April 17 and April 24.
Motion: Reserve April 24, 2027 as the gala date and authorize a venue deposit up to $5,000.
Proposed By: Priya Nair
Seconded By: Noah Bennett
Vote: 5 in favor, 0 opposed
Outcome: Passed
7. Resolutions / Decisions
- Approve the Cedar Construction roof repair proposal for $42,800, subject to final insurance verification.
- Reserve April 24, 2027 for the fundraising gala and authorize a venue deposit up to $5,000.
8. Action Items
- Verify Cedar Construction insurance documentation - Owner: Morgan Ellis - Due: 2026-09-10
- Place gala venue hold and confirm deposit terms - Owner: Priya Nair - Due: 2026-09-18
9. Next Meeting
Date: 2026-10-01
10. Adjournment
The meeting was adjourned at 7:18 PM.
Prepared By: Noah Bennett
Approved By: Not specified
Approval Date: Not specified
AI-Ready Template
TASK
Convert the transcript or raw notes into the template below.
SOURCE RULES
- Use only information explicitly contained in the source.
- Do not invent names, dates, owners, decisions, commitments, deadlines, metrics, reasons, votes, or outcomes.
- Do not treat a suggestion as a decision.
- Do not treat a discussion point as an action item.
- Do not infer an owner or due date.
- Use "Not specified" for a required field that is missing.
- Use "Unresolved" for a question that was raised but not answered.
- Keep discussion, decisions, action items, and open questions separate.
- Preserve uncertainty and disagreement when they exist.
FORMAL-MINUTES RULES
- Record a motion, second, vote, resolution, quorum status, or approval only when the source explicitly states it.
- Preserve the exact substance of motions and resolutions; do not upgrade informal agreement into a formal motion.
- Do not infer legal sufficiency, compliance, or approval status.
OUTPUT FORMAT
Organization: [ ]
Meeting Type: [ ]
Date: [ ]
Time: [ ]
Location: [ ]
Chair: [ ]
Secretary / Minute Taker: [ ]
Directors / Members Present: [ ]
Directors / Members Absent: [ ]
Guests: [ ]
1. Call to Order
[ ]
2. Quorum
[ ]
3. Approval of Previous Minutes
Motion / action: [ ]
Outcome: [ ]
4. Reports
Report: [ ]
Summary: [ ]
Action / Decision: [ ]
5. Unfinished Business
Topic: [ ]
Discussion: [ ]
Motion / Decision: [ ]
Vote / Outcome: [ ]
6. New Business
Topic: [ ]
Discussion: [ ]
Motion: [ ]
Proposed By: [ ]
Seconded By: [ ]
Vote: [ ]
Outcome: [ ]
7. Resolutions / Decisions
- [ ]
8. Action Items
- [Task] - Owner: [ ] - Due: [ ]
9. Next Meeting
Date: [ ]
10. Adjournment
[ ]
Prepared By: [ ]
Approved By: [ ]
Approval Date: [ ]
Return only the completed template.
Convert the transcript or raw notes into the template below.
SOURCE RULES
- Use only information explicitly contained in the source.
- Do not invent names, dates, owners, decisions, commitments, deadlines, metrics, reasons, votes, or outcomes.
- Do not treat a suggestion as a decision.
- Do not treat a discussion point as an action item.
- Do not infer an owner or due date.
- Use "Not specified" for a required field that is missing.
- Use "Unresolved" for a question that was raised but not answered.
- Keep discussion, decisions, action items, and open questions separate.
- Preserve uncertainty and disagreement when they exist.
FORMAL-MINUTES RULES
- Record a motion, second, vote, resolution, quorum status, or approval only when the source explicitly states it.
- Preserve the exact substance of motions and resolutions; do not upgrade informal agreement into a formal motion.
- Do not infer legal sufficiency, compliance, or approval status.
OUTPUT FORMAT
Organization: [ ]
Meeting Type: [ ]
Date: [ ]
Time: [ ]
Location: [ ]
Chair: [ ]
Secretary / Minute Taker: [ ]
Directors / Members Present: [ ]
Directors / Members Absent: [ ]
Guests: [ ]
1. Call to Order
[ ]
2. Quorum
[ ]
3. Approval of Previous Minutes
Motion / action: [ ]
Outcome: [ ]
4. Reports
Report: [ ]
Summary: [ ]
Action / Decision: [ ]
5. Unfinished Business
Topic: [ ]
Discussion: [ ]
Motion / Decision: [ ]
Vote / Outcome: [ ]
6. New Business
Topic: [ ]
Discussion: [ ]
Motion: [ ]
Proposed By: [ ]
Seconded By: [ ]
Vote: [ ]
Outcome: [ ]
7. Resolutions / Decisions
- [ ]
8. Action Items
- [Task] - Owner: [ ] - Due: [ ]
9. Next Meeting
Date: [ ]
10. Adjournment
[ ]
Prepared By: [ ]
Approved By: [ ]
Approval Date: [ ]
Return only the completed template.
4. 1:1 Meeting Notes Template
Blank Template
1:1: [Manager] + [Team member]
Date: [YYYY-MM-DD]
Time: [ ]
Check-In
- Energy / workload: [ ]
- Anything urgent: [ ]
Wins Since Last 1:1
- [ ]
Current Priorities
- [Priority] - Status: [ ]
Blockers
- [ ]
Manager Support Needed
- [ ]
Feedback for Team Member
- [Specific behavior / outcome / context]
Feedback for Manager
- [ ]
Career / Development
- Goal: [ ]
- Skill / experience to build: [ ]
- Opportunity / next step: [ ]
Topics the Team Member Wants to Raise
- [ ]
Decisions
- [ ]
Commitments / Follow-Ups
- [Commitment] - Owner: [ ] - Due: [ ]
Topics for Next 1:1
- [ ]
Date: [YYYY-MM-DD]
Time: [ ]
Check-In
- Energy / workload: [ ]
- Anything urgent: [ ]
Wins Since Last 1:1
- [ ]
Current Priorities
- [Priority] - Status: [ ]
Blockers
- [ ]
Manager Support Needed
- [ ]
Feedback for Team Member
- [Specific behavior / outcome / context]
Feedback for Manager
- [ ]
Career / Development
- Goal: [ ]
- Skill / experience to build: [ ]
- Opportunity / next step: [ ]
Topics the Team Member Wants to Raise
- [ ]
Decisions
- [ ]
Commitments / Follow-Ups
- [Commitment] - Owner: [ ] - Due: [ ]
Topics for Next 1:1
- [ ]
Filled Example
1:1: Olivia Park + Marcus Bell
Date: 2026-09-09
Time: 3:30 PM - 4:00 PM
Check-In
- Energy / workload: Marcus said workload is manageable but the reporting cycle has created several late afternoons.
- Anything urgent: The customer-health dashboard needs a final data check before Friday.
Wins Since Last 1:1
- Marcus completed the renewal-risk analysis two days early.
- The customer-success team adopted his revised escalation checklist.
Current Priorities
- Customer-health dashboard - Status: Final validation
- Q4 retention analysis - Status: In progress
- Onboarding documentation refresh - Status: Not started
Blockers
- Analytics has not confirmed the definition for "inactive account" in the new dashboard.
Manager Support Needed
- Olivia will ask Analytics to confirm the inactive-account definition by Thursday.
Feedback for Team Member
- Olivia said Marcus's renewal-risk analysis was easy to act on because it separated confirmed churn risk from early warning signals.
- Olivia asked Marcus to flag data-definition uncertainty earlier instead of waiting until final review.
Feedback for Manager
- Marcus asked for fewer last-minute priority changes during reporting week.
Career / Development
- Goal: Lead a cross-functional retention project in Q4.
- Skill / experience to build: Executive presentation and project coordination.
- Opportunity / next step: Marcus will present the retention analysis at the October operating review.
Topics the Team Member Wants to Raise
- Whether the onboarding documentation project can move to October.
Decisions
- Move the onboarding documentation refresh to the week of October 5.
Commitments / Follow-Ups
- Confirm inactive-account definition - Owner: Olivia Park - Due: 2026-09-10
- Prepare a five-slide retention summary for operating review - Owner: Marcus Bell - Due: 2026-09-30
Topics for Next 1:1
- Review operating-review presentation draft.
- Revisit workload during reporting week.
Date: 2026-09-09
Time: 3:30 PM - 4:00 PM
Check-In
- Energy / workload: Marcus said workload is manageable but the reporting cycle has created several late afternoons.
- Anything urgent: The customer-health dashboard needs a final data check before Friday.
Wins Since Last 1:1
- Marcus completed the renewal-risk analysis two days early.
- The customer-success team adopted his revised escalation checklist.
Current Priorities
- Customer-health dashboard - Status: Final validation
- Q4 retention analysis - Status: In progress
- Onboarding documentation refresh - Status: Not started
Blockers
- Analytics has not confirmed the definition for "inactive account" in the new dashboard.
Manager Support Needed
- Olivia will ask Analytics to confirm the inactive-account definition by Thursday.
Feedback for Team Member
- Olivia said Marcus's renewal-risk analysis was easy to act on because it separated confirmed churn risk from early warning signals.
- Olivia asked Marcus to flag data-definition uncertainty earlier instead of waiting until final review.
Feedback for Manager
- Marcus asked for fewer last-minute priority changes during reporting week.
Career / Development
- Goal: Lead a cross-functional retention project in Q4.
- Skill / experience to build: Executive presentation and project coordination.
- Opportunity / next step: Marcus will present the retention analysis at the October operating review.
Topics the Team Member Wants to Raise
- Whether the onboarding documentation project can move to October.
Decisions
- Move the onboarding documentation refresh to the week of October 5.
Commitments / Follow-Ups
- Confirm inactive-account definition - Owner: Olivia Park - Due: 2026-09-10
- Prepare a five-slide retention summary for operating review - Owner: Marcus Bell - Due: 2026-09-30
Topics for Next 1:1
- Review operating-review presentation draft.
- Revisit workload during reporting week.
AI-Ready Template
TASK
Convert the transcript or raw notes into the template below.
SOURCE RULES
- Use only information explicitly contained in the source.
- Do not invent names, dates, owners, decisions, commitments, deadlines, metrics, reasons, votes, or outcomes.
- Do not treat a suggestion as a decision.
- Do not treat a discussion point as an action item.
- Do not infer an owner or due date.
- Use "Not specified" for a required field that is missing.
- Use "Unresolved" for a question that was raised but not answered.
- Keep discussion, decisions, action items, and open questions separate.
- Preserve uncertainty and disagreement when they exist.
1:1 RULES
- Keep personal or sensitive conversation in neutral factual language.
- Do not convert casual comments into performance ratings, HR conclusions, diagnoses, or disciplinary findings.
- Attribute feedback to the speaker when attribution matters.
OUTPUT FORMAT
1:1: [ ] + [ ]
Date: [ ]
Time: [ ]
Check-In
- Energy / workload: [ ]
- Anything urgent: [ ]
Wins Since Last 1:1
- [ ]
Current Priorities
- [Priority] - Status: [ ]
Blockers
- [ ]
Manager Support Needed
- [ ]
Feedback for Team Member
- [ ]
Feedback for Manager
- [ ]
Career / Development
- Goal: [ ]
- Skill / experience to build: [ ]
- Opportunity / next step: [ ]
Topics the Team Member Wants to Raise
- [ ]
Decisions
- [ ]
Commitments / Follow-Ups
- [Commitment] - Owner: [ ] - Due: [ ]
Topics for Next 1:1
- [ ]
Return only the completed template.
Convert the transcript or raw notes into the template below.
SOURCE RULES
- Use only information explicitly contained in the source.
- Do not invent names, dates, owners, decisions, commitments, deadlines, metrics, reasons, votes, or outcomes.
- Do not treat a suggestion as a decision.
- Do not treat a discussion point as an action item.
- Do not infer an owner or due date.
- Use "Not specified" for a required field that is missing.
- Use "Unresolved" for a question that was raised but not answered.
- Keep discussion, decisions, action items, and open questions separate.
- Preserve uncertainty and disagreement when they exist.
1:1 RULES
- Keep personal or sensitive conversation in neutral factual language.
- Do not convert casual comments into performance ratings, HR conclusions, diagnoses, or disciplinary findings.
- Attribute feedback to the speaker when attribution matters.
OUTPUT FORMAT
1:1: [ ] + [ ]
Date: [ ]
Time: [ ]
Check-In
- Energy / workload: [ ]
- Anything urgent: [ ]
Wins Since Last 1:1
- [ ]
Current Priorities
- [Priority] - Status: [ ]
Blockers
- [ ]
Manager Support Needed
- [ ]
Feedback for Team Member
- [ ]
Feedback for Manager
- [ ]
Career / Development
- Goal: [ ]
- Skill / experience to build: [ ]
- Opportunity / next step: [ ]
Topics the Team Member Wants to Raise
- [ ]
Decisions
- [ ]
Commitments / Follow-Ups
- [Commitment] - Owner: [ ] - Due: [ ]
Topics for Next 1:1
- [ ]
Return only the completed template.
5. Team Sync / Weekly Team Meeting Notes Template
Blank Template
Team: [ ]
Meeting: [Weekly sync / team meeting]
Date: [YYYY-MM-DD]
Facilitator: [ ]
Attendees: [ ]
Weekly Goal
[ ]
Metrics / KPIs
- [Metric]: [Current value / change / note]
Progress Since Last Meeting
- [Workstream]: [Update]
Team Updates
- [Person / function]: [Update]
Blockers
- [Blocker] - Impact: [ ] - Owner: [ ]
Cross-Team Dependencies
- [Dependency] - Waiting on: [Team / person]
Decisions
- [Decision]
Action Items
- [Task] - Owner: [ ] - Due: [ ]
Announcements
- [ ]
Parking Lot
- [ ]
Next Sync
Date: [ ]
Focus: [ ]
Meeting: [Weekly sync / team meeting]
Date: [YYYY-MM-DD]
Facilitator: [ ]
Attendees: [ ]
Weekly Goal
[ ]
Metrics / KPIs
- [Metric]: [Current value / change / note]
Progress Since Last Meeting
- [Workstream]: [Update]
Team Updates
- [Person / function]: [Update]
Blockers
- [Blocker] - Impact: [ ] - Owner: [ ]
Cross-Team Dependencies
- [Dependency] - Waiting on: [Team / person]
Decisions
- [Decision]
Action Items
- [Task] - Owner: [ ] - Due: [ ]
Announcements
- [ ]
Parking Lot
- [ ]
Next Sync
Date: [ ]
Focus: [ ]
Filled Example
Team: Growth Operations
Meeting: Weekly Team Sync
Date: 2026-09-11
Facilitator: Aisha Grant
Attendees: Aisha Grant, Ben Wong, Chloe Martin, Diego Santos, Leah Price
Weekly Goal
Finish September campaign QA and remove the two blockers preventing the new lead-routing rule from going live.
Metrics / KPIs
- Qualified leads: 1,284 this week, up 6% week over week
- Demo-booking rate: 8.7%, down from 9.2%
- Lead-response SLA: 91% within 15 minutes, target 95%
Progress Since Last Meeting
- Campaign QA: 17 of 19 campaigns approved.
- Lead routing: CRM logic is built; territory mapping is waiting on Sales Ops confirmation.
- Reporting: New weekly funnel dashboard is live for the North America team.
Team Updates
- Ben: Found duplicate UTM rules affecting two paid-social campaigns.
- Chloe: Completed landing-page QA and sent three copy corrections.
- Diego: Waiting for final territory ownership file from Sales Ops.
- Leah: Scheduled a response-time review with SDR managers.
Blockers
- Territory ownership file is not final - Impact: Lead-routing launch cannot proceed - Owner: Diego Santos
- Two campaigns have duplicate UTM rules - Impact: Attribution may be split - Owner: Ben Wong
Cross-Team Dependencies
- Final territory ownership - Waiting on: Sales Operations
- Legal approval for one customer quote - Waiting on: Legal
Decisions
- Delay lead-routing launch until territory ownership is confirmed rather than launching with temporary rules.
Action Items
- Fix duplicate UTM rules - Owner: Ben Wong - Due: 2026-09-12
- Obtain final territory file - Owner: Diego Santos - Due: 2026-09-14
- Review lead-response SLA with SDR managers - Owner: Leah Price - Due: 2026-09-16
Announcements
- Monday's sync will start 30 minutes later because of the company all-hands.
Parking Lot
- Q4 dashboard redesign.
Next Sync
Date: 2026-09-14
Focus: Lead-routing go/no-go.
Meeting: Weekly Team Sync
Date: 2026-09-11
Facilitator: Aisha Grant
Attendees: Aisha Grant, Ben Wong, Chloe Martin, Diego Santos, Leah Price
Weekly Goal
Finish September campaign QA and remove the two blockers preventing the new lead-routing rule from going live.
Metrics / KPIs
- Qualified leads: 1,284 this week, up 6% week over week
- Demo-booking rate: 8.7%, down from 9.2%
- Lead-response SLA: 91% within 15 minutes, target 95%
Progress Since Last Meeting
- Campaign QA: 17 of 19 campaigns approved.
- Lead routing: CRM logic is built; territory mapping is waiting on Sales Ops confirmation.
- Reporting: New weekly funnel dashboard is live for the North America team.
Team Updates
- Ben: Found duplicate UTM rules affecting two paid-social campaigns.
- Chloe: Completed landing-page QA and sent three copy corrections.
- Diego: Waiting for final territory ownership file from Sales Ops.
- Leah: Scheduled a response-time review with SDR managers.
Blockers
- Territory ownership file is not final - Impact: Lead-routing launch cannot proceed - Owner: Diego Santos
- Two campaigns have duplicate UTM rules - Impact: Attribution may be split - Owner: Ben Wong
Cross-Team Dependencies
- Final territory ownership - Waiting on: Sales Operations
- Legal approval for one customer quote - Waiting on: Legal
Decisions
- Delay lead-routing launch until territory ownership is confirmed rather than launching with temporary rules.
Action Items
- Fix duplicate UTM rules - Owner: Ben Wong - Due: 2026-09-12
- Obtain final territory file - Owner: Diego Santos - Due: 2026-09-14
- Review lead-response SLA with SDR managers - Owner: Leah Price - Due: 2026-09-16
Announcements
- Monday's sync will start 30 minutes later because of the company all-hands.
Parking Lot
- Q4 dashboard redesign.
Next Sync
Date: 2026-09-14
Focus: Lead-routing go/no-go.
AI-Ready Template
TASK
Convert the transcript or raw notes into the template below.
SOURCE RULES
- Use only information explicitly contained in the source.
- Do not invent names, dates, owners, decisions, commitments, deadlines, metrics, reasons, votes, or outcomes.
- Do not treat a suggestion as a decision.
- Do not treat a discussion point as an action item.
- Do not infer an owner or due date.
- Use "Not specified" for a required field that is missing.
- Use "Unresolved" for a question that was raised but not answered.
- Keep discussion, decisions, action items, and open questions separate.
- Preserve uncertainty and disagreement when they exist.
OUTPUT FORMAT
Team: [ ]
Meeting: [ ]
Date: [ ]
Facilitator: [ ]
Attendees: [ ]
Weekly Goal
[ ]
Metrics / KPIs
- [Metric]: [ ]
Progress Since Last Meeting
- [Workstream]: [ ]
Team Updates
- [Person / function]: [ ]
Blockers
- [Blocker] - Impact: [ ] - Owner: [ ]
Cross-Team Dependencies
- [Dependency] - Waiting on: [ ]
Decisions
- [ ]
Action Items
- [Task] - Owner: [ ] - Due: [ ]
Announcements
- [ ]
Parking Lot
- [ ]
Next Sync
Date: [ ]
Focus: [ ]
Return only the completed template.
Convert the transcript or raw notes into the template below.
SOURCE RULES
- Use only information explicitly contained in the source.
- Do not invent names, dates, owners, decisions, commitments, deadlines, metrics, reasons, votes, or outcomes.
- Do not treat a suggestion as a decision.
- Do not treat a discussion point as an action item.
- Do not infer an owner or due date.
- Use "Not specified" for a required field that is missing.
- Use "Unresolved" for a question that was raised but not answered.
- Keep discussion, decisions, action items, and open questions separate.
- Preserve uncertainty and disagreement when they exist.
OUTPUT FORMAT
Team: [ ]
Meeting: [ ]
Date: [ ]
Facilitator: [ ]
Attendees: [ ]
Weekly Goal
[ ]
Metrics / KPIs
- [Metric]: [ ]
Progress Since Last Meeting
- [Workstream]: [ ]
Team Updates
- [Person / function]: [ ]
Blockers
- [Blocker] - Impact: [ ] - Owner: [ ]
Cross-Team Dependencies
- [Dependency] - Waiting on: [ ]
Decisions
- [ ]
Action Items
- [Task] - Owner: [ ] - Due: [ ]
Announcements
- [ ]
Parking Lot
- [ ]
Next Sync
Date: [ ]
Focus: [ ]
Return only the completed template.
6. Daily Standup Notes Template
Blank Template
Team: [ ]
Date: [YYYY-MM-DD]
[Person 1]
Yesterday: [ ]
Today: [ ]
Blockers: [None / ]
[Person 2]
Yesterday: [ ]
Today: [ ]
Blockers: [None / ]
Shared Dependencies
- [ ]
Decisions
- [ ]
Follow-Ups
- [Task] - Owner: [ ] - Due: [ ]
Move Offline
- [Topic that needs a separate discussion]
Date: [YYYY-MM-DD]
[Person 1]
Yesterday: [ ]
Today: [ ]
Blockers: [None / ]
[Person 2]
Yesterday: [ ]
Today: [ ]
Blockers: [None / ]
Shared Dependencies
- [ ]
Decisions
- [ ]
Follow-Ups
- [Task] - Owner: [ ] - Due: [ ]
Move Offline
- [Topic that needs a separate discussion]
Filled Example
Team: Mobile Product Squad
Date: 2026-09-14
Nina
Yesterday: Finished analytics events for the new onboarding flow.
Today: Validate events in staging and open the release PR.
Blockers: Waiting for the final event-name list from Analytics.
Owen
Yesterday: Fixed the Android keyboard overlap issue.
Today: Run regression testing on small-screen devices.
Blockers: None.
Sam
Yesterday: Completed copy review for steps 1-4 of onboarding.
Today: Update error-state copy and hand off final strings.
Blockers: Needs a decision on whether the phone-number step remains optional.
Shared Dependencies
- Analytics must confirm event names before Nina can merge the release PR.
Decisions
- Keep phone number optional in this release.
Follow-Ups
- Confirm analytics event names - Owner: Nina - Due: 2026-09-14
- Update optional-phone copy - Owner: Sam - Due: 2026-09-14
Move Offline
- Review onboarding experiment sample-size requirements after standup.
Date: 2026-09-14
Nina
Yesterday: Finished analytics events for the new onboarding flow.
Today: Validate events in staging and open the release PR.
Blockers: Waiting for the final event-name list from Analytics.
Owen
Yesterday: Fixed the Android keyboard overlap issue.
Today: Run regression testing on small-screen devices.
Blockers: None.
Sam
Yesterday: Completed copy review for steps 1-4 of onboarding.
Today: Update error-state copy and hand off final strings.
Blockers: Needs a decision on whether the phone-number step remains optional.
Shared Dependencies
- Analytics must confirm event names before Nina can merge the release PR.
Decisions
- Keep phone number optional in this release.
Follow-Ups
- Confirm analytics event names - Owner: Nina - Due: 2026-09-14
- Update optional-phone copy - Owner: Sam - Due: 2026-09-14
Move Offline
- Review onboarding experiment sample-size requirements after standup.
AI-Ready Template
TASK
Convert the transcript or raw notes into the template below.
SOURCE RULES
- Use only information explicitly contained in the source.
- Do not invent names, dates, owners, decisions, commitments, deadlines, metrics, reasons, votes, or outcomes.
- Do not treat a suggestion as a decision.
- Do not treat a discussion point as an action item.
- Do not infer an owner or due date.
- Use "Not specified" for a required field that is missing.
- Use "Unresolved" for a question that was raised but not answered.
- Keep discussion, decisions, action items, and open questions separate.
- Preserve uncertainty and disagreement when they exist.
STANDUP RULES
- Keep the output short.
- Do not turn status updates into a narrative meeting summary.
- Preserve each person's update separately unless the source explicitly combines work.
OUTPUT FORMAT
Team: [ ]
Date: [ ]
[Person]
Yesterday: [ ]
Today: [ ]
Blockers: [ ]
Shared Dependencies
- [ ]
Decisions
- [ ]
Follow-Ups
- [Task] - Owner: [ ] - Due: [ ]
Move Offline
- [ ]
Return only the completed template.
Convert the transcript or raw notes into the template below.
SOURCE RULES
- Use only information explicitly contained in the source.
- Do not invent names, dates, owners, decisions, commitments, deadlines, metrics, reasons, votes, or outcomes.
- Do not treat a suggestion as a decision.
- Do not treat a discussion point as an action item.
- Do not infer an owner or due date.
- Use "Not specified" for a required field that is missing.
- Use "Unresolved" for a question that was raised but not answered.
- Keep discussion, decisions, action items, and open questions separate.
- Preserve uncertainty and disagreement when they exist.
STANDUP RULES
- Keep the output short.
- Do not turn status updates into a narrative meeting summary.
- Preserve each person's update separately unless the source explicitly combines work.
OUTPUT FORMAT
Team: [ ]
Date: [ ]
[Person]
Yesterday: [ ]
Today: [ ]
Blockers: [ ]
Shared Dependencies
- [ ]
Decisions
- [ ]
Follow-Ups
- [Task] - Owner: [ ] - Due: [ ]
Move Offline
- [ ]
Return only the completed template.
7. Sales Call Notes Template
Blank Template
Account: [ ]
Contact: [Name]
Role / Title: [ ]
Date: [YYYY-MM-DD]
Sales Rep: [ ]
Meeting Stage: [Discovery / Demo / Evaluation / Negotiation / Renewal]
Call Objective: [ ]
Current Situation
- [ ]
Pain Points
- [Problem] - Business impact: [ ]
Existing Process / Tools
- [ ]
Requirements
- Must-have: [ ]
- Nice-to-have: [ ]
Stakeholders
- [Name / role / influence]
Decision Process
- Decision maker: [ ]
- Evaluation criteria: [ ]
- Approval process: [ ]
Budget
[ ]
Timeline
[ ]
Objections / Concerns
- [ ]
Competitors / Alternatives Mentioned
- [ ]
Commitments Made
Customer:
- [ ]
Sales team:
- [ ]
Next Step
[ ]
Owner: [ ]
Follow-Up Date: [ ]
Open Questions
- [ ]
Contact: [Name]
Role / Title: [ ]
Date: [YYYY-MM-DD]
Sales Rep: [ ]
Meeting Stage: [Discovery / Demo / Evaluation / Negotiation / Renewal]
Call Objective: [ ]
Current Situation
- [ ]
Pain Points
- [Problem] - Business impact: [ ]
Existing Process / Tools
- [ ]
Requirements
- Must-have: [ ]
- Nice-to-have: [ ]
Stakeholders
- [Name / role / influence]
Decision Process
- Decision maker: [ ]
- Evaluation criteria: [ ]
- Approval process: [ ]
Budget
[ ]
Timeline
[ ]
Objections / Concerns
- [ ]
Competitors / Alternatives Mentioned
- [ ]
Commitments Made
Customer:
- [ ]
Sales team:
- [ ]
Next Step
[ ]
Owner: [ ]
Follow-Up Date: [ ]
Open Questions
- [ ]
Filled Example
Account: Northstar Analytics
Contact: Rachel Kim
Role / Title: VP of Customer Success
Date: 2026-09-12
Sales Rep: Evan Brooks
Meeting Stage: Discovery
Call Objective: Understand Northstar's customer-call review workflow and determine whether a structured evaluation is warranted.
Current Situation
- Customer Success runs roughly 85 client calls per week across 14 CSMs.
- Managers manually review selected call notes before weekly risk meetings.
- Notes are stored inconsistently across the CRM, private documents, and Slack.
Pain Points
- Inconsistent notes - Business impact: Managers cannot reliably compare account risk across the team.
- Manual follow-up extraction - Business impact: CSMs spend 20-30 minutes after complex calls cleaning notes and creating tasks.
- Missing decision history - Business impact: Renewal discussions sometimes revisit issues that were already resolved.
Existing Process / Tools
- Zoom for most calls.
- Salesforce for account records.
- Google Docs for some call notes.
Requirements
- Must-have: CRM-ready summaries, clear action owners, searchable decision history, export control.
- Nice-to-have: Custom note formats by call type.
Stakeholders
- Rachel Kim - VP Customer Success - Executive sponsor.
- Omar Diaz - Director of RevOps - Will evaluate Salesforce workflow.
- IT Security - Must review data handling before pilot.
Decision Process
- Decision maker: Rachel Kim, with RevOps and IT Security input.
- Evaluation criteria: Note consistency, admin effort, Salesforce workflow, security review.
- Approval process: Two-week pilot followed by security and RevOps review.
Budget
Not specified. Rachel said budget is available if the pilot shows measurable time savings.
Timeline
Northstar wants a pilot completed before Q4 planning begins in October.
Objections / Concerns
- Rachel does not want CSMs to maintain another separate system.
- IT Security may require clear retention controls.
Competitors / Alternatives Mentioned
- Current manual Zoom + Google Docs workflow.
- Gong was mentioned as a platform the sales organization already uses, but Customer Success does not currently have licenses.
Commitments Made
Customer:
- Rachel will introduce Evan to Omar Diaz.
Sales team:
- Evan will send a pilot outline and Salesforce workflow diagram.
Next Step
30-minute technical workflow review with Rachel and Omar.
Owner: Evan Brooks
Follow-Up Date: 2026-09-17
Open Questions
- What retention policy will IT Security require?
- How many CSMs should be included in the pilot?
Contact: Rachel Kim
Role / Title: VP of Customer Success
Date: 2026-09-12
Sales Rep: Evan Brooks
Meeting Stage: Discovery
Call Objective: Understand Northstar's customer-call review workflow and determine whether a structured evaluation is warranted.
Current Situation
- Customer Success runs roughly 85 client calls per week across 14 CSMs.
- Managers manually review selected call notes before weekly risk meetings.
- Notes are stored inconsistently across the CRM, private documents, and Slack.
Pain Points
- Inconsistent notes - Business impact: Managers cannot reliably compare account risk across the team.
- Manual follow-up extraction - Business impact: CSMs spend 20-30 minutes after complex calls cleaning notes and creating tasks.
- Missing decision history - Business impact: Renewal discussions sometimes revisit issues that were already resolved.
Existing Process / Tools
- Zoom for most calls.
- Salesforce for account records.
- Google Docs for some call notes.
Requirements
- Must-have: CRM-ready summaries, clear action owners, searchable decision history, export control.
- Nice-to-have: Custom note formats by call type.
Stakeholders
- Rachel Kim - VP Customer Success - Executive sponsor.
- Omar Diaz - Director of RevOps - Will evaluate Salesforce workflow.
- IT Security - Must review data handling before pilot.
Decision Process
- Decision maker: Rachel Kim, with RevOps and IT Security input.
- Evaluation criteria: Note consistency, admin effort, Salesforce workflow, security review.
- Approval process: Two-week pilot followed by security and RevOps review.
Budget
Not specified. Rachel said budget is available if the pilot shows measurable time savings.
Timeline
Northstar wants a pilot completed before Q4 planning begins in October.
Objections / Concerns
- Rachel does not want CSMs to maintain another separate system.
- IT Security may require clear retention controls.
Competitors / Alternatives Mentioned
- Current manual Zoom + Google Docs workflow.
- Gong was mentioned as a platform the sales organization already uses, but Customer Success does not currently have licenses.
Commitments Made
Customer:
- Rachel will introduce Evan to Omar Diaz.
Sales team:
- Evan will send a pilot outline and Salesforce workflow diagram.
Next Step
30-minute technical workflow review with Rachel and Omar.
Owner: Evan Brooks
Follow-Up Date: 2026-09-17
Open Questions
- What retention policy will IT Security require?
- How many CSMs should be included in the pilot?
AI-Ready Template
TASK
Convert the transcript or raw notes into the template below.
SOURCE RULES
- Use only information explicitly contained in the source.
- Do not invent names, dates, owners, decisions, commitments, deadlines, metrics, reasons, votes, or outcomes.
- Do not treat a suggestion as a decision.
- Do not treat a discussion point as an action item.
- Do not infer an owner or due date.
- Use "Not specified" for a required field that is missing.
- Use "Unresolved" for a question that was raised but not answered.
- Keep discussion, decisions, action items, and open questions separate.
- Preserve uncertainty and disagreement when they exist.
SALES-CALL RULES
- Separate customer statements from salesperson statements.
- Label a commitment only when the person explicitly agrees to do something.
- Do not infer budget, buying authority, urgency, or purchase intent from tone.
- Preserve objections even when they conflict with positive signals.
OUTPUT FORMAT
Account: [ ]
Contact: [ ]
Role / Title: [ ]
Date: [ ]
Sales Rep: [ ]
Meeting Stage: [ ]
Call Objective: [ ]
Current Situation
- [ ]
Pain Points
- [Problem] - Business impact: [ ]
Existing Process / Tools
- [ ]
Requirements
- Must-have: [ ]
- Nice-to-have: [ ]
Stakeholders
- [ ]
Decision Process
- Decision maker: [ ]
- Evaluation criteria: [ ]
- Approval process: [ ]
Budget
[ ]
Timeline
[ ]
Objections / Concerns
- [ ]
Competitors / Alternatives Mentioned
- [ ]
Commitments Made
Customer:
- [ ]
Sales team:
- [ ]
Next Step
[ ]
Owner: [ ]
Follow-Up Date: [ ]
Open Questions
- [ ]
Return only the completed template.
Convert the transcript or raw notes into the template below.
SOURCE RULES
- Use only information explicitly contained in the source.
- Do not invent names, dates, owners, decisions, commitments, deadlines, metrics, reasons, votes, or outcomes.
- Do not treat a suggestion as a decision.
- Do not treat a discussion point as an action item.
- Do not infer an owner or due date.
- Use "Not specified" for a required field that is missing.
- Use "Unresolved" for a question that was raised but not answered.
- Keep discussion, decisions, action items, and open questions separate.
- Preserve uncertainty and disagreement when they exist.
SALES-CALL RULES
- Separate customer statements from salesperson statements.
- Label a commitment only when the person explicitly agrees to do something.
- Do not infer budget, buying authority, urgency, or purchase intent from tone.
- Preserve objections even when they conflict with positive signals.
OUTPUT FORMAT
Account: [ ]
Contact: [ ]
Role / Title: [ ]
Date: [ ]
Sales Rep: [ ]
Meeting Stage: [ ]
Call Objective: [ ]
Current Situation
- [ ]
Pain Points
- [Problem] - Business impact: [ ]
Existing Process / Tools
- [ ]
Requirements
- Must-have: [ ]
- Nice-to-have: [ ]
Stakeholders
- [ ]
Decision Process
- Decision maker: [ ]
- Evaluation criteria: [ ]
- Approval process: [ ]
Budget
[ ]
Timeline
[ ]
Objections / Concerns
- [ ]
Competitors / Alternatives Mentioned
- [ ]
Commitments Made
Customer:
- [ ]
Sales team:
- [ ]
Next Step
[ ]
Owner: [ ]
Follow-Up Date: [ ]
Open Questions
- [ ]
Return only the completed template.
8. Client Meeting Notes Template
Blank Template
Client: [ ]
Meeting: [ ]
Date: [YYYY-MM-DD]
Attendees - Client: [ ]
Attendees - Internal: [ ]
Meeting Purpose: [ ]
Current Status
- [ ]
Client Priorities
- [ ]
Client Feedback
- Positive: [ ]
- Concerns: [ ]
Requests
- [Request] - Priority: [ ]
Deliverables Discussed
- [Deliverable] - Status: [ ] - Target date: [ ]
Changes Requested
- [Change] - Approved / Pending / Rejected: [ ]
Risks / Concerns
- [ ]
Decisions
- [ ]
Client Commitments
- [ ]
Internal Commitments
- [ ]
Action Items
- [Task] - Owner: [ ] - Due: [ ]
Next Touchpoint
Date: [ ]
Purpose: [ ]
Meeting: [ ]
Date: [YYYY-MM-DD]
Attendees - Client: [ ]
Attendees - Internal: [ ]
Meeting Purpose: [ ]
Current Status
- [ ]
Client Priorities
- [ ]
Client Feedback
- Positive: [ ]
- Concerns: [ ]
Requests
- [Request] - Priority: [ ]
Deliverables Discussed
- [Deliverable] - Status: [ ] - Target date: [ ]
Changes Requested
- [Change] - Approved / Pending / Rejected: [ ]
Risks / Concerns
- [ ]
Decisions
- [ ]
Client Commitments
- [ ]
Internal Commitments
- [ ]
Action Items
- [Task] - Owner: [ ] - Due: [ ]
Next Touchpoint
Date: [ ]
Purpose: [ ]
Filled Example
Client: Brightline Health
Meeting: September Implementation Review
Date: 2026-09-10
Attendees - Client: Melissa Grant, Kevin Wu
Attendees - Internal: Nora Fields, Henry Cole, James Park
Meeting Purpose: Review implementation status, confirm training dates, and resolve the data-import issue.
Current Status
- Core configuration is complete.
- 87% of historical records have imported successfully.
- User acceptance testing starts September 21.
Client Priorities
- Complete the remaining historical-data import before UAT.
- Train the support team before the October 5 launch.
- Avoid any change to the client-facing login flow before launch.
Client Feedback
- Positive: Melissa said the permissions setup is clearer than the previous system.
- Concerns: Kevin is concerned that rejected import rows do not include enough error detail for his team to correct them quickly.
Requests
- Add row-level error reasons to the rejected-record export - Priority: High
- Provide a sandbox reset checklist - Priority: Medium
Deliverables Discussed
- Historical-data import - Status: 87% complete - Target date: 2026-09-18
- Admin training deck - Status: Draft - Target date: 2026-09-23
Changes Requested
- Add detailed import-error reasons - Approved / Pending / Rejected: Pending technical estimate
- Change login page layout - Approved / Pending / Rejected: Rejected for pre-launch scope; revisit after launch
Risks / Concerns
- Data-import cleanup could delay UAT if rejected rows are not resolved by September 18.
Decisions
- Keep the October 5 launch date.
- Do not change the login page before launch.
Client Commitments
- Kevin will send three sample rejected rows by September 11.
Internal Commitments
- Henry will provide an estimate for detailed import-error reasons.
- Nora will send the sandbox reset checklist.
Action Items
- Send rejected-row samples - Owner: Kevin Wu - Due: 2026-09-11
- Estimate import-error enhancement - Owner: Henry Cole - Due: 2026-09-14
- Send sandbox reset checklist - Owner: Nora Fields - Due: 2026-09-12
Next Touchpoint
Date: 2026-09-17
Purpose: Import readiness and UAT go/no-go review.
Meeting: September Implementation Review
Date: 2026-09-10
Attendees - Client: Melissa Grant, Kevin Wu
Attendees - Internal: Nora Fields, Henry Cole, James Park
Meeting Purpose: Review implementation status, confirm training dates, and resolve the data-import issue.
Current Status
- Core configuration is complete.
- 87% of historical records have imported successfully.
- User acceptance testing starts September 21.
Client Priorities
- Complete the remaining historical-data import before UAT.
- Train the support team before the October 5 launch.
- Avoid any change to the client-facing login flow before launch.
Client Feedback
- Positive: Melissa said the permissions setup is clearer than the previous system.
- Concerns: Kevin is concerned that rejected import rows do not include enough error detail for his team to correct them quickly.
Requests
- Add row-level error reasons to the rejected-record export - Priority: High
- Provide a sandbox reset checklist - Priority: Medium
Deliverables Discussed
- Historical-data import - Status: 87% complete - Target date: 2026-09-18
- Admin training deck - Status: Draft - Target date: 2026-09-23
Changes Requested
- Add detailed import-error reasons - Approved / Pending / Rejected: Pending technical estimate
- Change login page layout - Approved / Pending / Rejected: Rejected for pre-launch scope; revisit after launch
Risks / Concerns
- Data-import cleanup could delay UAT if rejected rows are not resolved by September 18.
Decisions
- Keep the October 5 launch date.
- Do not change the login page before launch.
Client Commitments
- Kevin will send three sample rejected rows by September 11.
Internal Commitments
- Henry will provide an estimate for detailed import-error reasons.
- Nora will send the sandbox reset checklist.
Action Items
- Send rejected-row samples - Owner: Kevin Wu - Due: 2026-09-11
- Estimate import-error enhancement - Owner: Henry Cole - Due: 2026-09-14
- Send sandbox reset checklist - Owner: Nora Fields - Due: 2026-09-12
Next Touchpoint
Date: 2026-09-17
Purpose: Import readiness and UAT go/no-go review.
AI-Ready Template
TASK
Convert the transcript or raw notes into the template below.
SOURCE RULES
- Use only information explicitly contained in the source.
- Do not invent names, dates, owners, decisions, commitments, deadlines, metrics, reasons, votes, or outcomes.
- Do not treat a suggestion as a decision.
- Do not treat a discussion point as an action item.
- Do not infer an owner or due date.
- Use "Not specified" for a required field that is missing.
- Use "Unresolved" for a question that was raised but not answered.
- Keep discussion, decisions, action items, and open questions separate.
- Preserve uncertainty and disagreement when they exist.
CLIENT-MEETING RULES
- Distinguish requests from approved scope changes.
- Do not describe a request as committed work unless approval is explicit.
- Keep client commitments and internal commitments separate.
OUTPUT FORMAT
Client: [ ]
Meeting: [ ]
Date: [ ]
Attendees - Client: [ ]
Attendees - Internal: [ ]
Meeting Purpose: [ ]
Current Status
- [ ]
Client Priorities
- [ ]
Client Feedback
- Positive: [ ]
- Concerns: [ ]
Requests
- [Request] - Priority: [ ]
Deliverables Discussed
- [Deliverable] - Status: [ ] - Target date: [ ]
Changes Requested
- [Change] - Approved / Pending / Rejected: [ ]
Risks / Concerns
- [ ]
Decisions
- [ ]
Client Commitments
- [ ]
Internal Commitments
- [ ]
Action Items
- [Task] - Owner: [ ] - Due: [ ]
Next Touchpoint
Date: [ ]
Purpose: [ ]
Return only the completed template.
Convert the transcript or raw notes into the template below.
SOURCE RULES
- Use only information explicitly contained in the source.
- Do not invent names, dates, owners, decisions, commitments, deadlines, metrics, reasons, votes, or outcomes.
- Do not treat a suggestion as a decision.
- Do not treat a discussion point as an action item.
- Do not infer an owner or due date.
- Use "Not specified" for a required field that is missing.
- Use "Unresolved" for a question that was raised but not answered.
- Keep discussion, decisions, action items, and open questions separate.
- Preserve uncertainty and disagreement when they exist.
CLIENT-MEETING RULES
- Distinguish requests from approved scope changes.
- Do not describe a request as committed work unless approval is explicit.
- Keep client commitments and internal commitments separate.
OUTPUT FORMAT
Client: [ ]
Meeting: [ ]
Date: [ ]
Attendees - Client: [ ]
Attendees - Internal: [ ]
Meeting Purpose: [ ]
Current Status
- [ ]
Client Priorities
- [ ]
Client Feedback
- Positive: [ ]
- Concerns: [ ]
Requests
- [Request] - Priority: [ ]
Deliverables Discussed
- [Deliverable] - Status: [ ] - Target date: [ ]
Changes Requested
- [Change] - Approved / Pending / Rejected: [ ]
Risks / Concerns
- [ ]
Decisions
- [ ]
Client Commitments
- [ ]
Internal Commitments
- [ ]
Action Items
- [Task] - Owner: [ ] - Due: [ ]
Next Touchpoint
Date: [ ]
Purpose: [ ]
Return only the completed template.
9. Project Review / Project Status Meeting Template
Blank Template
Project: [ ]
Review Period: [ ]
Date: [YYYY-MM-DD]
Project Owner: [ ]
Attendees: [ ]
Overall Status: [On track / At risk / Off track / Not stated]
Project Objective
[ ]
Milestones
- [Milestone] - Target: [ ] - Status: [ ]
Completed Since Last Review
- [ ]
In Progress
- [ ]
Upcoming
- [ ]
Timeline Status
[ ]
Budget / Resources
[ ]
Risks
- [Risk] - Probability / impact if stated: [ ] - Mitigation: [ ]
Issues / Blockers
- [Issue] - Owner: [ ]
Dependencies
- [Dependency] - Owner / team: [ ]
Scope Changes
- [Change] - Status: [Proposed / Approved / Rejected]
Decisions Needed
- [ ]
Decisions Made
- [ ]
Action Items
- [Task] - Owner: [ ] - Due: [ ]
Next Review
Date: [ ]
Focus: [ ]
Review Period: [ ]
Date: [YYYY-MM-DD]
Project Owner: [ ]
Attendees: [ ]
Overall Status: [On track / At risk / Off track / Not stated]
Project Objective
[ ]
Milestones
- [Milestone] - Target: [ ] - Status: [ ]
Completed Since Last Review
- [ ]
In Progress
- [ ]
Upcoming
- [ ]
Timeline Status
[ ]
Budget / Resources
[ ]
Risks
- [Risk] - Probability / impact if stated: [ ] - Mitigation: [ ]
Issues / Blockers
- [Issue] - Owner: [ ]
Dependencies
- [Dependency] - Owner / team: [ ]
Scope Changes
- [Change] - Status: [Proposed / Approved / Rejected]
Decisions Needed
- [ ]
Decisions Made
- [ ]
Action Items
- [Task] - Owner: [ ] - Due: [ ]
Next Review
Date: [ ]
Focus: [ ]
Filled Example
Project: Customer Portal Rebuild
Review Period: September Sprint 2
Date: 2026-09-09
Project Owner: Carmen Lewis
Attendees: Carmen Lewis, Dev Shah, Iris Wong, Taylor Moore, Luis Rivera
Overall Status: At risk
Project Objective
Launch the redesigned customer portal by November 2 with consolidated billing, support history, and account-management workflows.
Milestones
- Design system complete - Target: 2026-08-28 - Status: Complete
- Billing integration complete - Target: 2026-09-18 - Status: At risk
- Beta release - Target: 2026-10-05 - Status: Not started
- General release - Target: 2026-11-02 - Status: Not started
Completed Since Last Review
- Finalized account navigation.
- Completed support-history API integration.
- Finished accessibility review for the profile workflow.
In Progress
- Billing API integration.
- Invoice PDF redesign.
- Beta customer recruitment.
Upcoming
- End-to-end billing test.
- Beta environment setup.
- Customer support training draft.
Timeline Status
Billing integration is four business days behind the internal plan because the sandbox did not include two required invoice states. The November 2 release date has not changed.
Budget / Resources
No budget variance was reported. Dev requested one additional backend engineer for three days to recover the billing schedule.
Risks
- Billing API delay - Probability / impact if stated: High impact - Mitigation: Add temporary engineering capacity and finish missing sandbox fixtures.
- Beta recruitment below target - Probability / impact if stated: Not specified - Mitigation: Customer Success will invite ten additional accounts.
Issues / Blockers
- Missing invoice states in billing sandbox - Owner: Dev Shah
Dependencies
- Billing sandbox update - Owner / team: Finance Platform
- Beta account list - Owner / team: Customer Success
Scope Changes
- Add downloadable usage CSV to beta - Status: Proposed
Decisions Needed
- Whether to include downloadable usage CSV in the beta scope.
Decisions Made
- Add one backend engineer for three days to recover the billing timeline.
Action Items
- Secure temporary backend support - Owner: Carmen Lewis - Due: 2026-09-10
- Provide missing sandbox fixtures - Owner: Dev Shah - Due: 2026-09-11
- Invite ten additional beta accounts - Owner: Taylor Moore - Due: 2026-09-14
Next Review
Date: 2026-09-16
Focus: Billing recovery and beta readiness.
Review Period: September Sprint 2
Date: 2026-09-09
Project Owner: Carmen Lewis
Attendees: Carmen Lewis, Dev Shah, Iris Wong, Taylor Moore, Luis Rivera
Overall Status: At risk
Project Objective
Launch the redesigned customer portal by November 2 with consolidated billing, support history, and account-management workflows.
Milestones
- Design system complete - Target: 2026-08-28 - Status: Complete
- Billing integration complete - Target: 2026-09-18 - Status: At risk
- Beta release - Target: 2026-10-05 - Status: Not started
- General release - Target: 2026-11-02 - Status: Not started
Completed Since Last Review
- Finalized account navigation.
- Completed support-history API integration.
- Finished accessibility review for the profile workflow.
In Progress
- Billing API integration.
- Invoice PDF redesign.
- Beta customer recruitment.
Upcoming
- End-to-end billing test.
- Beta environment setup.
- Customer support training draft.
Timeline Status
Billing integration is four business days behind the internal plan because the sandbox did not include two required invoice states. The November 2 release date has not changed.
Budget / Resources
No budget variance was reported. Dev requested one additional backend engineer for three days to recover the billing schedule.
Risks
- Billing API delay - Probability / impact if stated: High impact - Mitigation: Add temporary engineering capacity and finish missing sandbox fixtures.
- Beta recruitment below target - Probability / impact if stated: Not specified - Mitigation: Customer Success will invite ten additional accounts.
Issues / Blockers
- Missing invoice states in billing sandbox - Owner: Dev Shah
Dependencies
- Billing sandbox update - Owner / team: Finance Platform
- Beta account list - Owner / team: Customer Success
Scope Changes
- Add downloadable usage CSV to beta - Status: Proposed
Decisions Needed
- Whether to include downloadable usage CSV in the beta scope.
Decisions Made
- Add one backend engineer for three days to recover the billing timeline.
Action Items
- Secure temporary backend support - Owner: Carmen Lewis - Due: 2026-09-10
- Provide missing sandbox fixtures - Owner: Dev Shah - Due: 2026-09-11
- Invite ten additional beta accounts - Owner: Taylor Moore - Due: 2026-09-14
Next Review
Date: 2026-09-16
Focus: Billing recovery and beta readiness.
AI-Ready Template
TASK
Convert the transcript or raw notes into the template below.
SOURCE RULES
- Use only information explicitly contained in the source.
- Do not invent names, dates, owners, decisions, commitments, deadlines, metrics, reasons, votes, or outcomes.
- Do not treat a suggestion as a decision.
- Do not treat a discussion point as an action item.
- Do not infer an owner or due date.
- Use "Not specified" for a required field that is missing.
- Use "Unresolved" for a question that was raised but not answered.
- Keep discussion, decisions, action items, and open questions separate.
- Preserve uncertainty and disagreement when they exist.
PROJECT-REVIEW RULES
- Use the stated project status. Do not calculate or infer Red/Amber/Green status unless the source defines the rule.
- Separate risks (possible future problems) from issues/blockers (current problems).
- Keep proposed scope changes separate from approved scope changes.
OUTPUT FORMAT
Project: [ ]
Review Period: [ ]
Date: [ ]
Project Owner: [ ]
Attendees: [ ]
Overall Status: [ ]
Project Objective
[ ]
Milestones
- [Milestone] - Target: [ ] - Status: [ ]
Completed Since Last Review
- [ ]
In Progress
- [ ]
Upcoming
- [ ]
Timeline Status
[ ]
Budget / Resources
[ ]
Risks
- [Risk] - Probability / impact if stated: [ ] - Mitigation: [ ]
Issues / Blockers
- [Issue] - Owner: [ ]
Dependencies
- [Dependency] - Owner / team: [ ]
Scope Changes
- [Change] - Status: [ ]
Decisions Needed
- [ ]
Decisions Made
- [ ]
Action Items
- [Task] - Owner: [ ] - Due: [ ]
Next Review
Date: [ ]
Focus: [ ]
Return only the completed template.
Convert the transcript or raw notes into the template below.
SOURCE RULES
- Use only information explicitly contained in the source.
- Do not invent names, dates, owners, decisions, commitments, deadlines, metrics, reasons, votes, or outcomes.
- Do not treat a suggestion as a decision.
- Do not treat a discussion point as an action item.
- Do not infer an owner or due date.
- Use "Not specified" for a required field that is missing.
- Use "Unresolved" for a question that was raised but not answered.
- Keep discussion, decisions, action items, and open questions separate.
- Preserve uncertainty and disagreement when they exist.
PROJECT-REVIEW RULES
- Use the stated project status. Do not calculate or infer Red/Amber/Green status unless the source defines the rule.
- Separate risks (possible future problems) from issues/blockers (current problems).
- Keep proposed scope changes separate from approved scope changes.
OUTPUT FORMAT
Project: [ ]
Review Period: [ ]
Date: [ ]
Project Owner: [ ]
Attendees: [ ]
Overall Status: [ ]
Project Objective
[ ]
Milestones
- [Milestone] - Target: [ ] - Status: [ ]
Completed Since Last Review
- [ ]
In Progress
- [ ]
Upcoming
- [ ]
Timeline Status
[ ]
Budget / Resources
[ ]
Risks
- [Risk] - Probability / impact if stated: [ ] - Mitigation: [ ]
Issues / Blockers
- [Issue] - Owner: [ ]
Dependencies
- [Dependency] - Owner / team: [ ]
Scope Changes
- [Change] - Status: [ ]
Decisions Needed
- [ ]
Decisions Made
- [ ]
Action Items
- [Task] - Owner: [ ] - Due: [ ]
Next Review
Date: [ ]
Focus: [ ]
Return only the completed template.
10. Project Kickoff Meeting Notes Template
Blank Template
Project: [ ]
Kickoff Date: [YYYY-MM-DD]
Project Lead: [ ]
Sponsor: [ ]
Attendees: [ ]
Business Objective
[ ]
Success Criteria
- [ ]
Scope - In
- [ ]
Scope - Out
- [ ]
Stakeholders
- [Name / role / responsibility]
Roles / Responsibilities
- [Person / team]: [Responsibility]
Key Deliverables
- [Deliverable] - Owner: [ ] - Target: [ ]
Milestones
- [Milestone] - Target date: [ ]
Dependencies
- [ ]
Risks / Assumptions
- Risk: [ ]
- Assumption: [ ]
Working Agreements
- [ ]
Communication Cadence
- [Meeting / channel / frequency]
Decision-Making Process
[ ]
Open Questions
- [ ]
Initial Action Items
- [Task] - Owner: [ ] - Due: [ ]
Kickoff Date: [YYYY-MM-DD]
Project Lead: [ ]
Sponsor: [ ]
Attendees: [ ]
Business Objective
[ ]
Success Criteria
- [ ]
Scope - In
- [ ]
Scope - Out
- [ ]
Stakeholders
- [Name / role / responsibility]
Roles / Responsibilities
- [Person / team]: [Responsibility]
Key Deliverables
- [Deliverable] - Owner: [ ] - Target: [ ]
Milestones
- [Milestone] - Target date: [ ]
Dependencies
- [ ]
Risks / Assumptions
- Risk: [ ]
- Assumption: [ ]
Working Agreements
- [ ]
Communication Cadence
- [Meeting / channel / frequency]
Decision-Making Process
[ ]
Open Questions
- [ ]
Initial Action Items
- [Task] - Owner: [ ] - Due: [ ]
Filled Example
Project: Finance Reporting Automation
Kickoff Date: 2026-09-07
Project Lead: Maya Torres
Sponsor: Daniel Brooks, CFO
Attendees: Maya Torres, Daniel Brooks, Nina Patel, Chris Allen, Victor Chen, Laura Perez
Business Objective
Reduce manual preparation time for the monthly management reporting pack and create one controlled source for recurring financial metrics.
Success Criteria
- Monthly reporting pack generated within one business day after close.
- No manual re-keying of approved ERP values into the management deck.
- Finance can trace every reported metric to its source table.
Scope - In
- Revenue, gross margin, operating expense, headcount, and cash metrics.
- Automated data pull from the ERP and HRIS.
- Standard monthly management deck.
Scope - Out
- Forecast-model redesign.
- Board deck redesign.
- Department-level budget workflow.
Stakeholders
- Daniel Brooks - Executive sponsor.
- Nina Patel - Finance process owner.
- Chris Allen - Data engineering lead.
- Victor Chen - Security review.
Roles / Responsibilities
- Maya Torres: Project coordination and scope control.
- Nina Patel: Metric definitions and acceptance testing.
- Chris Allen: Data pipeline and validation.
- Victor Chen: Access and security review.
Key Deliverables
- Metric dictionary - Owner: Nina Patel - Target: 2026-09-18
- Automated data pipeline - Owner: Chris Allen - Target: 2026-10-09
- Management deck prototype - Owner: Maya Torres - Target: 2026-10-16
Milestones
- Requirements sign-off - Target date: 2026-09-18
- First end-to-end test - Target date: 2026-10-12
- Parallel reporting cycle - Target date: 2026-11-02
Dependencies
- ERP read-only API access.
- HRIS field mapping.
- Finance approval of metric definitions.
Risks / Assumptions
- Risk: ERP API rate limits may slow the first data pull.
- Assumption: Existing monthly metric definitions will remain unchanged through the pilot.
Working Agreements
- Scope changes require written approval from Maya and Nina.
- Data-definition questions will be logged in the project channel, not resolved in private messages.
Communication Cadence
- 30-minute project sync every Tuesday.
- Written status update every Friday.
Decision-Making Process
Process decisions are owned by Nina; technical implementation decisions are owned by Chris; scope changes require Maya and Nina approval.
Open Questions
- Whether cash-forecast variance belongs in the first release.
Initial Action Items
- Draft metric dictionary - Owner: Nina Patel - Due: 2026-09-11
- Request ERP API access - Owner: Chris Allen - Due: 2026-09-09
- Create project risk log - Owner: Maya Torres - Due: 2026-09-09
Kickoff Date: 2026-09-07
Project Lead: Maya Torres
Sponsor: Daniel Brooks, CFO
Attendees: Maya Torres, Daniel Brooks, Nina Patel, Chris Allen, Victor Chen, Laura Perez
Business Objective
Reduce manual preparation time for the monthly management reporting pack and create one controlled source for recurring financial metrics.
Success Criteria
- Monthly reporting pack generated within one business day after close.
- No manual re-keying of approved ERP values into the management deck.
- Finance can trace every reported metric to its source table.
Scope - In
- Revenue, gross margin, operating expense, headcount, and cash metrics.
- Automated data pull from the ERP and HRIS.
- Standard monthly management deck.
Scope - Out
- Forecast-model redesign.
- Board deck redesign.
- Department-level budget workflow.
Stakeholders
- Daniel Brooks - Executive sponsor.
- Nina Patel - Finance process owner.
- Chris Allen - Data engineering lead.
- Victor Chen - Security review.
Roles / Responsibilities
- Maya Torres: Project coordination and scope control.
- Nina Patel: Metric definitions and acceptance testing.
- Chris Allen: Data pipeline and validation.
- Victor Chen: Access and security review.
Key Deliverables
- Metric dictionary - Owner: Nina Patel - Target: 2026-09-18
- Automated data pipeline - Owner: Chris Allen - Target: 2026-10-09
- Management deck prototype - Owner: Maya Torres - Target: 2026-10-16
Milestones
- Requirements sign-off - Target date: 2026-09-18
- First end-to-end test - Target date: 2026-10-12
- Parallel reporting cycle - Target date: 2026-11-02
Dependencies
- ERP read-only API access.
- HRIS field mapping.
- Finance approval of metric definitions.
Risks / Assumptions
- Risk: ERP API rate limits may slow the first data pull.
- Assumption: Existing monthly metric definitions will remain unchanged through the pilot.
Working Agreements
- Scope changes require written approval from Maya and Nina.
- Data-definition questions will be logged in the project channel, not resolved in private messages.
Communication Cadence
- 30-minute project sync every Tuesday.
- Written status update every Friday.
Decision-Making Process
Process decisions are owned by Nina; technical implementation decisions are owned by Chris; scope changes require Maya and Nina approval.
Open Questions
- Whether cash-forecast variance belongs in the first release.
Initial Action Items
- Draft metric dictionary - Owner: Nina Patel - Due: 2026-09-11
- Request ERP API access - Owner: Chris Allen - Due: 2026-09-09
- Create project risk log - Owner: Maya Torres - Due: 2026-09-09
AI-Ready Template
TASK
Convert the transcript or raw notes into the template below.
SOURCE RULES
- Use only information explicitly contained in the source.
- Do not invent names, dates, owners, decisions, commitments, deadlines, metrics, reasons, votes, or outcomes.
- Do not treat a suggestion as a decision.
- Do not treat a discussion point as an action item.
- Do not infer an owner or due date.
- Use "Not specified" for a required field that is missing.
- Use "Unresolved" for a question that was raised but not answered.
- Keep discussion, decisions, action items, and open questions separate.
- Preserve uncertainty and disagreement when they exist.
OUTPUT FORMAT
Project: [ ]
Kickoff Date: [ ]
Project Lead: [ ]
Sponsor: [ ]
Attendees: [ ]
Business Objective
[ ]
Success Criteria
- [ ]
Scope - In
- [ ]
Scope - Out
- [ ]
Stakeholders
- [ ]
Roles / Responsibilities
- [ ]
Key Deliverables
- [Deliverable] - Owner: [ ] - Target: [ ]
Milestones
- [Milestone] - Target date: [ ]
Dependencies
- [ ]
Risks / Assumptions
- Risk: [ ]
- Assumption: [ ]
Working Agreements
- [ ]
Communication Cadence
- [ ]
Decision-Making Process
[ ]
Open Questions
- [ ]
Initial Action Items
- [Task] - Owner: [ ] - Due: [ ]
Return only the completed template.
Convert the transcript or raw notes into the template below.
SOURCE RULES
- Use only information explicitly contained in the source.
- Do not invent names, dates, owners, decisions, commitments, deadlines, metrics, reasons, votes, or outcomes.
- Do not treat a suggestion as a decision.
- Do not treat a discussion point as an action item.
- Do not infer an owner or due date.
- Use "Not specified" for a required field that is missing.
- Use "Unresolved" for a question that was raised but not answered.
- Keep discussion, decisions, action items, and open questions separate.
- Preserve uncertainty and disagreement when they exist.
OUTPUT FORMAT
Project: [ ]
Kickoff Date: [ ]
Project Lead: [ ]
Sponsor: [ ]
Attendees: [ ]
Business Objective
[ ]
Success Criteria
- [ ]
Scope - In
- [ ]
Scope - Out
- [ ]
Stakeholders
- [ ]
Roles / Responsibilities
- [ ]
Key Deliverables
- [Deliverable] - Owner: [ ] - Target: [ ]
Milestones
- [Milestone] - Target date: [ ]
Dependencies
- [ ]
Risks / Assumptions
- Risk: [ ]
- Assumption: [ ]
Working Agreements
- [ ]
Communication Cadence
- [ ]
Decision-Making Process
[ ]
Open Questions
- [ ]
Initial Action Items
- [Task] - Owner: [ ] - Due: [ ]
Return only the completed template.
11. Interview Notes Template
Blank Template
Candidate: [ ]
Role: [ ]
Interview Stage: [ ]
Interviewer: [ ]
Date: [YYYY-MM-DD]
Competencies Assessed
- [Competency]
Question 1
Question: [ ]
Candidate Response / Evidence: [ ]
Evidence Rating: [Strong / Mixed / Limited / Not assessed]
Notes: [Job-relevant evidence only]
Question 2
Question: [ ]
Candidate Response / Evidence: [ ]
Evidence Rating: [Strong / Mixed / Limited / Not assessed]
Notes: [ ]
Strengths Supported by Evidence
- [ ]
Concerns / Gaps Supported by Evidence
- [ ]
Follow-Up Questions
- [ ]
Overall Job-Relevant Evidence
[ ]
Recommendation
[Advance / Hold / Do not advance / Not decided]
Reason: [Job-related evidence]
Next Step
[ ]
Role: [ ]
Interview Stage: [ ]
Interviewer: [ ]
Date: [YYYY-MM-DD]
Competencies Assessed
- [Competency]
Question 1
Question: [ ]
Candidate Response / Evidence: [ ]
Evidence Rating: [Strong / Mixed / Limited / Not assessed]
Notes: [Job-relevant evidence only]
Question 2
Question: [ ]
Candidate Response / Evidence: [ ]
Evidence Rating: [Strong / Mixed / Limited / Not assessed]
Notes: [ ]
Strengths Supported by Evidence
- [ ]
Concerns / Gaps Supported by Evidence
- [ ]
Follow-Up Questions
- [ ]
Overall Job-Relevant Evidence
[ ]
Recommendation
[Advance / Hold / Do not advance / Not decided]
Reason: [Job-related evidence]
Next Step
[ ]
Filled Example
Candidate: Taylor Morgan
Role: Senior Customer Success Manager
Interview Stage: Hiring Manager Interview
Interviewer: Renee Foster
Date: 2026-09-08
Competencies Assessed
- Enterprise account management
- Escalation handling
- Cross-functional communication
- Retention strategy
Question 1
Question: Tell me about a time you recovered an at-risk strategic account.
Candidate Response / Evidence: Taylor described a $480K ARR customer that had opened three executive escalations in one quarter. Taylor created a 30-day recovery plan, set weekly executive checkpoints, and worked with Product to separate a product gap from two configuration issues. The customer renewed for one year after the recovery plan.
Evidence Rating: Strong
Notes: Clear ownership, structured escalation process, and a measurable renewal outcome.
Question 2
Question: How do you prioritize across a large book of business?
Candidate Response / Evidence: Taylor uses a weekly risk review based on renewal date, product adoption, executive engagement, support severity, and expansion signals. Taylor said the model is reviewed manually when a large organizational change occurs at an account.
Evidence Rating: Strong
Notes: Specific prioritization criteria and evidence of judgment beyond a fixed score.
Question 3
Question: Tell me about a difficult cross-functional disagreement.
Candidate Response / Evidence: Taylor described a conflict with Sales over whether to promise a custom reporting feature during renewal. Taylor escalated the request to Product, documented the gap, and proposed a manual reporting workaround until the roadmap decision was final.
Evidence Rating: Mixed
Notes: Strong documentation and boundary setting. The example did not clearly explain how the relationship with Sales was repaired afterward.
Strengths Supported by Evidence
- Structured approach to account-risk management.
- Specific experience with executive escalations and renewals.
- Comfortable setting product-commitment boundaries.
Concerns / Gaps Supported by Evidence
- Limited evidence so far on coaching junior CSMs, which is part of the role.
Follow-Up Questions
- Ask for an example of coaching or mentoring a lower-performing teammate.
- Clarify experience managing accounts above $1M ARR.
Overall Job-Relevant Evidence
Taylor provided strong evidence for enterprise account management and escalation handling. Coaching experience remains insufficiently assessed.
Recommendation
Advance
Reason: Evidence meets the bar for the core account-management competencies; the panel should test coaching depth in the next round.
Next Step
Panel interview focused on leadership, coaching, and cross-functional influence.
Role: Senior Customer Success Manager
Interview Stage: Hiring Manager Interview
Interviewer: Renee Foster
Date: 2026-09-08
Competencies Assessed
- Enterprise account management
- Escalation handling
- Cross-functional communication
- Retention strategy
Question 1
Question: Tell me about a time you recovered an at-risk strategic account.
Candidate Response / Evidence: Taylor described a $480K ARR customer that had opened three executive escalations in one quarter. Taylor created a 30-day recovery plan, set weekly executive checkpoints, and worked with Product to separate a product gap from two configuration issues. The customer renewed for one year after the recovery plan.
Evidence Rating: Strong
Notes: Clear ownership, structured escalation process, and a measurable renewal outcome.
Question 2
Question: How do you prioritize across a large book of business?
Candidate Response / Evidence: Taylor uses a weekly risk review based on renewal date, product adoption, executive engagement, support severity, and expansion signals. Taylor said the model is reviewed manually when a large organizational change occurs at an account.
Evidence Rating: Strong
Notes: Specific prioritization criteria and evidence of judgment beyond a fixed score.
Question 3
Question: Tell me about a difficult cross-functional disagreement.
Candidate Response / Evidence: Taylor described a conflict with Sales over whether to promise a custom reporting feature during renewal. Taylor escalated the request to Product, documented the gap, and proposed a manual reporting workaround until the roadmap decision was final.
Evidence Rating: Mixed
Notes: Strong documentation and boundary setting. The example did not clearly explain how the relationship with Sales was repaired afterward.
Strengths Supported by Evidence
- Structured approach to account-risk management.
- Specific experience with executive escalations and renewals.
- Comfortable setting product-commitment boundaries.
Concerns / Gaps Supported by Evidence
- Limited evidence so far on coaching junior CSMs, which is part of the role.
Follow-Up Questions
- Ask for an example of coaching or mentoring a lower-performing teammate.
- Clarify experience managing accounts above $1M ARR.
Overall Job-Relevant Evidence
Taylor provided strong evidence for enterprise account management and escalation handling. Coaching experience remains insufficiently assessed.
Recommendation
Advance
Reason: Evidence meets the bar for the core account-management competencies; the panel should test coaching depth in the next round.
Next Step
Panel interview focused on leadership, coaching, and cross-functional influence.
AI-Ready Template
TASK
Convert the transcript or raw notes into the template below.
SOURCE RULES
- Use only information explicitly contained in the source.
- Do not invent names, dates, owners, decisions, commitments, deadlines, metrics, reasons, votes, or outcomes.
- Do not treat a suggestion as a decision.
- Do not treat a discussion point as an action item.
- Do not infer an owner or due date.
- Use "Not specified" for a required field that is missing.
- Use "Unresolved" for a question that was raised but not answered.
- Keep discussion, decisions, action items, and open questions separate.
- Preserve uncertainty and disagreement when they exist.
INTERVIEW RULES
- Include only job-relevant evidence contained in the source.
- Do not infer or evaluate protected or personal characteristics, including age, race, ethnicity, religion, sex, pregnancy, disability, family status, sexual orientation, or health.
- Do not turn style, accent, appearance, or personal circumstances into a hiring signal.
- If the interviewer did not make a recommendation, write "Not decided."
OUTPUT FORMAT
Candidate: [ ]
Role: [ ]
Interview Stage: [ ]
Interviewer: [ ]
Date: [ ]
Competencies Assessed
- [ ]
Question 1
Question: [ ]
Candidate Response / Evidence: [ ]
Evidence Rating: [ ]
Notes: [ ]
Strengths Supported by Evidence
- [ ]
Concerns / Gaps Supported by Evidence
- [ ]
Follow-Up Questions
- [ ]
Overall Job-Relevant Evidence
[ ]
Recommendation
[ ]
Reason: [ ]
Next Step
[ ]
Return only the completed template.
Convert the transcript or raw notes into the template below.
SOURCE RULES
- Use only information explicitly contained in the source.
- Do not invent names, dates, owners, decisions, commitments, deadlines, metrics, reasons, votes, or outcomes.
- Do not treat a suggestion as a decision.
- Do not treat a discussion point as an action item.
- Do not infer an owner or due date.
- Use "Not specified" for a required field that is missing.
- Use "Unresolved" for a question that was raised but not answered.
- Keep discussion, decisions, action items, and open questions separate.
- Preserve uncertainty and disagreement when they exist.
INTERVIEW RULES
- Include only job-relevant evidence contained in the source.
- Do not infer or evaluate protected or personal characteristics, including age, race, ethnicity, religion, sex, pregnancy, disability, family status, sexual orientation, or health.
- Do not turn style, accent, appearance, or personal circumstances into a hiring signal.
- If the interviewer did not make a recommendation, write "Not decided."
OUTPUT FORMAT
Candidate: [ ]
Role: [ ]
Interview Stage: [ ]
Interviewer: [ ]
Date: [ ]
Competencies Assessed
- [ ]
Question 1
Question: [ ]
Candidate Response / Evidence: [ ]
Evidence Rating: [ ]
Notes: [ ]
Strengths Supported by Evidence
- [ ]
Concerns / Gaps Supported by Evidence
- [ ]
Follow-Up Questions
- [ ]
Overall Job-Relevant Evidence
[ ]
Recommendation
[ ]
Reason: [ ]
Next Step
[ ]
Return only the completed template.
12. Leadership / Executive Meeting Notes Template
Blank Template
Meeting: [ ]
Date: [YYYY-MM-DD]
Executive Owner: [ ]
Attendees: [ ]
Meeting Objective
[ ]
Business Metrics
- [Metric]: [Value / change / context]
Strategic Topics
1. [Topic]
- Context: [ ]
- Options / trade-offs: [ ]
- Decision / next step: [ ]
Key Updates
- [ ]
Risks / Escalations
- [Risk] - Business impact: [ ] - Executive owner: [ ]
Resource Decisions
- [Budget / headcount / capacity decision]
Strategic Decisions
- [Decision] - Decision owner: [ ]
Communication Required
- Audience: [ ]
- Message / owner: [ ]
- Timing: [ ]
Action Items
- [Task] - Owner: [ ] - Due: [ ]
Issues Requiring Follow-Up
- [ ]
Next Review
[ ]
Date: [YYYY-MM-DD]
Executive Owner: [ ]
Attendees: [ ]
Meeting Objective
[ ]
Business Metrics
- [Metric]: [Value / change / context]
Strategic Topics
1. [Topic]
- Context: [ ]
- Options / trade-offs: [ ]
- Decision / next step: [ ]
Key Updates
- [ ]
Risks / Escalations
- [Risk] - Business impact: [ ] - Executive owner: [ ]
Resource Decisions
- [Budget / headcount / capacity decision]
Strategic Decisions
- [Decision] - Decision owner: [ ]
Communication Required
- Audience: [ ]
- Message / owner: [ ]
- Timing: [ ]
Action Items
- [Task] - Owner: [ ] - Due: [ ]
Issues Requiring Follow-Up
- [ ]
Next Review
[ ]
Filled Example
Meeting: Monthly Executive Operating Review
Date: 2026-09-04
Executive Owner: CEO - Claire Monroe
Attendees: Claire Monroe, CFO Daniel Brooks, COO Julia Chen, CRO Mark Ellis, CPO Anita Rao
Meeting Objective
Review August operating performance and decide resource changes for Q4 execution.
Business Metrics
- Revenue: $18.4M August revenue, 97% of plan
- Gross retention: 91.8%, down 0.7 percentage points from July
- Pipeline coverage: 2.7x Q4 target
- Support backlog: 1,420 open tickets, up 18% month over month
Strategic Topics
1. Support backlog
- Context: Ticket volume increased after the July product migration and weekend response times remain above target.
- Options / trade-offs: Temporary contractor capacity versus moving two internal implementation specialists for six weeks.
- Decision / next step: Move two implementation specialists to Support for six weeks and review backlog every Friday.
2. Q4 pipeline coverage
- Context: Enterprise pipeline is healthy, but mid-market coverage is below the internal target.
- Options / trade-offs: Increase paid acquisition versus reallocate outbound SDR capacity.
- Decision / next step: CRO will return with a revised mid-market coverage plan before the September 11 forecast call.
Key Updates
- Product migration error rate returned to normal range.
- Finance completed the first 2027 planning scenario.
Risks / Escalations
- Support backlog - Business impact: Renewal risk and slower implementation handoffs - Executive owner: Julia Chen
- Mid-market pipeline gap - Business impact: Q4 bookings risk - Executive owner: Mark Ellis
Resource Decisions
- Reassign two implementation specialists to Support for six weeks.
- No additional contractor budget approved at this meeting.
Strategic Decisions
- Weekly executive backlog review will continue until open tickets fall below 900 - Decision owner: Julia Chen
Communication Required
- Audience: Implementation and Support teams
- Message / owner: Six-week staffing shift and coverage plan / Julia Chen
- Timing: 2026-09-04
Action Items
- Publish staffing transition plan - Owner: Julia Chen - Due: 2026-09-04
- Deliver revised mid-market pipeline plan - Owner: Mark Ellis - Due: 2026-09-10
- Add backlog trend to Friday executive dashboard - Owner: Daniel Brooks - Due: 2026-09-11
Issues Requiring Follow-Up
- Whether implementation delivery dates need adjustment during the six-week staffing shift.
Next Review
September 11 forecast call for pipeline; September 18 operating check for support backlog.
Date: 2026-09-04
Executive Owner: CEO - Claire Monroe
Attendees: Claire Monroe, CFO Daniel Brooks, COO Julia Chen, CRO Mark Ellis, CPO Anita Rao
Meeting Objective
Review August operating performance and decide resource changes for Q4 execution.
Business Metrics
- Revenue: $18.4M August revenue, 97% of plan
- Gross retention: 91.8%, down 0.7 percentage points from July
- Pipeline coverage: 2.7x Q4 target
- Support backlog: 1,420 open tickets, up 18% month over month
Strategic Topics
1. Support backlog
- Context: Ticket volume increased after the July product migration and weekend response times remain above target.
- Options / trade-offs: Temporary contractor capacity versus moving two internal implementation specialists for six weeks.
- Decision / next step: Move two implementation specialists to Support for six weeks and review backlog every Friday.
2. Q4 pipeline coverage
- Context: Enterprise pipeline is healthy, but mid-market coverage is below the internal target.
- Options / trade-offs: Increase paid acquisition versus reallocate outbound SDR capacity.
- Decision / next step: CRO will return with a revised mid-market coverage plan before the September 11 forecast call.
Key Updates
- Product migration error rate returned to normal range.
- Finance completed the first 2027 planning scenario.
Risks / Escalations
- Support backlog - Business impact: Renewal risk and slower implementation handoffs - Executive owner: Julia Chen
- Mid-market pipeline gap - Business impact: Q4 bookings risk - Executive owner: Mark Ellis
Resource Decisions
- Reassign two implementation specialists to Support for six weeks.
- No additional contractor budget approved at this meeting.
Strategic Decisions
- Weekly executive backlog review will continue until open tickets fall below 900 - Decision owner: Julia Chen
Communication Required
- Audience: Implementation and Support teams
- Message / owner: Six-week staffing shift and coverage plan / Julia Chen
- Timing: 2026-09-04
Action Items
- Publish staffing transition plan - Owner: Julia Chen - Due: 2026-09-04
- Deliver revised mid-market pipeline plan - Owner: Mark Ellis - Due: 2026-09-10
- Add backlog trend to Friday executive dashboard - Owner: Daniel Brooks - Due: 2026-09-11
Issues Requiring Follow-Up
- Whether implementation delivery dates need adjustment during the six-week staffing shift.
Next Review
September 11 forecast call for pipeline; September 18 operating check for support backlog.
AI-Ready Template
TASK
Convert the transcript or raw notes into the template below.
SOURCE RULES
- Use only information explicitly contained in the source.
- Do not invent names, dates, owners, decisions, commitments, deadlines, metrics, reasons, votes, or outcomes.
- Do not treat a suggestion as a decision.
- Do not treat a discussion point as an action item.
- Do not infer an owner or due date.
- Use "Not specified" for a required field that is missing.
- Use "Unresolved" for a question that was raised but not answered.
- Keep discussion, decisions, action items, and open questions separate.
- Preserve uncertainty and disagreement when they exist.
LEADERSHIP-MEETING RULES
- Preserve trade-offs and dissent when stated.
- Do not turn an executive suggestion into an approved resource decision.
- Keep operational updates separate from strategic decisions.
OUTPUT FORMAT
Meeting: [ ]
Date: [ ]
Executive Owner: [ ]
Attendees: [ ]
Meeting Objective
[ ]
Business Metrics
- [Metric]: [ ]
Strategic Topics
1. [Topic]
- Context: [ ]
- Options / trade-offs: [ ]
- Decision / next step: [ ]
Key Updates
- [ ]
Risks / Escalations
- [Risk] - Business impact: [ ] - Executive owner: [ ]
Resource Decisions
- [ ]
Strategic Decisions
- [Decision] - Decision owner: [ ]
Communication Required
- Audience: [ ]
- Message / owner: [ ]
- Timing: [ ]
Action Items
- [Task] - Owner: [ ] - Due: [ ]
Issues Requiring Follow-Up
- [ ]
Next Review
[ ]
Return only the completed template.
Convert the transcript or raw notes into the template below.
SOURCE RULES
- Use only information explicitly contained in the source.
- Do not invent names, dates, owners, decisions, commitments, deadlines, metrics, reasons, votes, or outcomes.
- Do not treat a suggestion as a decision.
- Do not treat a discussion point as an action item.
- Do not infer an owner or due date.
- Use "Not specified" for a required field that is missing.
- Use "Unresolved" for a question that was raised but not answered.
- Keep discussion, decisions, action items, and open questions separate.
- Preserve uncertainty and disagreement when they exist.
LEADERSHIP-MEETING RULES
- Preserve trade-offs and dissent when stated.
- Do not turn an executive suggestion into an approved resource decision.
- Keep operational updates separate from strategic decisions.
OUTPUT FORMAT
Meeting: [ ]
Date: [ ]
Executive Owner: [ ]
Attendees: [ ]
Meeting Objective
[ ]
Business Metrics
- [Metric]: [ ]
Strategic Topics
1. [Topic]
- Context: [ ]
- Options / trade-offs: [ ]
- Decision / next step: [ ]
Key Updates
- [ ]
Risks / Escalations
- [Risk] - Business impact: [ ] - Executive owner: [ ]
Resource Decisions
- [ ]
Strategic Decisions
- [Decision] - Decision owner: [ ]
Communication Required
- Audience: [ ]
- Message / owner: [ ]
- Timing: [ ]
Action Items
- [Task] - Owner: [ ] - Due: [ ]
Issues Requiring Follow-Up
- [ ]
Next Review
[ ]
Return only the completed template.
13. Decision Log Template
Blank Template
Decision Log
Decision ID: [D-001]
Date: [YYYY-MM-DD]
Topic: [ ]
Context: [Why a decision was needed]
Options Considered:
- [Option A]
- [Option B]
Decision: [What was actually decided]
Rationale: [Why, if explicitly stated]
Decision Maker(s): [ ]
Impact: [Teams / scope / cost / timeline affected]
Owner for Follow-Through: [ ]
Review Date: [ ]
Status: [Active / Superseded / Reversed / Under review]
Source Meeting: [ ]
---
Compact Table Version
ID | Date | Topic | Decision | Rationale | Decision Maker | Impact | Review Date | Status
Decision ID: [D-001]
Date: [YYYY-MM-DD]
Topic: [ ]
Context: [Why a decision was needed]
Options Considered:
- [Option A]
- [Option B]
Decision: [What was actually decided]
Rationale: [Why, if explicitly stated]
Decision Maker(s): [ ]
Impact: [Teams / scope / cost / timeline affected]
Owner for Follow-Through: [ ]
Review Date: [ ]
Status: [Active / Superseded / Reversed / Under review]
Source Meeting: [ ]
---
Compact Table Version
ID | Date | Topic | Decision | Rationale | Decision Maker | Impact | Review Date | Status
Filled Example
Decision Log
Decision ID: D-014
Date: 2026-09-02
Topic: Q4 onboarding release scope
Context: The team needed to choose whether to include the account-import redesign in the October release.
Options Considered:
- Include the redesign in the October release.
- Move the redesign to the next release and keep the current import flow.
Decision: Move the account-import redesign to the next release and keep the current import flow for October.
Rationale: The redesign required an additional security review and would put the October launch date at risk.
Decision Maker(s): Priya Shah, Product Lead
Impact: Product scope; design and engineering work move to the next release.
Owner for Follow-Through: Leo Martin
Review Date: 2026-10-12
Status: Active
Source Meeting: Q4 Product Release Review
Decision ID: D-015
Date: 2026-09-05
Topic: Customer beta size
Context: The beta plan needed a final account count before invitations were sent.
Options Considered:
- 10 accounts
- 20 accounts
- 30 accounts
Decision: Start with 20 accounts and hold 10 additional accounts as a waitlist.
Rationale: The support team said it could cover 20 beta accounts without adding temporary staffing.
Decision Maker(s): Carmen Lewis and Taylor Moore
Impact: Beta recruitment and support capacity.
Owner for Follow-Through: Taylor Moore
Review Date: 2026-09-25
Status: Active
Source Meeting: Customer Portal Beta Planning
Decision ID: D-016
Date: 2026-09-09
Topic: Downloadable usage CSV
Context: The team discussed adding a usage export to the beta.
Options Considered:
- Add to beta
- Defer until general release
Decision: Unresolved
Rationale: Not stated
Decision Maker(s): Not specified
Impact: Potential beta scope change.
Owner for Follow-Through: Carmen Lewis
Review Date: 2026-09-16
Status: Under review
Source Meeting: Customer Portal Project Review
Compact Table Version
D-014 | 2026-09-02 | Q4 onboarding scope | Defer account-import redesign | Security review would threaten October date | Priya Shah | Product scope and schedule | 2026-10-12 | Active
D-015 | 2026-09-05 | Customer beta size | Start with 20; 10 on waitlist | Matches support capacity | Carmen Lewis, Taylor Moore | Recruitment and support load | 2026-09-25 | Active
D-016 | 2026-09-09 | Usage CSV | Unresolved | Not stated | Not specified | Potential beta scope | 2026-09-16 | Under review
Decision ID: D-014
Date: 2026-09-02
Topic: Q4 onboarding release scope
Context: The team needed to choose whether to include the account-import redesign in the October release.
Options Considered:
- Include the redesign in the October release.
- Move the redesign to the next release and keep the current import flow.
Decision: Move the account-import redesign to the next release and keep the current import flow for October.
Rationale: The redesign required an additional security review and would put the October launch date at risk.
Decision Maker(s): Priya Shah, Product Lead
Impact: Product scope; design and engineering work move to the next release.
Owner for Follow-Through: Leo Martin
Review Date: 2026-10-12
Status: Active
Source Meeting: Q4 Product Release Review
Decision ID: D-015
Date: 2026-09-05
Topic: Customer beta size
Context: The beta plan needed a final account count before invitations were sent.
Options Considered:
- 10 accounts
- 20 accounts
- 30 accounts
Decision: Start with 20 accounts and hold 10 additional accounts as a waitlist.
Rationale: The support team said it could cover 20 beta accounts without adding temporary staffing.
Decision Maker(s): Carmen Lewis and Taylor Moore
Impact: Beta recruitment and support capacity.
Owner for Follow-Through: Taylor Moore
Review Date: 2026-09-25
Status: Active
Source Meeting: Customer Portal Beta Planning
Decision ID: D-016
Date: 2026-09-09
Topic: Downloadable usage CSV
Context: The team discussed adding a usage export to the beta.
Options Considered:
- Add to beta
- Defer until general release
Decision: Unresolved
Rationale: Not stated
Decision Maker(s): Not specified
Impact: Potential beta scope change.
Owner for Follow-Through: Carmen Lewis
Review Date: 2026-09-16
Status: Under review
Source Meeting: Customer Portal Project Review
Compact Table Version
D-014 | 2026-09-02 | Q4 onboarding scope | Defer account-import redesign | Security review would threaten October date | Priya Shah | Product scope and schedule | 2026-10-12 | Active
D-015 | 2026-09-05 | Customer beta size | Start with 20; 10 on waitlist | Matches support capacity | Carmen Lewis, Taylor Moore | Recruitment and support load | 2026-09-25 | Active
D-016 | 2026-09-09 | Usage CSV | Unresolved | Not stated | Not specified | Potential beta scope | 2026-09-16 | Under review
AI-Ready Template
TASK
Convert the transcript or raw notes into the template below.
SOURCE RULES
- Use only information explicitly contained in the source.
- Do not invent names, dates, owners, decisions, commitments, deadlines, metrics, reasons, votes, or outcomes.
- Do not treat a suggestion as a decision.
- Do not treat a discussion point as an action item.
- Do not infer an owner or due date.
- Use "Not specified" for a required field that is missing.
- Use "Unresolved" for a question that was raised but not answered.
- Keep discussion, decisions, action items, and open questions separate.
- Preserve uncertainty and disagreement when they exist.
DECISION-LOG RULES
- Extract only decisions that were explicitly made.
- A proposal, recommendation, idea, preference, or unresolved debate is not a decision.
- If a decision was not reached, write "Unresolved" rather than choosing an option.
- If the rationale or decision maker is missing, write "Not stated" or "Not specified."
- When one decision supersedes another, preserve both records and mark the earlier one "Superseded" only when the source explicitly establishes that relationship.
OUTPUT FORMAT
Decision ID: [ ]
Date: [ ]
Topic: [ ]
Context: [ ]
Options Considered:
- [ ]
Decision: [ ]
Rationale: [ ]
Decision Maker(s): [ ]
Impact: [ ]
Owner for Follow-Through: [ ]
Review Date: [ ]
Status: [ ]
Source Meeting: [ ]
Return only the completed template.
Convert the transcript or raw notes into the template below.
SOURCE RULES
- Use only information explicitly contained in the source.
- Do not invent names, dates, owners, decisions, commitments, deadlines, metrics, reasons, votes, or outcomes.
- Do not treat a suggestion as a decision.
- Do not treat a discussion point as an action item.
- Do not infer an owner or due date.
- Use "Not specified" for a required field that is missing.
- Use "Unresolved" for a question that was raised but not answered.
- Keep discussion, decisions, action items, and open questions separate.
- Preserve uncertainty and disagreement when they exist.
DECISION-LOG RULES
- Extract only decisions that were explicitly made.
- A proposal, recommendation, idea, preference, or unresolved debate is not a decision.
- If a decision was not reached, write "Unresolved" rather than choosing an option.
- If the rationale or decision maker is missing, write "Not stated" or "Not specified."
- When one decision supersedes another, preserve both records and mark the earlier one "Superseded" only when the source explicitly establishes that relationship.
OUTPUT FORMAT
Decision ID: [ ]
Date: [ ]
Topic: [ ]
Context: [ ]
Options Considered:
- [ ]
Decision: [ ]
Rationale: [ ]
Decision Maker(s): [ ]
Impact: [ ]
Owner for Follow-Through: [ ]
Review Date: [ ]
Status: [ ]
Source Meeting: [ ]
Return only the completed template.
14. Action Items Template
Blank Template
Action Items Tracker
ID: [A-001]
Action Item: [Verb + specific deliverable]
Owner: [ ]
Due Date: [YYYY-MM-DD / Not specified]
Priority: [High / Medium / Low / Not specified]
Status: [Not started / In progress / Blocked / Done]
Dependency: [ ]
Source Meeting: [ ]
Notes: [ ]
---
Compact Table Version
ID | Action Item | Owner | Due Date | Priority | Status | Dependency | Source Meeting | Notes
ID: [A-001]
Action Item: [Verb + specific deliverable]
Owner: [ ]
Due Date: [YYYY-MM-DD / Not specified]
Priority: [High / Medium / Low / Not specified]
Status: [Not started / In progress / Blocked / Done]
Dependency: [ ]
Source Meeting: [ ]
Notes: [ ]
---
Compact Table Version
ID | Action Item | Owner | Due Date | Priority | Status | Dependency | Source Meeting | Notes
Filled Example
Action Items Tracker
ID: A-031
Action Item: Send the final territory ownership file to Growth Operations.
Owner: Grace Liu
Due Date: 2026-09-14
Priority: High
Status: In progress
Dependency: Sales leadership approval of two territory exceptions
Source Meeting: Growth Operations Weekly Sync - 2026-09-11
Notes: Lead-routing launch remains blocked until the file is final.
ID: A-032
Action Item: Fix duplicate UTM rules in the two paid-social campaigns.
Owner: Ben Wong
Due Date: 2026-09-12
Priority: High
Status: Not started
Dependency: None
Source Meeting: Growth Operations Weekly Sync - 2026-09-11
Notes: Recheck attribution after the change.
ID: A-033
Action Item: Draft the customer beta invitation email.
Owner: Taylor Moore
Due Date: Not specified
Priority: Not specified
Status: Not started
Dependency: Final beta account list
Source Meeting: Customer Portal Beta Planning - 2026-09-05
Notes: Due date was not assigned in the meeting.
Compact Table Version
A-031 | Send final territory ownership file | Grace Liu | 2026-09-14 | High | In progress | Territory exception approval | Growth Ops Weekly Sync | Blocks lead routing
A-032 | Fix duplicate UTM rules | Ben Wong | 2026-09-12 | High | Not started | None | Growth Ops Weekly Sync | Recheck attribution
A-033 | Draft beta invitation email | Taylor Moore | Not specified | Not specified | Not started | Final beta account list | Beta Planning | Due date not assigned
ID: A-031
Action Item: Send the final territory ownership file to Growth Operations.
Owner: Grace Liu
Due Date: 2026-09-14
Priority: High
Status: In progress
Dependency: Sales leadership approval of two territory exceptions
Source Meeting: Growth Operations Weekly Sync - 2026-09-11
Notes: Lead-routing launch remains blocked until the file is final.
ID: A-032
Action Item: Fix duplicate UTM rules in the two paid-social campaigns.
Owner: Ben Wong
Due Date: 2026-09-12
Priority: High
Status: Not started
Dependency: None
Source Meeting: Growth Operations Weekly Sync - 2026-09-11
Notes: Recheck attribution after the change.
ID: A-033
Action Item: Draft the customer beta invitation email.
Owner: Taylor Moore
Due Date: Not specified
Priority: Not specified
Status: Not started
Dependency: Final beta account list
Source Meeting: Customer Portal Beta Planning - 2026-09-05
Notes: Due date was not assigned in the meeting.
Compact Table Version
A-031 | Send final territory ownership file | Grace Liu | 2026-09-14 | High | In progress | Territory exception approval | Growth Ops Weekly Sync | Blocks lead routing
A-032 | Fix duplicate UTM rules | Ben Wong | 2026-09-12 | High | Not started | None | Growth Ops Weekly Sync | Recheck attribution
A-033 | Draft beta invitation email | Taylor Moore | Not specified | Not specified | Not started | Final beta account list | Beta Planning | Due date not assigned
AI-Ready Template
TASK
Convert the transcript or raw notes into the template below.
SOURCE RULES
- Use only information explicitly contained in the source.
- Do not invent names, dates, owners, decisions, commitments, deadlines, metrics, reasons, votes, or outcomes.
- Do not treat a suggestion as a decision.
- Do not treat a discussion point as an action item.
- Do not infer an owner or due date.
- Use "Not specified" for a required field that is missing.
- Use "Unresolved" for a question that was raised but not answered.
- Keep discussion, decisions, action items, and open questions separate.
- Preserve uncertainty and disagreement when they exist.
ACTION-ITEM RULES
- Extract an action item only when the source indicates that work needs to be done.
- Write the task as a concrete verb + deliverable without changing its meaning.
- Do not assign an owner from context unless the speaker explicitly owns or accepts the task.
- Do not invent a due date, priority, or status.
- Do not convert a question, idea, observation, or general responsibility into an action item.
OUTPUT FORMAT
ID: [ ]
Action Item: [Verb + specific deliverable]
Owner: [ ]
Due Date: [ ]
Priority: [ ]
Status: [ ]
Dependency: [ ]
Source Meeting: [ ]
Notes: [ ]
Return only the completed template.
Convert the transcript or raw notes into the template below.
SOURCE RULES
- Use only information explicitly contained in the source.
- Do not invent names, dates, owners, decisions, commitments, deadlines, metrics, reasons, votes, or outcomes.
- Do not treat a suggestion as a decision.
- Do not treat a discussion point as an action item.
- Do not infer an owner or due date.
- Use "Not specified" for a required field that is missing.
- Use "Unresolved" for a question that was raised but not answered.
- Keep discussion, decisions, action items, and open questions separate.
- Preserve uncertainty and disagreement when they exist.
ACTION-ITEM RULES
- Extract an action item only when the source indicates that work needs to be done.
- Write the task as a concrete verb + deliverable without changing its meaning.
- Do not assign an owner from context unless the speaker explicitly owns or accepts the task.
- Do not invent a due date, priority, or status.
- Do not convert a question, idea, observation, or general responsibility into an action item.
OUTPUT FORMAT
ID: [ ]
Action Item: [Verb + specific deliverable]
Owner: [ ]
Due Date: [ ]
Priority: [ ]
Status: [ ]
Dependency: [ ]
Source Meeting: [ ]
Notes: [ ]
Return only the completed template.
15. Retrospective Meeting Notes Template
Blank Template
Team / Project: [ ]
Retro Period: [Sprint / project / month]
Date: [YYYY-MM-DD]
Facilitator: [ ]
Participants: [ ]
Goal / Outcome Reviewed
[ ]
What Went Well
- [ ]
What Did Not Go Well
- [ ]
What We Learned
- [ ]
Root Causes Identified
- [ ]
Start
- [New behavior / process]
Stop
- [Behavior / process to stop]
Continue
- [Behavior / process to keep]
Experiments
- [Experiment] - Success measure: [ ] - Review date: [ ]
Action Items
- [Task] - Owner: [ ] - Due: [ ]
Unresolved Topics
- [ ]
Next Review Date
[ ]
Retro Period: [Sprint / project / month]
Date: [YYYY-MM-DD]
Facilitator: [ ]
Participants: [ ]
Goal / Outcome Reviewed
[ ]
What Went Well
- [ ]
What Did Not Go Well
- [ ]
What We Learned
- [ ]
Root Causes Identified
- [ ]
Start
- [New behavior / process]
Stop
- [Behavior / process to stop]
Continue
- [Behavior / process to keep]
Experiments
- [Experiment] - Success measure: [ ] - Review date: [ ]
Action Items
- [Task] - Owner: [ ] - Due: [ ]
Unresolved Topics
- [ ]
Next Review Date
[ ]
Filled Example
Team / Project: Checkout Experience Squad
Retro Period: Sprint 18
Date: 2026-09-13
Facilitator: Jonah Reed
Participants: Jonah Reed, Mei Tan, Alice Brown, Kareem Hassan, Lucy Ford
Goal / Outcome Reviewed
Ship the first version of address autocomplete and reduce checkout address errors without increasing page latency.
What Went Well
- Address autocomplete shipped on schedule.
- QA found the mobile keyboard issue before production release.
- Engineering and Support used one shared bug triage document during launch week.
What Did Not Go Well
- Analytics event names changed after implementation had started.
- Two test cases for apartment-number handling were missing until late QA.
- The team spent too much of the final review meeting re-reading issues that were already resolved.
What We Learned
- Analytics naming needs sign-off before implementation, not during QA.
- Launch review should separate unresolved issues from closed issues.
Root Causes Identified
- Analytics requirements were treated as an implementation detail instead of a release dependency.
- The QA checklist did not explicitly cover secondary address fields.
Start
- Require analytics event-name approval before frontend implementation begins.
- Use a launch-review view that shows only open or newly changed issues.
Stop
- Reopening resolved launch issues in the main review unless new evidence exists.
Continue
- Shared Engineering + Support bug triage during launch week.
Experiments
- Add an analytics sign-off gate to Sprint 19 planning - Success measure: No event-name changes after implementation begins - Review date: 2026-09-27
Action Items
- Add analytics sign-off to the release checklist - Owner: Mei Tan - Due: 2026-09-16
- Add secondary address-field cases to QA template - Owner: Alice Brown - Due: 2026-09-16
- Create open-issues-only launch view - Owner: Kareem Hassan - Due: 2026-09-18
Unresolved Topics
- Whether the team needs a dedicated pre-launch analytics review meeting.
Next Review Date
2026-09-27
Retro Period: Sprint 18
Date: 2026-09-13
Facilitator: Jonah Reed
Participants: Jonah Reed, Mei Tan, Alice Brown, Kareem Hassan, Lucy Ford
Goal / Outcome Reviewed
Ship the first version of address autocomplete and reduce checkout address errors without increasing page latency.
What Went Well
- Address autocomplete shipped on schedule.
- QA found the mobile keyboard issue before production release.
- Engineering and Support used one shared bug triage document during launch week.
What Did Not Go Well
- Analytics event names changed after implementation had started.
- Two test cases for apartment-number handling were missing until late QA.
- The team spent too much of the final review meeting re-reading issues that were already resolved.
What We Learned
- Analytics naming needs sign-off before implementation, not during QA.
- Launch review should separate unresolved issues from closed issues.
Root Causes Identified
- Analytics requirements were treated as an implementation detail instead of a release dependency.
- The QA checklist did not explicitly cover secondary address fields.
Start
- Require analytics event-name approval before frontend implementation begins.
- Use a launch-review view that shows only open or newly changed issues.
Stop
- Reopening resolved launch issues in the main review unless new evidence exists.
Continue
- Shared Engineering + Support bug triage during launch week.
Experiments
- Add an analytics sign-off gate to Sprint 19 planning - Success measure: No event-name changes after implementation begins - Review date: 2026-09-27
Action Items
- Add analytics sign-off to the release checklist - Owner: Mei Tan - Due: 2026-09-16
- Add secondary address-field cases to QA template - Owner: Alice Brown - Due: 2026-09-16
- Create open-issues-only launch view - Owner: Kareem Hassan - Due: 2026-09-18
Unresolved Topics
- Whether the team needs a dedicated pre-launch analytics review meeting.
Next Review Date
2026-09-27
AI-Ready Template
TASK
Convert the transcript or raw notes into the template below.
SOURCE RULES
- Use only information explicitly contained in the source.
- Do not invent names, dates, owners, decisions, commitments, deadlines, metrics, reasons, votes, or outcomes.
- Do not treat a suggestion as a decision.
- Do not treat a discussion point as an action item.
- Do not infer an owner or due date.
- Use "Not specified" for a required field that is missing.
- Use "Unresolved" for a question that was raised but not answered.
- Keep discussion, decisions, action items, and open questions separate.
- Preserve uncertainty and disagreement when they exist.
RETROSPECTIVE RULES
- Keep observations, inferred lessons, and confirmed root causes separate.
- Record a root cause only when participants explicitly identify or agree on it as a cause.
- Do not turn criticism of a process into criticism of a person unless the source explicitly frames it that way.
OUTPUT FORMAT
Team / Project: [ ]
Retro Period: [ ]
Date: [ ]
Facilitator: [ ]
Participants: [ ]
Goal / Outcome Reviewed
[ ]
What Went Well
- [ ]
What Did Not Go Well
- [ ]
What We Learned
- [ ]
Root Causes Identified
- [ ]
Start
- [ ]
Stop
- [ ]
Continue
- [ ]
Experiments
- [Experiment] - Success measure: [ ] - Review date: [ ]
Action Items
- [Task] - Owner: [ ] - Due: [ ]
Unresolved Topics
- [ ]
Next Review Date
[ ]
Return only the completed template.
Convert the transcript or raw notes into the template below.
SOURCE RULES
- Use only information explicitly contained in the source.
- Do not invent names, dates, owners, decisions, commitments, deadlines, metrics, reasons, votes, or outcomes.
- Do not treat a suggestion as a decision.
- Do not treat a discussion point as an action item.
- Do not infer an owner or due date.
- Use "Not specified" for a required field that is missing.
- Use "Unresolved" for a question that was raised but not answered.
- Keep discussion, decisions, action items, and open questions separate.
- Preserve uncertainty and disagreement when they exist.
RETROSPECTIVE RULES
- Keep observations, inferred lessons, and confirmed root causes separate.
- Record a root cause only when participants explicitly identify or agree on it as a cause.
- Do not turn criticism of a process into criticism of a person unless the source explicitly frames it that way.
OUTPUT FORMAT
Team / Project: [ ]
Retro Period: [ ]
Date: [ ]
Facilitator: [ ]
Participants: [ ]
Goal / Outcome Reviewed
[ ]
What Went Well
- [ ]
What Did Not Go Well
- [ ]
What We Learned
- [ ]
Root Causes Identified
- [ ]
Start
- [ ]
Stop
- [ ]
Continue
- [ ]
Experiments
- [Experiment] - Success measure: [ ] - Review date: [ ]
Action Items
- [Task] - Owner: [ ] - Due: [ ]
Unresolved Topics
- [ ]
Next Review Date
[ ]
Return only the completed template.
16. Brainstorm / Workshop Notes Template
Blank Template
Session: [ ]
Date: [YYYY-MM-DD]
Facilitator: [ ]
Participants: [ ]
Problem / Prompt: [ ]
Constraints: [ ]
Ideas
1. [Idea]
2. [Idea]
3. [Idea]
Themes / Clusters
- [Theme]: [Related ideas]
Questions Raised
- [ ]
Votes / Scores
- [Idea] - [Votes / score / criteria]
Shortlisted Ideas
- [ ]
Selected Direction
[Decision, or Unresolved]
Reasons
- [ ]
Ideas Not Selected / Deferred
- [Idea] - Reason if stated: [ ]
Next Experiments
- [Experiment] - Owner: [ ] - Due: [ ] - Success measure: [ ]
Action Items
- [Task] - Owner: [ ] - Due: [ ]
Date: [YYYY-MM-DD]
Facilitator: [ ]
Participants: [ ]
Problem / Prompt: [ ]
Constraints: [ ]
Ideas
1. [Idea]
2. [Idea]
3. [Idea]
Themes / Clusters
- [Theme]: [Related ideas]
Questions Raised
- [ ]
Votes / Scores
- [Idea] - [Votes / score / criteria]
Shortlisted Ideas
- [ ]
Selected Direction
[Decision, or Unresolved]
Reasons
- [ ]
Ideas Not Selected / Deferred
- [Idea] - Reason if stated: [ ]
Next Experiments
- [Experiment] - Owner: [ ] - Due: [ ] - Success measure: [ ]
Action Items
- [Task] - Owner: [ ] - Due: [ ]
Filled Example
Session: Reduce New-Customer Setup Time
Date: 2026-09-06
Facilitator: Morgan Hale
Participants: Morgan Hale, Priya Singh, Evan Ross, Jenna Clark, Luis Moreno
Problem / Prompt: How can the team reduce the average time from contract signature to first successful customer setup?
Constraints: No additional implementation headcount in Q4; security review cannot be removed.
Ideas
1. Pre-fill implementation forms from CRM opportunity data.
2. Replace the 60-minute kickoff with a 30-minute structured setup call.
3. Create an implementation-readiness checklist for Sales before handoff.
4. Build a self-service data-format validator.
5. Offer twice-weekly group setup office hours for smaller accounts.
6. Assign one implementation specialist by industry.
Themes / Clusters
- Better handoff data: CRM pre-fill, Sales readiness checklist.
- Faster validation: Self-service data validator.
- Meeting redesign: Shorter setup call, group office hours.
- Specialization: Industry-based specialist assignment.
Questions Raised
- How often is missing CRM data actually responsible for setup delays?
- Would group office hours work for customers with security-sensitive configurations?
Votes / Scores
- Sales readiness checklist - 5 votes
- Self-service data validator - 5 votes
- CRM pre-fill - 4 votes
- 30-minute setup call - 2 votes
- Group office hours - 2 votes
- Industry specialist assignment - 1 vote
Shortlisted Ideas
- Sales readiness checklist.
- Self-service data validator.
- CRM pre-fill.
Selected Direction
Run two experiments: a Sales readiness checklist and a lightweight data validator prototype. CRM pre-fill remains a follow-up idea pending data-quality analysis.
Reasons
- The readiness checklist can be tested immediately without engineering work.
- The validator targets a repeated source of implementation delay and can be prototyped before full development.
Ideas Not Selected / Deferred
- CRM pre-fill - Reason if stated: Need to measure source-data completeness first.
- 30-minute setup call - Reason if stated: Team wants evidence that kickoff length causes delay.
- Group office hours - Reason if stated: Security-sensitive accounts may require private sessions.
- Industry specialist assignment - Reason if stated: Conflicts with current capacity model.
Next Experiments
- Sales readiness checklist pilot - Owner: Jenna Clark - Due: 2026-09-14 - Success measure: Percentage of pilot handoffs arriving with all required information
- Data validator prototype - Owner: Luis Moreno - Due: 2026-09-21 - Success measure: Detect the five most common import-format errors before implementation review
Action Items
- Pull three months of handoff-delay reasons - Owner: Evan Ross - Due: 2026-09-11
- Draft readiness checklist - Owner: Jenna Clark - Due: 2026-09-09
Date: 2026-09-06
Facilitator: Morgan Hale
Participants: Morgan Hale, Priya Singh, Evan Ross, Jenna Clark, Luis Moreno
Problem / Prompt: How can the team reduce the average time from contract signature to first successful customer setup?
Constraints: No additional implementation headcount in Q4; security review cannot be removed.
Ideas
1. Pre-fill implementation forms from CRM opportunity data.
2. Replace the 60-minute kickoff with a 30-minute structured setup call.
3. Create an implementation-readiness checklist for Sales before handoff.
4. Build a self-service data-format validator.
5. Offer twice-weekly group setup office hours for smaller accounts.
6. Assign one implementation specialist by industry.
Themes / Clusters
- Better handoff data: CRM pre-fill, Sales readiness checklist.
- Faster validation: Self-service data validator.
- Meeting redesign: Shorter setup call, group office hours.
- Specialization: Industry-based specialist assignment.
Questions Raised
- How often is missing CRM data actually responsible for setup delays?
- Would group office hours work for customers with security-sensitive configurations?
Votes / Scores
- Sales readiness checklist - 5 votes
- Self-service data validator - 5 votes
- CRM pre-fill - 4 votes
- 30-minute setup call - 2 votes
- Group office hours - 2 votes
- Industry specialist assignment - 1 vote
Shortlisted Ideas
- Sales readiness checklist.
- Self-service data validator.
- CRM pre-fill.
Selected Direction
Run two experiments: a Sales readiness checklist and a lightweight data validator prototype. CRM pre-fill remains a follow-up idea pending data-quality analysis.
Reasons
- The readiness checklist can be tested immediately without engineering work.
- The validator targets a repeated source of implementation delay and can be prototyped before full development.
Ideas Not Selected / Deferred
- CRM pre-fill - Reason if stated: Need to measure source-data completeness first.
- 30-minute setup call - Reason if stated: Team wants evidence that kickoff length causes delay.
- Group office hours - Reason if stated: Security-sensitive accounts may require private sessions.
- Industry specialist assignment - Reason if stated: Conflicts with current capacity model.
Next Experiments
- Sales readiness checklist pilot - Owner: Jenna Clark - Due: 2026-09-14 - Success measure: Percentage of pilot handoffs arriving with all required information
- Data validator prototype - Owner: Luis Moreno - Due: 2026-09-21 - Success measure: Detect the five most common import-format errors before implementation review
Action Items
- Pull three months of handoff-delay reasons - Owner: Evan Ross - Due: 2026-09-11
- Draft readiness checklist - Owner: Jenna Clark - Due: 2026-09-09
AI-Ready Template
TASK
Convert the transcript or raw notes into the template below.
SOURCE RULES
- Use only information explicitly contained in the source.
- Do not invent names, dates, owners, decisions, commitments, deadlines, metrics, reasons, votes, or outcomes.
- Do not treat a suggestion as a decision.
- Do not treat a discussion point as an action item.
- Do not infer an owner or due date.
- Use "Not specified" for a required field that is missing.
- Use "Unresolved" for a question that was raised but not answered.
- Keep discussion, decisions, action items, and open questions separate.
- Preserve uncertainty and disagreement when they exist.
BRAINSTORM RULES
- Keep generated ideas separate from selected ideas.
- Do not treat a vote, high score, positive reaction, or suggestion as an approved decision unless the source says it was selected.
- Preserve deferred ideas instead of deleting them.
- Do not invent reasons for rejection or selection.
OUTPUT FORMAT
Session: [ ]
Date: [ ]
Facilitator: [ ]
Participants: [ ]
Problem / Prompt: [ ]
Constraints: [ ]
Ideas
1. [ ]
Themes / Clusters
- [Theme]: [ ]
Questions Raised
- [ ]
Votes / Scores
- [Idea] - [ ]
Shortlisted Ideas
- [ ]
Selected Direction
[ ]
Reasons
- [ ]
Ideas Not Selected / Deferred
- [Idea] - Reason if stated: [ ]
Next Experiments
- [Experiment] - Owner: [ ] - Due: [ ] - Success measure: [ ]
Action Items
- [Task] - Owner: [ ] - Due: [ ]
Return only the completed template.
Convert the transcript or raw notes into the template below.
SOURCE RULES
- Use only information explicitly contained in the source.
- Do not invent names, dates, owners, decisions, commitments, deadlines, metrics, reasons, votes, or outcomes.
- Do not treat a suggestion as a decision.
- Do not treat a discussion point as an action item.
- Do not infer an owner or due date.
- Use "Not specified" for a required field that is missing.
- Use "Unresolved" for a question that was raised but not answered.
- Keep discussion, decisions, action items, and open questions separate.
- Preserve uncertainty and disagreement when they exist.
BRAINSTORM RULES
- Keep generated ideas separate from selected ideas.
- Do not treat a vote, high score, positive reaction, or suggestion as an approved decision unless the source says it was selected.
- Preserve deferred ideas instead of deleting them.
- Do not invent reasons for rejection or selection.
OUTPUT FORMAT
Session: [ ]
Date: [ ]
Facilitator: [ ]
Participants: [ ]
Problem / Prompt: [ ]
Constraints: [ ]
Ideas
1. [ ]
Themes / Clusters
- [Theme]: [ ]
Questions Raised
- [ ]
Votes / Scores
- [Idea] - [ ]
Shortlisted Ideas
- [ ]
Selected Direction
[ ]
Reasons
- [ ]
Ideas Not Selected / Deferred
- [Idea] - Reason if stated: [ ]
Next Experiments
- [Experiment] - Owner: [ ] - Due: [ ] - Success measure: [ ]
Action Items
- [Task] - Owner: [ ] - Due: [ ]
Return only the completed template.
0 comments