Understanding Verified and Unverified Actions

Overview

Every Action in Alpine carries a verification status — either Verified or Unverified. This status affects how Actions are counted in reports and revenue totals, and serves as a built-in data quality checkpoint for your team.

Part 1: What Do Verified and Unverified Mean?

Verified

An Action is Verified when its Action Date is today or in the past. Verified Actions are counted in all reporting, including revenue totals, constituent giving summaries, and At a Glance statistics.

Unverified

An Action is Unverified when its Action Date is set in the future. Unverified Actions are recorded in Alpine but are excluded from revenue-based reporting and constituent totals until they are marked Verified.

Part 2: Why Verification Status Matters

Verification status ensures your reports reflect only confirmed activity — not anticipated or projected interactions.

For Donation, Membership Payment, and RSVP Actions specifically, an Unverified status means the Action will not count toward:

- Revenue totals on the Dashboard

- Constituent giving history and lifetime totals

- Campaign and Action-based reports

This makes verification particularly important for financial accuracy. A pledge entered with a future payment date, for example, will appear in Alpine but will not inflate your revenue figures until the payment is confirmed and the Action is verified.

Part 3: How Actions Become Verified

There are two ways an Action moves from Unverified to Verified:

1. Automatic verification — When an Action is entered with today's date or a past date, it is automatically marked Verified.

2. Manual verification — A staff member reviews an Unverified Action and marks it Verified individually. This is common for future-dated Actions once the interaction has taken place.

Part 4: Using Verification as a Data Quality Tool

Beyond date-based status, verification can also be used as a workflow checkpoint — a way for supervisors or data managers to confirm that Actions entered by other staff members are accurate and complete before they count toward reporting.

Common uses include:

- A Development Associate enters gift records; a Development Director verifies them before they count toward revenue totals.

- Event staff log RSVPs in advance; a coordinator verifies them after the event occurs.

- Volunteer coordinators review hours entered manually before confirming them.

The At a Glance panel in the Actions module displays a count of Unverified Actions, making it easy to spot a backlog that needs attention.

Pro Tips

- Use the Unverified filter in the Actions module to quickly surface all Actions pending review.

- If you notice a consistently high Unverified count, it may indicate future-dated Actions that were never followed up on — a good signal for a data cleanup.

- For financial Actions, make it a team habit to verify Donations, Membership Payments, and RSVPs promptly so your Dashboard and reports stay accurate.

- Actions can also be verified or unverified in bulk. See How to Mass Verify or Unverify Actions for details.