Inspectors record a batch inspection; the quality and production managers jointly release the batch or put it on hold, held batches get a root-cause analysis and corrective actions, and a report closes the record.
Sign in with your Edesy account; the setup wizard opens on this template.
Category
Type
Business process
Steps
3
Roles
Quality manager, Production manager, Quality engineer, Plant head
Level
Beginner, about 15 min to set up
For manufacturers, food processors and assembly units. The QC inspector records the batch, product, sample size, defects found by type and photos. The quality manager and production manager both decide: release the batch, or put it on hold. A held batch triggers a root-cause analysis by the quality engineer, who records the cause, corrective and preventive actions and the disposition of the batch (rework, scrap or concession). Every inspection ends with a flow report to the plant head, giving you a traceable QC record per batch.
Form: Quality Control Inspection
Starts the workflow
Release or hold batch {{trigger.body.batchNo}}
Approval · Quality manager, Production manager
Hold batch: Analysis & corrective actions · Release batch: Flow report
Analysis & corrective actions
Task · Quality engineer
Mark as done: Flow report
Flow report
Flow report
Quality Control Inspection
Starts the workflow · 12 questions
Root Cause & Corrective Action
Task form · 5 questions
You sign in to Edesy Flow with your Edesy account and the template wizard opens: map each role to a person, pick the app connections it needs, and Flow creates the forms and the workflow for you to edit.
Yes. The workflow opens in the visual builder, where you can add, remove or reorder steps, change who approves, edit the e-mails and add branches.
Authors upload a policy, specification or report; the document owner approves and signs it or asks for changes, and the signed version is filed in Google Drive.
7 steps · 2 rolesInvoice ApprovalVendor invoices are matched to the PO and goods receipt, routed to the right approver by value (budget owner, finance manager or CFO), filed in Google Drive and scheduled for payment.
11 steps · 4 rolesPurchase Order ApprovalA purchase request is approved and signed by the department head, goes to the COO above a spending limit, and the buyer then files the matching expense form.
9 steps · 4 rolesBook PublishingAuthors submit a manuscript; acquisitions screens it, an editor reviews it in depth, the author signs the publishing agreement, files go to Google Drive, an author meeting is booked and production starts.
9 steps · 4 rolesBusiness ProcessA new business enquiry becomes a signed engagement: an account manager prepares the proposal, the director approves it, the client e-signs, files go to Google Drive and the kickoff is booked.
8 steps · 2 rolesCall CenterAgents log inbound leads; a team lead qualifies them, a sales executive books and holds the meeting, the sales manager decides on next steps, and the customer is asked for feedback on the call.
9 steps · 3 roles