Assessment & Analytics
Technology and operations decisions where district leadership, IT, and stakeholders must align.
This interactive experience is the shipped product itself — the same application code customers run in production, mounted read-only in your browser over a real sample journey. Not a video, not a mockup: because the demo and the product are one codebase, it can never drift from the real thing.
Inside this journey
-
Outcome Discovery
Align on student learning goals, current assessment cadence, data systems, stakeholders, and measurable success signals for early intervention.
Discovery Questions
A quick shared starting point
- Briefly describe your role and primary responsibility for assessments and instruction
- On a typical semester, how frequently does your district run interim or benchmark assessments
- Which grade bands and subjects are highest priority for earlier intervention in your district
- Who on your team owns assessment scheduling, vendor integrations, and teacher training
- Tell me about a recent assessment cycle that went well and one that did not, and why
Where your current assessment process falls short
- What single result from your current interim testing would make you conclude the program is failing and prompt you to stop it
- How long does it currently take from test administration to teacher-facing, student-level results and reports
- When results arrive late, which instructional decisions are most affected and how does that show up in classrooms
- Which parts of assessment data do teachers trust least, standards alignment, item clarity, scoring, or subgroup reporting
- If your current approach could not report subgroup results by the start of the next grading period, would that stop your adoption
Hidden costs and the student impact you miss
- How many students each year do you estimate fall through the cracks because interim data arrives too late to change instruction
- Describe the most common equity gap you discover only after state tests and what it costs in interventions or remediation
- Who bears the budget or staffing burden when late or low-quality assessment data creates remediation needs
- What are the compliance or reputational consequences when achievement gaps go unnoticed until state results arrive
- If a new interim program reduced late-identified students by 50 percent, what internal barrier would still prevent you from adopting it immediately
How decisions actually get made here
- Which stakeholder on your team has a veto over assessment programs, and why
- Who has final sign-off on budget, procurement, and data sharing agreements
- Walk me through the last time you selected an assessment vendor, who influenced the choice, and what swung the decision
- How do teachers and principals get involved in pilot and adoption decisions, if at all
- If the steering committee required a pilot, would a six week pilot that produces teacher adoption and usage metrics be sufficient to move to contract
Technical and data practicalities that make or break rollout
- Which integration failure — SIS, gradebook, authentication, or reporting — would kill the timeline for delivery
- What student information systems, gradebook, and LMS endpoints must we integrate with for a minimal viable rollout
- How accessible and clean are your student demographic, enrollment, and historical assessment records for mapping
- Who owns API access, SFTP credentials, and data extracts in your organization
- If API access is not available and we must rely on nightly file drops, would that extend your minimum acceptable go-live date beyond your target window
The alternatives you are weighing
- What would have to be true about your current approach for you to keep it instead of moving to an external assessment platform
- Which other solutions or internal options are you actively evaluating
- Who is the incumbent for interim assessments and analytics today
- What price, timeline, or proof point would make you choose the internal build instead of a vendor
- If the incumbent committed to a two week delivery of a new reporting dashboard, would that stop your procurement
Success signals and acceptance criteria
- What single measurable outcome from a pilot would make your executive team sign a full contract within 30 days
- Which metrics do you require for teacher adoption and instructional use during a pilot
- How soon after administration must teachers see item-level and standard-level results to consider them useful
- Who must sign acceptance of data mapping, integration, and security before configuration begins
- If the pilot meets targets but legal delays data sharing for eight weeks, would you proceed to full deployment
Timeline, resources, and concrete next steps
- Name the calendar event that would force you to delay a fall deployment
- How many full time equivalents can your team commit to configuration, training, and data validation during deployment
- Which district calendars or assessment windows are non negotiable and must be respected in the assessment calendar
- Who will be the named owners for configuration, data extracts, and teacher training during rollout
- If you could get a guaranteed configuration slot within six weeks, would you be ready to sign commercial terms within two weeks
-
Solution Experience
Walk through how formative, interim, and benchmark assessments plus teacher-facing analytics deliver timely, specific instructional signals in the buyer's context.
Solution Experience
- Solution Experience Session — Assessments to Instruction
- Confirm the current state and its cost
- You confirm the demonstrated workflow would have identified the students you said were off-track and enabled next-day targeted instruction.
- Seller to run a sample assessment using the buyer's referenced grade and standards and deliver the resulting teacher-level analytics report before the follow-up meeting.
- Orientation: end-to-end assessment-to-instruction flow
- You agree on the pilot scope, acceptance criteria, and the specific evidence needed to move toward a decision.
- Seller to draft a one-page pilot plan with timeline, success metrics, and minimal data requirements for an initial roll out.
- Proof: run a real scenario using your context
- Buyer to provide a representative student roster, one recent assessment result file, and the list of priority grades and subjects for the pilot.
- You confirm the data access and roster details required for an accurate pilot and deployment plan.
- Buyer to identify a named pilot owner and confirm the preferred assessment window dates for the pilot.
- Show SIS/LMS integration and equity disaggregation
- Validate the fit to your need
- Agree remaining evidence and pilot acceptance criteria
- Solution Experience Session
- Solution Experience Deck
- Solution Brief
- meeting
- slides
- document
-
Solution Scope
Define included modules (assessments, item bank, analytics, SIS/LMS integrations, training), responsibilities, timeline, and measurable acceptance criteria.
Scope Configuration
- Provision standards-aligned item bank
- Create custom interim and benchmark assessments
- Deliver online test administration
- Provide paper-based test materials and scanning
- Automated scoring with item-level results
- Setup teacher dashboards with specific item analytics
- Configure standards mastery tracking
- Generate student growth measurement reports
- Produce equity-disaggregated student and subgroup reports
- Integrate assessment data with SIS and LMS
- Enable API and data export feeds
- Deliver teacher training on data-informed instruction
- Configure assessment calendar and release windows
Scope Questions
Provision standards-aligned item bank
- Which specific set of learning standards should items be aligned to (name the adopted state standards or standards set and provide the file if available)?
- How many test items do you require per standard or reporting cluster (for example, 6 items per standard or 20 items per reporting cluster)?
- Do items need to be tagged with depth-of-knowledge (DOK) level and item type (selected response, short answer, constructed response)?
- Provide the format and filename of your existing blueprint or mapping file (for example, CSV with columns standard_id,item_id,depth) or indicate if we should build the mapping from scratch.
- Which grade bands and course codes must be included in the provisioned bank (list grades and course identifiers as they appear in your curriculum guides)?
Create custom interim and benchmark assessments
- List the assessment windows and target grades for each custom interim or benchmark (for example, Fall window: Grade 3-5 ELA; Winter window: Grade 6-8 Math).
- How many distinct forms do you expect per window (for example, 1 benchmark form and up to 3 curriculum-check forms)?
- Do you require the test blueprints to enforce items-per-standard ratios or percentage distributions across standard strands?
- Provide the maximum student test length in minutes for each grade band and the maximum number of items per student per administration.
- Identify any content constraints for custom assessments (for example, no items referencing district-specific textbooks, items must avoid culturally sensitive contexts in these standards).
Deliver online test administration
- Select the online delivery modes required for this engagement (secure browser, standard browser with proctoring, mobile-responsive browser, offline app).
- What is the expected peak concurrent student session count you need the platform to support during a single administration?
- List the permitted student device types and OS versions for online delivery (for example, Chromebook build X, Windows 10, iPad iOS 14).
- State the required turnaround SLA for item-level scoring availability after student submission (hours or days) for both selected-response and constructed-response items.
- Indicate whether remote proctoring, live proctor monitoring, or local proctor authentication is required and provide the proctoring protocol document if available.
Provide paper-based test materials and scanning
- Estimate the number of paper copies needed per form and per testing site for each administration window.
- Specify the scan template format required for your current OMR/scanner processes (OMR template ID, CSV mapping, or image-based scanning), and attach a sample if available.
- Identify the logistics documents you require with shipments (packing lists, school ID sheets, chain-of-custody forms) and provide example filenames or templates where possible.
- What is your expected scanner turnaround time for scanned forms to be uploaded and available in the platform (hours/days) after scanning at the district site?
- List any special accommodations for paper materials (large-print, Braille, read-aloud directions) and identify which forms require those accommodations.
Automated scoring with item-level results
- Indicate which item types will use automated scoring and which require human scoring (for example, selected response automated, extended response human/hybrid).
- How will you provide rubrics and scoring guides for constructed responses (upload rubric files, enter into an online rubric builder, or provide PDF scored exemplars)?
- What acceptance criteria will validate automated scoring accuracy for constructed responses (for example, 95% agreement with human scorers on a 200-sample validation set)?
- Who will supply exemplar responses for calibration and how many exemplars per score point do you commit to provide (for example, 10 exemplars per rubric level)?
- Are audit logs required for scoring decisions at the item and student level for compliance or appeals, and if so what retention period is required (months/years)?
Setup teacher dashboards with specific item analytics
- Specify which educator roles should have dashboard access (classroom teacher, interventionist, curriculum coordinator, principal) and any role-based data restrictions.
- How quickly after administration do teachers need to view item-level performance data (real-time, same day, next day) to inform instruction?
- What filters and cross-tabs must be available on dashboards (standard, student subgroup flags such as FRPL/IEP/ELL, previous intervention history, mastery band)?
- Select the visualizations you want on teacher dashboards to support instruction (item-response heatmap, mastery ladder, student diagnostic list, recommended next lessons).
- Indicate whether professional development microcontent should be embedded directly in the dashboard for each standard or item (yes/no) and what format (video, quick guide, exemplar lesson).
Configure standards mastery tracking
- Choose the mastery calculation model you prefer for standards (percent-correct threshold, IRT/Rasch mastery rule, or custom band thresholds) and provide any district thresholds.
- How often should mastery status refresh for each student (after each administration, nightly batch update, or real-time rolling calculation)?
- What numerical thresholds define mastery for the grade and subject (for example, Grade 3 ELA mastery = 80% correct on standard-aligned items)?
- Provide the reporting view required for PLCs to monitor mastery over time (for example, standards-to-student trend over last 3 administrations) and the export format needed.
- Identify any standards or sub-standards that should be excluded from automated mastery calculations (for example, elective standards or locally maintained standards).
Generate student growth measurement reports
- Which growth metric do you require (student growth percentile, value-added, scaled-score gain) and for which grades/subjects should it be calculated?
- How many historical administrations are available for growth baselining (for example, prior two years of interim data or only last year)?
- Provide details of any state or district growth models that must be honored (model name, formula, or specification document), or confirm if a vendor-recommended model is acceptable.
- What reporting cadence and delivery format do you need for growth reports (weekly dashboards, quarterly PDFs, CSV exports for SIS ingestion)?
- Identify any student groups that must be excluded from growth calculations for fairness or policy reasons (for example, newly enrolled students within 30 days).
Produce equity-disaggregated student and subgroup reports
- Which subgroup flags from your SIS must be included for disaggregation (for example, FRPL, IEP, ELL, race/ethnicity) and provide the exact field names used in your SIS export.
- How many subgroup cross-tabs are required on reports (for example, school x FRPL x grade) and which are highest priority?
- What minimum cell size threshold must be enforced to suppress small-n subgroup reporting for privacy (for example, hide cells <10 students)?
- Provide any equity-focused success signals or targets that reports should measure against (for example, reduce proficiency gap between FRPL and non-FRPL by 10 percentage points).
- List the export formats and frequencies required for equity reports to be shared with district leadership (for example, monthly PDF, CSV for data warehouse).
Integrate assessment data with SIS and LMS
- Provide the SIS and LMS names and API protocols you currently use and the export file examples (for example, OneRoster CSV, SIS export with columns student_id,school_id,grade).
- What exact SIS fields must map to platform fields for rostering and demographics (for example, local_student_id, state_student_identifier, FRPL_flag, IEP_flag)?
- What acceptance criteria will confirm a successful SIS integration (for example, 99% student match rate, nightly roster sync completed within 2 hours)?
- Which gradebook or LMS gradebook mapping is required (pass/fail, percent score, item-level entries) and provide a sample gradebook schema if available.
- Identify any compliance constraints for data sharing (FERPA-required fields, local privacy agreements, or district data-sharing addenda) and attach the controlling document if available.
Enable API and data export feeds
- Specify the export feeds you require (student-level CSV, item-level response JSON, aggregated dashboard API) and the delivery cadence (real-time, nightly, weekly).
- What authentication protocol must the API support for your environment (for example, OAuth2, API key, SAML-based token) and who will provide access credentials?
- How many destination endpoints must we configure for exports (for example, SIS, district data warehouse, third-party analytics) and provide endpoint URLs and required field mappings.
- What throughput and latency SLAs do you require for exports or API responses during peak load (for example, under 5 seconds for dashboard API, nightly export completed within 2 hours)?
- Indicate your retention and archive requirements for exported data and API logs (retention in months/years and archival storage format).
Deliver teacher training on data-informed instruction
- Which teacher cohorts need training by role and grade (for example, Grade 3 classroom teachers, K-2 interventionists, principals) and how many participants per cohort?
- What training delivery models do you prefer (live in-person workshop, live virtual session, asynchronous microlearning modules) and which standards should be emphasized?
- How will training acceptance be measured for sign-off (for example, teacher competency checklist completion, demonstrated use of dashboard in 3 lessons)?
- List the artifacts you expect at training completion (for example, teacher competency checklist, sample lesson plans aligned to item analytics, go-live checklist).
- Identify any out-of-scope items for training under a fixed-fee engagement (for example, ongoing coaching, classroom modeling, custom content creation) so expectations are clear.
-
Mutual Commit
Finalize commercial and legal terms, data sharing and privacy requirements, integration commitments, and go/no-go acceptance criteria.
Agreement Modules
- Master Services Agreement (MSA)
- Statement of Work (SOW)
- Subscription Order Form
- Data Processing Agreement (DPA)
- Integration and Data Transfer Addendum
- Acceptance Criteria & Go/No-Go Checklist
- Public Sector Procurement and Security Rider
- Change Order Agreement
-
Deployment
Lock readiness facts and configuration values before execution begins.
-
Pre-Deployment Readiness
Confirm concrete readiness facts — SIS/LMS access, data extracts, assessment windows, named owners, and timeline constraints required before configuration.
Pre-Deployment Questions
Environment and site access
- Is the buyer's production SIS environment available for integration testing (roster, demographics, enrollment)? This determines whether we can start end-to-end mapping validation.
- If production access is not yet available or is 'Planned', what single date or blocker should the deployment team schedule around? (Provide one date or one short blocker statement so we can set the first integration milestone.)
Data and configuration readiness
- Has the buyer confirmed a single source-of-truth per required dataset (roster, interventions, prior assessment history, demographics) so field mappings can be finalized?
- Who will approve the field-mapping deliverable? Provide a single named approver (name and role). This approver will sign off on mappings before configuration starts.
People and ownership
- Who is the named technical contact responsible for coordinating SIS/LMS access and test extracts? (Provide one name and role—we will use this to request test files and schedule integration calls.)
- Who is the named assessment lead responsible for finalizing assessment windows and acceptance criteria? (Provide one name and role—this person will approve the assessment calendar and go/no-go.)
Timing and constraints
- Are there immovable blackout windows or assessment administration dates (state testing periods, district-wide events) that block integration work or data loads?
- Target go-live or pilot start date (and any immovable deadlines we must meet). Please provide one date and one short note on the critical deadline so we can align the rollout milestones.
-
Configuration Details
Capture exact configuration values the deployment team will use — integration credentials, field mappings, scoring rules, assessment calendar, and dashboard settings.
Configuration Details
Environments & endpoints
- Enter the production platform subdomain used for your district (format guidance: provide only the subdomain portion, e.g. 'springfield-district' or 'springfield-prod'; do not include 'https://' or a password). This exact value will be used to target the production instance.
- Select the deployment region for the production instance (Default: US-East). The deployment region determines hosting and data residency.
Integrations & authentication (SIS/LMS)
- Will you connect a Student Information System (SIS) to the platform for roster and demographics ingest? (Yes = we will configure an SIS connector to import rosters and demographics)
- Select the SIS integration method you will use for data delivery (choose the single option that matches how your SIS will provide files/endpoints).
- Enter the non-secret integration user identifier or client ID for the SIS connector exactly as it appears in your SIS or IdP (do NOT paste passwords or API secrets). Example: 'integration_user_123' or 'client-id-abc'.
- Choose how the SIS connector secret (password/API secret) will be handed off to the deployment team. We will NOT accept secrets in this form — the option selects the secure channel you will use at kickoff.
Field mappings (exact SIS field names)
- Enter the exact SIS field name containing the student's unique ID that the platform should use for matching (example format: 'student_id' or 'local_student_number'). This value is case-sensitive.
- Enter the exact SIS field name used for student grade level (example: 'grade_level' or 'enrollment_grade'). This value will drive roster grouping and assessment eligibility.
- Enter the exact SIS field name used for student race/ethnicity (primary demographic used for subgroup reporting and equity disaggregation). Example: 'race_ethnicity' or 'student_race'.
Assessment calendar & scoring
- Provide the canonical assessment calendar location the deployment should use (format: public URL to calendar file e.g. 'https://...' OR the exact filename you will upload to the deployment portal). If you will upload during kickoff, enter 'portal-upload' exactly.
- Use the platform default proficiency thresholds for reporting? Default thresholds: Beginning <60; Developing 60–74; Proficient 75–89; Advanced ≥90. (Select 'Yes' to accept defaults; select 'No' to provide custom cutpoints in the next question.)
- If you selected 'No' above, enter three ascending integer cutpoints (percentages) that define the thresholds between bands in this exact CSV format: '60,75,90' (where these numbers indicate the lower-bound percent for Developing, Proficient, Advanced). If you accepted defaults, leave this blank.
Dashboards, access, and reporting defaults
- Reporting timezone the platform should use for timestamped activity and report exports (format: IANA timezone string; default 'America/Chicago'). If you accept the default, enter 'America/Chicago'.
- Default teacher landing view on first dashboard load (select one). This sets the initial UI state for teacher accounts — owners can change per-user settings later.
Operational limits & retention
- Data retention period for student assessment records in days (Default: 3650 days = 10 years). Enter a numeric value (example: '3650')
- Maximum expected concurrent online assessment sessions for the district (Default: 1000). This numeric value informs capacity configuration — enter an integer (example: '1200').
-
Deployment
Execute integrations, data loads, automated scoring setup, teacher training, and phased rollout with clear owners and milestones.
-
-
Success
Validate outcomes against success signals, monitor adoption and equity-disaggregated results, and maintain a shared channel for issues and enhancements.
Success Reviews
- Go-live Health Check
- First Measurement Review
- Acceptance Gate Review (90-day)
- Quarterly Success Review
Issues & Enhancements
- Create a training refresh plan for schools below adoption target and schedule completion milestones.
- Produce a documented acceptance record that lists pass/fail status for each Solution Scope criterion.
- Capture a buyer signatory or documented buyer decision for the acceptance outcome where enterprise sign-off is required.
- Agree remediation items and dates for any unmet criteria so a close-out path exists.
- Publish the acceptance record with pass/fail status for each criterion and the documented buyer decision.
- Open remediation tickets for failed criteria with clear verification steps and target resolution dates.
- Schedule a follow-up verification check to confirm remediation completion within the agreed timeline.
- Adoption and usage trends
- Confirm adoption remains at or moves toward the teacher weekly active users target recorded in Solution Scope.
- Verify whether equity gaps are closing or widening and agree concrete interventions where gaps persist.
- Prioritize the top 3 operational or product improvements to address before the next quarterly review.
- Produce and circulate the quarterly metrics report with disaggregated results and trend charts.
- Add prioritized enhancement and remediation tasks to the backlog with target delivery dates.
- Re-confirm success criteria and owners
- Confirm deployment integrity and that integrations are passing expected data into the platform.
- Identify and document the top 3 onboarding or technical blockers that would prevent meaningful measurement.
- Agree immediate remediation steps and deadlines to prepare for the first measurement meeting.
- Publish a deployment validation report that lists integration endpoints, data samples verified, and any data gaps.
- Open tickets for each blocker with target resolution dates and required test steps.
- Schedule the First Measurement Review within the agreed 4-10 week window.
- Present first-data snapshot against Solution Scope targets
- Determine whether assessment scoring turnaround and teacher weekly active users are on track to meet Solution Scope targets.
- Document root causes for each shortfall and commit to corrective actions with target dates.
- Confirm the timeline and preconditions required to reach the Acceptance Gate at day 90.
- Deliver a data extract and short analysis showing per-school and per-grade values for the named metrics.
- Implement prioritized remediation steps for integration or training gaps and report progress before the acceptance gate.
- Update the acceptance gate timeline and circulate to stakeholders.
- Restate acceptance criteria and numeric targets
- Deployment and data migration validation
- Present outcome data for each criterion
- Outcome and equity-disaggregated results
- Diagnose root causes for any gaps
- Open issues, defects, and enhancement backlog
- Agree corrective actions, owners, and dates
- Early adoption signals and onboarding status
- Document pass or fail per criterion and capture decision
- Confirm readiness criteria for Acceptance Gate
- Agree remediation plan and resolution timeline for any failed criteria
- Agree next-quarter actions and verification steps
- Open technical and operational blockers
- Agree immediate remediation actions