Zeynep Arslan
- Member no.
- 128
- Approved
- 7 January 2026
From application to outcome,
every step on record.
A member joins, dues are paid, a need arises, the general assembly decides, a task gets done, money is spent and everyone sees the result. Elele keeps these seven steps in one linked chain of records.
SEVEN STEPS
A community’s year, one chain of records.
Example: Demo Village Association, 2026. At each step: who does what, which module is at work and what gets recorded.
People, amounts and record numbers are illustrative.
A member applies; the board approves
Zeynep applies through the community’s link. The board sees the application and approves it; she gets a member number and the member register updates itself.
- Who does it
- The applicant; the board approves
- Module
- Membership and roles
- What gets recorded
- Member record, role, member register entry
Sample record Member recordApproved Dues are charged and collected with a receipt
Annual dues of ₺600 are charged to the member in 12 instalments. When the treasurer collects January, a numbered receipt is issued and ₺50 goes into cash.
- Who does it
- Treasurer
- What gets recorded
- Dues plan (₺600 / 12 instalments), collection, numbered receipt, cash movement
Sample record ReceiptIssued 2026-000041
- Amount
- ₺50 · January dues
- Account
- Cash (+₺50)
A need is recorded
A student starting university needs a computer; the target is ₺15,000. The recipient’s name is visible only to authorised roles.
- Who does it
- The board (members can report needs too)
- Module
- Aid and needs management
- What gets recorded
- Need record: number, category, target amount, attachments
Sample record NeedAwaiting budget approval IHT-2026-007 · Computer support
- Target
- ₺15,000
- Category
- Education
The general assembly approves the budget
Attendance is taken at the general assembly, and resolution 2026-03 approves a ₺15,000 budget. The resolution is linked to the need and cannot be edited once finalised.
- Who does it
- General assembly; the chair records the resolution
- Module
- Boards and decisions
- What gets recorded
- Attendance list, numbered resolution, link to the need
Sample record ResolutionFinalised 2026-03 · Education support budget
- Attendance
- 64 of 112 members
- Budget
- ₺15,000
The decision becomes a task
A member is given the purchasing task. The owner and due date are clear; the task shows the resolution and need behind it and sends a reminder as the date approaches.
- Who does it
- The board assigns; the assigned member carries it out
- Module
- Tasks and projects
- What gets recorded
- Task: owner, due date, status, linked resolution and need
Sample record TaskUnder way GRV-2026-019 · Purchase and delivery
- Owner
- Murat Kaya
- Due
- 31 March 2026
The money is spent; the job closes
A ₺14,500 computer is bought and posted to the ledger with its receipt. On delivery the task closes and the need is marked “met”; ₺500 of the approved budget remains.
- Who does it
- The assigned member buys; the treasurer posts the expense
- What gets recorded
- Expense with attached receipt; task and need status; remaining budget
Sample record ExpensePosted Laptop (education support)
- Amount
- ₺14,500 · receipt attached
- Budget left
- ₺500
The member sees the result on their phone
Zeynep sees her own dues, the outcome of the need she helped fund and the community’s income and expense summary on her phone — even offline.
- Who does it
- Every member, as far as their permissions allow
- Module
- Reports
- What gets recorded
- Nothing new: the same records, summarised to the member’s permissions
Sample record My accountNothing overdue Dues status · 2026
- Paid / left
- ₺150 / ₺450
- IHT-2026-007
- Met
CONNECTIONS
Records, tasks and money know each other.
The seven steps work because of the links between them, not their order; no record stands alone.
Decision → task
Every task shows the resolution or need behind it, so nobody asks why it was done.
Task → money
A task’s spending is posted as an expense; its receipt stays attached to the task and the need.
Money → member
Collections reach the member’s account with a numbered receipt, expenses reach the reports; members see where they stand.
Entered once
Members, decisions and collections are entered once and reused by every module. Records entered offline sync when you reconnect.
MODULES
The modules at work in this flow.
Turn on what you need; switching a module off never deletes its records.
- Membership
Membership and roles
Applications, approvals, roles and the member register; you decide who sees what.
- Money
Income, expenses, dues and receipts
Dues plans, collections, numbered receipts, cash and bank, and a double-entry ledger.
- Mutual aid
Aid and needs management
Record the need, approve the budget, assign someone, share the outcome.
- Governance
Boards and decisions
General assemblies, attendance lists, polls and a numbered resolution book.
- Tasks
Tasks and projects
Every job has an owner, a due date and a status; projects move step by step.
- Reports
Reports
Income and expenses, balances, receivables and activity reports, ready for the AGM.
- Offline
Offline work
Keep recording without internet; it syncs on its own when you reconnect.
Related pages.
FAQ
Questions about the flow.
Do I have to follow this order?
No. You switch on modules as you need them; start with membership and dues and add aid and tasks later. A module you add uses the records you already have.
What can members see?
Their own dues and receipts, announcements, decisions and the reports the board shares. Personal details such as an aid recipient’s name or other members’ arrears are visible only to authorised roles.
What happens without internet?
Collections, expenses and task updates can be entered offline and sync to everyone when you reconnect. Receipt numbers are issued on sync, so they never clash.
GET STARTED
Set up the same flow for your community.
Create your community and start with the first member, the first dues plan and the first decision. Want to look first? The demo is ready.