Skip to main content
GullySystem
Other industries

Workflow and Approvals for Organic farms

Route business requests through defined approval steps.

Platform

Does this function belong in your operation?

Use when requests need explicit approval before money, stock or records change.

A transaction or request requires authorisation.

A new input such as bagged manure or a bio-pesticide goes to the organic manager first. The approved list is checked before purchase. No unlisted input reaches a field.

Bring the records the workflow depends on.

  • Request types
  • Approval limits
  • Delegation and escalation rules

Outputs to check

  • Request and decision history
  • Pending-approval queue
  • Authorised downstream action record

Follow the workflow and approvals 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 authority

    Set request types, value limits and delegation rules.

  2. 2. Submit the request

    Collect the evidence and proposed transaction details.

  3. 3. Route the decision

    Identify the approver with authority for the current request.

  4. 4. Record the outcome

    Retain approval, rejection or return comments and timestamps.

  5. 5. Release the handoff

    Allow only the authorised downstream action and reapprove material changes.

Who uses the module, and who approves?

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

Owner or partner

Clears the day’s approvals between meetings, and sees what they cleared last week.

Department head

Approves what belongs to their team and nothing beyond it.

Whoever raises it

Knows where the request is standing without ringing anyone.

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.

Approver unavailable

Use the documented delegation rule and retain the acting approver.

Value changes after approval

Return the revised request for the required approval rather than inheriting the old decision.

Request withdrawn

Stop pending actions and preserve the previous decision history.

Can this work independently?

Approval routing can operate as a standalone register, but blocking a transaction requires the transaction system to honour the decision. Role and delegation data identify authority; audit records retain evidence. An approval message alone should not be mistaken for execution of payment or fulfilment.

Systems and records it connects with

  • Purchase orders: Authorised supplier commitments and open line balances.
  • Price lists and schemes: Effective-dated rates and customer eligibility rules.
  • Credit control: Customer limits, current exposure and authorised order releases.
  • Leave and holiday management: Approved absence and branch calendar information.

Configure, test and introduce the workflow.

  • We sit with the owner and department heads. You describe what needs whose approval. A table of rules returns for your correction.
  • Named approvers and their stand-ins are entered. Each person sees what they will receive. Purchase orders, discounts or leave requests are linked to the rules. Test requests are raised for each type.
  • A single department uses the screens for real approvals. Its group chat is closed. Remaining departments follow. Waiting times and reasons for refusal are reviewed with the owner.

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.

  • Unapproved requests cannot take restricted actions.
  • Decisions retain an approver and time.
  • Absent-approver cases follow the agreed rule.
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 workflow and approvals?

Use when requests need explicit approval before money, stock or records change. A transaction or request requires authorisation.

What should we bring to the requirements discussion?

Bring anonymised examples of Request types; Approval limits; Delegation and escalation 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. Route business requests through defined approval steps. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

An approval workflow records authority; it does not determine whether a transaction is legally or commercially appropriate.

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. Unapproved requests cannot take restricted actions. Use this check when reviewing the first working version.

Talk to us

Discuss workflow and approvals 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