Minutes, transcripts,
and the record.

A transcript is what was said. Minutes are what it meant. Teams get into trouble when they treat one as a substitute for the other: a transcript is too long to be a record anyone consults, and minutes without a transcript behind them are one person's memory, dressed up as fact.

Think of them as two layers of the same record. The transcript is the evidence layer: complete, verbatim, searchable, the place you go when someone asks "did we really agree to that?". The minutes are the decision layer: short, structured, and written so a person who missed the meeting understands what happened in two minutes.

What belongs in minutes

Good minutes are boring on purpose. Whatever the meeting type, the same six elements cover almost everything a future reader needs:

Element	What it captures
Header	Meeting name, date, start and end time, location or platform
Attendance	Who was present, who sent apologies, who chaired
Decisions	Each decision as one sentence, with conditions if any
Action items	Task, one owner, one deadline (the next lesson is all about these)
Deferred items	What was raised but pushed to a future meeting
Approval	Who reviewed the minutes and when they were circulated

Notice what is missing: the debate. Recording positions ("Faisal preferred August") is occasionally necessary in formal governance, but as a default it makes minutes long, political, and slow to approve. Record the outcome; let the transcript hold the journey.

What makes a record "official"

A document becomes the official record through process, not formatting. Three steps do the work:

• A named author. Someone specific is responsible for producing the minutes, even when software writes the first draft.
• Review and approval. The chair (or the whole group, at the next meeting) confirms the minutes are accurate. Corrections happen here, once, not forever after.
• Circulation and storage. The approved version goes to a known place, on a known schedule, and later versions never silently replace it.

Do this consistently and your minutes acquire the quality that matters most: people trust them enough to stop re-litigating old decisions.

Arabic minutes have their own conventions

In Arabic-speaking institutions the meeting record, the mahdar ijtima' (محضر اجتماع), is often a formal instrument, not an informal recap. A few conventions to respect:

• Minutes are written in formal Arabic even when the meeting itself mixed dialect and English. The record is more formal than the room.
• The header carries full names and titles, the Hijri or Gregorian date per your institution's practice, and the name of the chair.
• Decisions are often numbered (القرار الأول، القرار الثاني) so later documents can cite them precisely.
• In many government and board settings the mahdar is signed by the chair, and sometimes by all attendees, before it is filed.

If your organization works in both languages, decide up front which language version is authoritative and state it on the document. A bilingual record is a convenience; an ambiguous one is a dispute waiting for a date.