Start Here: The People, Pace, and Pressure Behind Your Cycle

• Who is answering these questions and what is your primary role in admissions or enrollment operations? Options: Admissions Director, Enrollment Operations Manager, CIO/CTO, Registrar, Committee Chair, Other (please specify)
• Briefly describe your team: total FTEs working on application processing and the number dedicated during peak review weeks.
• Which application types are we talking about for this discussion? Options: First-year (UG), Transfer, Graduate, Professional programs (e.g., law, med), Scholarship or honors applications, Other
• What is your typical weekly intake during peak, and what is the largest single-day surge you’ve experienced (ballpark)? Options: Under 500/week, 500–1,000/week, 1,000–5,000/week, 5,000–10,000/week, 10,000+/day surge
• How do you currently track time-to-decision, applicant status visibility, and applicant experience metrics? Options: SIS reports, Spreadsheets/manual trackers, Homegrown dashboards, Vendor tools, We don’t actively track these

When Slow Decisions Cost You: A Straight Conversation About Yield

• How many admitted students do you estimate were lost last cycle because decisions arrived too late? Options: None/Appreciable, Fewer than 10, 10–50, 51–200, 200+
• Tell us about a recent cycle where delayed decisions clearly affected yield or enrollment—what happened, and what did you notice from applicants?
• How often do incomplete applications sit idle because applicants don’t know what’s missing or how to resolve it? Options: Almost always, Often, Sometimes, Rarely, Never
• When delays occur, how does it emotionally feel for your team and for applicants? Options: Frustrating and overwhelmed, Embarrassing or defensive, Resigned/used to it, Urgent and reactive, Other
• Which applicant-facing complaints do you hear most often about the application experience? Options: Confusing status, Slow responses, Lost documents, Payment/fee issues, Other

Where the Bottlenecks Live: Processes, People, and Systems

• If you could fix one thing today that would make the biggest dent in review time, what would it be? Options: Faster document intake, Clear applicant status visibility, Standardized reader rubrics, SIS integration and auto-decisioning, Committee scheduling/cohorting, Other
• Walk me through a single application’s flow at your institution—from submission to decision: who touches it and what tools do they use?
• Which of these systems are currently integrated into your admissions workflow? Options: Common App, Coalition/Common App supplements, Institutional application, Student Information System (SIS), Document storage (cloud/FTP), Payment processor, None of the above
• How confident are you that data remains accurate and complete after imports or migrations from legacy systems? Options: Very confident, Mostly confident, Somewhat confident, Not confident, Unknown
• Have you ever performed parallel processing (old system + new system) during a rollout? What worked and what failed?

Are We Just Managing Chaos—or Is There a Pattern We’re Missing?

• What recurring bottleneck do you tolerate because it’s ‘too political’ or feels too costly to change?
• Which stakeholder groups most resist workflow changes and why (readers, faculty, IT, leadership)? Options: Readers/evaluators, Faculty committee, IT/SIS team, Finance/Registrar, Executive leadership, Other
• How standardized are your reader scoring rubrics across programs and readers? Options: Fully standardized and enforced, Mostly standardized with exceptions, Very inconsistent, No rubric—freeform scoring
• What percent of final decisions rely on committee review vs. single-reader outcomes? Options: Nearly all committee, Majority committee, Mixed evenly, Mostly single-reader, Other
• When evaluation inconsistency happens, how do you detect and correct it today?

What Would Faster Decisions Actually Change for You?

• If every decision came three weeks earlier, what would be the most important business impact you’d expect to see? Options: Higher matriculation yield, Improved applicant satisfaction, Reduced reviewer overtime, Better coordination with financial aid, Other
• Describe concretely how a faster, clearer decision timeline would change your communication with applicants and internal partners.
• Which KPIs would you prioritize to prove success in the first 3, 6, and 12 months? Options: Time-to-decision, Yield/MAT rate, Incomplete application resolution time, Reviewer throughput per FTE, Applicant NPS/CSAT, SLA compliance
• What would need to be true about staff workload and morale for your leadership to call the deployment a success?
• Are there downstream processes (financial aid, housing, orientation) that would require changes to align with faster decisions? Options: Yes—multiple groups, Yes—one group, No, Unsure

Integration Dealbreakers, Migration Risks, and the Things That Keep You Up at Night

• Which type of integration or migration failure would be catastrophic for your operation? Options: SIS mapping errors/lost records, Common App ingestion failures, Lost or corrupted application documents, Broken decision transfers, Data privacy/compliance breach, Other
• Which systems or datasets represent the highest risk during migration (e.g., transcripts, test scores, legacy tags)? Options: Transcripts/grades, Test scores, Recommendation letters, Applicant status/history, Financial/fee records, Other
• Tell us about any past migrations or integrations that went poorly—what happened and how did you recover?
• What fallback or rollback procedures must be in place before you’d feel comfortable executing a peak-period cutover? Options: Parallel-run until validated, Frozen change window, Manual override path, Document-level reconciliation, SIS rollback plan, Other
• What regulatory or compliance constraints (FERPA, state rules) must we account for in integration and data handling? Options: FERPA, State privacy laws, Institutional policies, Third-party vendor agreements, None/Unsure

The Human Side: Readers, Training, and Making New Work Feel Familiar

• If your reviewers were candid, what part of a new reviewer workflow would they fear most?
• How do you currently onboard and train readers, and how long does it typically take for new readers to be productive? Options: Formal multi-day training, Short workshop + materials, On-the-job shadowing, No formal training, Other
• What incentives or accountability measures do you use to keep scoring consistent (calibration sessions, leaderboards, audits)? Options: Calibration sessions, Random audits, Performance metrics, Incentives/recognition, None
• How will you define and measure reviewer adoption success after rollout (e.g., % using new UI, scoring variance reduction)? Options: % active users, Time saved per reviewer, Scoring variance, Turnaround per application, Other
• Who inside your institution will champion adoption and who will be responsible for reader compliance? Options: Admissions Director, Operations Manager, Faculty Committee Chair, IT/Integration Lead, Other

Commitment, Timeline, and the Non-Negotiables

• If you had to name a single non-negotiable launch date or milestone, what is it and why can’t it move?
• What internal approvals (committees, finance, IT, executive) are required to start a proof-of-concept and what are their typical lead times? Options: Executive approval, Budget/finance, IT/security review, Academic committee, None/Unsure
• What budget decision process will be used and when is final funding likely to be available? Options: Already budgeted, Next fiscal cycle, Need one-off approval, Grant/external funding, Unsure
• Which risks would make you pause or delay a deployment even if the platform meets functionality tests? Options: Integration concerns, Reader resistance, Data migration uncertainty, Peak-season timing, Cost overruns, Other
• Realistically, what timeline do you see for: proof-of-concept start, parallel run, and full deployment? Options: Proof-of-concept: 0–1 months / 1–3 months / 3–6 months, Parallel run: 0–1 months / 1–3 months / 3–6 months, Full deployment: 3–6 months / 6–9 months / 9–12+ months
• Who will own post-deployment success (KPIs, ongoing improvements, support escalation)? Provide names/roles if possible.

Next Steps Together: Small Tests, Big Signals

• Which of these proof-of-concept objectives would give you the clearest yes/no signal to proceed (pick top two)? Options: Document ingestion speed/accuracy, Reader throughput and scoring consistency, SIS decision transfer accuracy, Applicant status visibility and CSAT, Peak-period cutover reliability
• Which measurable acceptance criteria would you require to greenlight full deployment? Options: <X days time-to-decision improvement, <Y% scoring variance reduction, 100% critical integration success, No data loss in migration, User adoption threshold met
• What would a small, low-risk pilot look like for you (scope, program, timeline)?
• How would we demonstrate that the platform genuinely reduces reviewer burden and improves applicant experience—what proof points matter most to your leadership? Options: Quantitative time savings, Improved yield, Positive applicant feedback, Reduced error rates, Other
• What concerns or questions should we anticipate from your stakeholders if we propose a pilot next month?

• Solution Experience Kickoff — Current State & Consequence Alignment
• Workflow Mapping Workshop — From Current Workflows to Outcome Scenarios
• Scenario Proof Sessions — Targeted Outcome Demos with Customer Data
• Parallel Run & Acceptance Criteria Planning
• Stakeholder Validation & Executive Summary

• Confirmed integration readiness and data quality checklist completed or scheduled.
• Assign SME owners for each scenario on both sides to prepare data and configuration.
• Intro: Rules & Validation Protocol
• Prove the future state for each prioritized scenario using customer data.
• Obtain explicit customer validation or documented objections for every scenario.
• Create a gap log mapping gaps to owners, priority, and remediation actions.
• Agree next steps toward a measurable parallel run or POC.
• Vendor to deliver recorded demo clips and a validation report mapping outcomes to success signals.
• Customer to review and confirm or annotate the gap log within 3 business days.
• Vendor to produce configuration change tickets for each validated gap and estimate effort.
• Both parties to schedule the Parallel Run Planning meeting with operational owners.
• Scope & Timebox
• A signed parallel-run plan with scope, dates, and responsibilities.
• Clear, measurable acceptance criteria tied to the success signals.
• Introductions & Meeting Rules
• Agreed monitoring and decision gates with named approvers.
• Customer to provision test API credentials and confirm SIS field mappings.
• Vendor to configure monitoring dashboards and baseline comparison reports.
• Both teams to finalize and distribute cutover and rollback procedures.
• Schedule training sessions for reviewers and operations staff prior to parallel run.
• One-sentence Current State & Consequence Summary
• Executive sign-off to proceed to the POC/parallel run or a short list of outstanding blockers with owners.
• Alignment on timeline, resource commitments, and success metrics at the sponsor level.
• Clear understanding of top risks and agreed mitigations.
• Collect executive approvals and circulate a one-page summary (state, consequence, target metrics, timeline).
• Vendor to finalize POC SOW and timelines for signature.
• Customer to confirm named approvers and resource availability for the run window.
• A single agreed one-sentence current-state statement signed off by key attendees.
• Numeric articulation of consequence (time, cost, yield) with supporting data sources identified.
• A prioritized list of success signals and measurable metrics to validate future-state claims.
• Clear list of artifacts/owners the vendor needs to build scenario proofs.
• Customer to deliver historical processing metrics, sample application records, and peak volume calendar.
• Customer to nominate core stakeholders and SMEs for scenario workshops.
• Vendor to draft the one-sentence current-state and a consequence summary for confirmation.
• Vendor to prepare template success-signal dashboard mock showing baseline vs target.
• Set date and logistics for Scenario Proof Session(s).
• Recap Kickoff Preconditions
• Validated workflow map capturing true end-to-end steps and owners.
• Clear list of bottlenecks with explicit operational consequences.
• One-sentence future-state outcomes defined for each prioritized bottleneck.
• A prioritized set of scenarios with required artifacts and owners assigned.
• Customer to tag and export the sample application records and anonymize PII for demo use.
• Vendor to produce detailed scenario definitions (inputs, expected behavior, success metric) for each prioritized scenario.
• One-sentence Current State
• Scenario A — Intake & Missing-Document Resolution
• Baseline vs Target Metrics
• Customer-led End-to-End Workflow Walkthrough
• Highlights from Scenario Proofs (Measured Results)
• Open Risks & Mitigations
• Identify Bottlenecks & Failure Modes
• Validation: Customer Confirms Outcome & Gaps (Scenario A)
• Quantify Consequence
• Data, Integration & Migration Readiness Checklist
• POC/Parallel-Run Scope, Timeline & Commitments
• Stakeholders, Peak Constraints & Failure Modes
• Define Desired Future-State Outcome for Each Bottleneck
• Reader Training, Rubric Alignment & Parallel Processes
• Scenario B — Reviewer Assignment, Scoring Consistency & Throughput
• Decision & Next Steps (Explicit Validation)
• Monitoring, Reporting & Acceptance Gates

• Configure Application Form Fields & Validations
• Enable Document Upload with OCR Classification
• Activate Automated Deficiency Notifications
• Provision Online Fee Payment & Reconciliation
• Deploy Reviewer Scoring Interface with Rubrics
• Launch Committee Decision Workspace with Ballot Capture
• Integrate SIS via Secure Bi-directional API Sync
• Migrate Legacy Applicant Records and Attachments
• Provision Role-Based Access, SSO, and MFA
• Enable Applicant Status Portal with Real-Time Updates
• Deploy Analytics Dashboards and Decision-Time Reports
• Configure Bulk Decision Notification Engine (Email/SMS)
• Enable Parallel Processing Mode for Pilot Cycles

Configure Application Form Fields & Validations

• Do you require separate application forms per program/department or a single unified form? Options: Single unified form, Separate program/department forms, Both (master + variants)
• How many unique form variants do you anticipate (used to estimate field mapping effort)? Options: 1, 2-5, 6-20, 20+
• Which field types will you need (select all that apply)? Options: Text, Numeric, Date, Dropdown/Single select, Multi-select, File upload, Calculated field, Signature/consent
• Do you need conditional logic (show/hide fields) or cross-field validations? Options: No, Basic conditional logic (field-level), Advanced conditional logic / cross-field validation
• What level of validation complexity is required (helps size rules and QA)? Options: Required fields and simple formats, Regex/format validations (e.g., phone, SSN), Cross-field rules and program eligibility logic
• Do forms require multi-language labels, localization, or right-to-left support? Options: No, Yes - multi-language, Yes - localization + regional formats

Enable Document Upload with OCR Classification

• Which document types will applicants upload that require OCR/classification? Options: Transcripts, Test scores, Recommendation letters, Personal statements/essays, Financial documents, Other
• Do you need automatic document classification (e.g., transcript vs. resume) and metadata extraction? Options: No, Yes - classification only, Yes - classification + data extraction (OCR)
• What languages and character sets must OCR support? Options: English only, English + major international (Spanish/French/German), Multiple languages including non-Latin scripts
• Maximum file size and allowed formats for uploads (e.g., PDF, JPG, DOCX)? Options: PDF/JPG/PNG only (up to 25MB), Include DOC/DOCX (up to 25MB), Custom limits/formats - describe in next field
• Are there retention, redaction, or PII masking needs for uploaded documents? Options: No, Yes - retention policy, Yes - redaction/masking required
• Do you require virus scanning, quarantine, or manual review workflows for flagged uploads? Options: No, Yes - automated scanning, Yes - scanning + manual quarantine workflow

Activate Automated Deficiency Notifications

• Which events should trigger deficiency notifications (select all that apply)? Options: Missing required documents, Invalid or unreadable uploads, Incomplete form fields, Missing fee payment, Other
• What channels should deficiency notices use? Options: Email, SMS/text, In-portal notification, Optional physical mail
• Do deficiency notifications require templated messaging with personalization tokens? Options: No - manual messages, Yes - simple templates, Yes - templates + conditional content
• Should notifications include direct upload links or step-by-step remediation guidance? Options: No, Yes - direct upload links, Yes - guided remediation with screenshots
• Do you want escalation rules if deficiencies are not resolved within X days? Options: No, Yes - escalate to admissions staff, Yes - escalate then auto-withdraw
• Are there specific compliance or audit trails needed for deficiency communication? Options: No, Yes - full audit trail required, Yes - limited retention/audit

Provision Online Fee Payment & Reconciliation

• Which payment methods/providers do you want to support? Options: Credit/Debit (Stripe/Adyen etc.), ACH/Bank transfer, Campus payment gateway, Third-party payment vendor, Other
• Do you require fee waiver logic and automated eligibility checks? Options: No, Yes - manual waiver workflow, Yes - automated waiver eligibility rules
• How should reconciliation be delivered (daily batch, real-time webhook, accounting export)? Options: Daily batch export, Real-time webhook notifications, Both
• Do refunds and chargebacks need to be automated and linked to applicant records? Options: No, Yes - manual refund process, Yes - automated refund workflows
• What reporting formats or GL exports are required for finance teams? Options: CSV export, Direct accounting integration (e.g., QuickBooks), Custom GL mapping - describe in next field
• Is PCI compliance or vendor-managed tokenization required for card storage? Options: No, Yes - vendor tokenization, Yes - full PCI scope

Deploy Reviewer Scoring Interface with Rubrics

• What scoring model do you use (select one)? Options: Numeric scale (e.g., 1-5), Rubric with criteria and descriptors, Checklist / Pass-Fail, Hybrid
• Do reviewers require blind review (applicant identity hidden) or partial masking? Options: No masking, Full blind review, Partial masking (name visible, other fields hidden)
• How many reviewer roles and permission levels are needed (e.g., reader, lead reader, admin)? Options: 1-2, 3-5, 6+
• Do you need calibration sessions, inter-rater reliability reporting, or scoring adjustment tools? Options: No, Yes - calibration sessions, Yes - calibration + analytics
• What reviewer UI features are required (annotations, redaction, time tracking, required fields)? Options: Annotations, Redaction, Time tracking, Required scorer comments, All of the above
• Are automated routing rules needed (e.g., highest score reviewers, load balancing)? Options: No, Yes - simple round-robin, Yes - advanced routing by expertise/availability

Launch Committee Decision Workspace with Ballot Capture

• What decision methods do committees use (single vote, ranked choice, consensus, weighted ballot)? Options: Single vote, Ranked/priority, Consensus/qualitative, Weighted ballot
• Do you need synchronous meeting tools (real-time discussion) or asynchronous decision capture? Options: Asynchronous ballot capture, Synchronous meeting tools, Both
• Will committee members require access to applicant dossiers, annotations, and scoring history? Options: No - limited view, Yes - full dossier access, Yes - configurable per role
• Are audit logs and decision rationale storage required for regulatory review? Options: No, Yes - audit logs only, Yes - audit logs + rationale capture
• Do you need ballot templates, comment moderation, or anonymized summary reports for committees? Options: No, Yes - templates only, Yes - templates + moderation + summaries
• What committee sizes and quorum rules should the workspace enforce? Options: Small (2-4), Medium (5-9), Large (10+)

Integrate SIS via Secure Bi-directional API Sync

• Which SIS vendor/platform are you integrating with? Options: Ellucian Banner, PeopleSoft, Colleague, Custom/In-house, Other
• What data objects need syncing (select all that apply)? Options: Applicant record, Application status/decision, Enrollment/term assignment, Financial holds, Student ID creation, Other
• What sync direction and cadence are required? Options: One-way to SIS (batch), One-way to SIS (real-time), Bi-directional (real-time), Bi-directional (scheduled batch)
• What authentication and connectivity method does your SIS support? Options: REST API (OAuth), SOAP API, SFTP file exchange, Direct DB connection, Other
• Do you have field-level mapping documentation or will mapping need to be discovered? Options: We have mapping docs, Partial mapping docs, No mapping docs - discovery required
• Are there PII/security restrictions, masking, or consent flags that must be enforced during sync? Options: No, Yes - PII restrictions, Yes - consent/FERPA controls required

Migrate Legacy Applicant Records and Attachments

• How many applicant records and attachments are in scope for migration? Options: <1,000, 1,000-10,000, 10,000-100,000, 100,000+
• What formats are legacy attachments stored in and where are they located? Options: File system (PDF/JPG), Legacy DB blobs, Third-party storage (Box/SharePoint), Other
• Is data cleansing, deduplication, or schema transformation required prior to import? Options: No, Yes - minimal cleansing, Yes - extensive transformation
• Do attachments require OCR/metadata extraction as part of migration? Options: No, Yes - OCR during migration, Yes - extract metadata only
• What rollback or verification acceptance criteria must be met before cutover? Options: Record count match, Checksum/hash verification, Sample validation of records, Full data reconciliation
• Are there retention, legal hold, or archival policies to enforce during migration? Options: No, Yes - retention policies, Yes - legal hold/archive required

Provision Role-Based Access, SSO, and MFA

• Which SSO providers or identity systems do you use (select all that apply)? Options: Okta, Azure AD, Google Workspace, Shibboleth/SAML, LDAP/AD, Other
• Do you require SCIM or automated user provisioning from your IdP? Options: No, Yes - SCIM provisioning, Yes - provisioning via SAML assertions
• Is multi-factor authentication (MFA) mandatory for all users or for elevated roles only? Options: Not required, Mandatory for all users, Mandatory for elevated/admin roles only
• How many distinct user roles and permission templates are needed? Options: 1-3, 4-7, 8+
• Do you need session timeout policies, IP restrictions, or audit logging configured? Options: No, Yes - session/IP restrictions, Yes - session/IP + audit logs
• Will you require training materials or role-based admin guides for identity management? Options: No, Yes - basic guides, Yes - in-depth training and workshops

Enable Applicant Status Portal with Real-Time Updates

• Which applicant-facing elements should be visible in the status portal? Options: Application progress, Missing documents, Decision status, Fee/payment status, Interview scheduling, Other
• Do applicants need the ability to upload documents or respond to deficiency requests from the portal? Options: No, Yes - upload only, Yes - upload + guided remediation
• Should the portal support applicant self-service updates (contact info, program changes)? Options: No, Yes - limited fields, Yes - full self-service
• Do you require branded/customized UI and content localization for the portal? Options: No, Yes - basic branding, Yes - full UI customization + localization
• What SLA and real-time expectations exist for status updates (immediate, near-real-time, daily)? Options: Immediate (real-time), Near-real-time (minutes), Daily batch
• Do you need applicant notifications tied to portal events (email/SMS in addition to portal)? Options: No, Yes - email only, Yes - email + SMS

• Non-Disclosure Agreement (NDA)
• Master Services Agreement (MSA)
• Statement of Work (SOW)
• Proof-of-Concept (POC) Objectives and Acceptance
• Pricing & Commercial Terms
• Project Timeline & Milestones
• Roles & Responsibilities Matrix
• Integration & Data Migration Plan
• Risk Mitigation & Peak Processing Plan
• Security & Compliance Addendum
• Change Control & Change Order Process
• Payment Schedule & Invoicing Authorization

• Success Review — Outcomes vs Success Signals
• Lessons Learned Workshop
• Operational Health & Escalation Channel Setup
• Enhancement Backlog Prioritization & Roadmap Alignment
• Stakeholder Adoption, Training & Communications Review

• Identify any blockers or dependencies requiring earlier mitigation.
• Schedule follow-up validation checkpoints if remediation is required.
• Publish the acceptance report mapping evidence to each success signal.
• Assign remediation owners and target dates for unresolved items.
• Schedule follow-up validation meeting(s) and checkpoints.
• Share meeting minutes and evidence artifacts to the shared channel.
• Review Current SLA and Monitoring Dashboards
• Confirm system health and identify any near-term operational risks.
• Create or confirm a durable shared channel and escalation protocol for issues and enhancements.
• Agree on an operational cadence and owners for routine health checks.
• Create the shared channel with documented subscriber list, severity matrix, and escalation contacts.
• Document and publish updated runbooks for top-severity incidents.
• Assign on-call rotations and confirm SLO/SLA alert thresholds.
• Schedule the recurring operational check-in meetings.
• Collect and Confirm Enhancement Requests
• Produce a prioritized enhancement backlog with clear rationale (impact vs effort).
• Align top-priority items to specific upcoming release windows and owners.
• Retrospective Goals & Ground Rules
• Publish the prioritized backlog and map items to release dates.
• Create scoping epics for top-priority items and schedule scoping sessions.
• Notify stakeholders of roadmap changes and any impacts to peak processing.
• Adoption KPIs Review
• Confirm adoption is tracking toward expected operational improvements.
• Identify and schedule targeted training and coaching for low-adoption cohorts.
• Finalize communications plan and governance to maintain applicant experience and internal alignment.
• Publish adoption and applicant experience KPI dashboard to the shared channel.
• Create training plans for identified cohorts and schedule sessions.
• Send approved applicant and campus communications per the agreed cadence.
• Confirm and document steering committee dates and stakeholder champions.
• Create a prioritized list of lessons with root causes and recommended fixes.
• Assign owners and realistic timelines for each recommended change.
• Identify at least 2 quick wins to implement within 30 days.
• Publish the lessons-learned document with root-cause notes and owners.
• Create tasks for quick wins and add to operational backlog.
• Schedule follow-up checkpoints to confirm implementation of recommendations.
• Welcome & Objectives
• Achieve shared agreement on which success signals are met and which require remediation.
• Document evidence supporting each acceptance decision.
• Define remediation scope, owners, and deadlines for any unmet signals.
• Timeline Walkthrough
• Data Integrity & Migration Verification
• Attendee Roles & Validation Rules
• Applicant Experience Metrics
• Impact Assessment (Student Experience, Ops, Risk)
• Training Effectiveness Analysis
• Effort & Dependency Review
• Review Agreed Success Signals
• Reviewer Scoring Consistency Check
• What Went Well — Evidence & Examples
• What Didn't Work — Concrete Incidents
• Open Incidents and High-Risk Items
• Prioritize Backlog (Impact x Effort)
• Present Measured Outcomes and Evidence
• Targeted Remediation & Additional Training Needs
• Root Cause Analysis
• Gap Analysis — Met vs Not Met
• Align Priority Items to Release Windows
• Establish Shared Channel & Escalation Paths
• Communications Plan for Applicants & Campus Stakeholders
• Recommend Changes & Quick Wins