Membership status tracker for standing decisions
Record the current standing, requested standing, reason, effective date and authorization before changing services, visibility or access.
The examples cover reinstatement after renewal, lapse after no response and a grace-period request still waiting for evidence.
Free for up to five users. No credit card required.
Adapt fields, workflows, and dashboards without code. Explore 1,000+ app templates and use cases
Preserve the reason, authorization and effective date behind every standing change
Give each status an operating meaning
Standing should tell staff and connected systems what changes next.
Active
The current term and eligibility are in force under the organization's policy.
Renewal due
The term is approaching its end and follow-up is required; the member is not yet lapsed.
Grace period
A dated exception keeps specified services available while an issue is resolved.
Lapsed or suspended
The reason, effective date and service consequences must remain distinguishable.
Use evidence and reason before applying standing
The example separates a proposed change from the member's current state.
Read the current record
Confirm the exact member, existing standing, term and related renewal evidence.
Record requested standing
Choose the proposed outcome and reason without overwriting the member yet.
Review the basis
Check payment confirmation, grace approval, policy case or member request as appropriate.
Apply the approved result
After authorization, update the exact member record and retain the change history.
Decide what standing controls
A status change matters because other processes consume it.
Directory visibility
Define whether lapsed or suspended records appear to members without deleting history.
Event eligibility
Set which standing values can register and which require review.
Committee service
Trigger review when a role requires active standing.
Communications
Adjust service and renewal messages without treating standing as consent for every campaign.
Document the evidence behind each standing transition
This protects both member service and policy consistency.
| Transition | Evidence or basis | Effective action |
|---|---|---|
| Renewal due → Active | Renewal accepted and dues resolved | Set next term |
| Renewal due → Grace period | Approved exception with end date | Retain defined services temporarily |
| Grace period → Lapsed | Exception expired and notice complete | Apply lapse consequences |
| Lapsed → Active | Reinstatement requirements met | Record new effective date |
| Active → Suspended | Authorized policy decision | Apply restricted services and review date |
Adapt member standing decisions without waiting for a development project
Build member standing decisions around the information, decisions and follow-up your team actually uses. Authorized staff can change the form, workflow, filtered views and dashboard without writing code.
Start with a working App for member standing decisions, then let the people who run it refine fields, workflow and reporting as needs change.Adjust the records and rules
Add the fields, categories and exception paths that member standing decisions requires, then revise them as the program changes.
Assign decisions to the right person
Use named review tasks, return-for-correction steps and permissions when member standing decisions needs a human decision rather than a status edited by anyone.
See the next useful action
Renewal evidence, exception reasons and authorization stay connected to the exact member whose standing changes.
Where Jodoo fits in member standing changes
Use Jodoo when member standing changes depends on connected records, assigned decisions and visible exceptions. Connect or retain specialist products for capabilities they already own well.
Manage in Jodoo
Forms, review steps, operational queues, reminders and dashboards that staff need to run member standing changes.
Connect the systems of record
When member standing changes needs payment transactions, accounting entries, bulk email or authentication, keep those functions in their system of record and pass the useful status back to staff.
When a purpose-built platform is the better choice
Disciplinary adjudication, legal case management and physical access enforcement need their own controls; the tracker should record the authorized outcome without pretending to replace them.
Questions about membership status tracker
What is the difference between member status and renewal status?
Renewal status describes the current renewal case; member standing describes the effective membership outcome.
Should a lapsed member be deleted?
Usually no. Retain the record and history under your retention policy while changing visibility and service access.
Can Jodoo update standing after approval?
Yes. The example uses a native authorization workflow and an operational rule targeted to the exact member ID.
Can we add our own standing values?
Yes. Define each value, transition, evidence requirement and downstream effect before configuring it.
Make every standing change explainable
Inspect the reinstatement, grace and lapse examples, then configure the transitions and downstream effects that match your policy.



