In this article

For Colleges: Parent Handraisers Data Access and Delivery

Parent Handraisers are parents and guardians on Scoir who have opted in to share their contact information with your institution so that you can also reach them outside of Scoir. Treat these records as a genuine invitation to engage the household through your other channels, and as a data point to help qualify or gauge interest.

This guide covers how to access Parent Handraiser data in Scoir, including automated delivery and manual downloads.

Requirements

Parent Handraisers is available as an early access trial through June 2027. Colleges partners must be on a Starter, Growth, or Enterprise plan and opt in to participate. International partners are not eligible at this time.

Users must also have the correct role(s) assigned to their account:

  • Handraisers role – Required for all users who need to view and download Handraiser data directly in Scoir
  • Handraisers role + Account Administrator role – Required to set up automated delivery of Handraiser data via SFTP Configuration

How Parent Handraiser Data Is Delivered

Parent Handraiser data can reach you in two ways:

Combined Student + Parent File

Standalone Parent File

Who gets it

All institutions in the trial

Trial institutions that request it from their CSM

Which parents are included

Parent Handraisers whose student has also raised their hand for your college

All Parent Handraisers, whether or not their student has raised their hand

Where you can access it

Your existing Student Handraisers file

A separate nightly file

Best for

Nesting parent relationship contacts within student records

Reaching parents as soon as they raise their hand, even before their student does

Combined Student + Parent File

Once your CSM turns on the trial, your Student Handraisers file will include parent contact information for any student whose parent or guardian has also raised their hand for your college. If a student's parent hasn't opted in, that student's parent fields will be blank.

See more info on Student Handraisers file setup and delivery

Because we're adding the data to an existing file, you won't have additional setup to do in Scoir, but you will need to update your CRM import to map the new data columns.

Included Data Fields

Field Name

Field Type/Format

Description

Parent_Scoir_ID

TEXT

Unique parent identifier

Parent_First_Name

TEXT

Parent first name

Parent_Last_Name

TEXT

Parent last name

Parent_Email

TEXT

Parent email address

Parent_Mobile_Phone_Number

TEXT

Parent mobile phone number

Parent_Relationship_To_Student

SELECT_ONE

Relationship type. Values are: Mother, Father, Stepmother, Stepfather, Legal Guardian

Parent_Residence

SELECT_ONE

U.S. State/Territory two-letter abbreviation or Internationalif parent resides outside the U.S.

Parent_Date_Interest_Shared

YYYY-MM-DD

The date the parent opted in to share their contact info. For the initial data file, this will reflect the original opt-in date. For all subsequent imports, it will match the date the data was delivered.

Parent_Interest_Origin

SELECT_ONE

A calculated value of parent_suggestion if the parent has suggested your college to their student or student_follow if the student added your college to their list without a parent suggestion.

Using Slate? Update the mappings in your Scoir Handraisers source format to include the new parent fields. Our recommendation is to map parent data to relationship fields. You will need to create custom relation-scoped fields for Scoir Parent ID and Scoir Parent Interest Origin. Prompts can be created to store Parent Interest Origin values, see table above.
When parent info appears in the file

A student and their parent can raise their hand at different times. Here's how each case is handled:

  • The student raises their hand first. The student is delivered in that night's file as usual, with the parent columns blank. When the parent opts in later, the student is sent again in that night's file, this time with the parent's contact info filled in.
  • The parent raises their hand first. Scoir holds the parent's info until the student also raises their hand. Then the student and parent are delivered together in that night's file.

A student handraiser can have any number of parent or guardian handraisers linked to it.

Because a student can appear in more than one file, set up your CRM import to update existing records instead of always creating new ones. Use Scoir ID as the match key.

See sample Handraisers file with parent contact info

Standalone Parent File

The standalone Parent Handraisers file includes every parent who has raised their hand for your college, whether or not their student has. You get parent contacts as soon as they opt in and can start engaging families earlier.

Included Data Fields

Field Name

Field Type/Format

Description

Scoir_ID

TEXT

Unique student identifier

College_Name

TEXT

The name of the college account where the student expressed interest. Useful for tracking interest across multiple accounts or campuses within a single CRM.

Parent_Scoir_ID

TEXT

Unique parent identifier

Parent_First_Name

TEXT

Parent first name

Parent_Last_Name

TEXT

Parent last name

Parent_Email

TEXT

Parent email address

Parent_Mobile_Phone_Number

TEXT

Parent mobile phone number

Parent_Relationship_To_Student

SELECT_ONE

Relationship type. Values are: Mother, Father, Stepmother, Stepfather, Legal Guardian

Parent_Residence

SELECT_ONE

U.S. State/Territory two-letter abbreviation or International if parent resides outside the U.S.

Parent_Date_Interest_Shared

YYYY-MM-DD

The date the parent opted in to share their contact info. For the initial data file, this will reflect the original opt-in date. For all subsequent imports, it will match the date the data was delivered.

Parent_Interest_Origin

SELECT_ONE

A calculated value of parent_suggestion if the parent has suggested your college to their student or student_follow if the student added your college to their list without a parent suggestion.

Graduation_Year

YYYY

Year of the student's high school graduation date.

See sample standalone Parent Handraisers file

Receiving the file
  • If you have automation turned on (Easy Slate SFTP or Manual SFTP): You don't need to configure anything else in Scoir. The standalone file is picked up automatically through your existing SFTP connection. In Slate, it's delivered to the Scoir Parent Handraisers (Coming Soon!) source format.
  • Manual Download: The standalone file is on the Handraisers > Files page with your other Handraiser files.
Even with automation on, you can download the standalone file from Handraisers > Files at any time.
Considerations for receiving parent data separately

With the standalone file, you'll often receive a parent before their student is in your CRM. The student may raise their hand in Scoir later, or reach you another way, such as an inquiry form, event registration or application. Plan for two things:

  1. Keep parent records separate until the student is known. Store standalone parents in their own dataset so you can engage them right away without creating placeholder student records.
  2. Link the parent to the student once both are known. When the student shows up in your CRM, connect the parent to that student and stop engaging the parent dataset record separately.
Matching fields

Scoir provides fields you can use to match a standalone parent to a student record and to an existing parent relationship record:

Match on

Use it to

Notes

Scoir_ID

Find a matching student record for the parent

Most reliable when the student came to you through Scoir, for example as a Student Handraiser or through application materials

Parent_Scoir_ID

Find a matching parent relationship record nested under a student

Most reliable matching key but only useful if the student is a Handraiser too

Parent First Name + Last Name + Email

Find a matching parent relationship record nested under a student

Use when the parent information you're matching to came from outside Scoir, such as the admission application, and there's no Scoir identifiers to match on

Setting up Slate for the standalone file

In Slate, the standalone file is processed by its own source format, Scoir Parent Handraisers (Coming Soon!), not the Scoir Handraisers source format.

The Scoir Parent Handraisers source format requires a custom Parents/Guardians dataset in Slate before it can consume the file. You can copy in a preconfigured dataset with a Suitcase.

  1. Import the Parents/Guardians dataset. In Slate, go to Database > Suitcase, click Import, and enter this Suitcase ID: 568e6cde-0a0e-4cf6-8aaa-e2a6d74eb21f:sco
  2. Review the dataset fields. Confirm the dataset includes fields for Parent_Scoir_ID, Scoir_ID and a Matched to Student flag (used in Marking parent records as matched).
  3. Map the source format (Coming Soon!). Go to Source Formats, open Scoir Parent Handraisers, and click Edit Mappings. Map each source field to its destination in the Parents/Guardians dataset, and click Save.
  4. Activate the source format. Set the Remap Active status to Active.

Linking parent records to students

Once parents are in the Parents/Guardians dataset, set up a recurring export/import so each parent is connected to their student when the student becomes known to you, whether through Scoir or another source. The process creates a relationship record on the student's person record from the matching parent dataset record.

  1. Build a query on the Parents/Guardians dataset. Include parent records where Matched to Student is not set.
  2. Join to person records. Match each parent to a student using Scoir_ID. For students who reached you outside Scoir, match the parent's First Name + Last Name + Email against existing relationship records.
  3. Export the matched results. Include the student's Slate ID or Scoir ID plus the parent's contact fields and Parent_Scoir_ID.
  4. Import the export into a source format that creates or updates relationship records on the matched student.
  5. Schedule it. Run the export/import on a recurring schedule, such as nightly after your Scoir files load, so parents are linked as soon as their student arrives.

Marking parent records as matched

After a parent is linked to a student, flag the original Parents/Guardians dataset record as matched. This tells your team, and your communication rules, that the parent should now be engaged through the relationship record under the student, not as a standalone contact.

  1. Include the dataset record ID in your linking export. Add the Parents/Guardians dataset record ID to the export in step 3 above.
  2. Set the Matched to Student flag. When the import runs, set Matched to Student to Yes on the dataset record (and, optionally, a Matched Date).
  3. Update your populations and communications. Exclude matched dataset records from standalone parent outreach so families don't get duplicate messages.
Not using Slate? The same approach applies to other CRMs: store standalone parents separately, match them to students using Scoir_ID, Parent_Scoir_ID or name + email, link them once the student is known, and flag the original record as matched.

Joining the Trial

To join the Parent Handraisers trial, tell your Customer Success Manager (CSM) you're interested. They'll turn it on for your institution.

Every institution in the trial receives the combined Student + Parent file. If you'd also like the standalone Parent file, mention that to your CSM too. Setup depends on how you receive Scoir files, such as Easy Slate SFTP, Manual SFTP or Manual Download, so your CSM will go over the options with you and help get it turned on.

Not sure who your CSM is? Reach out to Support@scoir.com and we'll connect you.

How did we do?

For Colleges: Understanding Scoir Data in Your CRM

Contact