PDF export
Turn the evidence you need into a shareable PDF.
Filter to the relevant records, then export the evidence set for review, audit or inspection.
CSA FSMS · Australia
Food-safety evidence ready when you need it.
Replace paper registers, spreadsheets and scattered evidence with structured checks, corrective actions and searchable records — so kitchen teams run food safety every day and managers can prove what happened when a regulator, auditor or board asks.
Built for restaurants, hotels and multi-site hospitality. Australian operating controls can be configured around Standards 3.2.2 and 3.2.2A and your business procedures.
One operational view
Know what is done, overdue and still open.
94%checks completed
3overdue controls
5open corrective actions
128attributed records today
Illustrative sample data. Property and group dashboards show where attention is required before it becomes an audit problem.
Daily controlsPhone, tablet or desktop
Corrective actionsFailure → action → close-out
Searchable evidenceFilter, review, CSV or PDF
Multi-site visibilityProperty and portfolio views
Australian food-safety management
Daily control first. Evidence follows automatically.
Standard 3.2.2A adds food-safety management tools for specified food-service, catering and retail businesses. Category one businesses must substantiate critical food-safety controls; category one and two businesses also have food-handler training and food-safety supervisor requirements.
- CSA focuses on the operational evidence layer. Checks can capture what was monitored, the result, who completed it, when it happened and what action followed.
- Records stay usable. Search, filter and export evidence instead of rebuilding an audit trail from folders, spreadsheets and messages.
- Your procedures remain yours. Forms, frequencies, limits and escalation rules are configured to the operation and the requirements that apply to it.
Regulatory reference: FSANZ — Standard 3.2.2A food safety management tools ↗
Real product. Real workflows.
See CSA FSMS in action.
Start with the management view, then see how teams retrieve evidence and handle frontline controls and corrective actions.
Five short workflows using the real product and sample/demo data.
Management view
See the whole operation before you chase anyone.
Completion, open corrective actions, audit scores and properties needing attention are visible in one management view.
From management view to evidence
What the kitchen team sees
Frontline control
A failed reading becomes an action.
The out-of-range result stays on the record and requires the corrective action before submission.
Evidence
Keep the proof with the corrective action.
What was done and the supporting photo stay with the same food-safety record.
Close-out
Close the loop after verification.
A supervisor can review the original record, recheck the issue and document the close-out.
From paperwork to proof
Food safety should not depend on finding the right folder.
CSA shows what was due, what happened, who completed it, what failed and what was done about it — without waiting for someone to send a spreadsheet, photo or message.
See today at a glance
Done, due and overdue controls are visible before service finishes.
Know who did what
Records carry the person, role, outlet and submission time.
Fix failures on the record
Corrective actions stay connected to the original result.
Retrieve evidence quickly
Filter to the exact dates, property, control or status being requested.
Record Explorer · sample evidence
Chiller 1 · 3.4°C07:48 · Main KitchenPASS
Cooling check14:20 · BanquetsCA OPEN
Hot holdingDue 18:00 · RestaurantDUE
Close-of-shift clean22:05 · Main KitchenDONE
Australian operating controls
Configure the checks around the controls your operation must demonstrate.
CSA does not hard-code one generic checklist for every business. The underlying forms, limits, frequencies and evidence rules can be configured to the operation.
Cold & hot holdingUse the applicable temperature-control limits and record the result against the equipment or food item.
CoolingCapture staged cooling readings and elapsed time so the process can be demonstrated.
Processing & cookingSet validated critical limits for the food/process and require action where the result falls outside them.
Goods receivedRecord condition, temperatures, supplier details and exceptions at receiving.
Cleaning & sanitisingSchedule checks, assign responsibility and preserve evidence of completion.
Equipment & calibrationKeep equipment, maintenance and probe-calibration history connected to operational records.
Temperature framework
Australian food-safety guidance generally defines temperature control for potentially hazardous food as 5°C or below or 60°C or above, unless the business can demonstrate another safe time/temperature approach. The 2-hour/4-hour rule and prescribed cooling requirements can also be built into relevant checks.
References: FSANZ 2-hour/4-hour rule ↗ · processing and cooling guidance ↗
Who it is for
One FSMS, configured for the complexity of the operation.
Restaurants & cafés
Run the controls without turning food safety into paperwork.
Daily checks, evidence, corrective actions and management review in one operating workflow.
Hotels & resorts
Control multiple kitchens, outlets and service periods.
Keep property-wide food-safety evidence, roles, documents and corrective actions connected.
Groups & multi-site
See where attention is needed across the portfolio.
Standardise core controls while retaining property-level settings and accountability.
Roles and accountability
Kitchen teams log. Supervisors verify. Leaders see the whole operation.
Kitchen
- Complete scheduled and event-based records
- See limits and prompts on screen
- Record corrective action when required
- Work offline and sync later
Supervisor
- Review property completion
- Verify and close corrective actions
- Search and export evidence
- Review issues and exceptions
Director / group
- Configure properties and forms
- See group completion and overdue work
- Monitor open corrective actions
- Standardise controls across sites
Data and security
Evidence should not be quietly rewritten after the event.
CSA is designed around attributed, traceable records and controlled access rather than editable spreadsheets.
Append-only operational evidence
Submitted records are preserved. Corrections are made through new entries rather than silently overwriting the original evidence.
Server-attributed identity
The signed-in session establishes who submitted the record, the role and the property context.
Client and property separation
Access is scoped to the business and property. Group roles can see the portfolio without exposing one client to another.
Offline continuity
Operational entries can be held on the device and synchronised when connectivity returns.
Exportable evidence
Filtered evidence can be reviewed on screen and exported as CSV or PDF for audit, regulator, insurer or internal review.
Private documents and photos
Supporting files are stored privately and accessed through the signed-in application rather than public links.
Hosted on Cloudflare and served over HTTPS. Detailed security, backup and business-continuity documentation can be provided during due diligence.
Implementation
Start with the operation you already have.
CSA is configured around your properties, kitchens, responsibilities and existing food-safety procedures rather than asking the operation to adopt a generic software template first.
01 · BASELINE
Map the operation
Properties, kitchens, service models, equipment, existing records and applicable controls.
02 · CONFIGURE
Build the working controls
Forms, frequencies, limits, roles, corrective-action rules and supporting registers.
03 · DEPLOY
Launch and verify
Train the operating team, monitor completion and adjust the setup based on real use.
Australian commercial model
Pricing is scoped to the operation, not restricted by feature tiers.
For Australian clients we currently quote based on property count, operational complexity, configuration and implementation requirements. The standard FSMS feature set remains complete.
Hemant Dadlani
Founder · Sydney, Australia
Built from hospitality operations
Designed around how professional kitchens actually work.
CSA FSMS grew from recurring operating problems: incomplete records, weak corrective-action follow-through and evidence that becomes difficult to retrieve when it matters. The platform combines hospitality operating experience with structured food-safety controls and digital evidence.
LinkedIn profile ↗Questions
Does CSA FSMS replace paper food-safety records?
Yes. Daily, weekly, monthly and event-based checks can be completed digitally on a phone, tablet or computer. Each record is attributed to the signed-in user and retained with its submission time and operating context.
How does CSA FSMS support Standard 3.2.2A?
For businesses to which the evidence requirements apply, CSA can capture and retain operational evidence for relevant prescribed controls such as receiving, storage, processing, display, transport, cleaning and sanitising. It supports food-safety management and substantiation; it does not certify compliance or replace requirements set by an authorised officer or regulator.
Does the system decide whether our business is Category 1 or Category 2?
No. Classification depends on the activities of the food business. CSA can be configured once the applicable requirements and operating controls have been confirmed. State, territory and local requirements should also be checked.
Can records be edited or deleted?
Submitted operational evidence is designed to be append-only. A correction is made as a new entry while the original remains in the history.
Can we export records for an authorised officer or auditor?
Yes. Record Explorer lets authorised users filter the history and export the relevant evidence set as CSV or PDF.
Does it work without internet?
Operational entries can be saved on the device and synchronised when connectivity returns. The interface shows when items are waiting to sync.
Can one group run different properties?
Yes. Each property can keep its own operational settings while central leaders see portfolio completion, overdue checks and open corrective actions.
Is CSA FSMS endorsed by FSANZ or a regulator?
No. CSA FSMS is independent software. It supports food-safety management, evidence and audit readiness; it does not provide regulatory approval, certification or legal advice.
Request a demo
Show us the operation. We will show you how CSA would fit it.
For Australian restaurants, hotels and hospitality groups, we can walk through the platform using realistic kitchen data and discuss the controls, evidence and rollout structure relevant to your business.