Workplace Campaign Overview
Campaign Structure
A workplace campaign in DonorPoint has two levels:
GivingCampaign — the umbrella campaign year. Defines the overall campaign period, participating organizations, and federation settings. Payout batches belong to the GivingCampaign.
Campaign (Form) — the employer-facing giving form. Each employer typically has their own form, pre-configured with their employees and payment methods. Multiple campaigns belong to one GivingCampaign.
Lifecycle
- Setup — configure the GivingCampaign, create employer forms from templates, import employee files
- Active — employees log in, make pledges; staff monitor participation
- Closing — campaign end date passes; final reminders sent; declines managed
- Payout — payout batches built from pledges; distributions calculated; remittance to agencies
Dashboards
DonorPoint provides two purpose-built dashboards for workplace campaigns:
- Workplace Dashboard — a real-time view of participation and giving for a single employer campaign. By default the dashboard is visible only to the workplace owner (the staff member responsible for that employer) and your federation administrators. This keeps each employer’s data private when multiple workplaces share the same DonorPoint account.
- Individual Dashboard — a per-employee view that lets a donor see their own pledge, payment history, designations, and matching-gift status. This is what employees see when they log into the donor portal mid-campaign and is also linked from confirmation emails.
Both dashboards are implemented as View Pages, so they can be customised per account: add custom widgets, tailor the metrics shown, or restrict visibility based on role.
Key Concepts
Employee Relationship — the link between a Contact and an Organization that represents employment. Employee relationships carry custom fields defined per organization and are the record through which payroll pledge tracking works.
Participation vs. Response — participation measures how many employees engaged with the campaign (logged in, opened emails). Response measures how many made a pledge. Both are tracked and reported separately.
Payroll Deduction — the primary payment method for workplace giving. The employee pledges; the employer deducts from payroll and remits to DonorPoint. DonorPoint records the pledge immediately and the payments as they arrive.
Federated Designations — employees designate their gifts to specific agencies. DonorPoint routes these designations through the payout engine to the appropriate federated agencies. See Designations and Payouts.
Year-Over-Year Rollover
Workplace campaigns typically repeat annually. DonorPoint supports rolling campaigns forward from one year to the next using campaign templates:
How Rollover Works
- Create the new GivingCampaign for the upcoming year
- Clone employer campaigns from the prior year’s templates — this copies the form configuration, items, payment methods, and customization
- Import updated employee files — the import process matches existing contacts by Employee ID and updates their records; new employees are added, terminated employees can be excluded
- Prior-year pledge data is available on each employee’s contact record for reference during the new campaign, enabling comparison reports and personalized ask amounts
Rollover Patterns
Organizations use different rollover models:
| Pattern | Description |
|---|---|
| Annual reconfirmation | Employee must make a new pledge each year; prior-year pledge is shown as a reference |
| Ongoing with reconfirmation | Prior-year pledge carries forward as a Pending transaction; employee confirms, modifies, or cancels |
| Ongoing automatic | Prior-year pledge is automatically renewed unless the employee opts out |
The rollover model is implemented through campaign template scripting — the template’s createEL and persistEL scripts can reference the employee’s prior-year transactions to pre-populate amounts and designations.
Rollover Transactions
When a prior-year pledge carries forward, it is created with a Pending transaction status. Pending transactions are not active — they await the employee’s confirmation through the campaign form. Once confirmed, the transaction moves to Active (for received payments) or Pledge (for payroll deductions).