FOG compliance software should not guess at local law. It should help teams preserve the operational records inspectors often request: service dates, readings, photos, manifests, signatures, and exports.
Organize the evidence, not legal opinions
Local FOG rules vary by jurisdiction. FOGProof focuses on timestamps, service readings, proof files, signatures, and exports so your team can show the work that happened.
Make the 25% rule easier to operationalize
Technicians enter grease, solids, and total liquid depth. FOGProof calculates the percentage and flags readings that are near or above the common service threshold.
Build packets before the inspection pressure hits
A branded packet pulls together service summaries, dates, volumes, files, signatures, and missing proof notes so records are not assembled from scratch under stress.
Keep jurisdiction-specific decisions outside the software
FOGProof stores the record. Your team still follows the cleaning frequency, forms, disposal rules, and submission process required by the local authority.
Grease trap FAQ
Does FOGProof guarantee compliance?
No. FOGProof helps organize operational records. Haulers and restaurants should follow their local FOG program, permit, and inspector instructions.
What FOG records should be easy to produce?
Common records include service dates, trap identity, readings, volume removed, disposal or manifest references, photos, notes, signatures, and next due dates.