How to write Arabic meeting minutes people can use
A useful Arabic meeting record lets a colleague who missed the call understand what changed and what happens next. It does not need to reproduce every sentence. Start with the recording or your notes, then separate the discussion from the decisions and the work people actually accepted.
Start with a small, repeatable structure
Give the record a clear title, the meeting date, the attendees and its purpose. Follow that with a short summary, decisions, action items and unresolved questions. Keep those headings in the same order every week so a colleague can find their part without reading everything.
A summary explains the conversation. A decision records a choice the group made. An action item records work someone agreed to do. If a topic produced no decision, say that it remains open. Moving a suggestion into the decisions section changes its meaning, even when the wording sounds reasonable.
- Summary: what the team discussed and why it matters.
- Decisions: the agreed choice, any conditions and the reason when it was stated.
- Action items: the deliverable, its owner and the agreed due date.
- Open questions: what still needs an answer and who will seek it.
Keep the meaning when moving from dialect to formal Arabic
People may speak Egyptian, Levantine or Gulf Arabic while the minutes use Modern Standard Arabic. Treat that as an editorial step. Make the writing easier to read without making a tentative statement sound final. Keep the original wording available when a commitment, objection or condition could be disputed.
Preserve names, product labels and English terms in the form your team recognizes. Do not translate an internal project name simply to make the page look uniform. Check numbers, units, currencies and negative statements against the audio; a missing “not” can reverse a decision.
Write one decision and one task as separate entries
Suppose a team reviews a customer proposal. The following invented record keeps the decision separate from the work required to carry it out. The owner and timing are part of this example, not information to infer from an unclear recording.
When a due date was not said, write “not agreed” and ask the owner to confirm it. When the speaker’s identity is uncertain, retain the speaker label until someone verifies the name. A visible gap is more useful than a confident guess that sends work to the wrong colleague.
Review the important claims before sharing
- Replay the source for each decision, deadline and promise. Listen to the preceding and following sentences as well.
- Check whether a later part of the meeting changed the earlier agreement.
- Confirm unfamiliar names and speaker labels. Attending a meeting does not prove which voice belongs to which person.
- Separate the original agreement from changes made after the meeting. Label later clarifications with their date.
- Share the record with the people who need it and ask owners to correct missing or ambiguous commitments.
Atlassian’s DACI decision guide also distinguishes decision roles and recommends recording the final outcome and its context. That is useful when a meeting needs a clear approver, beyond simply naming the person taking notes.
Use Qarar for the first draft, then do the review
Upload an existing audio or video recording to Qarar, or use its browser recorder with participants’ permission. Qarar keeps the transcript in the language spoken and offers summaries, decisions and action items as notes. Its source timestamps give you a place to begin checking the draft against the conversation.
Use the transcript to confirm names and the recording to resolve meaning. If you only have written notes, use the meeting-minutes template below to organize them yourself. The aim is a record colleagues can act on, with uncertainty still visible wherever the meeting left something undecided.