How to write meeting notes that make reporting easier
A simple method for meeting notes NGO teams can use: what to record, a five-part template, and how good notes turn into faster, stronger reports.
Short answer
Good meeting notes record decisions, actions, owners and deadlines, not every word said. Use the same short template for every meeting: purpose, attendees, key points, decisions, and actions with a named owner and a date. Share the notes within 24 hours. When notes follow one format, writing a monthly or donor report becomes a matter of collecting what is already there.
Key points
- Write down decisions and actions, not a transcript.
- Every action needs one owner and one deadline.
- Use the same five-part template for every meeting.
- Share notes within 24 hours, while people still remember.
- Tag points that belong in a report, so reporting is faster later.
Why meeting notes matter for reporting
Most project reports are written at the end of a month or quarter, from memory and scattered messages. Facts get lost. Dates become vague. A decision that changed the work plan is forgotten until a donor asks why an activity moved.
Meeting notes fix this, if they are written well. They are the first draft of your reporting record. Each coordination meeting, partner call or field review produces facts a report needs: what happened, what was decided, what changed and who is responsible. When those facts are written down the same day, in the same format, reporting becomes a job of collecting and organising, not remembering.
What should meeting notes include?
Good notes are short. They do not try to capture every sentence. They capture what the team will need later.
| Part | What to write | Example |
|---|---|---|
| Purpose | One line on why the meeting happened | Monthly partner review, Township A |
| Attendees | Names and organisations, plus who was absent | 6 staff from two partners; finance officer absent |
| Key points | Short bullets on facts shared | Distribution in Village B delayed one week by road access |
| Decisions | What the group agreed | Move hygiene kit distribution to 20 March |
| Actions | Task, owner, deadline | Update work plan — Ko Aung — 15 March |
The decisions and actions are the most important parts. If you only have time to write two things, write those.
A five-step method for every meeting
- Prepare the template before the meeting. Copy the five headings into a new document and fill in the purpose and attendees. This takes two minutes and keeps the notes consistent.
- Listen for decisions. When the group agrees on something, write it as a full sentence: "The team decided to…". If a decision is unclear, ask the chair to confirm it before moving on.
- Turn every task into an action line. An action has three parts: what, who and when. "Follow up with the partner" is not an action. "Ma Hnin calls the partner about the delayed report by Friday" is.
- Mark report material. Add a simple tag, such as [REPORT], next to points that will matter in the monthly or donor report: changes to activities, risks, achievements and lessons.
- Share within 24 hours. Send the notes to everyone who attended and to anyone who owns an action. Ask people to correct mistakes within two days. After that, the notes stand as the record.
How do good notes make reports faster?
When every meeting follows the same template, you can build a report by searching your notes. Look for the [REPORT] tags and the decisions for the period. You will find:
- Progress: what activities happened and when.
- Changes: what moved, and the reason recorded at the time.
- Risks and issues: problems the team discussed and how it responded.
- Lessons: what the team said it would do differently.
This gives you facts with dates, which makes your reports more credible. A sentence such as "The distribution moved to 20 March after the partner reported road access problems on 8 March" builds more trust than "Some activities were delayed due to the context." Our guide on writing a clear project report shows how to turn these facts into a report structure.
Common mistakes to avoid
- Writing a transcript. Long notes hide the decisions. Readers skip them.
- Actions without owners. "Team to follow up" means nobody follows up.
- Notes that never leave the laptop. Notes that are not shared cannot be corrected or used.
- Different formats every time. Searching becomes slow and facts go missing.
- Sensitive details in shared notes. In insecure contexts, do not record names of community members, exact locations or security details in notes that are widely shared. Keep them in a restricted file, or leave them out.
Making it a team habit
A method only works if the whole team uses it. Agree on the template at your next team meeting and save it in a shared folder. Rotate the note-taker role, so everyone learns it. Review action lines at the start of each meeting: this shows that notes are used, which motivates people to write them well. Over a few months, you will build a searchable record of your project that supports reporting, handovers and evaluations. For the next step, read minutes and action points in five steps.
How EMPO can help
EMPO is a trusted, Myanmar-based training and consultancy provider and one of the country's leading names in practical NGO training, with 1,200+ people trained and 15 partner organisations. We run report writing training for NGO and CSO teams, online over Zoom or in person in Yangon and across Myanmar, in English and Burmese. Teams can also commission training designed for their own reporting needs. See our training services or contact us to plan a session.
Questions people ask
Who should take the notes?
Choose a note taker before the meeting starts, and rotate the role. The chair should not take notes, because running the discussion and writing at the same time leads to gaps.
Should meeting notes be in English or Burmese?
Use the language the team works in. If a donor report must be in English, keep the decisions and actions in English, even if the discussion happened in Burmese, so they can be copied into the report later.
How long should meeting notes be?
For a one-hour meeting, one page is usually enough. If notes run longer, check whether they record discussion instead of decisions.
