What to take into your next decision
- Record observation and interpretation separately.
- Distinguish a contact attempt from a confirmed handoff.
- Keep evidence references and unresolved follow-up connected to the record.
Begin with an identifiable event
Include an incident reference, client account reference, site, camera or zone, event type and the time zone used. Keep the event time, review time and action time separate when the system provides them. Do not make different clocks look comparable without checking their time settings.
Use the reference to connect notes, media and later updates. If a recording is unavailable or the camera view is obstructed, record that limitation. An incomplete view is useful context for the recipient; omitting it makes the account sound more certain than it is.
Define the fields before choosing the report format
The following is a proposed blank structure for partner discussions. It is not an export from 1Degree software, a customer incident or a guarantee of a particular reporting format.
| Record field | What belongs here |
|---|---|
| Reference and location | Incident reference, account reference, site and exact monitored zone. |
| Times and time zone | Event received, review started, each action, handoff and closure; note unavailable timestamps. |
| Observed activity | Visible action, direction of movement and relevant scene conditions. |
| Verification status | Confirmed authorized activity, unresolved activity, technical issue or other approved classification. |
| Operator actions | The action taken, its time and the instruction or authority used. |
| Contact attempts | Contact role, method, attempt time and whether contact was established. |
| Handoff | Recipient, acknowledgment, information supplied and external reference if provided. |
| Media references | Clip or image reference, relevant time span, access restrictions and any unavailable media. |
| Outcome and limits | Last observed state; distinguish it from later information reported by someone else. |
| Follow-up | Open issue, assigned owner, next action and review status. |
Use wording that preserves the evidence
Describe activity before assigning intent. The examples below are writing examples only, not accounts of real incidents.
| Avoid collapsing the distinction | Prefer an observable statement |
|---|---|
| A thief entered the site. | A person crossed the marked boundary; authorization could not be confirmed from the available information. |
| The police responded. | A call was placed to the designated contact. Record acknowledgment or attendance separately when confirmed. |
| The incident was prevented. | The person left the camera view after the audio message; subsequent activity was not visible. |
| The area was clear. | No person was visible in the reviewed camera views during the recorded check. |
Read a completed example without filling in the gaps
Fictional training example: a person is visible near a closed loading gate. The purpose is to show how a record preserves uncertainty, not to describe a customer incident or a response-time commitment.
| Field | Example entry |
|---|---|
| Observation | A person approached the loading gate and remained in view. The gate appeared closed; lock status was not visible. |
| Account context | No scheduled visit was listed in the instructions available for this review. |
| Action and contact | A call was attempted to the designated site contact. No answer was received. |
| Handoff status | No handoff acknowledged. The next authorized contact remains the next step in the contact ladder. |
| Outcome | Authorization unresolved. No conclusion about criminal intent or prevention recorded. |
Make a handoff more than a sent message
A sent email, unanswered call and acknowledged handoff are different states. Record the method, the intended recipient's role, the result and the next action under the site's escalation instructions.
If a guard, client representative or public-safety contact provides an update, attribute it to that source and record when it was received. The operator's observation and another person's report can sit in the same record without being presented as the same kind of evidence.
Do not add a guaranteed arrival time or a conclusion about liability to an event report. Keep the record focused on the service activity and the information available.
Keep access, retention and corrections usable
Decide who may receive the report and who can access its media. A working clip link for an operator may be inaccessible to the intended partner recipient. Test that handoff using the agreed access roles.
Define the relevant retention and export arrangements with the account owner and provider. Do not assume a report link preserves the underlying recording indefinitely. The report should make an unavailable or expired evidence reference clear.
When correcting a record, preserve the original entry where the system allows and identify the correction, author and time. Keep unresolved follow-up visible until the assigned person records its outcome.
Review a specimen before launching the account
Ask the provider to walk through a permitted, redacted specimen or a clearly labeled demonstration. Check whether your team can identify the event, understand the actions, access the authorized evidence and find the remaining owner for follow-up.
Use the blank template to identify required fields, then discuss the actual report format and delivery route.
Questions partners ask
Should every alert be described as an incident?
Use the account's classification rules. Preserve the distinction between an alert, an observation, an authorized activity, an unresolved event and a technical issue.
What if the contact does not answer?
Record the attempt separately from an acknowledged handoff, then follow the account’s authorized fallback route. The record should identify the next action and its owner.
