Reference · built on requestOperator by FibricSafety, security & compliance

Compliance Evidence

Collects work orders, inspection records and sensor logs against a control checklist. Proposes an evidence pack and lists the gaps.

Request accessPricing ↗

About

An audit asks for proof that the extinguishers were inspected monthly, the cold room stayed below its limit, and the emergency lighting was tested. The proof exists in several systems and a shared drive. Compliance Evidence works from a control checklist you keep in a sheet: each control names what counts as evidence, how often, and where it lives.

On the schedule you set, it reads completed work orders from your CMMS, inspection files from SharePoint or Google Drive, and readings from your sensor platform, and matches each to its control and period. It proposes an evidence pack, a folder per control with the matched records, and a gap list for every control with nothing to show. A person reviews the pack before it goes anywhere.

This is a reference listing. It documents what Fibric would read from Compliance Evidence 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

  • Completed work orders and procedure results from MaintainX or UpKeep, by asset, date and procedure template
  • Inspection files and their metadata in SharePoint or Google Drive, through the Microsoft Graph driveItem or Google Drive API, matched by folder and name
  • Sensor readings and alert history from Monnit or Disruptive Technologies, delivered by their data webhooks or data connectors
  • The control checklist you maintain in Google Sheets or Smartsheet: control, evidence type, frequency, source and owner
  • Open gap issues in Jira, so a gap already assigned is not proposed again

Proposed actions

  • Target capability: propose an evidence pack for the period: one folder per control in SharePoint or Google Drive, with the matched records linked or copied
  • Target capability: propose a gap list naming each control with missing or late evidence, its owner and the period it covers
  • Target capability: propose a Jira issue per gap, assigned to the control owner, with what evidence would close it
  • Target capability: propose a sign-off request to the compliance owner once the pack is complete, with the gap list attached

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

What you can build

  • Prove monthly extinguisher checks

    Each extinguisher's monthly inspection in MaintainX is matched to the control. Missing months become a gap per unit. The pack folder in SharePoint holds each completed procedure.

    With MaintainX, Microsoft SharePoint

  • Show the cold room held temperature

    Monnit readings for the walk-in cooler are matched to the temperature control by period, with any alerts listed beside the checklist row in Google Sheets. Days with no readings appear in the gap list, not silently as passes.

    With Monnit iMonnit, Google Sheets

  • Assign each gap before the audit

    Every control with no evidence gets a Jira issue for its owner, naming the evidence that would close it. The compliance owner approves the batch, and the pack lands in Google Drive a month before the audit date.

    With Jira, Google Drive

Requirements

  • A CMMS connector with completed work orders and procedure results, such as MaintainX or UpKeep
  • A file connector for inspection records and for the pack itself, such as Microsoft SharePoint or Google Drive
  • A sensor platform connector for readings that serve as evidence, such as Monnit or Disruptive Technologies, where a control needs them
  • A control checklist with evidence type, frequency and source per control, kept in Google Sheets or Smartsheet
  • A ticket connector for gaps, such as Jira
Authentication
Compliance Evidence signs in to nothing. It reads work orders, files and readings through the connectors you have connected, and the pack and gap issues are proposals until the compliance owner approves them.

Limits

  • Records match controls by asset, date, template and file location. A record with none of those markers is not matched and shows as a gap.
  • It does not judge whether an inspection was done well. A completed work order counts as evidence that it was done.
  • Sensor evidence depends on the platform serving history for the period. Readings from before the connector was added are not available.
  • The pack is assembled in your own file store. Nothing is sent to an auditor or regulator by the operator.

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 Compliance Evidence ↗

Questions and answers

What does the compliance owner approve?
The pack and the gap list. They see each control, the records matched to it, and the controls with nothing matched. They can reject a match, add a record by hand, or dismiss a gap with a reason. Approval writes the pack folder and opens the gap issues.
Is a gap the same as a failed control?
No. A gap means no evidence was found where the checklist said to look. The inspection may have been done and filed elsewhere. The gap issue asks the owner to supply it.
What record does the pack itself leave?
A manifest per pack: each control, the records matched, where they came from, who approved the pack, and the gap issues opened. Rebuilding the pack for the same period gives the same manifest unless the sources changed.
Ask about Compliance Evidence

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