Skip to main content

Template-Driven Flows

Scenario: Your organization needs consistent processes. Whether it's a healthcare facility processing patient intake, a legal firm managing new cases, or an HR team handling employee requests, every case must follow the same structure and workflow.

The Problem

Without standardized templates, teams face:

  • Inconsistent data: Different staff capture different information, making it impossible to aggregate or report reliably
  • Missing critical information: Important details get skipped because there's no checklist; only discovered later when it's needed
  • Training burden: Every new hire needs extensive training on what to collect and how to process cases
  • Compliance risks: Auditors can't verify that required steps were followed; documentation is incomplete
  • Reporting gaps: Data inconsistency makes it impossible to generate meaningful reports or analytics
  • Rework: Cases sent back repeatedly because required fields are missing or incorrect

How Avikto Solves It

Template-Based Case Creation

In Avikto, you design case templates that define exactly what data gets captured for each case type. A template is like a form that guides users through case creation.

Example: Healthcare Patient Intake Template

Section 1: Patient Information
- Full Name (Required)
- Date of Birth (Required)
- Contact Phone (Required)
- Email Address
- Insurance Provider (Dropdown: Blue Cross, Aetna, Cigna, Self-Pay)

Section 2: Visit Reason
- Chief Complaint (Required, Text)
- Symptom Duration (Dropdown: < 1 day, 1-3 days, 1-2 weeks, > 2 weeks)
- Severity (Dropdown: Mild, Moderate, Severe)
- Related Medical History (Optional, Rich Text)

Section 3: Appointment Details
- Preferred Provider (Dropdown, can be empty)
- Appointment Type (Dropdown: Virtual, In-person, Phone)
- Preferred Date Range (Date picker)
- Scheduling Notes (Optional, Text)

Every patient intake now captures the same information, in the same format, with the same quality.


Building Template-Driven Workflows

Step 1: Design the Template

Your template defines the "shape" of the data. When you design a patient intake template, you're saying: "Every patient case must have these fields."

Key Template Elements:

  • Required fields — Must be filled before case submission
  • Field types — Text, numbers, dates, dropdowns, checkboxes, rich text, file uploads
  • Conditional fields — "If Insurance = Self-Pay, collect payment method"
  • Field validation — Phone numbers must be valid format, dates can't be in the past
  • Help text — Guide users on what to enter
  • Sections — Organize related fields (Patient Info, Visit Details, Insurance)

Step 2: Standardize the Workflow

Once a case is created from your template, it enters a defined workflow:

Workflow: Patient Intake Process

1. New Case Created (from Patient Intake template)

2. Triage (Staff reviews completeness, assigns to appropriate department)

3. Pre-screening (Nurse reviews and flags any concerns)

4. Provider Review (Provider determines next step)

5. Appointment Scheduled (Case moves to appointment system)

6. Follow-up (Post-visit check-in)

7. Closed (Case resolved or archived)

Every case flows through these stages. Workflows automate the transitions:

Trigger: Case created from "Patient Intake" template
Conditions: All required fields complete
Actions:
- Move to queue: "Triage"
- Notify: Triage staff
- Set status: "Waiting for Review"
- Set due date: Today + 4 hours

Practical Examples by Industry

Healthcare: Patient Intake

Template captures:

  • Patient demographics
  • Chief complaint and history
  • Symptoms and severity
  • Urgency level
  • Insurance and payment info
  • Provider preferences

Workflow:

  • New → Triage → Pre-screening → Provider Review → Scheduled → Follow-up → Closed

Automation benefits:

  • ✅ Ensures no patient information is missing
  • ✅ Routes urgent cases (severe symptoms) to providers instantly
  • ✅ Schedules follow-ups automatically
  • ✅ Generates patient reports for records

Template captures:

  • Client name and contact
  • Case type (contract, litigation, compliance, etc.)
  • Case summary
  • Key dates (deadline, important milestones)
  • Parties involved
  • Document uploads
  • Billing classification

Workflow:

  • New → Initial Review → Attorney Assignment → Research → Discovery → Settlement/Closure

Automation benefits:

  • ✅ All case details captured consistently
  • ✅ Critical deadlines are visible from day one
  • ✅ Cases automatically routed to specialized attorneys
  • ✅ Billing is standardized and trackable

HR: Employee Request

Template captures:

  • Employee ID and name
  • Request type (Time off, expense, equipment, training)
  • Details specific to request type
  • Manager approval routing
  • Urgency level
  • Cost/budget impact (if relevant)

Workflow:

  • New → Department Manager Approval → HR Review → Finance Approval (if needed) → Completed/Denied

Automation benefits:

  • ✅ Different request types flow through different approval chains
  • ✅ Finance is automatically notified of high-cost requests
  • ✅ Employees get status updates automatically
  • ✅ Reports show request volumes and approval times

Advanced Template Features

Conditional Fields

Show or hide fields based on user selections:

Question: "What is the nature of the request?"
Option A: "Time Off" → Show fields: Start Date, End Date, Reason, Coverage Plan
Option B: "Equipment" → Show fields: Equipment Type, Quantity, Justification, Budget Code
Option C: "Training" → Show fields: Course Name, Provider, Cost, Learning Objective

This keeps the form clean and relevant to each request type.

Field Validation

Ensure data quality:

Phone Number: Must match pattern (###) ###-####
Email: Must be valid email format
Date: Cannot be in the past (for appointments)
Dropdown: Only predefined values allowed
Number: Must be between 0 and 100
File Upload: Accepted formats: PDF, DOCX, images only; Max 10 MB

Multi-Step Templates

For complex processes, break the template into steps:

Step 1: Basic Information (Name, Contact, Type)
Step 2: Details (specific to the request type)
Step 3: Attachments (supporting documents)
Step 4: Review & Approval (confirmation before submission)

Users complete the template over multiple pages, not all at once.


Template Versioning

As your process evolves, templates can be updated without breaking existing cases:

Patient Intake Template
├── v1.0 (original)
├── v1.1 (added insurance verification field)
└── v2.0 (restructured for new clinic workflow)
  • New cases use the latest version
  • Old cases keep their original template
  • You can view history showing what template version each case used

Reporting and Compliance

Because all cases use the same template structure, you get:

Data Quality

  • ✅ No missing critical information
  • ✅ Consistent field formats
  • ✅ Reliable data for aggregation and analysis

Reporting

  • ✅ Custom reports based on template fields
  • ✅ Dashboards that aggregate data across cases
  • ✅ Export data for external analysis

Compliance

  • ✅ Audit trail showing all required fields were filled
  • ✅ Proof that cases followed defined processes
  • ✅ Comprehensive documentation for regulatory reviews

Example Reports

Patient Intake Report (Healthcare):
- New patients by week
- Intake completion rate (% with all fields complete)
- Average time in each workflow stage
- Patient volume by chief complaint
- Insurance coverage distribution

Request Fulfillment Report (HR):
- Requests by type (time off, equipment, training)
- Approval time trend
- Approval/denial rates
- Cost impact summary
- Bottleneck analysis (which stage slows requests)

Getting Started with Templates

Phase 1: Design

  1. Map your current manual process
  2. Identify all data you need to capture
  3. Define field types (text, dropdown, date, etc.)
  4. Add validation rules and help text
  5. Organize fields into sections

Phase 2: Build

  1. Create the template in Avikto
  2. Test with a few sample cases
  3. Refine based on feedback
  4. Get stakeholder approval

Phase 3: Deploy

  1. Train staff on the new template
  2. Set it as the default for new cases
  3. Migrate existing relevant cases (if applicable)
  4. Monitor for questions and adjust as needed

Phase 4: Optimize

  1. Review feedback after 2-4 weeks
  2. Adjust fields that are confusing or redundant
  3. Add automation rules as patterns emerge
  4. Create reports to track case health

Key Benefits Summary

BenefitImpact
ConsistencyEvery case captures the same information, every time
QualityValidation prevents bad data from entering the system
SpeedPre-defined fields and logic make case creation faster
TrainingNew staff understand the process because it's built into the form
ComplianceAudit-ready documentation showing every required step was followed
ReportingClean, consistent data enables reliable analytics
AutomationWorkflows can act based on template fields with confidence

Next: Learn how to create and manage templates in detail.