What you will finish
Create a coordinator-owned schedule of shifts, confirmed assignments, gaps and substitutes, with checks against duplicate entries and overlapping commitments.
1. Gather these details
- Choose an activity you are authorised to organise and describe its actual roles. Help out is vague; specify the task, place and participation requirements.
- Prepare start and finish times and the number required for each shift. Allow suitable breaks and travel rather than assuming immediate movement between tasks.
- Use a minimal volunteer reference with permission. Keep ordinary contact channels separate where possible; identity documents and sensitive personal details are unnecessary for basic scheduling.
- Agree how confirmations and cancellations are communicated and who can approve replacements. An old message in a group is not evidence of current availability.
2. Define how the project works
1. Define the shift before adding names
Record the date, times, place, role and number needed, together with information someone needs before agreeing. Greeting visitors is different from moving equipment or photographing participants. Give a clear meeting point and responsible contact. If a task requires training or permission, check that before assigning anyone. The planner organises commitments; it does not give a volunteer qualifications or authorisation that they do not already have.
2. Separate interest from a confirmed commitment
Use interested, confirmation requested, confirmed, declined and substitute states. Only the coordinator changes a state after a clear conversation. Interested people do not fill confirmed capacity, and substitutes do not become confirmed without being asked. Note when an arrangement was last reviewed. If more people volunteer than a shift needs, use the substitute list instead of hiding the surplus or assuming everyone will find useful work on arrival.
3. Check clashes before sharing assignments
Compare a person’s proposed shift with their other assignments, including the transition time you allowed. A clash needs a decision before both are accepted. Display required, confirmed and remaining places for each shift, with substitutes separately. Once reviewed, send each person their own role details through the agreed channel. Confirming an assignment does not require distributing a complete list of everybody else’s names, contact details and availability.
4. Record changes as actual decisions
When someone declines, reopen the place and contact a substitute. Confirm the substitute’s acceptance before closing the gap. After the activity, record actual attendance separately: a confirmed person may not attend. Review unclear instructions and retain only information you still need. This version is run by one coordinator, not by a group sharing a login. A second operator requires a separately designed permission model rather than a shared verification code.
3. Work through an example
| Shift | Required and confirmed | Remaining |
|---|---|---|
| Welcome desk, 10–12 | Three required; two confirmed | One |
| Room setup, 12–1 | Two required; two confirmed | Zero |
| Closing tasks, 1–2 | Two required; one confirmed | One |
| Substitute list | Two without confirmed assignments | Excluded from confirmed totals |
There are seven required assignments, five confirmed assignments and two gaps. Assignments are not necessarily distinct people: one person may cover compatible shifts.
4. Set up your account and start the build
- 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.
- 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.
- 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. - 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.
- 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.
- 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.
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 ONE PAGE on MeNooN for my private volunteer shift planner for [activity]. Use Gammal Tech login and separate per-user storage. This has one responsible coordinator, not a shared account or public list of participants. Store shift date, start, finish, place, role, required capacity and transition time. Use minimal volunteer references with permission and interested, confirmation-requested, confirmed, declined and substitute states. Keep actual attendance separate. Count only confirmed assignments towards capacity. Prevent duplicate people within a shift and overlapping commitments, including transition time. Calculate remaining places and flag excess capacity without silently changing assignments. Do not send messages or promote substitutes automatically; I contact people and record agreed decisions. Do not collect identity documents or sensitive details. Include a clear review view, confirmed deletion and saving that preserves existing records if loading fails. Use explicitly fictional sample references. Before starting, quote the one-time build fee separately from the first month of standard 100 EGP hosting for an available name of at least three characters, plus usage costs. Wait for approval and explain recording a cancellation and confirming a replacement.
6. Test the result before relying on it
- Enter the three shifts and two substitutes in the example.Expected result: The totals show seven required assignments, five confirmed and two gaps. Substitutes do not increase confirmed capacity.
- Assign the same reference twice to a shift or to overlapping shifts.Expected result: A duplicate or clash is flagged before acceptance, and the count does not increase from a repeated record.
- Cancel a confirmed assignment and select an unconfirmed substitute.Expected result: The confirmed total falls and the gap remains until the coordinator records the substitute’s agreement.
- Leave a finish time blank, then save valid records and sign in again.Expected result: The incomplete shift is refused; valid records return with correct states and remain separate from other accounts.
7. Use the project during its first week
Start with one small activity or one day. Confirm each person’s assignment privately before relying on the numbers. During the first week, review the schedule after every cancellation or change. The day before the activity, repeat the time, place and role to confirmed participants. Afterwards, compare confirmations with attendance and ask what instructions were missing. Use the record to improve arrangements, not to publicly judge volunteers. If two coordinators become necessary, specify separate access before expanding rather than sharing credentials.
Your first weekly review note
Coordinator review: [number] shifts are planned and [number] places still need confirmation. I will contact substitutes individually before finalising assignments. My private planner: [website link]. Each confirmation will state the task, time and place; initial interest is not a final assignment.
Questions about this project
Can volunteers book a shift themselves?
Not in this version. They tell the coordinator their availability, and the coordinator checks capacity and clashes before confirming. Direct shared booking needs additional logic and permissions.
Does confirmed mean attended?
No. Confirmation is an agreement before the activity; attendance records what happened. Keeping both avoids rewriting the planning history afterwards.
Should I post the whole schedule in a group?
Share general information when appropriate, but each person primarily needs their own assignment. Do not circulate others’ contact information or private notes unnecessarily.