Events, Forms, And Applications

This page is written for staff who are new to C2 and need practical, step-by-step guidance.

Start Here: What These Tools Do

• Events help you schedule operations and track attendance.
• Forms help you collect structured information from members.
• Applications help you review and process candidate submissions.

A simple way to think about it:

• Events = scheduling and turnout
• Forms = data collection
• Applications = decisions and review workflow

Workflow: Create An Event

Prerequisites

• You can open the event creation screen.
• You have permission to create events.

Steps

1. Open Events and select Create.
2. Fill in event details.
3. Choose whether this is a one-time or recurring event.
4. Choose whether C2 should send Discord notifications.
5. Review and save as either:

• a draft (staff-only work in progress), or
• a published event (ready for participants).

Event Fields Explained

Expected Result

• The event appears in the event list.
• If saved as draft, it appears in draft views until published.

Common Issues

• Missing required fields (usually name/date/time).
• Recurrence settings that do not match the chosen recurrence type.
• Notification enabled with incomplete channel selection.

Workflow: Configure Recurrence (Optional)

Use recurrence when the same event repeats weekly, biweekly, or monthly.

Recurrence Fields Explained

Practical Tip

If your unit runs training every Saturday at 19:00, use:

• Type: Weekly
• Day: Saturday
• End: set one if you only want a seasonal run.

Workflow: Configure Event Notifications (Optional)

When To Use

Enable notifications when you want Discord posting to happen automatically.

Notification Fields Explained

Common Issues

• Notification turned on but no channel selected.
• Wrong role chosen (pings too broad or too narrow).

Workflow: Record And Manage Attendance

Prerequisites

• You can open an event detail.
• Attendance statuses are configured.

Steps

1. Open the event.
2. Review attendance by profile or by unit.
3. Apply statuses in bulk where appropriate.
4. Save and verify summary counts.

Attendance Statuses: Recommended Starter Set

• Attending
• Late
• Excused
• Unavailable
• No Response

Expected Result

• Staff can quickly see who is confirmed, uncertain, or absent.
• Unit-level attendance views stay current for planning.

Workflow: Build A Community Form

Prerequisites

• You can open the form builder.
• You have permission to create or edit forms.

Steps

1. Open Form Builder.
2. Add form metadata (name, description, tags).
3. Add fields in the order users should complete them.
4. Add validation rules where needed.
5. Preview and save.

Form Metadata Fields Explained

Common Field Types (With Examples)

Note: available field types can vary based on your C2 configuration.

Validation Rules In Plain Language

Validation rules help you keep data clean. Common examples:

• Required: user must answer before submitting.
• Minimum length: response must be detailed enough.
• Allowed options only: prevents free-text drift for standardized reports.

Workflow: Process Form Submissions

Prerequisites

• Form is active and visible to the right audience.
• Submission statuses are configured.

Steps

1. Open the form detail page.
2. Review incoming submissions.
3. Open each submission to inspect answers.
4. Update submission status as it moves through review.

Submission Status Examples

• New
• In Review
• Needs Follow-Up
• Approved
• Closed

Expected Result

• Staff can triage quickly and maintain a clean review queue.

Workflow: Configure And Process Applications

Applications follow a similar pattern to forms, but usually with stricter review discipline.

Suggested Application Pipeline

1. Received
2. Initial Review
3. Interview
4. Approved or Rejected

Steps

1. Define application questions in the configurator.
2. Define submission statuses that match your process.
3. Review each applicant submission.
4. Leave reviewer comments for handoffs between staff.
5. Move the application through your status pipeline.

Example Reviewer Comment Style

• Good: Strong radio discipline example. Verify availability for Saturday slot before approval.
• Weak: Looks fine.

Specific comments make handovers much easier.

New-Team Setup Template

If you are starting from scratch, use this quick template:

1. Create one training event with attendance tracking.
2. Create one debrief form with 5-8 fields.
3. Create one application form with clear stages.
4. Create statuses before collecting live submissions.
5. Run one internal test submission for each workflow.
6. Add one simple onboarding automation flow so new signups are processed consistently.

Related Pages

• Personnel Workflows
• Roles And Permissions
• Automation Flows
• Logs And Audit Trails
• Errors And Troubleshooting