Features / Operations

Security team

The safety team has its own roster and its own incident file.

Incidents, training, and the schedule live with the people who serve on security. An incident locks when it is submitted. Notes and files can still be added after that.

The moment this is for

Safety schedules get copied from the greeting roster, and an incident write-up lives in a personal document that can still be edited next month.

01 · The team

Their own people and their own Sundays

The roster and the schedule belong to the security team. A background check can be required before someone is placed.

02 · The file

Write a draft, then submit it

An incident moves from draft to submitted, and then the account of what happened locks. You can still add notes and files. The original account does not stay editable.

03 · The training

Training and expirations sit on the person

Training, expirations, and procedure acknowledgements sit next to the people who serve, so a lapse is visible before the Sunday they are scheduled.

04 · Not facilities

A repair is not an incident

A leak or a broken door is a work order. An incident file is for what happened, not for tracking a building repair.

Who feels the difference

Pastor

You can read what was submitted, as it was submitted.

Admin

The safety schedule is not a copy of the greeting schedule.

Volunteer

Training dates are on your record, not in a group text.

Family

The people at the door are a team with a record.

After a Sunday incident

The file is submitted before the debrief

The lead writes what happened, attaches the notes, and submits. The account locks. Monday’s debrief reads that file. If the door also needs a repair, that is a separate work order.