Build a Meeting Agenda and Action Register That Makes Decisions Clear

1. Gather these details

• Choose one meeting with a concrete desired result, such as agreeing a delivery date. Write the question the session must answer instead of a broad subject heading.
• Set a duration and use no more than three main discussion items initially. Identify the information required to decide each item before inviting anyone to attend.
• Use short names or role labels for action owners. The register does not need everyone’s phone number, email address or a separate participant account.
• Define statuses such as not started, in progress, waiting for another party and complete. A deadline passing must never be treated as evidence of completion.
• Decide how you will manually send the summary afterwards and confirm that owners understand their tasks. The tool organises decisions rather than communicating them for you.

2. Define how the project works

1. Start with the decision needed

Write the meeting’s purpose in one sentence and include only agenda items needed to achieve it. Give each item an expected duration and a question or decision, rather than a vague heading such as project discussion. When essential information is missing, record who must supply it before the session. Time allocation provides a reason to defer a new topic instead of extending the meeting indefinitely and helps participants prepare useful information.

2. Separate decisions from conversation

During the meeting, capture concise agreements rather than transcribing every remark. A decision states what will happen; an action identifies the work needed to make it happen. If no agreement is reached, mark the decision pending with the missing information and the next review point. Do not present one person’s suggestion as a final group agreement simply because it appears in the register. Record the actual outcome of the discussion.

3. Give each action an owner and date

For every action, specify one accountable person or clear role, an observable result and a date. Follow up is vague; send the list of missing items by Monday is actionable. Mention helpers in notes while keeping responsibility clear. Before the session ends, read back the actions or review them in the conversation. That short check prevents people leaving with different interpretations of who will do what and when.

4. Review completion using a short reference

Send a summary through your usual channel after the meeting and record when you sent it. At the next review, update progress from what you have checked, using a brief delivery or confirmation reference. An overdue action does not complete itself, and silence from an owner does not confirm agreement. Preserve the original decision and note any changed scope or date so the record explains why execution differed from the initial plan.

3. Work through an example

5 + 10 + 10 + 5 = 30 minutes. Adding an eight-minute item should produce 38 minutes and a warning that the planned meeting duration is exceeded.

4. Set up your account and start the build

1. Use your account or register.Visit www.gammal.tech/join. New account activation takes 1–10 days. Use a National ID from a country whose citizenship you hold; the official account guide explains the limited exceptions for Egyptian citizens. Submit identity documents only through the official registration process.
2. Activate the WhatsApp subscription.After approval, open my.gammal.tech and add EGP 200 to your wallet, or use sufficient existing funds. Activate the monthly WhatsApp subscription in your account and check that it is active. Funding the wallet alone does not activate it. This subscription covers light personal use; website creation is charged separately.
3. Open the building conversation.Message +201033998844 and send the following command by itself, including the required square brackets. Wait for confirmation of build mode:

   [mode: build]

   [mode: web] is an alternative for the same mode; you only need one command.
4. Send the request in the next section.Replace its placeholders and ask for exactly one page using an available name of at least three characters. Before execution, request an itemised quote separating the one-time build fee, EGP 100 for the first month of standard hosting and any additional usage. Ask how changes beyond the agreed scope are charged.
5. Check the total and approve the build.Once you understand the quote, return to your account and add any missing funds. Return to WhatsApp and confirm the scope and price. Some simple sites take minutes; requirements and revisions affect timing. Open the resulting address and run this guide’s acceptance checks.
6. Record the renewal date.MeNooN hosting renews manually: select the duration and confirm payment before expiry. Leaving funds in your wallet does not renew it automatically. Send [exit], including brackets, when you finish the building conversation.

Budget: quoted build fee + EGP 100 hosting + EGP 200 for one WhatsApp month if it is not already active, plus agreed usage. Twelve months of standard hosting cost EGP 1,200; adding one WhatsApp month makes EGP 1,400 before build and usage fees. Keeping WhatsApp active for further months costs separately.

For private saving, ask the builder to connect Gammal Tech sign-in and register the correct website address in your project. If requested, open the developer area, select the project or create it under the agreed quote, and copy its ID; never guess it. Check that the final site address is registered before testing saves. Each account has its own data. Test save and reload, then ask a trusted person using their own genuine account to check that your records are not visible. Do not share sign-in codes or create another account for yourself. User-data storage is free, with a 1 MB limit per user, so keep short text records rather than files or photographs. Paid sign-in codes may need project funds after the free allowance: fund your wallet, then transfer a usage budget to the project in the developer area. Sign-in does not automatically disclose identity or contact details to the site owner.

Open the developer area

Service steps and prices reviewed on 18 October 2026. Check the amount shown in your account before paying. WhatsApp steps · Hosting and renewal

5. Adapt and send this request

Replace every bracketed placeholder with your real details. Copy this request after the assistant confirms build mode. Do not publish the illustrative figures as your own.

Build a private one-page meeting agenda and action register named [tool name]. Use Gammal Tech login and separate per-user storage. I am the single coordinator entering records; do not invent a shared team database, calendar invitations or automatic notifications. Each meeting needs a title, purpose, date, duration and agenda items with expected minutes and a question to resolve. Add the item durations and compare the sum with the meeting length. Keep decisions separate from actions. Each action needs an observable output, short owner label, date, status and completion reference I enter manually. Use not started, in progress, waiting for another party and complete; a passed date must not imply completion. Allow pending decisions with reasons and date changes with explanatory notes while preserving the original wording. Provide a summary I can copy myself and a view of open actions for the next meeting. Do not collect sensitive participant details or send messages. Before building, quote the one-time cost separately from the first month of standard one-page hosting at EGP 100, disclose additional usage costs and wait for approval.

6. Test the result before relying on it

1. Set thirty minutes and agenda items of five, ten, ten and five minutes.Expected result: The total is thirty of thirty. Adding eight minutes changes it to thirty-eight and flags the excess.
2. Create an action without an owner or date and try to mark it ready for assignment.Expected result: The tool requests the missing details or clearly retains an incomplete draft rather than implying a complete assignment.
3. Give a not-started action a date in the past and inspect the review list.Expected result: It remains open and is shown as overdue. The date passing does not make it complete.
4. Record a decision, change its action date with a reason, save and sign in again.Expected result: The decision, action and change note remain available privately; signed-out visitors cannot see the records.

7. Use the project during its first week

Use the tool for one meeting during the first week and compare the decisions reached with the actual time spent. Avoid adding a field for every possible detail. After manually sending the summary, ask owners whether the task and date are clear and record corrections before monitoring progress. Begin the next meeting with open actions instead of retelling the previous conversation. If a session produces neither decisions nor actions, consider whether a short information message would have served the purpose better. The record should help improve meetings, not merely document them.

Your first weekly review note

Meeting review note: [website link]. We agreed [decision]. The next action is [output], owned by [role], due [date]. [Issue] remains pending until [information] arrives, and I will manually send the summary for confirmation.

Questions about this project

Can the whole team edit this record?

Not in this project. One coordinator maintains it privately and shares an appropriate summary outside the tool. Multi-user access and permissions require a separate verified design.

How is a decision different from an action?

A decision states an agreement, such as choosing a launch date. An action assigns work supporting that decision, such as completing a checklist by a named date.

Do I need to record every remark?

No. Capture the decision, brief reason, action, owner and date. A transcript can make review harder and retain information unnecessary to achieve the meeting’s purpose.