Working as a team: roles, audit trail and who-changed-what

A solo formulator can keep everything in their head. The moment a second person touches a formula — a colleague, a reviewer, a quality manager — you need answers to questions a spreadsheet cannot give: who can change what, who changed this, and when. Team formulation needs structured roles, an audit trail, and a clear record of who-changed-what. These turn a shared formula from a source of confusion into an accountable, controlled asset. Here is how software provides them.

Roles: who can do what

When several people work in the same system, not everyone should be able to do everything. A formulator builds formulas; a reviewer approves them; a viewer can look but not change; an admin manages the setup. Structured roles — owner, admin, formulator, reviewer, viewer — give each person the right level of access, so people can do their job without being able to accidentally or inappropriately change things outside it.

This is the difference between a free-for-all and a controlled environment. Roles encode who is responsible for what, which is the foundation of any serious multi-person workflow — and a prerequisite for approval steps, where only a reviewer can approve.

The audit trail: what happened

The second essential is an audit trail — an append-only record of what happened: which formula or ingredient was changed, by whom, and when. Unlike a spreadsheet, where a change overwrites the past silently, an audit trail keeps the history, so you can always reconstruct what was done. Nothing important happens invisibly.

This matters for two reasons. Operationally, it answers "who changed this and when" — invaluable when something looks wrong and you need to understand how it got that way. And for compliance, an audit trail is the backbone of accountability: regulated work expects you to be able to show the history of changes to a product.

Who-changed-what, on every record

Concretely, this shows up as "last modified by" and a change history on formulas and ingredients. You can see who created a record, who last changed it, and — through the audit trail — the sequence of changes over time. When a colleague asks "who updated this formula?", the answer is right there, not a matter of guesswork or accusation.

This transparency is healthy for a team: it is not about surveillance but about clarity and accountability — everyone can see the state of shared work and how it got there.

Why this enables real collaboration

Roles and audit together are what make genuine collaboration safe. Tasks can be assigned knowing who has which role; formulas can be reviewed and approved knowing only the right people can approve; changes can be made knowing they are recorded. Without these, multi-person work is risky — anyone can change anything, and no one knows who did what. With them, a team can work on shared formulas confidently.

A foundation, built early

Roles and audit are foundations, best in place before a team and its data grow large. Retrofitting accountability onto a system already full of unattributed changes is painful; having it from the start means every change is attributed and every permission enforced from day one. For a growing team, this foundation is what keeps shared formulation controlled as it scales.

Because record-keeping and accountability requirements differ by market and quality system, confirm the requirements that apply to your specific operation rather than relying on a general summary.

Where Lemoniq fits

Lemoniq provides the team foundations: structured roles — owner, admin, formulator, reviewer, viewer — so each person has the right access; an append-only audit trail recording what changed, by whom, and when; and who-changed-what visibility, with "last modified by" and change history on formulas and ingredients. Together these make team formulation accountable and safe, support review and approval workflows, and provide the change history regulated work expects — built in from the start, not retrofitted.

The takeaway

When more than one person touches a formula, you need roles (who can do what), an audit trail (what happened), and who-changed-what visibility — the things a spreadsheet cannot provide. Structured permissions and an append-only audit log make team formulation accountable, enable review and approval, and supply the change history compliance expects. Build these foundations early, and a growing team can work on shared formulas with confidence and clarity.

Lemoniq gives teams structured roles, an audit trail, and who-changed-what visibility — so shared formulation is accountable and safe. We solve this exact problem. See how it works