Skip to main content
GullySystem
Other industries

Audit Trail for Organic farms

Record who changed important business data and when.

Platform

Does this function belong in your operation?

Use when changes to money, permissions or business records need accountability.

A monitored record is created, changed or deleted.

Every edit to a field record, input entry or lot is stamped with who changed it and when. Certifiers read the history without asking for a printout. Backdated entries stand out.

Bring the records the workflow depends on.

  • Events to record
  • User identities
  • Retention and access rules

Outputs to check

  • Event and change history
  • Restricted audit-review view
  • Exported investigation evidence

Follow the audit trail workflow.

Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.

  1. 1. Define event coverage

    List the records, actions and systems to be observed.

  2. 2. Capture the event

    Retain actor, timestamp, reference and relevant changed values.

  3. 3. Protect the history

    Apply restricted access and the agreed retention controls.

  4. 4. Investigate a change

    Trace the event sequence without editing the underlying evidence.

  5. 5. Export or retain evidence

    Record authorised access and preserve context needed to interpret the history.

Who uses the module, and who approves?

Keep responsibilities distinct even when one person holds more than one role.

Owner

Looks once, when something does not add up.

Accounts assistant

Settles a difference between the ledger and the print without calling three people.

Your accountant or auditor

Asks how a figure changed and gets the history, which is faster than a reconstruction.

Branch manager

Sees corrections made at the counter, and the reasons given.

Decide how exceptions are handled.

These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.

Shared user account

Flag the attribution limitation and assign individual accounts before relying on personal accountability.

Missing external event

Record the coverage gap instead of implying that all systems were monitored.

Deletion request

Apply authorised retention and legal review without allowing ordinary users to rewrite event history.

Can this work independently?

An audit trail must receive events from the business processes being reviewed; it is not a standalone source of truth for systems it cannot observe. Roles control review access, and retention rules determine how long event evidence is kept.

Systems and records it connects with

  • Roles and permissions: Named user access and action-level authority.
  • Invoice management: Issued invoice references, line amounts and outstanding balances.
  • Workflow and approvals: Authorised decisions and pending request status.
  • Finance and accounting reporting: Ledger-based period totals and reconciliation outputs.

Configure, test and introduce the workflow.

  • You list the records where a silent change would hurt: rates, receipts, credit limits, payouts. You get a written note of the fields to be logged and those left out. Start small.
  • Assign named users and confirm which actions are recorded. In a trial environment, change representative records and verify actor, timestamp and before-and-after values. Check that ordinary users cannot alter the history.
  • The owner names the few people who can open it. Access rules are written down, and each of those people has a test login. Access stays narrow. The log runs alongside normal entry. After a month the group meets to see which questions it answered and which fields should be added.

Check the result before rollout.

Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.

  • Recorded changes identify an actor and time.
  • Reviewers can distinguish earlier and current values.
  • Ordinary users cannot edit the audit history.
Organic farms

How the business operates.

Organic growers answer to an inspector as well as a buyer. The farm must show how long a field has been out of conventional use, which inputs went on, and that organic and non-organic produce never mixed. Both want the same records.

Field history and conversion status

Hold each parcel with its conversion start date, status, buffer zones and every crop, input and cover crop it has carried. The full history prints on one sheet.

Approved input register

Keep a list of permitted seed, fertilisers, soil improvers and pest controls, each with its supplier statement attached. An unlisted product cannot be recorded against a field until someone on the farm has reviewed it and filed the supplier’s statement beside it.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Parcel register and conversion status. Hold each parcel with its area, conversion start date, status and buffer zones. Past crops, inputs and cover crops print as one history sheet.
  • Approved input list. Maintain a dated list of permitted seed, fertilisers and plant protection products with supplier statements. A product not on the list cannot be applied in the record until it is reviewed.
  • Seed source statements. File the organic status or approved exception for each seed lot, with the supplier, the variety and the quantity sown on each parcel.
  • Compost and manure batches. Record source materials, windrow number, turning dates and temperature readings. Each application on a parcel names the batch.

Operational bottlenecks to check

Field history is spread over seasons of paper

Conversion dates, previous crops and past applications are in folders from different years. The inspector asks for three years on one field. Someone spends a day finding them.

Nobody checks an input against the approved list

A foliar feed arrives from a new supplier, and the label says little. Whether it is permitted is settled by memory or a phone call, after it has been sprayed on the crop. Too late.

How work flows across this business

This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.

  1. 1. Parcel set-up

    Each parcel is entered with its conversion start date, buffer strips, neighbouring land use and the crops it has carried. Status shows on every screen that touches it.

  2. 2. Planning and seed

    Rotations, cover crops and green manure are planned per parcel. Seed is ordered with the supplier’s organic status statement attached to the line.

  3. 3. Inputs and compost

    Any fertiliser, soil improver or pest control is checked against the approved list before it is recorded. Compost is made in numbered windrows with turning and heat readings.

  4. 4. Growing and field work

    Sowing, weeding, mulching and netting are logged against the parcel. Observations on pests and disease are filed with photographs.

  5. 5. Harvest and packing

    A harvest creates a lot code with parcel, crop and date. Grading, packing and weights are recorded against that lot, after a cleaning record is signed.

  6. 6. Sale and audit

    Orders for boxes, stalls and trade customers are packed from named lots. At audit time the history, statements and trails are printed from one place.

Industry reports to connect with

  • Parcel history for any chosen number of years, with crops, inputs and cover crops
  • Inputs applied by product, parcel and date, with approval reference
  • Compost batches with source, turning and heat readings, and where each was spread
  • Lot trail from parcel to pack to customer, forwards and backwards

Questions before implementation.

When should organic farms consider audit trail?

Use when changes to money, permissions or business records need accountability. A monitored record is created, changed or deleted.

What should we bring to the requirements discussion?

Bring anonymised examples of Events to record; User identities; Retention and access rules. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.

Does this replace our existing business software?

The starting point is your current system and the gap you need to close. Record who changed important business data and when. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Audit records do not by themselves prove regulatory compliance or prevent unauthorised activity.

How are scope, price and rollout decided?

The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. Recorded changes identify an actor and time. Use this check when reviewing the first working version.

Talk to us

Discuss audit trail for your business.

Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements