# Basic Ad-hoc/Tactical Meeting Agenda

For a Google doc version of this agenda you can easily copy into a new doc, click [here](https://docs.google.com/document/d/13GgRiidIxEiIi3RRQ_xbT1Jz_8UGxj0W4RP4NTFOsZs/edit).

{% hint style="info" %}
The [Before-Action](/for-organizers/model-agendas-and-activities/before-action-review.md) and [After-Action](/for-organizers/model-agendas-and-activities/after-action-review.md) Review agendas are designed for a single task, like hosting an event. This agenda is better suited for a fixed team that repeatedly collaborates on similar tasks, though such a team could still use BARs and AARs for a specific project.
{% endhint %}

* Clarify the roles of each person present, including facilitator.
* Silent meditation proportional to meeting length.
* Check-in round.
* [*Contemplation of why we are here*](/for-organizers/model-agendas-and-activities/contemplation-of-why-we-are-here.md) *(optional).*
* State purpose of meeting: *\[purpose]*
* Update on action items, projects, and metrics as needed.
* Build agenda
  * *\[list agenda items, or use the table below]*
* [Process agenda items](https://static1.squarespace.com/static/5d1239a79c02150001db74d4/t/5e263afd3779916755048268/1579563773750/Tactical-Card_V.5_09-24-19.pdf)
* Check-out round.

#### Agenda Table

| **Agenda Item**             | **Name & role bringing it** | **Time (best guess in minutes)** | <p><strong>Type</strong></p><p>1. Request of someone else to do something</p><p>2. Ask for information or help making a decision</p><p>3.  Share information or give input into someone else’s decision</p><p>4.  Governance</p> | <p><strong>Priority</strong> </p><p>1. Mission critical: something really bad will happen if this isn’t processed today</p><p>2. There’s a good reason why this is urgent</p><p>3. Can go after mission critical & urgent stuff</p><p>4. Not time-sensitive<br></p> |
| --------------------------- | --------------------------- | -------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Example: Marketing strategy | Arjun                       | 10                               | 2                                                                                                                                                                                                                                | 3                                                                                                                                                                                                                                                                   |
|                             |                             |                                  |                                                                                                                                                                                                                                  |                                                                                                                                                                                                                                                                     |


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://handbook.proanimal.org/for-organizers/model-agendas-and-activities/basic-ad-hoc-tactical-meeting-agenda.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.