---

Understanding Schild's operation workflow

Category: Operations
Summary:
This article explains Schild's operation workflow-the operations supported, how they work, and the rules.

---

Overview

Schild supports sixteen operation types—physical and cyber—and we’re adding more. Current types: alarm tests, compliance audits, equipment inspections, escorts, incident responses, lockups, meetings, patrols, penetration tests, perimeter checks, phishing simulations, posts, shifts, training sessions, transports, vulnerability scans.

Security vs. non-security

• Security operations (13): Alarm tests, compliance audits, equipment inspections, escorts, incident responses, lockups, patrols, penetration tests, perimeter checks, phishing simulations, posts, transports, vulnerability scans.
• Non-security (3): Meetings, shifts, training sessions.

Security operations are assigned only to approved security officers; non-security operations can be assigned more broadly. The workflow is simple: admins assign operations; assignees independently complete them and report back with results.

Lifecycle at a glance (how it fits together)

1. Create operation → add orders/tasks or reference policies.
2. Assign users → assignees are notified to accept or decline.
3. Do the work → check-in/out and attendance, complete orders/tasks.
4. Submit results → notes and evidence, mark items complete.
5. Admin review → verify evidence, triage follow-ups.

---

Access controls

Operations are where most users spend their time. Access is controlled by two layers:

1. Permissions (what actions you can perform), and
2. Sensitivity clearances (what data you’re allowed to see).

Assignees can always see and work on their own assigned operations. Broader access (e.g., browsing or editing ops) depends on permissions and, if used, clearance.

Permissions

Action	Meaning
View	Can view the operation.
Add	Can create new operations.
Change	Can edit existing operations.
Delete	Can remove operations.

Example: An administrator with view_alarmtest and change_alarmtest permissions can view and update alarm tests, but cannot create and delete them.

Sensitivity clearances

Sensitivity	Meaning
Top secret	Unauthorized disclosure could reasonably cause exceedingly great damage to the organization or associative parties (including people).
Secret	Unauthorized disclosure could reasonably cause serious damage to the organization or associative parties (including people).
Confidential	Unauthorized disclosure could reasonably cause damage to the organization or associative parties (including people).
Controlled, unclassified	All else

Using sensitivities when creating operations is optional.

Rules

• Users cannot be assigned to operations above their clearance.
• Users have to be designated security officers on their profiles in administration to be assignable to security operations.
• Users must have a user approval on their page in administration to be assignable to the particular operation type-for an alarm test, a user must have an alarm test user approval. Without the approval, the user will not appear as an option when selecting users to assign. Also, the user cannot be automatically assigned.
• In the case events are specified as requiring weaponry, users have to be approved for the weapon type to be assignable to the event. For example, if a post requires a firearm, the user must have on their profile a firearm user approval type-without the approval, the user will not appear as an option when selecting users to assign. Also, the user cannot be automatically assigned.
• Users who are not available during the window cannot be assigned to the operation, automatically or manually-when selecting users, those unavailable do not appear. The system does not select users who specify they're unavailable during the operation window.

---

Tasks/orders

Operations are designed to complete specific, actionable work and collect data. Meetings and training sessions use tasks; shifts and security operations (e.g., patrols, escorts, alarm tests, posts, etc.) use orders. The fields differ by operation type, but the purpose is the same: tell the assignee exactly what to do and what to capture.

What an order/task typically includes

• What to do – the action, scope, or control to check.
• Why it matters – short context or objective to avoid guesswork.
• How to do it – tools, method, access notes, safety/armed guidance.
• What to capture – fields/results to fill, photos or files to attach.
• Required? – mark as required when an assignee must complete it.

You can also keep instructions high-level by referencing policies/SOPs. If you don’t add orders for an operation, assignees won’t see a checklist—they’ll rely on policy guidance and free-form results.

Writing effective orders (quick tips)

• Be specific: "Inspect north door strike plate; attach photo."
• Be atomic: one action per order; use multiple orders for multi-step work.
• Be verifiable: say what evidence to attach (photo, doc, measurement).
• Be scoped: include location, asset identifier, or client reference.
• Be time-aware: if something must happen before/after a step, say so.

Rules

• Orders cannot be changed less than fifteen minutes before the event’s start. This protects officers from last-second scope changes. If you need a change inside this window, cancel and re-issue or create a follow-up operation.

---

Results

As work is completed, assignees submit results—one result per order/task—so admins can review what happened and what evidence was captured. These appear on the operation detail page at Operations → [Op type] → Op.

What a result contains:

• Task/order data.
• Notes (observations, outcomes, exceptions)
• Completed/not completed
• Timestamps (e.g., completed at time)
• Evidence: uploaded photos and documents tied to the specific order

Rules

• Uploaded media can be deleted, the results themselves cannot.

---

Attendance records

At check-in an attendance record is created, and at check-out the record is updated. These appear on the event page in administration immediately. They are also available under Organizations → Attendance records. Depending on the event specifics, attendance records show user coordinates at check-in and check-out. On the event page, user locations are also displayed on maps in relation to the event's site. The check-in and check-out times and coordinates are color-coded.

Color-coding, distance

Green	Yellow	Red
≤ .05mi	> 0.05mi	> 0.1mi

Color-coding, timing

Green	Yellow	Red
≤ 5m	≤ 10m	> 10m

---

Creating operations

Creating operations is simple:

1. Navigate to the desired operation by clicking or tapping Operations → [Op type].
2. Click or tap ADD [OP TYPE].
3. Fill out the fields.
4. Add orders as necessary.
5. Click or tap a save option.

You're all set!

Rules

• The event details cannot be changed after creation.
• It's possible canceling, but no later than fifteen minutes prior the event's start.

---

Deleting operations

Deleting operations is simple. There are two ways to delete operations. If you've prematurely created an event, or it's a no go:

1. Navigate to the desired operation by clicking or tapping Operations → [Op type].
2. Click or tap Delete, at the bottom.

You're all set!

If you've got a lot of operations without assignments living in administration:

1. Navigate to the desired operation type by clicking or tapping Operations → [Op type].
2. Select the checkboxes in the leftmost part of the rows.
3. Select the delete option in the Action dropdown.
4. Hit Go.

You're all set!

---

Editing operations

Although event details cannot be changed after creation, other details can. The other details include administrative notes, the tasks/orders, and results. Results include uploaded media. Administrative notes can be edited anytime, other details cannot.

Rules

• Attendance records are read-only.
• Results are read-only. The associated media is not.
• Tasks/orders are read-only later than fifteen minutes before event starts.

---

Viewing operations

Viewing operations is easy. Operations are viewable in administration and on the main site. In administration there are multiple ways of viewing. In administration a calendar view of all scheduled operations is available by navigating to Operations (clicking or tapping Operations). A list of all operations for an operation type past, present, and future is available by clicking or tapping the particular op type: Operations → [Op type]. Operation detail pages are viewable by navigating to the detail page at Operations → [Op type] → Op. On the main site, users can view their assigned operations by navigating to Profile → Requests and Profile → Duties. Assignments which have not received a response live in Profile → Requests. Assignments which have been accepted live in Profile → Duties.