Reference · built on requestOperator by FibricSafety, security & compliance

Incident Draft

Drafts an incident report from the ticket, badge events, camera links and alarms in the window. The safety lead edits and approves.

Request accessPricing ↗

About

An incident report is written after the fact by someone who has to visit several systems to find out what happened. Incident Draft does the gathering. When a ticket is tagged as an incident, it takes the time window and the location from the ticket, then pulls the door events from your access platform, the alarms and audit entries from your building platform, the alerts and footage links from your video platform, and the channel messages posted during the window.

It writes a first draft: a timeline, the people and doors involved, the alarms that fired, and links to each source. The safety lead edits the draft and approves it. It is attached to the ticket with the sources it was built from.

This is a reference listing. It documents what Fibric would read from Incident Draft and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Incident tickets in Jira Service Management, ServiceNow, or Freshservice, with their time, location and description fields
  • Door events in the window, by door and credential, from Verkada Get Access Events or Brivo Access Events
  • Alarms and audit entries in the window from Metasys activities or the Desigo CC Event List, with priority and acknowledgement state
  • Camera alerts and footage links for the window, through Verkada Get Alerts and Get Link to Footage, or the Milestone XProtect Events and Alarms APIs
  • Messages posted to the incident channel in Microsoft Teams or Slack during the window
  • Work orders open at the location during the window, from MaintainX or UpKeep, where a contractor was on site

Proposed actions

  • Target capability: propose a draft incident report on the ticket, with timeline, people, doors, alarms and source links, for the safety lead to edit
  • Target capability: propose a footage hold request to the video administrator for the cameras and window named in the draft
  • Target capability: propose follow-up tasks on the ticket, such as witness statements or a door inspection, each assigned for approval
  • Target capability: propose a notice to the safety lead in Teams or Slack that a draft is waiting
  • Target capability: propose a wider window when door or alarm events cluster just outside the ticket's stated time

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Turn a slip-and-fall ticket into a timeline

    A Jira Service Management ticket names the lobby and a time. The operator pulls Verkada door events and alerts for the window, drafts the timeline with footage links, and attaches it for the safety lead.

    With Jira Service Management, Verkada

  • Draft a forced-door report with the alarm record

    A door forced event in Brivo coincides with a Metasys intrusion alarm. The operator drafts one report from both records, proposes a footage hold, and files it on the ServiceNow incident.

    With Brivo Access, Johnson Metasys, ServiceNow

  • Keep the channel chatter with the report

    Messages posted to the incident channel in Teams during the window are quoted in the draft with their times, so the Freshservice report reflects what people saw as it happened.

    With Microsoft Teams, Freshservice

Requirements

  • A ticket connector with an incident type or tag, such as Jira Service Management, ServiceNow, or Freshservice
  • An access control connector that serves door events by time and door, such as Verkada or Brivo
  • A building platform connector that serves alarms with timestamps, such as Johnson Metasys or Siemens Desigo CC
  • A video platform connector that serves alerts or footage links by camera and time, such as Verkada or Milestone XProtect
  • A messaging connector for the incident channel, such as Microsoft Teams or Slack
Authentication
Incident Draft carries no credentials. It reads tickets, door events, alarms, video links and messages through the connectors you have connected, and writes the draft back only through the ticket connector once approved.

Limits

  • The draft is built from records. It does not interpret footage, assign fault, or state a cause. Those sentences are the safety lead's.
  • Footage is linked, not copied. Retention on the video platform still governs whether a link plays later, which is why a hold is proposed.
  • Door and alarm history reaches only as far back as each platform's API serves it.
  • Nothing is sent to an insurer, a regulator, or the police. The approved report stays on the ticket until a person sends it.

Access and pricing

Reference listing. Fibric builds the operator under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Incident Draft ↗

Questions and answers

Who signs off on the report?
The safety lead, or whoever you name. The draft arrives as a proposal on the ticket. They edit any line, add what the records cannot show, and approve it. The approved text is what the ticket keeps; the draft is kept beside it.
Does it decide what caused the incident?
No. It lists what the systems recorded, in order, with a link to each source. Cause, fault, and corrective action are written by a person. A blank section is left for them.
What is kept after approval?
The approved report on the ticket, the draft it came from, every source link, who approved it and when, and any footage hold request that was made. If the report is later amended, the earlier version stays.
Ask about Incident Draft

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This operator is developed, published, and supported by Fibric. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy