Starting from Today: How Your Office Runs

• Walk me through a typical aid processing week in your office, from FAFSA intake to award notification
• In a typical month, how many student files does your team touch for verification or packaging? Options: Fewer than 500, 500 to 1,999, 2,000 to 4,999, 5,000 to 9,999, 10,000 or more
• Which systems do you rely on daily for student records, billing, and award letters Options: Your primary SIS, Your billing platform, Manual spreadsheets, Third party document portal, Other systems
• Who on your team currently owns packaging rules and updates when federal guidance changes Options: Financial aid director, Associate director or manager, Business office lead, Shared responsibility across roles, No single owner
• How confident are you that your current weekly throughput meets peak-period demand Options: Very confident, Somewhat confident, Barely keeping up, Not confident at all
• Describe the last moment when processing speed affected an enrollment decision or student complaint

Where the Current Setup Breaks Down

• If a single packaging error were cited in a federal program review, what would that reveal about your core process weaknesses
• How often do packaging or verification mistakes reach the student or the billing office each term Options: Multiple times per week, Weekly, A few times per term, Rarely, Never in recent years
• When an over award or reporting error happens, how long does it usually take to discover and correct it Options: Less than 24 hours, 1 to 3 days, 4 to 10 days, More than 10 days
• Which process step creates the most manual work for your staff—verification intake, packaging exceptions, disbursement reconciliation, or reporting Options: Verification intake, Packaging exceptions, Disbursement reconciliation, Federal reporting, Other
• What downstream cost or risk do you incur most often when those failures occur, for example audit exposure, refunds, or lost enrollment Options: Increased audit risk, Refunds and repayments, Student churn or enrollment loss, Extra staff overtime, Other
• Which single compliance gap would force you to pause awarding until it is fixed Options: Packaging engine rules not aligned with ED guidance, Disbursement reconciliation failing, Reporting inaccuracies, Lack of verified eligibility records, None would force a pause

Other Paths You Might Take

• Which alternatives to changing your current setup are you actively evaluating right now Options: Stay with incumbent vendor, Replace with another vendor, Build enhancements internally, Do nothing for now, Process redesign with same tools
• What would have to be demonstrably true about your current approach for you to decide to keep it through the next federal audit cycle
• Has anyone on your campus proposed solving verification or packaging internally instead of partnering with a vendor, and if so how far has that idea progressed Options: Yes, active plan in development, Yes, discussed but not started, No internal proposal, Not sure
• Which single proof point from another vendor would make you switch vendors immediately, for example a verified audit result or a packaging accuracy report Options: Packaging accuracy benchmark, Successful parallel run with another school, Signed reference from similar sized school, Demonstrated integration with our SIS and billing, Other
• If you stayed with your incumbent, what hidden costs or manual steps would need to be resolved to consider that success

Who Carries the Risk and How They Experience It

• Which role in your office most frequently escalates when packaging or disbursement issues appear Options: Financial aid director, Manager of operations, Verification lead, Business office contact, No single role
• Tell me about a recent case where a handoff between offices broke down and how the issue was resolved
• How many full time equivalents are dedicated to processing federal aid during peak season Options: Fewer than 3, 3 to 6, 7 to 12, 13 to 20, More than 20
• Which tasks are single person dependencies that would be at risk if that person left or was unavailable Options: Rule configuration, COD reconciliation, Manual packaging overrides, Federal reporting exports, None are single person dependencies
• If one key person left tomorrow, which capability would be impossible to maintain and force a timeline reset

Data and Integrations That Decide Timelines

• Which single integration or data feed, if not available, would prevent you from meeting Department of Education deadlines Options: Student information system feed, Billing/tuition interface, COD/COD-like origination feed, Third party document portal, None are blockers
• Do your SIS and billing systems provide APIs or automated exports we can use for nightly updates Options: APIs available and documented, Automated exports available, Only manual extracts, Not sure
• Who owns access to each system and how quickly can they grant integration credentials Options: SIS owner with immediate access, SIS owner with 2 to 4 week lead, Business office owner with delay, Third party vendor must approve, Unknown
• What format and cadence do your billing and student records teams prefer for award and enrollment updates Options: Daily API sync, Nightly batch export, Weekly CSV, Ad hoc manual updates
• Are there firewall, SSO, or security review processes that typically add time to integrations Options: Yes formal security review, Yes IT window for VPN and firewall changes, No formal process, Not sure
• Which single missing technical capability would require you to delay a pilot or go-live Options: No API for SIS, No COD-like endpoint access, No billing interface, No SSO for staff portal, None would require delay

Volume, Edge Cases, and Regulatory Triggers

• Where do volume spikes or unusual student populations create the highest risk of mispackaging or delayed awards Options: New freshmen surge, International students, Large scholarship cohorts, Short term certificates, Other
• How many manual packaging overrides does your team process in a typical peak week Options: Fewer than 50, 50 to 199, 200 to 499, 500 or more
• Describe an edge case that consistently requires manual review, for example cross enrollment or consortium agreements
• How quickly do you typically adapt packaging rules after a federal guidance change Options: Within days, Within 2 weeks, Within a month, Longer than a month
• If we asked you to run a parallel validation for one full term, what operational barrier would most likely prevent you from agreeing Options: Staff capacity, System access windows, Academic calendar conflict, Budget or approvals, None

Concrete Gates and Deal Killers

• Which operational constraint would force you to pause or cancel an implementation before it starts Options: Unable to provide SIS access, No budget approval, Legal or compliance hold, Staffing not available, Other
• Do you have a named technical contact and a named compliance signatory who must approve integrations and rule configurations Options: Yes both named, Technical named only, Compliance named only, Neither named yet
• What is your target window for a parallel run and final cutover, and who can lock those dates Options: Next available term start, Within 3 months, 3 to 6 months, 6+ months
• Which internal approvals are required before vendor access is granted, such as IT security, legal, procurement, or compliance Options: IT security review, Legal review, Procurement contract, Compliance signoff, All of the above
• Is there any contractual or regulatory precondition that would outright prevent a vendor from handling disbursement or reporting Options: Yes, regulatory restriction, Yes, existing contract limitation, No such precondition, Not sure
• Who is the final signatory for committing to compliance configurations, and if they withhold approval, will the project stop Options: Financial aid director signs, Dean or VP signs, Procurement signs, Committee signs, Project would stop if approval withheld

What Success Looks Like and How You Measure It

• If this engagement is a clear success at 12 months, which single metric will you point to first Options: Packaging accuracy rate, Time to award notification, Number of audit findings, Reduction in manual overrides, Improved enrollment yield
• What is an acceptable packaging accuracy target for your office, expressed as a percentage Options: 95%, 97%, 99%, 100%
• How quickly do you expect student award notifications to be issued after file clearance in a healthy state Options: Same day, Within 24 hours, Within 48 to 72 hours, More than 72 hours
• What level of reduction in staff time spent on manual verifications would you require to call this a productivity win Options: 25% reduction, 50% reduction, 75% reduction, Minimal change
• If a pilot meets the agreed accuracy and timing metrics, who on your side can approve moving to full implementation within 30 days Options: Financial aid director, VP enrollment, Procurement, Implementation steering committee, Not sure
• Which operational report or dashboard do you need from day one to feel confident in moving forward Options: Packaging audit trail, Verification completion dashboard, Disbursement reconciliation, Federal reporting readiness, Other

Next Steps and Early Commitments

• Which single early commitment from your side would accelerate scheduling a pilot or parallel run Options: Provide SIS credentials, Allocate 1 to 2 FTE for parallel run, Sign confidentiality agreement, Approve pilot budget, Other
• How ready is your executive team to prioritize a pilot within the next quarter Options: Very ready, Somewhat ready, Needs more briefing, Not ready
• Who else should we involve in the next conversation to clear technical, compliance, and budget questions Options: IT director, Business office lead, Compliance officer, Procurement, VP of enrollment
• Are there any upcoming regulatory deadlines or internal reporting cycles we must avoid when planning a pilot Options: Yes, major deadlines in next 30 days, Yes, within next 3 months, Yes, within next 6 months, No blocking cycles
• Finally, what would make you say yes to a pilot this month rather than later

• Solution Experience Session

• Confirm the current state and what it is costing
• You confirm the demonstrated packaging workflow removes the manual rework that caused over-awards and missed deadlines.
• Provide three representative student records including one known edge case and the current expected outcome for each.
• Prove automated packaging on a real student scenario
• You confirm the verification workflow provides a repeatable evidence trail that addresses your audit and compliance concerns.
• Run a sandbox proof using the provided scenarios and deliver the packaging outputs, verification exception log, and reporting extract before the follow-up session.
• Prove verification and document workflow on an edge case
• Document and confirm measurable acceptance criteria for packaging accuracy, verification completeness, and reporting parity.
• You agree on the specific artifacts and acceptance criteria required for a scoped proof run toward a buying decision.
• Schedule a follow-up validation session to review the sandbox proof results and close remaining questions on integration boundaries.
• Prove reporting and audit outputs
• Validate that this matches what you meant
• Agree next validation steps and acceptance evidence

• Solution Experience Session
• Solution Experience Deck
• Solution Brief

• meeting
• slides
• document

• Import FAFSA/ISIR Data
• Configure Need Analysis Engine
• Deploy Packaging Engine and Award Rules
• Deploy Student Self-Service Portal and Notifications
• Document Collection and Verification Workflows
• Integrate Disbursement with COD and Billing Systems
• Integrate with Student Information System (SIS)
• Implement SAP Monitoring and Alerts
• Automate Return of Title IV Calculations
• Automate Federal Reporting and IPEDS Export
• Configure Scholarship and Institutional Aid Management
• Deliver Compliance Dashboards and Audit Reporting
• Migrate Financial Aid Records and Reconcile
• Deliver Staff Training and Parallel Processing Validation

Import FAFSA/ISIR Data

• How many ISIR records do you process in a peak month? Options: Less than 1,000, 1,000-5,000, 5,000-20,000, More than 20,000
• Which ISIR transaction types must be ingested (initial, correction, reject, duplicate)? Options: Initial, Correction, Reject, Duplicate, Other
• Which ISIR fields do you treat as critical for downstream packaging (for example dependency status, student aid index/expected family contribution field, federal student aid flags)?
• Who in your office owns reconciliation between ISIR imports and NSLDS/ISIR flags?
• When do you require ISIR updates to be available (nightly batch, intraday, real-time API) to avoid packaging delays? Options: Nightly batch, Intradaily (2-4x/day), Real-time/API, Both batch and real-time
• Which ISIR fields are most frequently missing or rejected in your current imports and cause manual intervention?

Configure Need Analysis Engine

• Which federal need analysis method do you apply (pre-FAFSA simplification EFC, post-simplification student aid index, institution-specific adjustments)? Options: Pre-simplification EFC, Post-simplification SAI, Institutional adjustments applied
• How many custom institutional adjustments or overrides do you expect to configure in the need-analysis calculations? Options: None, 1-5, 6-20, More than 20
• Specify the ISIR or FAFSA-derived fields you rely on for need determination (income fields, household size, untaxed income fields, dependency indicators).
• Who approves changes to need-analysis formulas during an award year and how are change approvals documented?
• Which verification item sets (V1 through V5 or custom institutional checks) do you currently apply and need automated in the engine? Options: V1 Tax-related, V2 Income-Related, V3 Identity/Household, V4 Child Support/Other, V5 Custom items
• Which historical need-analysis exceptions occurred most often in the last award year that we should replicate or remediate?

Deploy Packaging Engine and Award Rules

• What award types and terms must the packaging engine support (for example Pell grant, SEOG, Direct Loan origination, institutional grant by term/year)? Options: Pell, SEOG, Direct Loan Origination, Institutional Grants/Scholarships, Other
• Which packaging priorities and bundling rules must be enforced (need-based before merit, loan limits per term, inter-term bundling)?
• Estimate the number of packaging rule variants across student populations (undergraduate, graduate, consortium, study-abroad) that will require separate configurations. Options: 1-3, 4-10, 11-25, More than 25
• List the specific thresholds that should trigger a manual packaging review (for example overaward greater than $50, COA variance >10%).
• Who signs off on final packaged awards prior to student notification, and how is that approval recorded?
• When should packaging engine behavior be validated in parallel with your legacy system (pilot term, full parallel for one term, ad-hoc validation)? Options: During implementation (sandbox), Pilot term (selected students), Full parallel for one term, No parallel required

Deploy Student Self-Service Portal and Notifications

• Which student-facing notifications must be supported in the portal (award letters, missing documentation requests, loan acceptance reminders, disbursement notices)? Options: Award letters, Missing document requests, Loan acceptance reminders, Disbursement notices, Other
• Which authentication methods do you require for student login (single sign-on via your SIS, institution email/password, multifactor)? Options: SIS single sign-on, Institution email/password, Multifactor authentication, OAuth/Social logins
• What award letter formats and regulatory disclosure elements must be included (net price, cost of attendance, grant vs loan breakdown, award conditions)?
• Who will maintain notification templates and business rules for auto-reminders and conditional messaging?
• Provide the expected volume of portal sessions per day during peak packaging cycles to help size performance (estimate). Options: Less than 500, 500-2,000, 2,000-10,000, More than 10,000
• Are there accessibility or FERPA-related controls required for student-facing documents (for example role-based redaction, consent capture, PDF archival requirements)? Options: Yes, No

Document Collection and Verification Workflows

• Which verification documents do you collect per student (for example IRS tax transcript, signed verification worksheet, proof of identity)? Options: Tax transcript, Verification worksheet, Identity documents, Other
• Estimate the average number of documents submitted per student during verification at peak (attachments or uploaded files). Options: 1-2, 3-5, 6-10, More than 10
• What specific rules or data mismatches trigger manual verification case assignment (for example ISIR income mismatch with tax transcript, dependency conflicts)?
• Who are the points of contact for resolving verification exceptions and uploading institutional documentation?
• Which document retention and e-signature standards must be met for audit (for example retain 7 years, time-stamped PDF, chain of custody)? Options: Retain 3 years, Retain 7 years, Retain indefinitely per legal hold, Other
• What percentage of verification cases are resolved without manual follow-up today (estimate) to set automation goals? Options: Less than 10%, 10-30%, 31-60%, More than 60%

Integrate Disbursement with COD and Billing Systems

• Which COD disbursement flows must be supported (origination, disbursement, cancellation, returns)? Options: Origination, Disbursement, Cancellation, Return to COD
• Which billing interfaces must synchronize with aid disbursement (student ledger entries, tuition refunds, third-party billing journals)?
• Who holds the COD trading partner credentials and the COD enrollment numbers required for test and production exchanges?
• When are your primary disbursement windows and how do they align with billing cycles and term dates? Options: At term start, Weekly windows, Monthly windows, Custom schedule
• Provide the required acceptance criteria for COD and billing integration testing (for example successful test cycle with 99.9% file acceptance, zero invoice mismatches).
• Are there existing encryption, file naming, or batching protocols your billing vendor or COD exchanges require (for example SFTP, PGP, batch header formats)? Options: Yes, No

Integrate with Student Information System (SIS)

• Which SIS tables and specific fields must be synchronized (enrollment status, program of study, term dates, student IDs)?
• Estimate the expected frequency of SIS synchronization required for packaging and disbursement (near real-time webhook, nightly batch, weekly). Options: Near real-time/webhook, Nightly batch, Weekly, Other
• What mapping rules for term coding and program codes must be preserved to avoid packaging and enrollment misalignment?
• Who provides SIS export files or API credentials and who will approve field-mapping decisions during implementation?
• Indicate acceptable latency for enrollment status changes to be reflected in packaging calculations (for example within 1 hour, within 24 hours). Options: Within 15 minutes, Within 1 hour, Within 4 hours, Within 24 hours
• Describe any SIS customizations, transforms, or nonstandard feeds that will require connector development beyond standard REST or batch endpoints.

Implement SAP Monitoring and Alerts

• Which Satisfactory Academic Progress (SAP) policies do you enforce (minimum GPA, pace of progression, maximum timeframe) and where are they documented?
• How frequently should SAP status be recalculated (end of term, weekly, on grade posting) for compliance and enrollment holds? Options: End of term, Weekly, On grade posting, Other
• What appeal and probation workflows must be automated including required documentation, deadlines, and committee review steps?
• Who reviews SAP override requests and which audit trail fields must be captured for federal program review?
• Indicate the alert channels and escalation thresholds for SAP violations (for example email to FA officer, registration hold after X days).
• Are SAP calculation inputs drawn from your SIS grade records, completed credits, and transfer credit feeds that require mapping? Options: Yes, No

Automate Return of Title IV Calculations

• Which withdrawal scenarios must trigger automated Return to Title IV (R2T4) calculations (official withdrawal, unofficial stop-out, leave of absence)? Options: Official withdrawal, Unofficial stop-out, Leave of absence, Other
• What institutional calendar types and payment period definitions (term-based, nonterm, weeks of instruction) must R2T4 use for pro rata calculations?
• Who signs off on R2T4 worksheets prior to returning funds to COD or lenders, and how is that sign-off recorded?
• List the rounding rules and treatment of institutional charges that must be applied when calculating earned versus unearned aid.
• When must R2T4 outputs be available relative to the student withdrawal date to meet your compliance windows? Options: Within 24 hours, Within 3 business days, Within 10 business days, Other
• Identify any historical R2T4 cases with special handling we must replicate (for example institutional refunds to third parties, consortium agreements).

Automate Federal Reporting and IPEDS Export

• Which federal reports do you file that must be automated (for example COD reporting, FISAP, IPEDS, cohort default data)? Options: COD reporting, FISAP, IPEDS, Cohort/default, Other
• What extract formats and field mappings does your IPEDS export require (CSV schema, included enrollment statuses, demographic flags)?
• Who reviews and signs federal report exports before submission to the Department of Education or IPEDS?
• Indicate the retention window and audit trail required for submitted federal exports (for example retain 7 years with time-stamped submission logs). Options: 3 years, 7 years, Retain per legal hold, Other
• List the recurring schedule and deadlines for each federal report you want automated (monthly, termly, annual).
• Do you have local or state reporting obligations that differ from federal schemas we must include in exports? Options: Yes, No

• Master Services Agreement (MSA)
• Statement of Work (SOW)
• Subscription Order Form
• Service Level Agreement (SLA)
• Parallel-Run Validation & Acceptance Plan
• FERPA Data Use Addendum (conditional)
• Change Order Agreement

• Go-live Health Check (Weeks 1-4)
• First Measurement Review (Weeks 4-10)
• 90-day Realization and Incumbent Wind-down Review (Around Day 90)
• Quarterly Compliance and Operations Review (Ongoing)

• Move approved enhancements into the upcoming release window and confirm expected delivery dates.
• Restate acceptance targets from Solution Scope
• Verify platform outcomes against the numeric targets recorded in Solution Scope and identify any remaining gaps.
• Confirm the incumbent system is decommissioned or retained in read-only with archived data and no active fallback use.
• Agree remediation timelines for any open gaps and add enhancement requests to the operational backlog.
• Produce the 90-day outcomes report mapping each metric to the targets recorded in Solution Scope and current status.
• Archive or migrate remaining legacy data and document the incumbent decommissioning state.
• Publish the prioritized remediation and enhancement list with target completion windows.
• Compliance dashboard and open exceptions
• Keep compliance exceptions within acceptable thresholds and close high-severity items within agreed timelines.
• Maintain or improve packaging accuracy rate and processing time toward targets recorded in Solution Scope.
• Ensure the enhancement backlog is prioritized and that operational defects are burning down at an acceptable rate.
• Publish the quarterly compliance and operations summary with outstanding items and due dates.
• Schedule the next validation snapshot and any required training refresh sessions.
• Reconfirm commitments and owners
• Deployment checklist items are confirmed complete or have an assigned remediation task and due date.
• Early adoption signals indicate baseline user activity or a clear remediation plan to reach baseline.
• Critical blockers are documented with remediation actions and target dates for closure.
• Distribute deployment health summary and migration logs for async review.
• Produce a prioritized list of critical defects and target closure dates.
• Confirm access to any missing data sources or integration endpoints required for stabilization.
• Present first measurement data
• Determine whether packaging accuracy rate and average processing time are moving toward targets recorded in Solution Scope.
• Document root causes for any metric gaps and agree on mitigation tasks with clear timelines.
• Confirm a date for the next validation snapshot to verify the effectiveness of corrective actions.
• Publish the first-measurement data pack and the root-cause analysis for the off-target metrics.
• Implement agreed configuration or process changes and schedule the validation run against the same metrics.
• Add any required enhancement requests to the tracked backlog for prioritization in the next quarterly review.
• Deployment and migration validation
• Operational metrics and trend analysis
• Diagnose root causes for any gaps
• Present consolidated outcome data
• Agree corrective actions and timeline
• Document remaining gaps and remediation plan
• Enhancement backlog and ticket burn-down
• Early adoption signals and usage patterns
• Validation plan for corrective actions
• Blockers and open issues triage
• Incumbent system wind-down confirmation
• Quarter action plan and next validation
• Enhancement requests and operational handoff
• Agree immediate remediation actions