Meeting Agenda Topics - 60+ Examples for Effective Meetings

This guide covers suggested agenda topics for a variety of common meeting types. Each section includes a short intro with best practices, followed by a breakdown of agenda items tailored to the meeting’s purpose. Use it to plan more focused, effective meetings–whether you’re leading a team check-in or presenting at a board meeting.

Meeting Agenda for Team Check-ins (Weekly or Bi-Weekly)

Team check-ins might be short, but they pack a punch when it comes to keeping everyone on the same page. These quick catch-ups are a great way to build trust, share progress, and even celebrate small wins. The best ones stay informal and consistent, making sure everyone gets a chance to speak. Keep it friendly and supportive, and your team will actually look forward to these mini huddles.

‍

• Wins & Shout-outs (5 min): Start on a positive note by acknowledging team successes or individual accomplishments since the last meeting. This boosts morale and sets an optimistic tone for the discussion.
  
  
• Progress Updates (10–15 min): Have each team member give a brief update on their key tasks and achievements since the last check-in (aim for 1–2 minutes per person to keep it concise)​. Focus on highlights relevant to the group rather than granular details, and capture any follow-up actions as needed.
  
  
• Challenges & Blockers (5–10 min): Discuss any obstacles or issues hindering progress. Team members can raise problems they’re facing, and the group can brainstorm solutions or offer support. Addressing roadblocks early helps prevent minor issues from escalating.
  
  
• Upcoming Priorities (5 min): Align on what’s next – each person (or the team as a whole) briefly outlines their main focus or goals for the coming week(s). This ensures everyone knows the plan going forward and can coordinate efforts.
  
  
• Announcements & Housekeeping (5 min): Share important news, updates, or logistical information. This could include company announcements, policy changes, upcoming deadlines, PTO notices, or any “need-to-know” items for the team.
  
  
• Action Items & Wrap-Up (2 min): Reserve a moment to recap any decisions made and list out action items with owners. Confirm deadlines or next steps for these tasks so everyone leaves clear on responsibilities.

‍

Example Agenda for Project Kickoffs

The best kickoff meetings strike a balance: come prepared with an agenda, but keep the vibe enthusiastic and leave plenty of room for questions. Set a positive tone now, and you'll have everyone feeling fired up and clear on the plan.

‍

• Introductions & Roles (5 min): Introduce all participants, including project team members and stakeholders. Briefly clarify each person’s role in the project so everyone knows who is responsible for what from the outset. If some team members haven’t met before, an intro round ensures everyone is acquainted.
  
  
• Project Overview & Goals (10 min): Provide background on why the project exists and what it aims to achieve. Cover the project’s purpose, key objectives, and what success looks like. This aligns the team on the “why” and “what” of the initiative from the start (the 5 W’s: who, what, where, when, why – plus how)​.
  
  
• Scope & Deliverables (5 min): Clearly define the project scope – what’s included and, just as importantly, what’s out of scope. List the major deliverables or outcomes expected. Establishing scope boundaries upfront manages expectations and prevents scope creep.
  
  
• Timeline & Milestones (5 min): Review the high-level timeline, including key milestones and deadlines. Share the project schedule or roadmap so everyone understands the major phases and dates. Visuals like a simple timeline or Gantt chart can help illustrate how the project will unfold.
  
  
• Roles & Responsibilities (5 min): Dive deeper into who is doing what. Clarify task ownership and team member responsibilities for different work streams. For example, identify the project manager, technical lead, QA responsible, etc. (even if some of this was mentioned in introductions, here you ensure no overlaps or gaps in duties).
  
  
• Communication Plan & Tools (5 min): Agree on how the team will collaborate and communicate. Discuss the meeting cadence (e.g., weekly syncs or daily stand-ups), preferred channels (email, Slack, project management software), and tools/repositories everyone will use for documents or tracking. Setting these norms prevents confusion later.
  
  
• Risks & Dependencies (5 min): Highlight any known project risks, constraints, or external dependencies. For example, note if you’re waiting on a vendor or if there’s a tight regulatory deadline. Brainstorm mitigation plans for major risks. Encouraging openness about risks early helps the team be proactive.
  
  
• Q&A and Feedback (10 min): Open the floor for questions. Give team members (and clients, if present) a chance to clarify uncertainties, raise concerns, or offer suggestions. This ensures everyone has a shared understanding and any ambiguities are addressed before work begins.
  
  
• Next Steps & Action Items (5 min): Conclude by outlining immediate next steps. This might include scheduling the next team meeting, setting up project boards, or specific tasks like “Alice will send the updated requirements document by tomorrow.” Make sure each action item has an owner and due date.

‍

‍

Strategic Planning Meeting Agenda

Strategic planning sessions are where we zoom out and think big picture. This meeting often shapes the direction of the team or company, so the tone is focused. But. it doesn't have to be stiff.

‍

One tip: set clear goals for the session and encourage everyone to speak up, because big ideas can come from anywhere. Mix a bit of creativity and candor, and you'll keep it engaging while charting the path forward.

‍

• Mission Refresher & Current State: Begin by reaffirming the organization’s mission or vision and reviewing where things stand today. This might include a quick recap of recent performance versus goals, and any notable internal updates. Setting this context ensures everyone starts the planning session with a shared understanding of the baseline.
  
  
• External Environment Review: Discuss external factors that influence your strategy. This can cover market trends, competitive landscape, customer feedback, or industry changes. For example, identify emerging opportunities or threats (new competitors, regulatory changes) that the company must account for in its plan.
  
  
• SWOT Analysis: Many strategic planning sessions formally or informally assess the company’s Strengths, Weaknesses, Opportunities, and Threats. Identify internal strengths to leverage and weaknesses to address, along with external opportunities to pursue and threats to mitigate. This analysis helps pinpoint areas of focus and informs goal setting.
  
  
• Define Strategic Goals: Agree on a handful of high-level strategic objectives for the upcoming period (e.g., year or multi-year horizon). These should be broad goals aligned with the company’s vision – for example, “Expand into 2 new markets” or “Improve customer retention by 15%.” Ensure they are clear and that leadership is aligned on these top priorities.
  
  
• Brainstorm Initiatives: For each strategic goal, brainstorm possible initiatives or projects to achieve it. Encourage creative thinking – at this stage, all ideas are welcome. This could involve breakout groups generating ideas for different goals. The aim is to develop a list of potential strategic initiatives (e.g., new product launches, marketing campaigns, operational improvements) that support the goals.
  
  
• Prioritization & Resource Allocation: Evaluate and rank the proposed initiatives. Consider impact, effort, and resources required. It’s often useful to discuss which initiatives will have the biggest payoff or are most urgent. From this, decide which initiatives to pursue (you might use a vote or a scoring system). Align this with a high-level view of resource allocation – for instance, ensure the budget or team capacity is considered for each major initiative.
  
  
• Action Plan & Next Steps: Outline how the strategy will be finalized and executed. This can include assigning owners to each strategic initiative (who will flesh out the plan for it), setting deadlines for creating detailed project plans or OKRs, and scheduling follow-up strategy review meetings. Summarize any immediate next steps – for example, “Finance will model the budget impact of the top 3 initiatives by next month” or “We will reconvene for a final strategy approval meeting on [date].”

‍

Client Update Meeting Agenda

This is your chance to show the client what's going on behind the scenes, and that you've got things under control. The vibe should be friendly and transparent; after all, nobody likes unwelcome surprises in a progress update.

‍

Come prepared with clear highlights and give a heads-up on any issues. Be ready to listen to their feedback and questions. This sets a collaborative tone and makes the client feel involved and confident in the team.

‍

• Welcome & Introductions (if needed): Start by greeting the client and introducing any team members or client representatives who are new. Reiterate the meeting’s purpose (e.g., “monthly project update” or “quarterly business review”) so everyone knows the objectives.
  
  
• Project Status Overview: Provide a high-level summary of progress since the last client meeting. This might include a recap of what’s been completed, current stage of the project, and overall status (on track, ahead/behind schedule). Visual status reports (like a dashboard or percent-complete bar) can be helpful here to quickly convey progress.
  
  
• Key Results & Metrics: Review any important metrics or KPIs relevant to the client. For example, if it’s a marketing campaign update, share lead numbers or ROI; if it’s a service engagement, report on performance stats or support ticket volumes. Highlight positive outcomes and trends (e.g., “website traffic is up 20% this month”) and be transparent about any metrics below target. Sharing concrete numbers helps demonstrate value to the client​.
  
  
• Deliverables Completed: Go over the deliverables or milestones achieved in the period. For instance, mention if a particular module was delivered, a phase was finished, or any reports were submitted. This lets the client clearly see what they have “in hand” as a result of the team’s work since the last meeting. If appropriate, this could include a brief demo or showcase of work done.
  
  
• Current Issues & Risks: Discuss any challenges that have arisen. Be candid about problems (e.g., a delay in timeline, a technical hurdle, supply chain issue) and explain what is being done to address them. Similarly, note any risks on the horizon that the client should be aware of, along with mitigation plans. Clients appreciate proactivity, so raising issues with a solution-oriented approach builds trust. Also address any changes in requirements or scope that came up, and confirm how they’re being handled.
  
  
• Next Steps & Upcoming Work: Lay out what’s coming up before the next client meeting. This includes upcoming deliverables, key activities, or milestones expected in the next period. Provide dates if possible (“We plan to complete X by <date>”). This gives the client a clear picture of the roadmap ahead and sets expectations for what they will see next.
  
  
• Client Input & Feedback: Invite the client to share their feedback or priorities. This can be a discussion of whether the project is meeting their expectations, any adjustments they’d like, or questions they have about the work. It’s important to give space for the client’s voice – for example, they might have new information or shifting goals that need to be incorporated.
  
  
• Action Items & Closing: End by summarizing any agreed-upon actions. This could include tasks for your team (e.g., “send revised timeline”) as well as actions the client promised (e.g., “provide approval on design by Friday”). Confirm deadlines and owners for each item. Finally, thank the client for their time and confirm the next meeting or update schedule.
  
  

‍

Agenda for Executive Leadership Meetings

Executive leadership meetings are typically high-level discussions. But. the best ones are still collaborative and even a bit upbeat.

‍

It helps to set a crisp agenda and stick to it. Everyone’s time is precious at this level.

‍

Encourage open dialogue, focus on solutions, and you'll make real progress while keeping the meeting engaging.

‍

• Company Metrics & Dashboard (15 min): Begin with a review of key company-wide metrics and performance indicators. Each executive or department head can contribute a brief update (perhaps ~2 minutes each) on their area’s top KPIs – for example, sales pipeline figures, marketing campaign results, product development milestones, financials, etc. This round-robin of updates keeps all leaders informed of overall progress and highlights where the organization is on/off target. Consider using a visual dashboard or scorecard for clarity.
  
  
• Key Issues & Roadblocks (15 min): Next, discuss any critical issues affecting the business. This is a time for leaders to raise cross-departmental problems or risks that require attention (e.g. a major client issue, a supply chain disruption, resource constraints). The team can then collectively problem-solve or decide on escalation steps. Focusing on a short list of the most pressing issues ensures the meeting addresses obstacles that could impede company objectives​.
  
  
• Strategic Initiative Updates (10 min): Review the status of major strategic projects or initiatives. For example, if the company has a big product launch or an expansion plan in motion, the executive owner of that initiative provides an update on progress, timeline, and any help needed from the group. This keeps all executives aligned on long-term projects beyond the day-to-day metrics.
  
  
• Decision & Discussion Items (15+ min): Tackle agenda items that require the leadership team’s input or formal decisions. These could range from approving a budget or policy change, to deciding on a strategic pivot, to resolving interdepartmental conflicts. Ensure each decision topic is introduced with necessary context (often pre-read materials are helpful) and then open the floor for discussion. Allocate time per item and try to reach a conclusion or next step for each.
  
  
• Organizational Matters (10 min): Cover any people or organizational topics at the leadership level. This might include updates on key hires or talent gaps, culture or morale updates, upcoming organizational changes, or announcements (e.g., “We’re opening a new office” or “Our all-hands meeting is next week”). Leaders can share any broad concerns from their teams that others should be aware of.
  
  
• Future Outlook & Strategy (optional, 5 min): If time allows, spend a few minutes on forward-looking discussion. This could be a quick brainstorming on an emerging opportunity or a roundtable where each exec shares a short insight (for instance, a market trend they’re watching). The idea is to keep strategic thinking in the mix, even in a routine meeting, without getting lost in details.
  
  
• Recap & Action Items (5 min): Conclude by summarizing decisions made and listing out action items. For example, “CFO will circulate the Q3 budget adjustments by Tuesday; CMO and Head of Sales to meet on lead attribution issue,” etc. Clearly assign owners and deadlines. Confirm if any topics need follow-up in the next meeting. Ending with a quick recap ensures accountability and that everyone leaves on the same page regarding next steps.

‍

Agenda for Departmental Reviews (e.g. Marketing, Sales, Product)

Departmental reviews offer a chance to step back and see how your team is doing as a whole. 

‍

The tone can be open and honest. Celebrate the wins, but also talk about challenges without pointing fingers.

‍

It's a good idea to bring data or examples so discussions stay grounded in reality. Keep it constructive and collaborative, and everyone will leave with a clear sense of what's next and what can be improved.

‍

• Goals & KPI Review: Start by reviewing the department’s targets for the period (quarter, month, etc.) and the actual performance against those key metrics. For example, a Sales department might look at quota attainment or new bookings, while Marketing might review lead generation numbers or campaign ROI. Identify which goals were met or exceeded, and which fell short, to set a fact-based foundation for the discussion.
  
  
• Wins & Highlights: Celebrate the department’s notable successes. This could include big deals closed, successful campaigns, product launches, quality improvements, or any milestone worth recognizing. Beginning with highlights (“Good news”) helps reinforce what’s working well and acknowledges team efforts​. It also energizes the meeting before delving into heavier topics.
  
  
• Project/Campaign Updates: Go through the status of major ongoing initiatives within the department. Each project owner (or the department head) gives a brief update on progress, significant results so far, and any recent deliverables. For instance, Marketing might update on a branding campaign’s performance, or Product team might demo a new feature release. This informs everyone of the current workload and achievements.
  
  
• Challenges & Lessons Learned: Candidly address what didn’t go as planned. Discuss any projects that underperformed or targets that were missed, and analyze why. For example, “Q2 sales were 10% below target due to longer client procurement cycles” or “The social media campaign didn’t gain traction, possibly due to timing and platform choice.” Extract lessons from these setbacks – what the team can do differently or what support is needed – so the same issues aren’t repeated.
  
  
• Cross-Functional Dependencies: If the department’s work intersects heavily with other teams, discuss any inter-departmental issues. This is the time to bring up needs or concerns involving other groups (e.g., Sales might need more Marketing support for leads; Product might be waiting on Engineering for a fix). Ensuring alignment and addressing bottlenecks between departments is key in a review, especially if leaders from other functions are present.
  
  
• Upcoming Plans: Outline the department’s plan for the next period. Talk about upcoming projects, campaigns, or priorities and how they tie into the company’s objectives. For instance, Sales might preview a strategy for a new market segment next quarter, or Product might share a roadmap update. This gives attendees insight into the department’s focus moving forward and opens the floor for any feedback or alignment questions before plans are executed.
  
  
• Resource & Support Needs: If applicable, discuss whether the department has the resources (budget, staff, tools) to meet its upcoming goals. This can be a place to request additional resources or justify them – such as hiring needs, increased budget for an initiative, or support from another department. It’s important to surface these needs during the review so that executives or other stakeholders can consider and address them.
  
  
• Q&A and Feedback: Invite questions from the audience (which might include executives or colleagues from other departments). There may be clarifying questions about why certain goals were or weren’t met, or suggestions for improvement from different perspectives. It’s also an opportunity for senior management to provide feedback or strategic guidance to the department.
  
  
• Action Items & Decisions: Conclude the review by summarizing any decisions made (e.g., approval of a new hire, agreement to pivot strategy) and listing action items. For example, “Marketing will prepare a revised content plan by next month,” or “Need IT support on upgrading the analytics software – CIO to follow up.” Make sure each item has an owner. End by thanking the team for their hard work and clarifying any changes in direction or expectations as a result of the review.

‍

Agenda for Retrospectives/Post-Mortem Meetings

Hindsight is 20/20, and that's the whole point of a retrospective. This type of meeting is all about learning from the past, so the team can improve going forward.

‍

The key is to create a space where everyone feels comfortable sharing what went well and what didn’t. Accordingly, start with a quick round of positives or thank-yous to set a supportive tone. Keep it honest and focused on improvement (not finger-pointing), and you'll turn lessons learned into actionable next steps.

‍

• Purpose & Ground Rules: Begin by setting a constructive tone. Remind everyone that the goal of the retrospective/post-mortem is to learn and improve, not to assign blame. Establish a safe environment where team members can speak openly. (In agile teams, this might involve citing the “prime directive” that everyone did their best given what they knew at the time.) This introduction helps the team feel comfortable sharing honest feedback.
  
  
• Recap Goals & Outcomes: Restate what was supposed to happen. If this is a sprint retrospective, briefly go over the sprint goals and whether they were achieved. For a project post-mortem, summarize the project’s objectives, timeline, and final outcome. Also review any key data or metrics (e.g., “Project X was delivered 2 weeks late,” or “Sprint velocity dropped by 10%,” or “Incident resolved in 3 hours”) to ground the discussion in facts.
  
  
• What Went Well: Have the team identify and discuss the successes. These can be anything that the team wants to celebrate or continue in the future – effective collaboration, hitting a milestone on time, high quality output, etc. It’s important to acknowledge these positives so the team can replicate those practices. Listing “went well” items often boosts morale and balances the conversation before focusing on problems​.
  
  
• Challenges & What Didn’t Work: Invite the team to share what problems or pain points they encountered. This could be issues like unclear requirements, communication breakdowns, timeline slips, bugs in production, or any hurdle that impeded progress. For each item, dig a little deeper into root causes – why did it happen? Was it avoidable, or what contributed to it? The aim is to understand, not blame: e.g., “We missed the deadline because we under-estimated the testing phase and lacked a backup QA.” By analyzing root causes, the team can pinpoint process changes to prevent future recurrences.
  
  
• Brainstorm & Prioritize Solutions: For each major issue identified, brainstorm potential solutions or improvements. Encourage everyone to contribute ideas on how the team could work differently to avoid that issue or handle it better next time. This might yield multiple ideas – list them out (could use sticky notes or a whiteboard if in-person, or a digital board for remote). Then prioritize which changes to implement. The team might vote or agree on the most impactful improvements to pursue first​. For example, “Idea: implement a code-freeze 2 days before release to allow more testing – Team agrees to adopt this.”
  
  
• Action Items (Improvement Plan): Turn the top improvement ideas into concrete action items. Assign an owner to each action. For instance, “Alice will create a QA checklist template by next sprint,” or “Bob will set up a brief daily sync during crunch time on the next project.” If this is a project post-mortem, actions might include documentation updates or sharing lessons with other teams (“Write a post-mortem report and schedule a knowledge sharing session”). Make sure each action is clear and time-bound. In some cases, there may also be follow-up tasks like addressing any remaining open issues from the project. Each attendee might leave with a task to help address issues raised​.
  
  
• Lessons Learned & Closing: Sum up the key takeaways from the meeting. It can be helpful to explicitly list 2–3 “lessons learned” – e.g., “We learned we need more realistic sprint planning when half the team is on vacation,” or “Early client demos help catch requirement misunderstandings.” Thank the team for their honesty and contributions. End on an optimistic note that the next project or sprint will benefit from these insights. Also, if applicable, let the team know how these lessons will be shared (e.g., stored in a knowledge base or reported to stakeholders).
  
  

‍

Agenda for Cross-Functional Collaboration Meetings

Cross-function meetings should be inclusive and transparent, making it easy for folks to speak up and understand each other. No heavy jargon that leaves half the room lost.

‍

One best practice is to start by clarifying the common goal and each team’s role. Everyone loves knowing how their piece fits into the puzzle. When you get communication right and keep an open mind, these meetings can break down silos and spark some awesome ideas.

‍

• Goals & Overall Progress: Open with a reminder of the shared objectives of the group or project. Review any top-level performance metrics or milestones that concern all teams present (for example, progress on a company OKR that multiple departments contribute to). This provides a unified view and sets the stage for why cross-team collaboration is needed. Keeping everyone aligned on the big-picture goals helps underscore the purpose of the meeting​.
  
  
• Wins & Major Announcements: Celebrate recent successes that resulted from collaboration or that affect all teams. For instance, hitting a project milestone, securing a big client (that involves Sales, Delivery, and Support), or a successful cross-team event. Also share any announcements that all groups should hear, such as organizational changes or new corporate initiatives, so everyone stays informed​.
  
  
• Updates from Each Team: Give each department or functional group represented a chance to provide a brief update. This is like a roundtable: e.g., Engineering shares the status of a product build, Marketing updates on a campaign supporting that product, Sales shares customer feedback that impacts product and marketing, etc. Each update should include recent progress, upcoming plans, and any current roadblocks that others should know about​. By the end of this round, everyone should understand what their counterparts are working on and any issues emerging in each area.
  
  
• Identify Interdependencies & Issues: As teams present, take note of points where one team’s work intersects with another’s. Discuss these interdependencies explicitly. For example, “Marketing’s timeline for the launch depends on Product hitting the feature freeze by June 1st – is that on track?” or “Sales needs support from Engineering on a technical question for a client.” Address any misalignments or conflicts in priorities and adjust plans or expectations as needed. This agenda item is critical for preventing siloed efforts – it’s where the group ensures no team’s plans inadvertently hinder another’s.
  
  
• Collaborative Discussion/Brainstorm: Use some time for open discussion on cross-functional topics that benefit from multiple perspectives. This could be problem-solving (e.g., “How do we improve the hand-off process between Teams A and B?”) or brainstorming a new initiative that would involve several departments. It’s an opportunity to leverage the diverse expertise in the room. Ensure the discussion remains relevant to all parties (side issues concerning only two teams might be flagged and taken offline).
  
  
• Next Steps & Action Items: End by compiling action items that arose during the meeting. Given the collaborative nature, many action items might involve coordination – e.g., “Engineering and Support will meet to refine the integration process,” or “Each team will update the shared project document by next week.” Make clear who owns each follow-up task and any deadlines. Also, recap any decisions made (for example, agreeing on a new process or adjusting a timeline). Confirm the date or trigger for the next cross-functional check-in. A quick summary like “So to wrap up, we decided X, Y, Z and here are the takeaways…” ensures everyone leaves with a consistent understanding.

‍

Example Board Meeting Agenda

Board meetings have a reputation for being formal and high-stakes, and they are–but that doesn’t mean they can’t be engaging. Think of it as telling your company’s story to the people at the top.

‍

Best practices here include solid preparation and sticking to the big picture. But, you’ll also want to foster an open dialog for questions and insights. Keep it respectful and on-point, and you'll find even a serious board meeting can run smoothly and end on a positive note.

‍

• Call to Order & Opening Remarks: The board chair (or meeting leader) formally opens the meeting, noting the start time. A brief welcome may be given, and if any new board members or guests are present, introductions are made. Sometimes the organization’s mission or vision statement is read aloud to ground the meeting (optional, but common in some nonprofits)​. This stage sets a formal tone and ensures everyone is ready to proceed with the official agenda.
  
  
• Approval of Previous Minutes: The board reviews the minutes from the last meeting (usually circulated in advance) and formally approves them, often via a quick vote or unanimous consent. This is a routine item to ensure the record of the last meeting is accurate. Any corrections to the minutes would be discussed and amended here before approval.
  
  
• Executive Reports: Key officers or executives present their reports. Typically, the CEO or Executive Director gives an update on the overall state of the organization, highlighting important developments, acco-mplishments, and challenges since the last meeting. Additionally, a Financial Report is given (often by the CFO or Treasurer), summarizing financial performance, budget status, fundraising, etc.​ There might also be other officer reports (e.g., a Chief Operating Officer on operations, if applicable). These reports inform the board about the organization’s health and progress on strategy. Board members may ask questions or discuss points from the reports.
  
  
• Committee Reports: If the board has committees (such as Audit, Governance, Compensation, etc.), the chair of each committee provides a brief report on their recent activities and any recommendations requiring board action​. For example, the Audit Committee might report on the annual financial audit results, or the Governance Committee might propose a new board member candidate. These reports ensure the full board is aware of work done in smaller groups and tees up any decisions the board needs to make based on committee work.
  
  
• Old Business: The chair leads a review of any unresolved issues from prior meetings that are on the table (“old business”). This includes items that were deferred, requested for follow-up, or not fully resolved previously​. Each item is discussed and ideally concluded (or deferred again if absolutely necessary). For instance, if at the last meeting there was an open question about approving a policy pending more research, this is where that decision is revisited and hopefully finalized.
  
  
• New Business: Introduce new topics or proposals that the board needs to address at this meeting​. New business can span a wide range: approving the next fiscal year’s budget, considering a strategic plan or major project, discussing a partnership or acquisition, reviewing a significant risk or crisis, etc. Each new business item typically has an overview (often presented by a relevant executive or board member), followed by board discussion and decision or resolution. It’s good practice to list these items in the agenda sent out beforehand so board members can prepare.
  
  
• Discussion & Decisions: This isn’t always listed as a separate agenda line, but effectively, for both old and new business, the board will discuss and then move to decide or vote as needed. Ensure time is allocated for thorough discussion on critical issues. For decisions that require a formal vote (e.g., “Motion to approve the 2025 budget”), follow proper procedure: a motion is made and seconded, discussion is held, and then a vote is taken and recorded. The chair should clarify the outcome of each decision for the minutes.
  
  
• Other Business and Announcements: An open slot for any additional items or last-minute announcements. Board members can raise minor items or reminders here. For example, announcing dates for an upcoming board retreat or congratulating the team on a recent award (this might also include any ceremonial actions like recognizing a retiring board member). Essentially, it’s a catch-all before closing.
  
  
• Adjournment: The board chair formally closes the meeting and notes the end time. Often the next meeting date (if not already scheduled) is confirmed here as well. Board meetings often end with a confirmation of any follow-up items – e.g., “We have our action items set and we’ll see everyone at the next quarterly meeting on [date]. Meeting adjourned.”
  
  

Board meetings are typically formal in nature. It’s crucial to circulate an agenda and relevant documents well in advance (many boards require materials a week or more prior) so that board members can review items like financials or proposals before the meeting. Time management matters because there’s often a lot to cover; assign rough time blocks for each major section and stick to them.

‍

Many boards utilize a consent agenda at the start for routine items (like committee reports that don’t need discussion) to approve them in one go and save time. Additionally, boards may have an executive session – a portion of the meeting where non-board members (and sometimes management) are asked to leave so that the board can discuss sensitive matters privately (often at the end of the meeting). Always follow any bylaws or governance policies regarding quorum and voting procedures. Document decisions clearly in the minutes. Board meetings commonly run anywhere from 1 to 3 hours depending on frequency (monthly vs. quarterly) and agenda complexity, so plan accordingly with breaks if needed.

‍

Town Halls or All-Hands Meeting Agenda

Town halls (or all-hands meetings) are the big team huddles where everyone from the CEO to the newest hire comes together. The atmosphere is usually upbeat and inclusive. You want people to feel comfortable and even excited about speaking up or asking questions.

‍

Use this meeting to celebrate wins, share candid updates, and reinforce the big-picture vision, all while keeping the tone down-to-earth. When done right, a town hall makes everyone feel in the loop and pumped about where the company is headed.

‍

• Introduction & Welcome: A senior leader (often the CEO or department head) kicks off the town hall with a warm welcome to all employees. They should briefly state the purpose of the meeting (e.g., “update everyone on our progress and take your questions”) and outline the agenda. This introduction sets a positive, inclusive tone and grabs everyone’s attention from the start.
  
  
• Company Updates: Leadership presents key updates about the business. This segment can include a variety of sub-topics: an overview of recent performance, progress on big projects or OKRs, noteworthy client wins, product launches, market expansion plans, or changes in company strategy. Essentially, it answers “Here’s where we stand and where we’re going.” Visual slides or charts are useful to convey metrics or progress. Keep the messaging high-level and relevant to the whole audience, avoiding overly technical details.
  
  
• Department Spotlights (optional): Many all-hands include rotating spotlights where a particular team or department shares a short presentation. For example, Engineering might demo a new feature, or HR might introduce a new training program. This fosters cross-department visibility and allows employees to appreciate what their colleagues are working on. If included, limit each spotlight to a few minutes to maintain pace.
  
  
• Achievements and Shout-outs: Take time to recognize outstanding work and milestones. This could mean highlighting top performers, project successes, new client acquisitions, or any achievement that deserves company-wide applause​. Some companies have an “employee of the month” or give kudos to teams that hit targets. Celebrating wins publicly boosts morale and reinforces a culture of recognition. It’s also common to acknowledge new hires or promotions during this segment, welcoming new team members to the whole company.
  
  
• Announcements & News: Share any general announcements that affect everyone. This might include policy updates (e.g., new remote work guidelines), benefit changes, upcoming company events, office relocations, etc. Keeping everyone informed of such news at the same time prevents misinformation. If there are any big organizational changes (leadership changes, reorganizations), the town hall is a good forum to explain them directly.
  
  
• Q&A Session: Open the floor (or the chat, for virtual meetings) for questions from employees​. Encourage people to ask about anything on their minds – it could relate to the updates given or other topics. Often, teams use a moderator or a tool to gather questions (some even collect questions anonymously ahead of time). Leaders then respond to these questions live. This segment is crucial for transparency and employee engagement; it allows leadership to address concerns, clarify doubts, and hear feedback. Allocate sufficient time for Q&A – in many town halls, this can be 15 minutes or more, depending on frequency of the meetings.
  
  
• Closing Remarks: The leader hosting the meeting thanks everyone for attending and reiterates any core messages or takeaways (e.g., “We have great momentum going into next quarter, let’s keep it up”). They might also remind employees of any actions (like filling out a feedback survey about the town hall, or upcoming deadlines for internal initiatives). End on an encouraging note – perhaps a motivational comment or re-emphasizing the vision – to leave employees with a sense of unity and purpose. If appropriate, mention when the next town hall will be, especially if they’re on a regular cadence.

‍

‍