Welcome
Live operational overview.
Families
All families in the system. Search or filter — the full list loads by default.
Family Applications
Public requests to be registered. Each is checked against existing families — review possible duplicates, then create the family or reject.
Family stories
Impact stories and photos for donor reporting — track consent (with signature) and what has been reported.
People Search
Search any individual across all families. Read-only profile — edits are made from the family file.
Visits
Assign, conduct, and review visits. Decision visits set eligibility; informational visits are logged only.
Schedule visits
Schedule fills one social worker's day: pick the worker and date, choose 30-minute slots, then pick families (one per slot). To assign a single visit to one family instead, open that family and use Assign Visit.
▸Scheduled visits for this day
1Visit details
2Select families
3Assign time slots
Bulk assign visits
Filter the family list by criteria, select families, then assign a visit to all of them at once. They land in the pending visits queue.
1Find families
2Matching families
3Visit assignment
4Review & assign
Awaiting Enrollment
Your to-enroll worklist and report: every ELIGIBLE (active) family with no active project enrollment — so no one found eligible after a visit is forgotten. Filter by location, nationality, religion, household size, and whether they ever benefited; clear the list by enrolling.
Queue
Call families to each service line. Numbers reset daily per service (R-001, M-001…). This board refreshes automatically.
Projects
Define projects, allowed items, and quantity rules. Rules are editable at any time.
Shared Item Catalog
Warehouse
Stock is earmarked per project. Balance = total in − total out.
Balances
Recent Movements
Follow-up Lists
Two coordinator work queues. Nothing happens automatically — every entry waits for a human to act and mark it done.
Reference Teams
Small teams of employees, each following its group of families. Assignments live in history: previous team, new team, date, who, why.
Recent transfers
Family references (introduced by)
Distribution
Arrival → Verify → Deliver. Scan the barcode or enter the voucher number. Any correction is a reversal — no deleting or editing the record.
Relief SMS
SMS and WhatsApp through one engine. Pick a verified sender and a template, then choose recipients.
Batches — who goes when
Families · 0 selected
Message, date & time slots
Send a test
Send the campaign
WhatsApp follow-up · invited vs received
Assessment Forms
The question forms visitors fill during home visits. Build forms, add questions, and set which visit types use them.
Settings
Configure the system. You only see the categories your role is allowed to manage.
Visit Requests
Families who asked for a visit from the portal, with their preferred date and time.
Complaints
Feedback and complaints families submitted from the portal.
Clinic Queue
Everyone waiting in the clinic, and call the next patient per speciality.
Clothes Settings
Pricing & rules, the item catalog and categories, and the seasons — each on its own tab.
Rules
Prices
Item categories
Items
Barcode label
Warehouse locations and their sub-shelves. Boxes are stored in a location · sub-shelf you pick from here.
Clothes Warehouse
A separate warehouse for the clothes ministry — items with per-gender variants (barcode + price), an immutable stock ledger, and pre-packed boxes.
Recent operations
Clothes Enrollment
Mark which families are eligible for a season — add existing families, enroll a group by criteria, or create a new outside family on the spot.
Add an existing family
Enroll a group by criteria
Enrolled families
Clothes Payment
Take a family's payment before distribution. The members paid for become a per-category item allowance that carries over through the season.
Find an enrolled family
Benefit
Clothes cash reports
Clothes Distribution
Scan items to hand out. Allowance seasons draw down each category's balance; by-item seasons charge the item price and enforce the per-member cap (with an admin OTP to override). Families can come back across multiple visits.
Find an enrolled family
Take payment
Clothes Queue
A separate waiting line per branch — issue a number, call the next family, and show the now-serving number on a public screen.
Issue a ticket
Clothes SMS
Invite enrolled families by SMS or WhatsApp — filter, assign a day and time slots, write the message, preview, and send.
Recipients · 0
Day & time slots
Message
Medical SMS
Invite patients by SMS or WhatsApp — from a clinic campaign, the chronic program, or all families.
Families · 0 selected
SMS / WhatsApp message
Campaign
×Campaign
×Campaign
×WhatsApp messages
×Open each chat and press send. Browsers block opening many tabs at once, so open them one by one.
New outside family
×Category
×Season
×Item
×Print label
×Location
×Box
×Stock
×Record a stock operation
×Item
×Box
×Administration
Users, role permissions, and database.
Exchange rate (USD → LBP)
Database
Info
Database backups
AdministratorsAlternative: scheduled server cron
Sample data & reset
AdministratorsUse these to test the whole system with realistic data, then start over before going live.
A full database backup is saved first, then only the checked tables are cleared. Settings/config are never listed. Families is shared — clearing it affects Clothes, Relief & Medical.
Apply update
AdministratorsHR & Leaves
Employees, leave settings, and public holidays.
Employees
Staff records — profiles, logins, rates, and leave.
Attendance
Attendance, payslips, and the check-in links.
Reports
Per-project stock and distribution statistics by project, area, and month.
Requests & Feedback
Submit a feature idea, an improvement, or a problem you hit. Everyone can see all requests.
Excel Migration
Five steps, in order. Each one saves its progress as it goes, so a slow sheet or a server timeout costs you a click, not the work. Nothing touches the live tables until step 5, and step 5 takes a full backup first.
Files and sheets
Reports
Review queue —
Households the matcher joined across two different legacy codes on evidence too weak to trust on its own. Each block below is one household: its rows are the appearances that were merged, and you choose which one to Keep as the primary record (the others are dropped as duplicates of it, but their projects and give-outs still import). Or Split an appearance out into its own household. Standing rule: when a household spans programs, the CFGB / Crows_Team appearance is pre-selected as the base — it wins the family's code and open/closed status; Winter / Displaced appearances fold in as duplicates.
Possible duplicates (kept separate) —
Families that look similar — a shared phone, the same name in the same area, or overlapping member names — are automatically kept separate. Suspicious similarity is never enough to merge: a wrong merge mixes two families' histories, while keeping them apart is harmless and reversible. This list is your reference: after import, merge any pair that really is one family (Families → Merge), or merge here before import if you're certain.
Conflicts (resolved automatically) —
UN-number disagreements are handled by standing rule, so nothing blocks the import: same legacy code + different UN spellings = one family with a typo — accepted; different codes + different UN = wrongly joined — split by code into separate families. Each decision is recorded below for your audit; you can still override one manually.
Import details
A full server-side backup runs before the first row is written. Households, members and enrollments commit as one transaction; give-outs commit in chunks, each carrying a unique reference so a resumed or repeated import never doubles a row. CFGB give-outs dated on or after 2026-06-01 are not imported as history — export them instead and put them through the live system.
Verify import —
After importing, this reconciles the live database against what the run intended and runs a set of sanity checks — did every family and give-out land, is cash in USD, was the 2026 CFGB round correctly held back for the phase upload, and so on. Green everywhere means the import is sound.
Trace a file number / receipt
Type a legacy file number (e.g. S879) or a receipt (e.g. CFGB#2229). This looks in live families, live vouchers, and the migration staging at once and tells you exactly where those give-outs are — imported, orphaned, or never staged. Read-only.
CFGB phase upload — bring a phase into the live system
Upload a phase file — either the Warehouse-Operations receipts layout (رقم الايصال …, one phase per file) or the Master Data Phases roster (Month · phase · رقم الملف · Date Of delivery · عدد حصص · حليب · حفاض; may hold several phases). Every row is a real distribution in its phase: rows with a delivery date become DELIVERED vouchers; rows without a date become OPEN vouchers (created but not received). The active CFGB cohort = families in the file's latest phase — they are enrolled for the next phase; families seen only in earlier phases are STOPPED (enrollment ended, history kept). Re-uploading never duplicates.
CFGB base reconciliation — the workbook is the truth
Upload the base workbook (one sheet per phase; columns Code · حصة · حليب · حفاض, the full cohort in every sheet, zeros included). It compares each phase against the system — past phases against their vouchers, the LAST sheet against the active enrollments and their commitments — and can align the enrollments to the base in one click. Keyed by the legacy code. Voucher history is never rewritten.
Past phases can also have their distribution reconciled to the workbook — use Compare first, then the button inside each past-phase card. That one rewrites vouchers (creates missing deliveries, fixes quantities/milk, cancels extras) and takes a backup before it runs.
Data quality — members & heads
Duplicate members: two members of the same family whose names are identical once spaces/spelling folds are ignored (e.g. جان دارك / جاندارك) — keep one, archive the other. Missing heads: families with no head of household get the oldest member appointed, males first.
Crows Team — align to "Active Today"
Upload the Master_List (Crows) workbook. Only the families in its "Crows Team Active Today" sheet stay enrolled — each on its schedule (شهرياً → Monthly · كل شهر و نصف → Every 45 days · كل شهرين → Every 60 days · حفاض حليب → Milk-Diapers), with the sheet's remaining count and committed items (حصة / حليب / حفاض). The استلام dates become the family's delivered history. Everyone else's Crows enrollment is ended (history kept).
Areas — consolidate spellings
The same place is written different ways (plus Excel leftovers like _x000D_). Auto-clean & canonicalize fixes artifacts and rewrites every spelling that already equals a system area. What remains needs a manual choice — pick the system area per spelling, or create it as a new area.
Activity History
Every recorded action, who did it, and what changed. Reversible actions can be undone; history itself is never edited or deleted.
Laundry Service
Eligibility, laundry days, calling, attendance, and reports — built on the existing family records.
Audit
Full lifecycle of a single voucher or project. For the system-wide log (with search, field changes and Undo), use Activity History.
Medical — Pharmacy
Shared pharmacy stock for both medical services. Track on-hand by active ingredient, manage the medication catalog and brand→ingredient map. Every movement is recorded; corrections are reversals, never edits.
Chronic Medication Program
Recurring monthly medication refills at the member level. Enroll a patient with a frequency and a standing med list, build the eligible list for a distribution day, print vouchers, and hand over against the shared pharmacy stock.
Eligible now
Distribution days
Hand-over
Renewal review
Medical Reports
Consumption and refill reporting across the chronic medication program. Pick a date range for dispensing, or leave it blank for all-time.
Medical Settings
Specialities
Exchange rate
Medical Campaign / Clinic
Run a clinic day: book patients, check them in, take vitals, and record the doctor's consultation. Each step is handled by its own station.