Pearson SAFT Recruitment and Test Administration Procedures

Meeting Logistics and Standard Operating Procedures

  • Monthly Call Cadence: A recurring monthly check-in is established as the minimum requirement for the team. This frequency is deemed sufficient for project oversight without becoming excessive.

  • Pre-Meeting Requirements: To ensure efficiency, an agenda must be provided in advance of every monthly meeting. Additionally, Site Solutions must provide a summary of work completed since the previous meeting to allow for targeted questioning and discussion.

  • Meeting Notes Policy:

    • Meeting notes must be captured for every session to ensure accountability.

    • Completed notes should be uploaded to the dedicated Pearson folder within a few days (typically 11 to 22 days) after the call.

    • Daryl Weinstein and Gabrielle Boltz emphasize the importance of these notes for future reference regarding decisions and discussions.

  • Transparency and Access: Site Solutions has access to the Pearson SharePoint folders and is expected to place all deliverables, including reports and notes, there for ongoing shared access.

Technological Tools and Administrative Access

  • Microsoft Copilot: The team uses the Copilot AI feature within Microsoft Teams to capture transcriptions and notes.

    • The Copilot button is a blue icon featuring two white stars located in the top corner of the interface.

    • Transitioning to AI-assisted note-taking is preferred because it is considered more accurate than human documentation.

  • Pearson Dashboard:

    • A centralized dashboard is used to track the schedule and upcoming administration dates.

    • New users, such as Riley Kahlon, must request access to the dashboard and notify Daryl Weinstein if they encounter any access restrictions.

  • SharePoint Folder Structure:

    • The primary folder path for field test operations is the "From Pearson" folder, specifically the "Standalone Field Test Files" subfolder.

    • This folder contains email templates, student rosters, and administration manuals.

Strategic Recruitment and Demographic Objectives

  • Fairness and Diversity: The recruitment of schools is driven by the goal of making tests fair for all students. This requires capturing specific demographic data.

  • High-Priority Demographics: Historically, finding schools with significant Asian and African American populations for testing is the most challenging. Consequently, recruitment efforts must eventually target these groups specifically.

  • Demographic Tracking:

    • Reports must eventually include the demographics of schools that show interest.

    • Data can be gathered at the district level (e.g., Smith Unified School District might be 50%50\% White students, 40%40\% Asian students, and 2%2\% Black students).

    • A target goal example provided by Gabrielle Boltz involves balancing populations, such as reaching 1,0001,000 Black students if recruitment is currently skewed toward 4,0004,000 White students.

    • Tools for tracking demographics include the website "Great Schools".

  • School Qualifications: The project accepts public, private, and charter schools. While some automated searches pull up correctional facilities, the focus remains on traditional K-12 environments. Schools with combined levels (e.g., K-8) are eligible, but only the specific target grade (e.g., 8th8\text{th} grade) can participate.

Recruitment Status and Database Management

  • Personnel Changes: Jalynn is no longer with Site Solutions. Riley Kahlon and Sarah DeJoy are currently covering Jalynn's schools while a replacement is sought. Nathalie is the point of contact for staffing updates.

  • Recruitment Metrics (as of August 12, 2026):

    • Riley Kahlon has added approximately 3,0003,000 new contacts (precisely 2,9552,955) to the database.

    • Sarah DeJoy has added 508508 new contacts.

    • A robust report detailing these numbers is due to be sent by Friday, August 14, 2026.

  • Database Cleanup: Riley Kahlon is conducting "detective work" to replace bounced emails with updated contact information. This involves visiting individual school websites as many databases currently contain outdated information.

  • Reporting Requirements: Future reports will be incremental rather than just cumulative. They must detail what occurred since the last update, specifically:

    • Number of sends, opens, and link clicks.

    • Number of bounces and "out of office" replies.

    • Specific tracking of personal responses and schools that requested to be removed from lists.

    • A specific section for calls made, as phone outreach is prioritized for September when schools are fully back in session.

Financial Oversight and Historical Lessons Learned

  • Finance Contact: Kristina Zampella is the designated person for details regarding financial distributions to schools.

  • Payment Verification: Past experiences with paper VMRT field tests revealed issues where payments meant for a specific school were sent to the district instead. It is critical to confirm that the specific individuals or schools expecting payment actually receive the funds (direct deposit or check).

  • Return Participation: Schools that have participated in previous years are encouraged to re-test. Examples of previously participating schools include Brubaker and Gainesville. Brubaker, under Gina Hall, is one entity identified as being interested in returning.

Upcoming Test Administration: Palmas/Thomas

  • Target School: The next school scheduled for administration is Palmas (also referred to as Thomas).

  • Initial Outreach: A "Thanks for Signing Up" email must be sent next week (starting August 17, 2026). This email must include the Student Roster Template Excel file.

  • Template Verification:

    • Roster data must be submitted using the standardized Student Roster Template.

    • Email templates contain placeholders for demo high school testing dates and specific next steps.

    • It is mandatory to manually replace these example dates with actual administration dates to avoid previous errors where example text was sent to schools.

  • Other Pending Schools: Las Vegas expressed interest in participating in the fall but needs to be contacted to establish specific testing dates.

Communication Protocols and Documentation

  • Blind Copy (BCC) Requirement: When Site Solutions sends administration emails to schools, they must BCC Daryl Weinstein. This allows Pearson to verify that outreach has occurred without the school feeling monitored by the prime contractor.

  • Technical Setup Support: Subsequent emails to schools will involve instructions for TestNav setup and providing testing manuals. These are sent only after the school has returned the completed roster file.

  • NDA and Acknowledgements: Before administration starts, schools must complete the Non-Disclosure Agreement (NDA) and other required acknowledgement documents.

Schedule and Future Deliverables

  • Sarah DeJoy's Report: Expected on Friday, August 14, 2026.     

  • Next Meeting: Scheduled for Monday, August 17, 2026, at 9:00 AM9:00\,\text{AM} Eastern.

    • This will be a 3030-minute to 11-hour technical call to walk through the email templates and folder organization.

    • The team is expected to familiarize themselves with all documents in the SharePoint folder before this meeting.

  • Recruitment Timeline: Recruitment in March, April, and May is critical as this is when schools finalize their master schedules for the next year. Testing occurring in October is possible but difficult for schools to coordinate if not planned in the spring.