Process management for associations and foundations.
An association or foundation does the same work every week: recording new members, chasing dues, logging donations, assigning volunteers, reviewing aid applications and getting the board to approve decisions. When all of that runs through shared inboxes and spreadsheets the organisation can operate, but it cannot grow. Tenderely BPM connects every one of those recurring steps into one traceable system without writing a single line of code.
What does an association or foundation repeat every week?
01
Member registration and dues
New members join, existing ones renew, some fall behind on payments. Knowing exactly who is active, who is overdue and who has lapsed should not require a manual audit.
02
Donor and donation records
Individual and corporate donors give once or regularly. Each contribution needs to be tied to a donor, a campaign and a reporting period — so that acknowledging and reporting on it later is straightforward.
03
Volunteer coordination
Volunteers sign up, declare availability and get assigned to activities. Without a central record of who is assigned where, double-booking and gaps appear on the same day.
04
Aid applications and social assessment
Applicants request support; a staff member or social worker reviews the case and gathers evidence; the finding goes forward for board consideration. Each of these is a distinct step that must happen in order.
05
Project and activity management
Planned activities have budgets, responsible people, timelines and outcomes. Progress needs to be visible during execution, not only in the year-end report.
06
Board decisions and approvals
Expense approvals, aid grants and policy decisions need a board resolution. That resolution must be numbered, dated, signed and retrievable during any inspection.
Where does this break down today?
Member data lives in a spreadsheet nobody fully trusts
One person maintains it, it goes out of date between updates and when that person is absent nobody knows which version is current. Active member counts become a matter of guesswork ahead of a general assembly.
Aid applications wait in an inbox
A request arrives by e-mail or on paper. It needs a social assessment, then board approval. Without a defined flow each application moves at the speed of whoever happens to notice it, and the applicant has no idea where it stands.
Board decisions are hard to find
Resolutions are drafted in a word processor, approved by e-mail thread and filed in a folder nobody has indexed. When a donor, an auditor or a government body asks for decision number 47, a search begins.
Volunteers and staff work from different lists
Volunteer availability is in a chat group, assignments are in a calendar, outcomes are nowhere. Coordinating a single event means pulling three separate sources together, and doing it again next time.
What changes with Tenderely BPM
01
Every member is a live record
Membership status, dues history and contact details stay on one record that anyone with the right role can read. There is no spreadsheet to reconcile before a general assembly.
02
Aid applications move through defined steps
Application, social assessment and board approval are separate stages in a single flow. Each stage opens only when the previous one is complete, so nothing is skipped and the applicant's progress is always visible.
03
Board decisions have an automatic register
Every approved resolution is a dated, numbered record with an audit trail of who voted and when. Retrieving decision number 47 takes a search, not an afternoon.
04
Volunteers apply and get assigned from outside
A public form lets anyone express interest and state their availability without needing an account. Assignments then come back to them as notifications, and the coordinator sees the full picture in one place.
05
Approvals happen on a phone
Board members and managers who are not in the office can review and approve on iOS or Android. An expense or an aid grant does not wait until the next in-person meeting.
06
Tenderely gives the whole organisation one view
Active members, pending aid cases, volunteer coverage for upcoming activities and committed budgets sit on a dashboard instead of across four separate files, so leadership can make decisions on current information.
FAQ
Can we start with a ready-made setup and adjust it later?
+
Yes. The Association and Foundation package opens with forms, workflows and a dashboard already in place. You then adjust each form to your own organisation's needs and publish it. The package is a starting point, not a constraint — anything can be changed without code.
Can aid applicants submit their requests online without having an account?
+
Yes. A public form can be shared as a link or embedded on your website. An applicant fills it in without registering, and their submission opens a record that travels through your internal assessment and approval steps.
How do we handle the board approval step without all board members being present at the same time?
+
Approval steps can run in parallel, so each board member receives the item and can respond independently on web or mobile. The step closes — approved or rejected — once the required responses are collected, and every response is timestamped in the audit history.
Who can see sensitive data such as a beneficiary's social assessment?
+
Role-based and field-level permissions decide exactly who sees what. A social worker can access assessment details while a volunteer coordinator sees only activity assignments. Sensitive records log every view, so you always know who accessed what and when.
Can donors or members be notified automatically — for example when a payment is due or a request is processed?
+
Yes. Notifications can be sent by in-app message, e-mail or push at any point in a flow. A step with an SLA will also remind the responsible person if the deadline passes, so a pending assessment or approval does not sit silently.