Identity Verification Status Change Report
This purpose of this page is to help colleges request and understand the Identity Verification Status Change Report.
On this page:
Introduction
The purpose of the Identity Verification Status Change Report is to provide colleges with two reports:
a one-time “catch-up” report that identifies students who have had a change in identification verification since they first set up their account
recurring update reports regarding student verification status changes over specified periods of time
The recurring report provides a snapshot of daily or weekly changes when a student becomes Verified or Unverified. The report is intended to give colleges visibility into these changes in order to track financial aid eligibility and support your investigations of application fraud.
This report is one of two vehicles that provides notification of identification verification changes to the colleges. The other vehicle, delivered by SuperGlue, provides events-driven data to support the reasons behind these status changes. It should be noted that not all event-driven notifications are specific to ID.me or DMV Wallet verification status changes. For more information on events-driven notifications, see Events Table Fields and Payload Data.
Read more: The links below will take you to sections in related public pages.
DMV Wallet | ID.me |
|---|---|
Purpose & Scope
The purpose of the Identification Verification Status Change Report is to provide colleges with daily visibility of their student’s identity verification status changes in order to help Admissions & Records and Financial Aid Office staff streamline financial aid eligibility processes and assist in fraud prevention activities.
The Identification Verification Status Change Report runs one time per day, at midnight. When the report runs, it compares the current data to the report run in the previous day. If it finds that a student’s verification status has changed to verified or unverified, that student’s record will show on the change report. The student’s record will not show if the status changed to any of the other states (expired or staff_verified).
Report Format
The Identification Verification Status Change Report presents CCCApply Application data submitted to the college, including:
the student’s CCCID
the Application ID and submit date
data to track the student’s previous verification status and and status at the time when their last application was submitted
timestamps to identify their current verification status at the end of the previous day
If a student’s verification status is different at midnight (has changed) than it was at the start of the day, a record of the change (line-item) will be included in the Identification Verification Status Change Report. If the student’s verification status value is the same at midnight as it was at the start of the day, it will NOT be included in the report.
For detailed data definitions, see Identification Verification Status Change Fields.
Differences Between the Identification Verification Status Change Report and the SuperGlue Events Notifications
In order to keep colleges informed of changes to student’s verification changes, event-driven notifications are triggered by OpenCCC and delivered to the colleges in two formats:
Identification Verification Status Change Report (currently only available for student applications validated through ID.me)
Event notifications delivered to an Events Table via SuperGlue
Both vehicles deliver status changes, but in different formats. For data field definitions and specifications for each format, see the Identification Verification Status Change Data Fields page.
Status change data will be stored in duplicate verification fields, one with the idme name and one with the verification name. In a future release, expected to be in FY26-27, the idme fields will be deprecated and the verification fields will be the primary source for data.
Format | Current Status | Previous Verification Status |
|---|---|---|
Status Change Report | Current Status | Latest App Status |
SuperGlue Events | Current Status | Previous Status |
Regardless of the vehicle, the field values for all “status” fields are the same.
Status Change Logic
What constitutes a verification status change?
The following workflows will cause a verification status change:
A student Verifies or Re-verifies their identity
Never verified (null or blank) to Verified
Staff verified
Verified to Unverified to Verified
A student’s Verified status expires
Verified to Unverified (expired)
Staff verified to Unverified (expired)
A student makes a manual change or update to any of the Account Profile fields that can cause their Verified status to change
Verified to Unverified
Staff verified to Unverified
Regardless of the notification vehicle or format, these events and triggers will change a verification status change.
NOTE: The Verification Status Change Report will only be triggered when a status changes to verified or unverified. For more details, see Identification Verification Status in the Events Table.
Account Profile Changes That Cause a Verification Status Change
If a Verified student manually changes or updates any of the Account Profile fields listed below, their Verified status WILL change to become Unverified.
First Name
Last Name
Date of Birth
Social Security Number
Address fields:
Street Address 1; Street Address 2
City
State
Postal Code/Zip Code
Country
Account Profile Changes That do NOT Cause a Verification Status Change
If a change or update of any kind is made to any of the Account Profile fields listed below, the verification status will not change:
Email address
Phone number
Middle Name
Preferred Method of Contact
Taxpayer Identification Number
Password
Important Note: Though not every Account Profile change or update leads to a verification status change, all Profile updates will trigger an UPDATE_PROFILE event notification that gets delivered to the Events table via SuperGlue. For more information about SuperGlue Event notifications, including the UPDATE_PROFILE event and the FEDERATED_IDENTITY_LINK event, see Identification Verification Status in the Events Table.
Events That Trigger the Identification Verification Status Change Report
If the Verification Status changes, SuperGlue will only send a notification report if one of these conditions are met:
Previous Status ( | Current Status ( |
null or blank | verified |
unverified | verified |
verified | unverified |
For example, if the Status changes to expired, a notification report would not be sent.
Report Layout & Content
What data is included in the Report?
The report includes the following columns:
Field Name | Description |
College MIS Code | MIS Code |
Student’s CCCID | Unique identifier for a student. |
Latest Application ID | The Application ID |
Latest App Submit Timestamp | The date and time of the latest (most recent) CCCApply application submitted to the college. |
Latest App Status | Indicates the Workflow Status at the date and time of the student’s latest (most recently) submitted CCCApply application. |
Latest App Opt-In Timestamp | Indicates the Opt-In Timestamp (date and time) of the student’s latest (most recent) CCCApply application. |
Latest App Confirmation Timestamp | Indicates the Confirmation Timestamp (date and time) of the student’s latest (most recent) submitted CCCApply application. |
Current Status | Indicates the student’s current Workflow Status at the date/time the report is run or when a workflow status change is set. |
Current Status Change Timestamp | Indicates the date and time of the most recent change made to the student’s Workflow Status. |
Additional information can be added to the report upon request:
Current Opt-In Timestamp: Indicates the student’s current Opt-In Timestamp at the date/time that the report is run or a workflow status change is set.
Current Confirmation Timestamp: Indicates the student’s Confirmation timestamp at the date/time that the report is run or a workflow status change is set.
Student data will only appear on the report if a student’s verification status (workflow status) has a different value than their previous status. For example:
A “verified” student becomes “unverified” (
idme_status=unverified) or (verification_workflow_status=unverified).In the same day (between 12:01 am and midnight) returns to and re-verifies (
idme_status=verified) or (verification_workflow_status=verified).
That student’s data will not appear on the Status Change Report because their status the day before was verified and when the report runs at midnight, it will show verified. See the Use Cases section below for more scenarios to interpret the report.
How often is the Identification Verification Status Change Report data refreshed?
Verification data in the Superset report system is updated every night at midnight (12:00 am).
How often does a recurring Status Change Report run and delivered to the college?
Colleges have the option to request a recurring daily or weekly Identification Verification Status Change Report configured for their college or district.
The daily report is run and delivered to the college or district daily - Monday through Sunday - and will contain all instances where the idme_workflow_status or verification_workflow_status field has a different value than the prev_idme_workflow_status or prev_verification_workflow_status field at midnight (12:00 am) on the previous day.
The weekly report is run and delivered to the college or district weekly on Mondays, containing all instances where the idme_workflow_status or verification_workflow_status field has a different value than the prev_idme_workflow_status or prev_verification_workflow_status field at midnight (12:00 am) each day.
Requesting the Report
To request a recurring daily or weekly Identification Verification Status Change Report, please have an authorized director-level college or district staff member submit a request by email to the CCCTC Staff Support team at staffsupportccctc@openccc.zendesk.com, or by contacting your College Experience Manager (CEM) directly at cems@ccctechcenter.org.
The email request should include the name of the authorized recipient, their email address, and whether you prefer the daily or weekly change report.
Use Cases
User Status | Scenario | Trigger or Event |
|---|---|---|
First-Time Verified |
|
|
Staff-Verified |
|
|
Verified to Unverified |
|
|
Verified to Unverified to Verified |
|
|
Note: If a verified student becomes unverified and then re-verifies all within the same day before midnight, a record of those changes will not appear on the Identification Verification Status Change Report because the student’s new current status (current_idme_workflow_status = Verified) is once again the same as their previous status (prev_idme_workflow_status = Verified) from the previous day at midnight. Thus a record of the change is not included on the report. However, both change event notifications are sent to the college via SuperGlue. | ||
If a new or returning student who has never completed the verification process previously, verifies their identity today at 10:00am - and does not update any of their Account Profile information between 10:00am and midnight, their current workflow status at midnight will be “verified” - which is a change from their previous status which was ‘never verified’ (which appears as null or blank on the report).
Known Issues
The following is a list of known issues relative to the status change notifications. Fixes for these issues are currently under-development now. A planned release will be communicated to the colleges in the coming weeks.
Type or Format | Issue | Fix |
|---|---|---|
Change Logic | Currently, a manual change or update to a Verified student’s middle name <middle_name> in their Account Profile will cause them to become unverified and will trigger a status change notification. This is an error. Middle Name should not be included in verifications status changes. | The CCCTC is working to remove Middle Name <middle_name> from the verification status change logic |
Events Payload | Several Account Profile fields that affect a student’s verification status are not included in Event payload schema. These fields are needed to identify the reason behind a status change that triggered the delivery of an UPDATE_PROFILE event.
| The CCCTC is working to add the following data fields to the Events payload schema:
|
Events Payload | The Events payload schema is lacking the full suite of Account Profile fields needed to interpret the UPDATE_PROFILE event type notification, whether the event pertains to verification status or not. The fields that need to be added are:
| The CCCTC is working to add the following data fields to the Events payload schema for the UPDATE_PROFILE event type:
|
Identification Verification Status Change Report | Internal issue causing the intermittent display of duplicate status change records on the Identification Verification Status Change Report. | This is an internal IdP system issue currently being investigated and prioritized. Work-around will be provided to colleges until a solution is confirmed. |
Identification Verification Status Change Report | An issue regarding some verification timestamps being overwritten for verified students when they did not reverify or make multiple sign-ins to after being verified. | Spike: Developers are investigating why some timestamps are being overwritten when verified students are not reverifying or changing Account data. |
See the Identification Verification Status Change Data Fields document for all status change data specifications across all notification vehicles.
Request the Identification Verification Status Change Report
Colleges may request access to the Identification Verification Status Change Report(s) by sending an email request directly to CCCTC Staff Support at staffsupportccctc@openccc.zendesk.com or by contacting your College Experience Manager (CEM) at cems@ccctechcenter.org.
Note: the report is only available for students who verified through ID.me. Data for students who verified with DMV Wallet will be added in a future release.
Get Identification Verification Status Change Notifications via SuperGlue
While the report provides your student verification changes in user-friendly format, ID verification changes can also be delivered in real-time to a new Events table via SuperGlue. Get the latest SuperGlue schema update that implements the Events table by contacting your College Experience Manager (CEM) at cems@ccctechcenter.org, or by contacting CCCTC Staff Support directly at staffsupportccctc@openccc.zendesk.com.