Knowledge and Records Management

Document version tracking with access control, notes history tied to operational records, encrypted filestream storage, a Manual Library with compliance links, and integrated search across all knowledge records.

Notes history works differently from a comment field or a free-text annotation. In FireFlight, notes are tied to specific operational records a work order, a compliance task, a client record, an asset and retained in the exact form they were written, with the timestamp and author attached. The note that was added when a decision was made is still there six months later, in the context of the record it was written about, without anyone having to remember to preserve it.

The practical value shows up most clearly during investigations and audits. When a regulator or an internal reviewer asks what was known about a specific situation at a specific point in time, the notes history attached to the relevant record provides the answer directly. No one has to reconstruct the timeline from emails, meeting minutes, and personal recollections. The record was built in real time, in context, by the people who had the information. It is still there.

Workspace apps

Documents History Manual Library Custom Reporting Ad-Hoc Reporting Notes History

VA note: Manual Library app card is using the FireFlight placeholder icon. Replace with confirmed icon from the elementor/thumbs directory when available.

Integrated systems

ERP (Enterprise Resource Planning)

Meet Ikhana

Your Personal Guide on Every Page

From the first click to the final step, Ikhana, your on-screen tutor, shows you how it all works. Every field, every button, every page explained with clarity, right where you need it.

In the Knowledge and Records Management workspace, Ikhana walks through document upload and version approval, manual library categorization, note creation tied to specific records, and compliance reference linking. New team members learn the correct records management process on day one rather than developing their own approach that creates inconsistencies the next audit will find.

Learn more about Ikhana

What the workspace gives your operation

• Document version tracking and access control. Every document has a complete revision history: who created it, who changed it, what changed in each version, and when each version was accessed or approved. The current approved version is what opens in day-to-day operations. Previous versions are retained in history and accessible to authorized users for audit purposes. Access control at the file level defines who can view, edit, or approve each document type.
• Notes history tied to operational records. Notes are written in the context of the specific work order, compliance task, client record, or asset they apply to and retained in append-only format with timestamp and author. What was documented at each point in time is preserved exactly as it was written. The note attached to a compliance decision made eighteen months ago is still there, in context, when an auditor asks what was known and when.
• Fully encrypted filestream storage. All documents stored in FireFlight are encrypted at rest and in transit at the file level. Sensitive compliance records, personnel documents, and proprietary operational procedures are protected from unauthorized access regardless of how the system is accessed. Encryption combined with role-based access control makes a centralized document system more secure than the distributed shared drives most operations currently use.
• Manual Library with category and asset mapping. Safety manuals, SOPs, equipment guides, and regulatory references are categorized and mapped to the assets, processes, and compliance obligations they apply to. The relevant manual is accessible from the record it applies to not from a folder hierarchy that requires knowing where to look. For operations managing equipment across multiple sites, the mapping means a technician pulling up an asset record sees the applicable procedures in the same view.
• Document-linked compliance references. Permits, inspection records, regulatory submissions, and certification documents are linked directly to the compliance tasks or operational records they support. An auditor reviewing a compliance record sees the supporting documentation in the same view, attached to the task that required it, rather than in a separate folder that someone has to locate and produce separately under time pressure.
• Integrated search across all knowledge records. A single search covers document titles and content, note text, manual categories, and compliance reference associations simultaneously. Finding every record related to a specific permit condition, equipment model, or regulatory citation takes one search rather than three separate checks across document folders, the manual library, and note histories. For audit preparation and incident investigations, this is the difference between an hour of search and a few minutes.

What operations see after deployment

• Procedure updates reach every team member automatically. When a document is approved in a new version, the old version moves to history. No email distribution, no shared drive folder to update, no team member accidentally working from the superseded procedure three weeks later because the update did not reach them.
• Audits stop being reconstruction exercises. Supporting documentation is linked to compliance records at the time the work is done. When an auditor asks for the documentation behind a specific compliance event, the response is producing the linked record not searching through file folders for documents that may or may not be organized by the right name or date.
• Operational knowledge survives staff transitions. Notes, procedures, and decision records are in the system rather than in individual inboxes or personal drives. When someone leaves, the institutional knowledge they accumulated in those records stays in FireFlight. The next person in the role inherits the record, not a blank slate.
• Compliance gaps close before auditors find them. Document-linked compliance references and integrated search make it possible to identify records with missing documentation before an external review does. The organization finds the gap and addresses it rather than learning about it from an audit finding that requires a corrective action plan.

Questions compliance and records teams ask before deploying FireFlight

What does document version tracking do in FireFlight?

+

Document version tracking in FireFlight maintains a complete history of every document in the system: who created it, who modified it, what changed in each revision, and when each version was accessed. When a team member opens a document, they are seeing the current approved version. Previous versions are retained and accessible to authorized users, but they do not surface as the current document in day-to-day operations. For regulated environments where document control is a compliance requirement, this is the audit trail that answers regulators' questions without a manual reconstruction effort.

How does notes history work in FireFlight and what makes it different from a comment field?

+

Notes history in FireFlight ties written records directly to the operational records they reference a specific work order, a compliance task, a client record, or an inspection finding. Each note is timestamped, attributed to the author, and retained in the order it was created. Unlike a comment field that can be overwritten, notes history is an append-only record. What was known and documented at each point in time is preserved exactly as it was written, which is what makes it useful as a compliance reference and an operational audit trail.

What is the Manual Library in FireFlight and what does it store?

+

The Manual Library centralizes safety manuals, standard operating procedures, equipment guides, and regulatory references in a single searchable repository. Each manual is categorized and mapped to the assets, processes, or compliance requirements it applies to. When a technician needs the procedure for a specific piece of equipment, the relevant manual is accessible from the equipment record rather than from a shared drive folder that may or may not have the current version.

What does fully encrypted filestream storage mean for document security?

+

Encrypted filestream storage means every document stored in FireFlight is encrypted at rest and in transit. Encryption is applied at the file level, so documents are protected regardless of which storage layer they reside in. Access control defines who can view, edit, or download specific documents. Encryption and access control together protect sensitive operational, compliance, and personnel records from both unauthorized external access and unauthorized internal access.

How do document-linked compliance references work in FireFlight?

+

Compliance references in FireFlight link specific documents permits, inspection records, regulatory submissions, certification records directly to the compliance tasks or operational records they support. When a compliance task requires documented evidence, the linked document is attached to the record rather than referenced by filename in a separate tracking spreadsheet. Auditors reviewing a compliance record see the supporting documentation in the same view, not in a separate folder that someone has to locate and produce.

How does integrated search work across all knowledge records in FireFlight?

+

FireFlight's integrated search covers the full knowledge and records workspace: document titles, document content, note text, manual categories, and compliance reference links. A search for a specific regulation number, equipment model, or procedure name returns results from documents, manuals, and notes simultaneously. For operations where critical information is distributed across multiple document types, this is the difference between finding what you need in seconds and spending twenty minutes checking three different locations.

How long does it take to deploy the Knowledge and Records Management workspace?

+

Most operations are running live document management and manual libraries in weeks, not months. The timeline depends on the volume of existing documents being migrated, the category structure being built for the Manual Library, and the complexity of the compliance reference mappings. PCG handles configuration and document migration. Your team does not rebuild the document library from scratch.

Allison Woolbert

Principal, Phoenix Consultants Group  |  Developer, FireFlight Data Systems

PCG founded 1995. 500+ applications built across 31 years, roughly one-third in regulated environments where software failure carries direct operational and compliance consequences. FireFlight is the platform built from that body of work. When you contact PCG, Allison is the person who answers.

phxconsultants.com LinkedIn

FireFlight Data Systems is a product of Phoenix Consultants Group. PCG founded 1995. All system configurations are custom-built for each deployment. Implementation timelines, module availability, and integration scope vary by organization. Contact PCG directly to discuss requirements specific to your operation.