How to Spot Check Your Data

Once your Constituent data is successfully uploaded to EverTrue, we recommend using these tips and tricks to spot check your data:

Giving Data - Lifetime Giving, Last Gift and Largest Gift

Giving data is incredibly important in EverTrue and here are some tips to make sure it is imported correctly.  First, we recommend scrolling to the right on the Browse page in EverTrue and clicking on "Edit Columns":

Move the Last, Lifetime and Largest columns to the Active section and click Save Columns.  This view will allow you to check your data thoroughly.  

As you scroll through and spot check, some questions to ask yourself are:

  1. Is the Last Gift the same or less than the Largest Gift?
  2. Is the Lifetime Giving the same or more than the Largest Gift?  

LYBUNT & SYBUNT

We recommend checking your LYBNUTs and SYBUNTS in EverTrue.  LYBUNT status occurs when last gift date is within one previous year from the fiscal year start date. Similarly, SYBUNT status occurs when there is a last gift date that occurs prior to one previous year from the fiscal year start date. Filter on Giving Patterns and spot check some of your LYBUNTs and SYBUNTs. Make sure that the last gift field and the fiscal year totals reflect this status.   You can also see their Giving Pattern on their profile:

Mapped Addresses

Ensuring your addresses are being imported correctly is another important aspect when you are checking your data in EverTrue.  When browsing through the data, you can toggle between a Table view and a Map view.

If your constituents are being mapped properly, the constituent will appear populated on the map.  

Constituency Codes

Verify that your code formatting is correct. Constituency codes are specific to your institution, however in the below example, there are both Alum and Alumni.  When importing constituency codes, we recommend keeping the codes concise and not include too many (like the below example) in order to avoid confusion:

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.