Grant Reporting

Persona

Role: Grants management developer at a non-profit managing 25 active grants totaling $4M in annual funding.

The grants team tracks deliverables in individual spreadsheets per funder, stores compliance documentation in shared folders organized by grant name, and compiles reports manually before each deadline. When a funder changes reporting requirements, the team scrambles to adapt because there is no centralized view of what is owed, to whom, and by when.

Business Problem

Missing a grant reporting deadline or failing a compliance check can result in funding clawbacks and damaged funder relationships. Each grant has unique milestones, reporting frequencies, and compliance requirements that are tracked in isolation. The grants team cannot see which milestones are coming due across all grants, and compliance evidence is scattered. This scenario builds a grant reporting workflow that tracks milestones with evidence, monitors compliance requirements, and provides a unified view of reporting obligations across all funders.

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 Grant, Milestone, and ComplianceCheck.

• Mission metric focus: greater mission reach, stronger stewardship, and better reporting quality.
• 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 Grant Reporting journey with complete, trusted context.
• Required data: Grant context such as funder, amount, purpose, and startDate.
• 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 Grant Reporting without forcing the human reviewer to assemble the case manually.
• Required data: Grant state and history; Milestone fields such as description, dueDate, evidence, and status.
• 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: Milestone actions such as completeMilestone; ComplianceCheck fields such as requirement, notes, checkedDate, and status.
• 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 Grant, Milestone, and ComplianceCheck.
• 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 greater mission reach, stronger stewardship, and better reporting quality.
• 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 Grant Reporting through Object Types, tenant-scoped resources, document processing, chat workflows, and CLI verification. For this scenario, the main records are Grant, Milestone, and ComplianceCheck.

Process step	What EAI provides	Calling pattern
Step 1. Capture demand and context	Tenant-scoped intake resources for Grant context such as funder, amount, purpose, and startDate. 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 Grant records with useResources('Grant') or eai resources create Grant, and keep browser calls behind /api/eai/....
Step 2. Prepare the decision	Linked resource queries over Grant state and history; Milestone fields such as description, dueDate, evidence, and status. Search, schema checks, document classification or RAG indexing, and chat summaries turn raw context into a prepared decision.	Use useResources('Grant') 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 Milestone actions such as completeMilestone; ComplianceCheck fields such as requirement, notes, checkedDate, and status. 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 Grant, Milestone, and ComplianceCheck. 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 Grant Reporting with Object Types for Grant, Milestone, ComplianceCheck. 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
Grant	funder (text), amount (number), purpose (text), startDate (date), endDate (date), status (select: pending, active, closed, suspended)	one-to-many → Milestone, one-to-many → ComplianceCheck	activateGrant
Milestone	description (text), dueDate (date), evidence (text), status (select: upcoming, in-progress, completed, overdue)	many-to-one → Grant	completeMilestone
ComplianceCheck	requirement (text), notes (text), checkedDate (date), status (select: compliant, non-compliant, pending-review)	many-to-one → Grant	--

CLI Workflow

1. Scaffold the project

   eai init grant-reporting

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 your Object Types

   Create the Grant, Milestone, and ComplianceCheck types in src/eai.config/object-types.ts (see code example below).

4. Validate the type definitions

   eai types validate

   Tenant: grant-reporting
   ✔ Grant — 6 props, 2 links, 1 action
   ✔ Milestone — 4 props, 1 link, 1 action
   ✔ ComplianceCheck — 4 props, 1 link, 0 actions
   
   ✔ All Object Types are valid

5. Seed types to the platform

   eai types seed

6. Create sample resources

   eai resources create Grant --data '{"funder": "Ford Foundation", "amount": 500000, "purpose": "Community health worker training program", "startDate": "2025-01-01", "endDate": "2027-12-31", "status": "active"}'

7. Start local development

   eai dev

Code Example

// src/eai.config/object-types.ts
export const objectTypes = {
  'grant-reporting': [
    {
      name: 'Grant',
      displayName: 'Grant',
      description: 'A funding grant from a foundation or government entity',
      properties: [
        { name: 'funder', type: 'text' as const, required: true, indexed: true },
        { name: 'amount', type: 'number' as const, required: true },
        { name: 'purpose', type: 'text' as const, required: true },
        { name: 'startDate', type: 'date' as const, required: true, indexed: true },
        { name: 'endDate', type: 'date' as const, required: true, indexed: true },
        { name: 'status', type: 'select' as const, required: true, defaultValue: 'pending', options: [
          { label: 'Pending', value: 'pending' },
          { label: 'Active', value: 'active' },
          { label: 'Closed', value: 'closed' },
          { label: 'Suspended', value: 'suspended' },
        ]},
      ],
      linkTypes: [
        { name: 'milestones', targetObjectType: 'Milestone', cardinality: 'one-to-many' as const },
        { name: 'complianceChecks', targetObjectType: 'ComplianceCheck', cardinality: 'one-to-many' as const },
      ],
      actions: [
        {
          name: 'activateGrant',
          displayName: 'Activate Grant',
          description: 'Mark a pending grant as active after agreement execution',
          requiredRole: 'tenant-staff',
          validationRules: { requiredFields: ['funder', 'amount', 'startDate', 'endDate'], requiredStatus: 'pending' },
          sideEffects: [
            { type: 'set_field', field: 'status', value: 'active' },
          ],
        },
      ],
      status: 'published' as const,
    },
    {
      name: 'Milestone',
      displayName: 'Milestone',
      description: 'A deliverable or reporting milestone for a grant',
      properties: [
        { name: 'description', type: 'text' as const, required: true },
        { name: 'dueDate', type: 'date' as const, required: true, indexed: true },
        { name: 'evidence', type: 'text' as const, required: false },
        { name: 'status', type: 'select' as const, required: true, defaultValue: 'upcoming', options: [
          { label: 'Upcoming', value: 'upcoming' },
          { label: 'In Progress', value: 'in-progress' },
          { label: 'Completed', value: 'completed' },
          { label: 'Overdue', value: 'overdue' },
        ]},
      ],
      linkTypes: [
        { name: 'grant', targetObjectType: 'Grant', cardinality: 'many-to-one' as const },
      ],
      actions: [
        {
          name: 'completeMilestone',
          displayName: 'Complete Milestone',
          description: 'Mark a milestone as completed with supporting evidence',
          requiredRole: 'tenant-user',
          validationRules: { requiredFields: ['evidence'], requiredStatus: 'in-progress' },
          sideEffects: [
            { type: 'set_field', field: 'status', value: 'completed' },
          ],
        },
      ],
      status: 'published' as const,
    },
    {
      name: 'ComplianceCheck',
      displayName: 'Compliance Check',
      description: 'A compliance verification for a grant requirement',
      properties: [
        { name: 'requirement', type: 'text' as const, required: true },
        { name: 'notes', type: 'text' as const, required: false },
        { name: 'checkedDate', type: 'date' as const, required: false, indexed: true },
        { name: 'status', type: 'select' as const, required: true, defaultValue: 'pending-review', options: [
          { label: 'Compliant', value: 'compliant' },
          { label: 'Non-Compliant', value: 'non-compliant' },
          { label: 'Pending Review', value: 'pending-review' },
        ]},
      ],
      linkTypes: [
        { name: 'grant', targetObjectType: 'Grant', cardinality: 'many-to-one' as const },
      ],
      actions: [],
      status: 'published' as const,
    },
  ],
};

Key Takeaways

• Cross-grant visibility: All milestones across all grants are indexed by due date, providing a single view of upcoming deliverables regardless of funder.
• Evidence-based completion: Milestones require evidence documentation before they can be marked complete, ensuring the grants team has supporting materials ready for funder review.
• Compliance monitoring: Ongoing compliance checks are linked to their grant, making it easy to demonstrate adherence to funder requirements during audits.
• Grant lifecycle management: The structured status flow from pending through active to closed tracks each grant from award notification through closeout.