CiviForm Docs
HomeAboutContactNewsFAQ
  • CiviForm Docs
  • Overview
    • What is CiviForm?
    • How does CiviForm work?
    • Glossary
  • User Manual
    • CiviForm Admin Guide
      • CiviForm Admin training overview
      • How to navigate CiviForm
      • Working with programs
        • Create a program
        • Edit a program
        • Show or hide questions based on inputs
        • Manage program eligibility
        • Manage address & service area validation
        • Manage notifications
        • How to publish programs
        • Set a pre-screener
      • Working with questions
        • Manage questions
        • Question export settings
        • Universal and Primary Applicant Information questions
        • Using enumerator questions & screens in a program
      • Manage translations for programs & questions
      • Manage versions for programs & questions
      • Working with applications
        • Add statuses to a program
        • Download exported data
      • Role management
        • Manage Program Admins
        • Manage Trusted Intermediaries
      • Manage API keys
      • Using Markdown
      • Migrating programs between environments
    • Program Admin Guide
      • How to become a Program Admin
      • Review completed applications
    • Trusted Intermediary Guide
      • Apply to a program
    • Onboarding Guide
      • Organization assessment
      • Program assessment
      • Getting started with service design
      • Journey mapping
      • Discovery, eligibility, and intake
      • Consolidating questions across programs
      • Working with existing tools and processes
      • Working across jurisdictions
      • Data reporting and other integrations
      • Security and privacy considerations
      • Staffing overview
  • IT Manual
    • Technical Deployment Guide
      • Initial Deployment
        • Terraform deploy system
          • AWS Terraform deployment
        • Authentication setup
        • Email configuration
        • GIS Service configuration
      • Upgrading to a New Release
        • CiviForm server environment variables
          • v1.20.0
          • v1.20.1
          • v1.21.0
          • v1.22.0
          • v1.23.0
          • v1.23.1
          • v1.24.0
          • v1.24.1
          • v1.24.2
          • v1.25.0
          • v1.26.0
          • v1.27.0
          • v1.28.0
          • v1.29.0
          • v1.30.0
          • v1.30.1
          • v1.31.0
          • v1.33.0
          • v1.34.0
          • v1.34.1
          • v1.34.2
          • v1.35.0
          • v1.36.0
          • v1.37.0
          • v1.38.0
          • v1.38.1
          • v1.38.2
          • v1.39.0
          • v1.40.0
          • v1.41.0
          • v1.42.0
          • v1.43.0
          • v1.44.0
          • v1.45.0
          • v1.46.0
          • v1.47.0
          • v1.48.0
          • v1.49.0
          • v1.50.0
          • v1.51.0
          • v1.52.0
          • v1.53.0
          • v1.54.0
          • v1.55.0
          • v1.56.0
          • v1.56.1
          • v1.57.0
          • v1.58.0
          • v1.59.0
          • v1.60.0
          • v1.61.0
          • v1.62.0
          • v1.63.0
          • v2.0.0
          • v2.0.1
          • v2.0.2
          • v2.1.0
          • v2.10.0
          • v2.11.0
          • v2.12.0
          • v2.13.0
          • v2.14.0
          • v2.15.0
          • v2.16.0
          • v2.17.0
          • v2.18.0
          • v2.19.0
          • v2.2.0
          • v2.20.0
          • v2.21.0
          • v2.22.0
          • v2.23.0
          • v2.24.0
          • v2.25.0
          • v2.26.0
          • v2.27.0
          • v2.28.0
          • v2.29.0
          • v2.3.0
          • v2.30.0
          • v2.31.0
          • v2.32.0
          • v2.33.0
          • v2.34.0
          • v2.35.0
          • v2.36.0
          • v2.37.0
          • v2.38.0
          • v2.39.0
          • v2.4.0
          • v2.4.1
          • v2.4.2
          • v2.4.3
          • v2.5.0
          • v2.6.0
          • v2.7.0
          • v2.8.0
          • v2.9.0
      • Monitoring
      • Troubleshooting Production
      • Disaster Recovery
      • Database Disaster Recovery
      • Production Database Access
    • Infrastructure Requirements
    • Existing deployments
    • API Integration
      • Authentication
      • List applications
    • Testing & QA
      • Testing resources
      • SQL queries to look for missing questions
  • Governance & Management
    • Project Management
      • On Call Guide
    • Governance
      • Roles, Committees, & Responsibilities
      • Governance Processes
      • Development Principles
      • Communication
Powered by GitBook
On this page
  • What department or organization administers this program?
  • What challenges do you face in administering or managing this program?
  • How do residents typically find out about the program?
  • Where or how do residents typically submit applications to the program?
  • Do residents typically apply on their own, or do they receive assistance in applying?
  • How many applications do you process each (day, week, month, year)?
  • What information is necessary to apply to the program?
  • How long do applications typically take to be completed (from start to submission)?
  • Once submitted, how long do applications take to be processed (from submission to approval)?
  • What steps are involved in the life cycle of applying to the program, processing an application, and delivering benefits?
  • What applications, systems, websites, tools, or other resources are used to process information or applications for this program?
  • Do you cross-check eligibility information or other details with any other programs or data sources?
  • Do you report your program data to any organizations or stakeholders? What do you report and how is it reported?

Was this helpful?

Edit on GitHub
Export as PDF
  1. User Manual
  2. Onboarding Guide

Program assessment

Answering these questions will make it easier to understand how CiviForm and other tools should adapt to the needs of applicants and program staff. Answering these questions can help form a journey map of applicants and program staff experiences to inform where and how changes might be implemented.

What department or organization administers this program?

What challenges do you face in administering or managing this program?

Any details are fine, the challenges do not need to be technology-related.

How do residents typically find out about the program?

Include websites, community organizations, or other channels.

Where or how do residents typically submit applications to the program?

Include websites, electronic forms, paper forms, community organizations, program offices, or other channels.

Do residents typically apply on their own, or do they receive assistance in applying?

For example, from program staff, call centers, community organizations, social workers, or others.

How many applications do you process each (day, week, month, year)?

What information is necessary to apply to the program?

Share a link to the form or application, or share the questions directly here.

How long do applications typically take to be completed (from start to submission)?

Once submitted, how long do applications take to be processed (from submission to approval)?

What steps are involved in the life cycle of applying to the program, processing an application, and delivering benefits?

Include the end-to-end life cycle from discovery to the delivery of benefits in as much detail as you can manage, including typical timelines, individuals or roles involved, and steps from both the applicant side and the program/administrative side (and any other stakeholders involved).

For example:


Discovery and application (X minutes total):

  1. Resident discovers program through local community group

  2. Resident fills out application X via website at www.example.com with help from local staff member (30 minutes)

  3. Resident comes into program office to drop off paper form (30 minutes)

  4. Paper form is prepared for processing by program staff in X group (once daily)

Processing (X days total):

  1. Program staff is assigned an application to process (once daily)

  2. Program staff begins processing application within X days after submission

  3. Program staff from group A enters information into computer system Y

  4. Program staff cross-references data in systems Y and Z

  5. Program staff calls applicant to verify information D (X minutes)

  6. Applicant must bring document D into office (X days waiting)

  7. Program staff verifies document D against database Y (X minutes)

  8. Application is approved. Status is shared with applicant through system Y (X days)

Delivery (X days total):

  1. Approved application is marked for delivery in system A (once per application manually, 10 minutes)

  2. Data is exported from system A to system B for fulfillment (once daily for all applications automatically)

  3. Benefits are delivered through mail (X days)

(feel free to adjust these section categories or use your own)


Discovery and application (X minutes total):

  1. ...

  2. ...

  3. ...

Processing (X days total):

  1. ...

  2. ...

  3. ...

Delivery (X days total):

  1. ...

  2. ...

  3. ...

What applications, systems, websites, tools, or other resources are used to process information or applications for this program?

Include tools used at all steps, including for application intake, record-keeping, benefits processing and delivery, status notification, data aggregation, reporting, or any other tools.

Do you cross-check eligibility information or other details with any other programs or data sources?

Do you report your program data to any organizations or stakeholders? What do you report and how is it reported?

PreviousOrganization assessmentNextGetting started with service design

Last updated 2 years ago

Was this helpful?