Chama Meeting Action Review: 7 Clear Steps to Close Tasks
A chama meeting action review turns the last meeting’s promises into a short, useful conversation about progress. Instead of reading every minute again, officials check what was assigned, what has happened, and what support is still needed. The aim is to leave each action with an accurate status and an agreed next step.
For Kenyan groups, this routine can prevent the same unfinished item from appearing on every agenda. This guide explains how to prepare a chama meeting action review, discuss delays fairly, record completion evidence, and carry forward genuine unfinished work. The examples use fictional group activities and can be adapted to your own procedures.

1. Start your chama meeting action review with the original decision
An action should be traceable to a decision, not to someone’s memory of the discussion. Open the approved minutes and identify the instruction that created the task. Record the meeting date, agenda item, expected result, and person responsible. If the wording is unclear, flag the uncertainty instead of silently rewriting the decision.
For example, “check the venue” could mean requesting a quotation, visiting the room, confirming access, or making a booking. These are different tasks. A useful action statement might say, “Ask the venue manager for written confirmation of room capacity and available dates before the next committee meeting.” That wording makes the expected evidence easier to recognise.
Keep the original decision separate from later progress notes. The decision explains what the group authorised; the notes explain what happened afterwards. When the scope changes, record the later instruction and its date. This preserves a clear sequence without making the first decision appear more detailed than it really was.
For a short reference that isolates one decision, see the TAS guide to preparing a chama minutes extract. Bring the relevant extract into the review pack rather than circulating unrelated member information.
2. Give every task one accountable owner
Several members may help with an activity, but someone needs to coordinate the update. Name one accountable owner and list supporting people separately. This avoids the familiar situation in which everyone assumed another member would contact the supplier, prepare the document, or report a problem.
Ask the owner to confirm that they understood the task and accepted the deadline. Assignment alone does not prove agreement, especially when a member was absent. If acceptance has not been recorded, mark it as awaiting confirmation. The secretary can then arrange a direct check before treating the task as overdue.
An owner should not become a permanent bottleneck. Agree how the group will transfer responsibility if someone becomes unavailable. The handover note should identify work already completed, outstanding questions, relevant files, and the new owner. Preserve the earlier updates so that the replacement does not need to start from nothing.
A chama meeting action review works best when responsibility is specific but discussion remains respectful. Ask what is needed to finish the work. Avoid assigning blame based only on a missing update, because the underlying task may already be complete or waiting on a third party.
3. Use statuses that describe actual progress
Choose a small set of statuses that everyone understands. A practical list is not started, in progress, waiting, ready for review, and closed. Add cancelled only when the group has agreed that the work is no longer needed. Too many labels can make a simple tracker harder to maintain.
Define waiting carefully. An action can be waiting for a quotation, clarification, approval, or information from another member. Record what is missing and who can provide it. “Waiting” without an explanation is not a useful update, because nobody knows what would allow progress to restart.
Ready for review means the owner believes the work is complete but another person must check the result. Closed means the agreed completion check has happened. Separating these stages is helpful for tasks involving documents, venue arrangements, or member communications, where producing an item and approving it are different responsibilities.
During the chama meeting action review, update the status only after hearing the evidence. A member saying “almost done” may still have a significant unresolved step. Ask for that step in plain language and record it. The tracker should describe actual work.
4. Check chama meeting action review evidence
Completion evidence should be proportionate. A meeting notice may need a dated copy and a record of the agreed distribution method. A venue inquiry may need the supplier’s reply. A revised attendance form may need a final version checked by the secretary. Avoid collecting documents that do not help establish the result.
Use a link or reference to the evidence where possible, rather than copying long messages into the action list. Give the file a clear name and keep it in the appropriate folder. If the evidence contains personal information, share only what the reviewers need to see for this decision.
A simple completion test is to compare the result with the original action statement. If the task was to obtain three available dates, a reply offering one date is partial progress. If the task was to circulate an approved agenda, an unapproved draft does not yet satisfy the instruction.
Use the chama meeting attachment list to check that supporting documents are included in the pack. This is particularly useful when different owners submit their evidence at different times.
5. Discuss overdue actions before choosing new dates
A missed deadline needs an explanation and a realistic response. Ask whether the obstacle was unclear scope, limited availability, missing information, or a dependency outside the owner’s control. Different causes require different solutions. Replacing the date without addressing the obstacle often creates another missed deadline.
Suppose an owner was asked to compare meeting rooms but has only received one quotation. The next step may be to contact two alternative venues, reduce the shortlist, or ask the committee whether the available option is sufficient. The owner should not invent additional quotations simply to close the action.
Record the reason for any revised deadline and who agreed to it. Keep the original due date visible in the history. That allows the group to learn whether tasks are consistently underestimated, while avoiding the misleading impression that all work was completed on the first schedule.
Reserve meeting time for decisions that need the group. Routine progress updates can be gathered before the session. The chama meeting timekeeper guide can help the chair protect time for unresolved actions without rushing members through important questions.
6. Record the chama meeting action review in a compact register
Use one row per action. Useful fields include action reference, decision date, task description, owner, due date, status, latest update, evidence reference, and next review date. A separate closure field can record who accepted the result and when. Keep the wording short enough to scan during a meeting.
For a fictional community event, action A01 might be “confirm room availability,” owned by the secretary. Its latest update could read, “Two dates received; committee to choose one.” The status is waiting for decision, not closed. The next step is a committee choice rather than another request to the venue.
Action A02 might be “prepare the attendance sheet,” owned by the assistant secretary. If the final document has been checked and filed, it can be closed with a reference to that version. These examples show why status, evidence, and next step should be separate fields.
Where an action concerns shared equipment, connect it to the chama equipment loan register. The action list records what needs doing; the equipment register records the item’s custody and return. Neither document needs to duplicate every field from the other.
7. Close the loop after the meeting
Send owners a concise summary of the actions that affect them. Include the agreed task, due date, any changed scope, and the next check. Ask them to flag mistakes promptly. This gives members who attended and those who were absent a consistent record of what they are expected to do.
Do not circulate an entire action register automatically if it contains information that some recipients should not receive. Prepare a relevant extract or use the group’s approved access arrangements. Clear communication includes controlling the audience, not just making the text easier to read.
At the next chama meeting action review, begin with the carried-forward items and newly assigned tasks. Keep closed items accessible in the history, but do not spend meeting time reopening them without a reason. A new concern about a completed task can become a new action linked to the original reference.
Review the process itself occasionally. If every item remains in progress for months, the actions may be too broad. Split a large activity into observable steps, each with a useful result. This makes progress easier to verify without turning the register into a list of trivial daily movements.
For a longer activity, agree an intermediate checkpoint before the final deadline. An owner arranging an event might first confirm the venue options, then present the chosen arrangement for review. These checkpoints help the committee notice obstacles early without asking for constant messages. Keep each checkpoint connected to the original action reference, so that it remains clear which overall task it supports. During the chama meeting action review, ask whether the next checkpoint is still realistic and whether another decision is needed. Record any dependency explicitly, including who must respond. This gives the owner a practical route forward and helps the group distinguish useful monitoring from unnecessary repetition during the next meeting.
Chama meeting action review preparation checklist
Before the meeting, collect owner updates, check references, and identify decisions needed. Highlight missing evidence separately from missed work. Prepare a short list of items that need discussion, rather than reading every unchanged entry aloud. Agree who will make updates while the meeting is in progress.
After the meeting, check that revised dates, new owners, cancellations, and closures have been recorded consistently. Save the final review version and tell members where the approved record is kept. An orderly filing habit makes the next review faster and reduces disagreement about what was previously agreed.
If you are testing a digital workflow, start with fictional tasks. The chama software demo data guide explains how to avoid using live member records in a demonstration. Test the complete sequence from assignment to closure before moving your routine into a new tool.
Chama meeting action review questions
Should every action be discussed at every meeting?
Not necessarily. Ask owners for updates before the meeting, then prioritise overdue work, blocked tasks, proposed closures, and decisions requiring the group. Members should still be able to inspect the relevant register through the agreed process. Efficient review should not mean hiding unresolved work.
Who closes tasks after a chama meeting action review?
Use the authority stated in the original decision or the group’s procedures. Some tasks can be checked by the secretary; others need committee or member approval. Record the acceptance clearly. The owner completing the work does not automatically mean that every required review has happened.
Can a cancelled task disappear from the list?
Keep a brief history showing that it was cancelled and why. Deleting it entirely makes later questions harder to answer. A cancelled action is different from a completed action, and the register should preserve that distinction without presenting cancellation as a failure in every case.
Tools and related websites
Explore TAS chama management when considering how to organise your group’s records. Confirm the workflow you need during a demonstration instead of assuming that every example in this guide is an automatic product feature.
Members researching other services can visit Prim, Zama, and Vega. Additional websites included in this resource list are Awasa, Saseni, JAAT, and Dereva. Check each site’s current services and terms independently; these links are not evidence that it provides the action-review workflow described here.
For help discussing your group’s recordkeeping needs, call 0725345345. Bring one anonymised example of an action that is difficult to follow up. A concrete example makes it easier to explain the owner, evidence, and review steps that your chama needs to manage.