Enterprise content management platforms are mature, well-engineered systems for controlling documents. Law firms, engineering companies and finance departments run on them. A food safety management system has a document control component, which is why these platforms get proposed for it, but documents are the smaller part of an FSMS. The larger part is records: thousands of them a month, each made against a limit, at a scheduled time, by a named person, with a verification by someone else and an alert when it does not happen. A document system does not know what a critical limit is. That is the whole difference, and it is why sites that implement a generic platform for food safety end up running paper or spreadsheets alongside it within a year.
What a document management system does well
Version control, approval workflows, access rights, search, retention and audit trails on documents. If your only problem were sixty procedures and the controlled copies on the floor, a document platform would solve it, and solve it well. FSSC 22000 and BRCGS auditors are satisfied by a properly configured document system for clause 7.5 and section 3.2 respectively. The trouble is that document control is one of perhaps thirty things an FSMS has to do.
What an FSMS needs that a document system does not have
- Scheduled records with alerts. A CCP check due every two hours, with an alert to the supervisor if it is fifteen minutes late. A document system has no concept of a record being due.
- Limits and forced corrective action. A temperature of 9°C against a limit of 5°C must open a corrective action that cannot be dismissed. A document system stores the form, it does not read the number.
- Separation of entry and verification. The operator records, the supervisor verifies, the auditor sees both timestamps. Approval workflows in document systems approve a document once, they do not verify a record every shift.
- Standards content. FSSC 22000 Version 7, BRCGS Issue 9, GLOBALG.A.P. IFA v6 and R638 requirements mapped to procedures, checklists and records, maintained when the standard changes. A document system is empty on day one and stays empty until you build all of it.
- Traceability and mass balance. Lots, movements, consumption and dispatch, with a trace in both directions. This is a data model, not a folder structure.
- Supplier evidence with expiry. Certificates that remind the supplier before they lapse and flag the quality team when they do.
- A floor interface. A four-item screen on a phone for the person doing the 06:00 check, offline, with the time preserved. Document platforms’ mobile apps are built around documents and workflows, not around recording a CCP against a limit in a wash-down area.
The cost comparison people miss
Enterprise content platforms are typically licensed per named user. A food plant with a quality manager, three supervisors, twelve operators and a technical manager needs seventeen licences to have everyone recording in the system, and then needs the forms, workflows and reports built by an integrator at a day rate. Seventeen per-user licences plus integrator days adds up quickly, and none of it buys food safety content. ASCloud is priced per site, from R3,800 per month for a full document FSMS, with the standards content included and the setup done by ASC food safety specialists in five working days.
When a document platform is still the right answer
If your group already runs an enterprise content platform for finance, HR and engineering, keep it for those. Some sites run both, with the corporate platform holding the top-level policies and the FSMS holding the operational procedures, checklists and records, linked by reference. That is a sensible architecture. What does not work is asking the corporate platform to be the FSMS.
What to ask a vendor who proposes a document system for food safety
Show me a CCP check that is overdue and the alert it sends. Show me a temperature entered above its limit and what happens next. Show me a mock recall from a finished lot back to supplier lots. Show me the FSSC 22000 Version 7 additional requirements mapped to procedures. If the answer to any of these is “we would configure that”, the integration bill has started.
A system that knows what a CCP is
Scheduled records, limits, alerts, verification, traceability and standards content, built in. Full document FSMS from R3,800 per site per month.
Frequently asked questions
Can ASCloud replace our document management system entirely?
For food safety documents, yes. For corporate documents outside food safety, most groups keep their existing platform and link the two by reference.
Does ASCloud have proper document control?
Yes. Version history, approval by authorised users, automatic withdrawal of superseded versions, a document register and clause mapping. It meets ISO 22000 clause 7.5 and BRCGS section 3.2.
Can we import documents from our current document system?
Yes. Setup loads your current document set in Word, PDF or exported form and maps it to the relevant clauses.
Is pricing really per site with unlimited users?
Yes. Every operator, supervisor and manager on the site can have a login on the site plan.