Skip to main content
GullySystem
Manufacturing

Workflow and Approvals for API manufacturers

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 batch record moves from production to quality assurance for review and then to the head of quality for release. Reviewers sign with a name and a time. Rework needs an extra approval.

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.
API manufacturers

How the business operates.

An API plant makes a molecule in stages. Starting materials become intermediates, intermediates become crude product, and crude product is purified, dried, milled and packed. At every stage a sample is tested, and a stage that fails its specification can send material back for rework, reprocessing or rejection, each of which must be written down. Every step leaves a record.

Route and stage master

Hold each product’s synthesis route as stages with inputs, solvents, equipment and in-process test points.

Batch manufacturing records

Record charges, temperatures, hold times, yields and sample draws for each stage, with a reviewer’s sign-off.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Starting materials and suppliers. Receive materials with supplier lot, quarantine status and sampling records, and keep approved supplier lists.
  • Route and stage master. Define each synthesis route as stages with inputs, solvents, equipment and test points, with revisions under change control.
  • Batch manufacturing records. Record charges, parameters, hold times, yields and sample draws for each stage and each reviewer’s sign-off.
  • Intermediate lot genealogy. Link final lots to their intermediates and starting materials, including reprocessed and recovered material.

Operational bottlenecks to check

Intermediates lose their lineage

A final lot is built from three intermediate lots, and a reprocessed lot is blended in. The chain from final lot back to starting material is rebuilt from folders each time a customer asks.

Deviations sit in a separate file

A deviation raised during drying is tracked in a register that is not tied to the batch. Release goes ahead without anyone checking if it is closed. The gap is found later.

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. Starting material receipt

    Materials arrive against a purchase order, are sampled and are held until released by quality staff.

  2. 2. Stage charge and reaction

    Charges, temperatures, pressures and hold times are logged against the stage and the reactor used.

  3. 3. Isolation and drying

    Filtration, centrifuging and drying are recorded with yields and samples drawn.

  4. 4. Test and review

    Results are posted against the specification. The batch record is reviewed with its deviations before the next stage or release.

  5. 5. Mill, blend and pack

    The final powder is milled, blended and packed in sealed drums, each with a recorded seal number.

  6. 6. Release and dispatch

    The lot is released, a certificate is produced and the load is shipped with the retest date visible.

Industry reports to connect with

  • Batches by stage and product
  • Yield by stage across campaigns
  • Open deviations by age and stage
  • Intermediate lots and the final lots they fed

Questions before implementation.

When should api manufacturers 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