Quinabra

Context

Quinabra is a mid-sized chemical manufacturer in São Paulo, operating under sanitary regulation — ANVISA, good-practice validations, systematic audits by regulators and by B2B clients (multinationals that audit a supplier before approving a batch).

Control of regulatory activities — equipment calibration, method validation, mandatory training, SOP review, supplier qualification — historically lived in physical notebooks, some with 8-10 years of history, kept per area. When an audit came, the director assembled the picture by going notebook by notebook, page by page, building the overview on the spot.

The pain

Two structural problems:

• Pre-audit recomposition time. Each audit required 2-3 days of the directors’ work to reconstruct what was current, what had expired, what had been done but not recorded. Important intellectual work (regulatory decisions) got held back.
• Risk of an undetected gap. The notebook only reveals what happened, not what should have happened and didn’t. An expired calibration, an outdated SOP, training that needed redoing — these only showed up when the auditor asked or when the problem had already appeared in a batch.

The director described the problem precisely: “I don’t have time to look at what hasn’t happened yet.”

The solution

We moved control to a system built on a codified recurring-task model:

• Catalog of regulatory activities — each activity (calibration X, validation Y, training Z) registered with frequency, owner, and required evidence.
• Automatic generation of recurring tasks — the system fires the task before the due date, with deadline, owner and an evidence checklist. Nothing depends on “someone remembering.”
• A single screen with time and category filters — the directors see in 30 seconds what’s current, what’s due in 30/60/90 days, what’s overdue.
• Native audit trail — every task execution is recorded with who did it, when, and the evidence attachment. External audits get a formatted export with no rework.

Rollout ~6 weeks, with the regulatory catalog mapped together with the technical team.

The result

Measured in the first full audit cycle under the new model:

• Pre-audit prep time dropped from 2-3 days to a few hours. The directors recovered time equivalent to a week of work per quarter.
• Forward-looking visibility. For the first time the operation could see “what hasn’t expired yet” and act before the deadline. Overdue activity disappeared as a category.
• Calm during external audits. Filter ready on screen, evidence attached per task, exportable. The auditor covers the scope without touching a physical file.

How it would run today on F7 KORE

This project was delivered by the team behind F7 KORE, with a recurring-task system, checklists and an audit trail. On today’s platform, the same control would gain three things:

• Recorded at the source. Whoever performs the activity records it in the form on a phone or tablet; the photo of the evidence is read by the AI and fills in the record’s fields.
• Regulations tracking the catalog. A change in a sanitary regulation becomes an alert cross-referenced with the affected activities, instead of a discovery at the next audit.
• A trail third parties can verify. Every execution goes into a hashchain anchored in immutable storage: the external auditor checks the chain without relying on F7.