Demo rezervasyonu yapın Speak AI'yı ücretsiz deneyin. Giriş

Cross-Departmental Meeting Agenda Template (60-Minute Collaboration Meeting)

Use this cross-departmental meeting agenda when two or more departments depend on each other to ship something. It runs 60 minutes, puts handoffs and blockers on the table early, and ends with one owner per decision.

Demo rezervasyonu yapınSpeak AI'yı ücretsiz deneyin.

Used by 300,000+ individuals and teams. Free trial, no credit card required.

Cross-departmental meeting agenda: the template

Eight timed items for a departmental or collaboration meeting. Each has an owner and an example entry, so you can swap in your own teams and dates.

Cross-departmental meeting agenda

Total time: 60 minutes

  • Shared goal: [Goal all departments are working toward]
  • Date and time: [Date, start time]
  • Location or link: [Room or video link]
  • Facilitator: [Name, from a neutral department if possible]
  • Note taker: [Name]
  • Departments present: [Product, Sales, Support, Finance, etc.]
  • Pre-read: [Link to shared tracker or status doc]
  1. 0:005 min
    Shared goal and what each team owns

    Restate the goal everyone is working toward in one sentence, then name what each department is accountable for.

    ExampleGoal: launch the new onboarding flow on 14 June. Product builds, Support writes the help articles, Sales briefs customers.
    SahipFacilitator
  2. 0:0510 min
    Status by department

    Two minutes each. Done since last meeting, on track or at risk, and one number. No slides.

    ExampleSupport: 6 of 9 help articles drafted, at risk because screenshots need the final UI.
    SahipEach department lead
  3. 0:1510 min
    Handoffs and dependencies

    List what one team is waiting on from another. Each dependency gets a giver, a receiver and a date.

    ExampleProduct to Support: final UI build by 3 June. Support to Sales: customer FAQ by 8 June.
    SahipFacilitator
  4. 0:2510 min
    Blockers and conflicting priorities

    Surface where one team's priority collides with another's. Decide now or name who decides and by when.

    ExampleEngineering and Support both need the same two designers in week 2. Decision owner: VP Product, by Friday.
    SahipDepartment leads
  5. 0:3510 min
    Decisions needed

    Take only the decisions that cannot be settled between two teams. Record the decision and the reason.

    ExampleApprove a one week delay to add the migration banner. Decided: yes, launch moves to 21 June.
    SahipSponsor or senior lead
  6. 0:455 min
    Shared metrics check

    Review the two or three numbers every department agreed to watch, against target.

    ExampleActivation rate 31% vs 35% target. Support tickets on onboarding down 12%.
    SahipOperations lead
  7. 0:505 min
    Communication plan

    Agree what gets announced, to whom, and who sends it, so teams are not hearing news from each other second hand.

    ExampleSales hears the final date from Product on Monday, before the customer email goes out.
    SahipFacilitator
  8. 0:555 min
    Actions and next meeting

    Read back every action with its owner and date. Confirm the next meeting date and whether it can be shorter.

    Example7 actions, all with owners. Next meeting in two weeks, 45 minutes.
    SahipNote taker

İşlem Öğeleri

Task Sahip Due
Deliver final UI build to Support for screenshots Product lead 3 June
Resolve designer capacity conflict for week 2 VP Product Friday
Send the revised launch date to all department leads Facilitator Same day
Update the shared tracker with new dependencies Operations lead Next working day
Copy as textDownload .txtPrint or save as PDF

Copy-ready agenda text

Paste this into Google Docs, Word, Notion or an email. Replace anything in [brackets].

Copy the text
CROSS-DEPARTMENTAL MEETING AGENDA

Shared goal: [Goal all departments are working toward]
Date and time: [Date, start time]
Location or link: [Room or video link]
Facilitator: [Name, from a neutral department if possible]
Note taker: [Name]
Departments present: [Product, Sales, Support, Finance, etc.]
Pre-read: [Link to shared tracker or status doc]

TIMED AGENDA (60 minutes)

0:00  Shared goal and what each team owns (5 min) | Owner: Facilitator
      Restate the goal everyone is working toward in one sentence, then name what each department is accountable for.
0:05  Status by department (10 min) | Owner: Each department lead
      Two minutes each. Done since last meeting, on track or at risk, and one number. No slides.
0:15  Handoffs and dependencies (10 min) | Owner: Facilitator
      List what one team is waiting on from another. Each dependency gets a giver, a receiver and a date.
0:25  Blockers and conflicting priorities (10 min) | Owner: Department leads
      Surface where one team's priority collides with another's. Decide now or name who decides and by when.
0:35  Decisions needed (10 min) | Owner: Sponsor or senior lead
      Take only the decisions that cannot be settled between two teams. Record the decision and the reason.
0:45  Shared metrics check (5 min) | Owner: Operations lead
      Review the two or three numbers every department agreed to watch, against target.
0:50  Communication plan (5 min) | Owner: Facilitator
      Agree what gets announced, to whom, and who sends it, so teams are not hearing news from each other second hand.
0:55  Actions and next meeting (5 min) | Owner: Note taker
      Read back every action with its owner and date. Confirm the next meeting date and whether it can be shorter.

ACTION ITEMS
Task | Owner | Due
[Task] | [Name] | [Date]

How to run this meeting

  1. Pick a facilitator from outside the biggest team

    When the loudest department also runs the meeting, the others stop pushing back. A neutral facilitator keeps the airtime even and the agenda on time.

  2. Use one shared tracker, not five status decks

    Ask every department to update the same tracker before the meeting. Spend the hour on the red items, not on reading out what is already written.

  3. Turn every dependency into a pair

    A dependency without a giver, a receiver and a date is only a worry. Write each one as 'Team A gives X to Team B by Y' and read it back.

  4. Escalate in the room, not afterwards

    If two leads cannot agree in five minutes, name the person who decides and the day they will decide. Do not let a conflict roll into next meeting.

Keep every department's commitments on the record

In a cross-departmental meeting, the risk is that each team remembers a different version of what was agreed. Speak AI records the call and gives everyone the same transcript, summary and action list.

  • Record the meeting on Zoom, Google Meet or Microsoft Teams, or upload the file afterwards.
  • Get a transcript with speakers labelled, so you can check which department committed to which date.
  • Get an automatic summary of status, blockers and decisions for the whole group.
  • Get action items with owners and due dates pulled out, ready to paste into your shared tracker.

See how the Yapay zekâ destekli toplantı asistanı ve yapay zeka not tutucu work, or start with a free account.

Demo rezervasyonu yapınSpeak AI'yı ücretsiz deneyin.

Sıkça sorulan sorular

What should be included in a good agenda for a departmental meeting?

The shared goal, a short status from each department, handoffs and dependencies, blockers, decisions needed, shared metrics, and a read-back of actions. Each item needs an owner and a time limit so one team does not take the hour.

What are 5 things you would include in a meeting agenda?

The purpose, a list of topics in priority order, a time limit and an owner for each topic, any pre-reading, and a slot at the end for actions and next steps. Add attendees and the date and place.

What are the 5 P's of a meeting agenda?

Purpose, product (the outcome you want), participants, process (how the time is used) and practicalities (date, place, link, pre-reading). Writing all five on the invite means people arrive knowing why they are there.

What are some examples of good meeting agendas?

A good agenda is timed, names an owner per item, and states the decision needed. For example: 'Handoffs, 10 min, Facilitator: Product gives Support the final UI by 3 June.' This template has eight such items to copy.

How often should a cross-departmental meeting happen?

Every one to two weeks while a joint project is active, then monthly once it is stable. Shorten it to 30 or 45 minutes when most items are green. Cancel it if the shared tracker already answers every question.

Related templates and tools

Cross Functional Team Meeting Notes TemplateAlignment Meeting Agenda TemplateChange Management Meeting Agenda TemplateAll meeting templatesYapay Zeka Toplantı AsistanıAI Notetaker

Run the meeting, let Speak AI keep every team's commitments

Book a demo to see how Speak AI turns a cross-team call into a summary, decisions and action items, or try it free on your next meeting.

Demo rezervasyonu yapınSpeak AI'yı ücretsiz deneyin.