Admissions Portal

Persona

Role: Director of Admissions Technology at a private university.

You oversee the technology stack supporting the admissions office, which processes 12,000 applications annually across undergraduate, graduate, and professional programs. Each application involves document collection, committee review, and a final decision with potential conditions. The existing portal is aging and cannot accommodate new program types without extensive custom development.

Business Problem

Applications arrive through a web portal, but supporting documents -- transcripts, recommendation letters, test scores -- are uploaded to a separate file share with no automated link to the application. Committee members review applications in a spreadsheet, and decisions are communicated via mail merge. There is no single view of an application's completeness or decision status. You need:

• A unified application record with program and term tracking.
• Document management linked to applications with verification status.
• Structured decision records that capture committee outcomes and conditions.

Four-Step Application

This scenario works best as a four-step, human-in-the-loop application. The existing object model already gives this scenario a strong delivery backbone through Application, Document, and Decision.

• Mission metric focus: faster decisions, better learner experience, and stronger enrollment or completion outcomes.
• Human + AI pattern: Each step combines structured workflow data with chat assistance, background generation, document understanding, and accessible interaction patterns when they improve the experience.

Step 1. Capture demand and context

• Goal: Make it easy for the user to start the Admissions Portal journey with complete, trusted context.
• Required data: Application context such as the core workflow data.
• AI support: Use chat to guide intake, generate clearer prompts, create accessible summaries, and assist with voice or vision-led capture when a form alone is not the best experience. EAI can support structured intake, chat workflows, and document-centred capture today; richer native multimodal capture may still need workflow extensions or connected services.
• Business impact: Improve completion rate, reduce first-touch effort, and raise customer or staff confidence in the UX from the very first interaction.
• EAI delivery: Model the intake as tenant-isolated object types and resources, then use actions, chat workflows, and document indexing or classification to keep the initial record complete and usable.

Step 2. Prepare the decision

• Goal: Turn the captured context into the next best action for Admissions Portal without forcing the human reviewer to assemble the case manually.
• Required data: Application state and history.
• AI support: Run background summarisation, extraction, classification, recommendation drafting, and answer generation so a reviewer sees a prepared case instead of raw fragments. EAI delivers the structured records and AI workflow hooks for this today; specialised scoring engines, external rules, or advanced reasoning controls may still need integration work.
• Business impact: Reduce cycle time, improve quality and consistency, and protect the mission-critical metric before the case moves into execution.
• EAI delivery: Link records across the scenario, persist decision state as resources, and use workflow actions plus chat assistance to keep humans in control while AI prepares the work.

Step 3. Execute and collaborate

• Goal: Coordinate the actual work, handoffs, approvals, and user updates needed to deliver the service or outcome.
• Required data: Document execution state.
• AI support: Draft replies, produce work packets, monitor exceptions in the background, and surface the next action for each operator. EAI can orchestrate tenant-isolated records, actions, chats, and document workflows today; deeper system-to-system automation may require additional connectors or workflow capability.
• Business impact: Increase operator productivity, reduce rework across handoffs, and improve service consistency across the application journey.
• EAI delivery: Use linked object types, actions, resource updates, and workflow-triggered AI assistance so the team can execute in one model instead of splitting work across disconnected tools.

Step 4. Resolve, explain, and improve

• Goal: Close the loop with a clear outcome, an understandable explanation, and feedback that improves the next case.
• Required data: final status, outcome, audit history, and follow-up signals across Application, Document, and Decision.
• AI support: Generate outcome summaries, customer-friendly answers, compliance-ready notes, management insights, and accessible follow-up content. EAI can store outcome records and support answer generation today, while richer proactive agents, advanced analytics, or channel-specific accessibility features may need additional product capability.
• Business impact: Increase trust, quality, and measurable business value through faster decisions, better learner experience, and stronger enrollment or completion outcomes.
• EAI delivery: Keep the full audit trail in structured resources, use AI workflows to explain outcomes, and feed the resulting signals into future product, service, and operational improvement work.

EAI Platform Support By Step

EAI provides the safe service boundary for Admissions Portal through Object Types, tenant-scoped resources, document processing, chat workflows, and CLI verification. For this scenario, the main records are Application, Document, and Decision.

Process step	What EAI provides	Calling pattern
Step 1. Capture demand and context	Tenant-scoped intake resources for Application context such as the core workflow data. Object Type validation, starter forms, optional document intake, and chat-guided capture keep the first record complete.	Define fields in src/eai.config/object-types.ts, run eai types validate and eai types seed, create initial Application records with useResources('Application') or eai resources create Application, and keep browser calls behind /api/eai/....
Step 2. Prepare the decision	Linked resource queries over Application state and history. Search, schema checks, document classification or RAG indexing, and chat summaries turn raw context into a prepared decision.	Use useResources('Application') list/query/search patterns, verify shape with eai resources schema, use useDocuments().upload/classify/ragIndex, eai docs upload, eai docs classify, and eai docs index where supporting material exists, and send decision-support prompts through useChat(workflowId, 'chat') or eai chat send.
Step 3. Execute and collaborate	Resource updates and actions for Document execution state. Status changes, assignments, notes, generated work packets, and chat support keep humans in control during execution.	Model actions in the Object Type code, call client.resources.executeAction(type, id, action) or the app hook equivalent, update records through the app service layer, and verify with eai resources get/list/query.
Step 4. Resolve, explain, and improve	Outcome resources for final status, outcome, audit history, and follow-up signals across Application, Document, and Decision. Audit-friendly links, indexed final documents, reporting snapshots, and answer generation make the result explainable and reusable.	Persist outcomes as resources, index final material with eai docs index or useDocuments().ragIndex, send explanation prompts with useChat or eai chat stream, and use eai resources aggregate/search for reporting checks.

Prompt, Code, And Service Pattern Mapping

The Object Type code example on this page is the implementation contract for the EAI platform services. eai-gofer should read that code as the source of truth for which resource, document, and chat calls belong in the app.

Use this prompt shape when asking eai-gofer or another coding agent to implement the scenario:

Use the EAI App Template. Model Admissions Portal with Object Types for Application, Document, Decision. Use useResources for records and actions, useDocuments for uploads/classification/RAG where documents appear, useChat for workflow assistance, and verify with eai types/resources/docs/chat commands. Use eai publicapi only when no named command covers the required platform call.

Scenario artifact	How it maps to EAI service calls
Four-step process	Step 1 becomes resource creation, Step 2 becomes resource query/search plus optional document or chat preparation, Step 3 becomes resource update/action calls, and Step 4 becomes outcome persistence plus explanation/reporting calls.
Object Type definitions	eai types validate, eai types seed, and eai resources schema make the model available and checkable before UI work starts.
Properties and indexes	Fields become useResources payloads, filters, list views, and eai resources create/list/query/search checks. Indexed fields should support lookup and triage, not duplicate canonical records.
Links between Object Types	Relationships become linked-resource UI, timeline context, and audit trails that app code loads through resource queries rather than separate bespoke stores.
Actions and status fields	Workflow buttons and operator transitions call resource action/update helpers, then verify state with eai resources get/list/query.
Document and chat prompts	Prompts should call the platform documents and chat patterns: useDocuments().upload/classify/ragIndex, eai docs upload, eai docs classify, and eai docs index for documents, and useChat, eai chat send, or eai chat stream for conversational assistance.

Object Types

Name	Key Properties	Links	Actions
Application	applicant, program, term, status	has many Documents, has one Decision	submit, review, request-info
Document	application, type, fileUrl, verified	belongs to Application	upload, verify, reject
Decision	application, committee, outcome, conditions	belongs to Application	recommend, approve, deny, defer

CLI Workflow

1. Scaffold the app

   eai init admissions-portal

2. Authenticate and pull environment

   eai login
   eai env pull --include-secrets

   If you are an external developer, see [Configuration](/docs/configuration) for login and local environment setup.

3. Define Object Types

   Add Application, Document, and Decision to src/eai.config/object-types.ts.

4. Validate and seed

   eai types validate
   eai types seed

   Tenant: admissions-portal
   ✔ Application — 4 props, 2 links, 3 actions
   ✔ Document — 4 props, 1 link, 3 actions
   ✔ Decision — 4 props, 1 link, 4 actions
   
   ✔ All Object Types are valid

5. Create an application

   eai resources create Application \
     --data '{"applicant": "jordan.lee@email.com", "program": "ms-data-science", "term": "Fall 2026", "status": "submitted"}'

6. Upload a document record

   eai resources create Document \
     --data '{"application": "app-001", "type": "transcript", "fileUrl": "/uploads/transcript-jordan-lee.pdf", "verified": false}'

7. List applications by program

   eai resources list Application --filter 'program=ms-data-science'

8. Start local development

   eai dev

Code Example

// src/eai.config/object-types.ts
export const objectTypes = {
  'admissions-portal': [
    {
      name: 'Application',
      displayName: 'Application',
      description: 'A student application to a specific academic program and enrollment term',
      properties: [
        { name: 'applicant', type: 'text' as const, required: true, indexed: true },
        { name: 'program', type: 'select' as const, required: true,
          options: [
            { label: 'BS Computer Science', value: 'bs-computer-science' },
            { label: 'MS Data Science', value: 'ms-data-science' },
            { label: 'MBA', value: 'mba' },
            { label: 'JD', value: 'jd' },
            { label: 'PhD Biology', value: 'phd-biology' },
          ],
        },
        { name: 'term', type: 'text' as const, required: true, indexed: true },
        { name: 'status', type: 'select' as const, required: true, defaultValue: 'draft',
          options: [
            { label: 'Draft', value: 'draft' },
            { label: 'Submitted', value: 'submitted' },
            { label: 'Complete', value: 'complete' },
            { label: 'Under Review', value: 'under-review' },
            { label: 'Decision Made', value: 'decision-made' },
          ],
        },
      ],
      linkTypes: [
        { name: 'documents', target: 'Document', cardinality: 'many' as const },
        { name: 'decision', target: 'Decision', cardinality: 'one' as const },
      ],
      actions: [
        { name: 'submit', displayName: 'Submit Application' },
        { name: 'review', displayName: 'Begin Review' },
        { name: 'request-info', displayName: 'Request Additional Info' },
      ],
      status: 'published' as const,
    },
    {
      name: 'Document',
      displayName: 'Document',
      description: 'A supporting document uploaded as part of an admissions application',
      properties: [
        { name: 'application', type: 'text' as const, required: true },
        { name: 'type', type: 'select' as const, required: true,
          options: [
            { label: 'Transcript', value: 'transcript' },
            { label: 'Recommendation Letter', value: 'recommendation' },
            { label: 'Personal Statement', value: 'personal-statement' },
            { label: 'Test Score', value: 'test-score' },
            { label: 'Resume', value: 'resume' },
            { label: 'Portfolio', value: 'portfolio' },
          ],
        },
        { name: 'fileUrl', type: 'text' as const, required: true },
        { name: 'verified', type: 'boolean' as const, required: true },
      ],
      linkTypes: [
        { name: 'application', target: 'Application', cardinality: 'one' as const },
      ],
      actions: [
        { name: 'upload', displayName: 'Upload Document' },
        { name: 'verify', displayName: 'Verify Document' },
        { name: 'reject', displayName: 'Reject Document' },
      ],
      status: 'published' as const,
    },
    {
      name: 'Decision',
      displayName: 'Decision',
      description: 'The admissions committee decision for a specific application',
      properties: [
        { name: 'application', type: 'text' as const, required: true },
        { name: 'committee', type: 'text' as const, required: true },
        { name: 'outcome', type: 'select' as const, required: true,
          options: [
            { label: 'Admit', value: 'admit' },
            { label: 'Admit with Conditions', value: 'admit-conditions' },
            { label: 'Waitlist', value: 'waitlist' },
            { label: 'Deny', value: 'deny' },
            { label: 'Defer', value: 'defer' },
          ],
        },
        { name: 'conditions', type: 'text' as const, required: false },
      ],
      linkTypes: [
        { name: 'application', target: 'Application', cardinality: 'one' as const },
      ],
      actions: [
        { name: 'recommend', displayName: 'Recommend Decision' },
        { name: 'approve', displayName: 'Approve Admission' },
        { name: 'deny', displayName: 'Deny Admission' },
        { name: 'defer', displayName: 'Defer Decision' },
      ],
      status: 'published' as const,
    },
  ],
};

Key Takeaways

• Document completeness tracking prevents review delays. Linking Documents to Applications with a verified flag lets the admissions office quickly identify incomplete applications before sending them to committee.
• Program-specific filtering streamlines committee work. Committee members can filter applications by program and term, focusing their review on the relevant applicant pool.
• Conditional admissions are first-class records. The Decision type captures conditions alongside outcomes, ensuring that conditional admits receive appropriate follow-up.
• Unified application lifecycle. From draft through submission to decision, every stage is captured in structured status fields, giving leadership real-time visibility into pipeline health.