Volunteer Coordination

Persona

Role: Developer at a community organization with 300+ active volunteers supporting events and programs year-round.

Volunteer signups happen through email and paper forms. Shift assignments are managed in a shared calendar that only coordinators can access, and hours are self-reported on paper timesheets that are transcribed monthly. The organization cannot tell how many volunteer hours were contributed last year or which volunteers are most active.

Business Problem

Volunteer engagement suffers when people sign up but never hear back, or when they arrive at an event with no clear assignment. Hour tracking is unreliable because self-reported paper timesheets are often submitted weeks late with estimated hours. Funders and board members ask for volunteer hour totals that take days to compile. This scenario builds a volunteer coordination workflow that maintains volunteer profiles with skills and availability, schedules shifts for events, and logs verified hours.

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 Volunteer, Shift, and HourLog.

• 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 Volunteer Coordination journey with complete, trusted context.
• Required data: Volunteer context such as name, skills, availability, and totalHours.
• 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 Volunteer Coordination without forcing the human reviewer to assemble the case manually.
• Required data: Volunteer state and history; Shift fields such as event, date, volunteersNeeded, and description.
• 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: Shift actions such as completeShift; HourLog fields such as hours, supervisor, verified, and notes.
• 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 Volunteer, Shift, and HourLog.
• 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 Volunteer Coordination through Object Types, tenant-scoped resources, document processing, chat workflows, and CLI verification. For this scenario, the main records are Volunteer, Shift, and HourLog.

Process step	What EAI provides	Calling pattern
Step 1. Capture demand and context	Tenant-scoped intake resources for Volunteer context such as name, skills, availability, and totalHours. 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 Volunteer records with useResources('Volunteer') or eai resources create Volunteer, and keep browser calls behind /api/eai/....
Step 2. Prepare the decision	Linked resource queries over Volunteer state and history; Shift fields such as event, date, volunteersNeeded, and description. Search, schema checks, document classification or RAG indexing, and chat summaries turn raw context into a prepared decision.	Use useResources('Volunteer') 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 Shift actions such as completeShift; HourLog fields such as hours, supervisor, verified, and notes. 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 Volunteer, Shift, and HourLog. 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 Volunteer Coordination with Object Types for Volunteer, Shift, HourLog. 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
Volunteer	name (text), skills (text), availability (text), totalHours (number), status (select: active, on-leave, alumni)	one-to-many → HourLog	--
Shift	event (text), date (date), volunteersNeeded (number), description (text), status (select: open, filled, completed, cancelled)	one-to-many → HourLog	completeShift
HourLog	hours (number), supervisor (text), verified (boolean), notes (text), loggedDate (date)	many-to-one → Volunteer, many-to-one → Shift	verifyHours

CLI Workflow

1. Scaffold the project

   eai init volunteer-coordination

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 Volunteer, Shift, and HourLog types in src/eai.config/object-types.ts (see code example below).

4. Validate the type definitions

   eai types validate

   Tenant: volunteer-coordination
   ✔ Volunteer — 5 props, 1 link, 0 actions
   ✔ Shift — 5 props, 1 link, 1 action
   ✔ HourLog — 5 props, 2 links, 1 action
   
   ✔ All Object Types are valid

5. Seed types to the platform

   eai types seed

6. Create sample resources

   eai resources create Volunteer --data '{"name": "Carlos Mendez", "skills": "Event setup, registration desk, first aid", "availability": "Weekends and evenings", "totalHours": 120, "status": "active"}'

7. Start local development

   eai dev

Code Example

// src/eai.config/object-types.ts
export const objectTypes = {
  'volunteer-coordination': [
    {
      name: 'Volunteer',
      displayName: 'Volunteer',
      description: 'A registered volunteer with the organization',
      properties: [
        { name: 'name', type: 'text' as const, required: true, indexed: true },
        { name: 'skills', type: 'text' as const, required: false },
        { name: 'availability', type: 'text' as const, required: false },
        { name: 'totalHours', type: 'number' as const, required: false, defaultValue: 0 },
        { name: 'status', type: 'select' as const, required: true, defaultValue: 'active', options: [
          { label: 'Active', value: 'active' },
          { label: 'On Leave', value: 'on-leave' },
          { label: 'Alumni', value: 'alumni' },
        ]},
      ],
      linkTypes: [
        { name: 'hourLogs', targetObjectType: 'HourLog', cardinality: 'one-to-many' as const },
      ],
      actions: [],
      status: 'published' as const,
    },
    {
      name: 'Shift',
      displayName: 'Shift',
      description: 'A scheduled volunteer shift for an event or program',
      properties: [
        { name: 'event', type: 'text' as const, required: true, indexed: true },
        { name: 'date', type: 'date' as const, required: true, indexed: true },
        { name: 'volunteersNeeded', type: 'number' as const, required: true },
        { name: 'description', type: 'text' as const, required: false },
        { name: 'status', type: 'select' as const, required: true, defaultValue: 'open', options: [
          { label: 'Open', value: 'open' },
          { label: 'Filled', value: 'filled' },
          { label: 'Completed', value: 'completed' },
          { label: 'Cancelled', value: 'cancelled' },
        ]},
      ],
      linkTypes: [
        { name: 'hourLogs', targetObjectType: 'HourLog', cardinality: 'one-to-many' as const },
      ],
      actions: [
        {
          name: 'completeShift',
          displayName: 'Complete Shift',
          description: 'Mark a shift as completed after the event',
          requiredRole: 'tenant-staff',
          validationRules: { requiredStatus: 'filled' },
          sideEffects: [
            { type: 'set_field', field: 'status', value: 'completed' },
          ],
        },
      ],
      status: 'published' as const,
    },
    {
      name: 'HourLog',
      displayName: 'Hour Log',
      description: 'A record of hours worked by a volunteer during a shift',
      properties: [
        { name: 'hours', type: 'number' as const, required: true },
        { name: 'supervisor', type: 'text' as const, required: true },
        { name: 'verified', type: 'boolean' as const, required: true, defaultValue: false },
        { name: 'notes', type: 'text' as const, required: false },
        { name: 'loggedDate', type: 'date' as const, required: true, indexed: true },
      ],
      linkTypes: [
        { name: 'volunteer', targetObjectType: 'Volunteer', cardinality: 'many-to-one' as const },
        { name: 'shift', targetObjectType: 'Shift', cardinality: 'many-to-one' as const },
      ],
      actions: [
        {
          name: 'verifyHours',
          displayName: 'Verify Hours',
          description: 'Supervisor verification of logged volunteer hours',
          requiredRole: 'tenant-staff',
          validationRules: { requiredFields: ['hours', 'supervisor'] },
          sideEffects: [
            { type: 'set_field', field: 'verified', value: true },
          ],
        },
      ],
      status: 'published' as const,
    },
  ],
};

Key Takeaways

• Skills-based matching: Volunteer profiles with skills and availability enable coordinators to match the right people to the right shifts.
• Verified hour tracking: Supervisor verification on hour logs replaces unreliable self-reported timesheets with accountable records.
• Shift lifecycle management: Shifts flow from open through filled to completed, giving coordinators visibility into staffing levels for upcoming events.
• Aggregate reporting: Linking hour logs to both volunteers and shifts enables reports by individual, event, or time period for funder and board reporting.