Growing
Events
Running an event once and letting the information reach everywhere it is relevant, instead of retyping it into four modules.
Enter it once
This is an event operations workspace, not an event database. The organizing rule is that the organization does the work once and FundWisr reuses it wherever it is relevant.
Event tasks live in the Action Center
Deliberately. An event task is an action carrying the event on it, so one task appears in the event workspace, in the Action Center, in the assignee's own list, and on the Command Center, and completing it anywhere completes it everywhere.
Running one well
Create the event with its capacity and its dates.
Capacity is enforced against registrations, so you are not counting by hand on the day.
Set up registration, including any ticket types and prices.
Paid registrations become revenue records automatically, in the right certainty category.
Add the tasks, with owners and dates, as ordinary actions.
After the event, record attendance rather than assuming registration equals attendance.
The gap between the two is one of the more useful numbers a nonprofit can have and one of the least often kept.
Read next
- Donors & RelationshipsOne record per person or organization, whatever their relationship to you, and a cultivation plan you can actually read.
- Action CenterWhere a finding becomes somebody's job: tasks, owners, priorities, projects, subtasks, and where the work came from.
- FinanceBudgets, what you are owed, what you owe, what you have spent, and the restricted money you are holding for somebody else's purpose.
Something here wrong, missing, or out of date? Email support@fundwisr.ai and tell us which chapter. Documentation defects are treated as defects.