Workflow app examples: Order releases without emails & Excel
Table of Contents
Email chains get lost, CC lists grow to infinity, and "final_final_v7.xlsx" is never really final. If your approvals still run via inboxes and tables, a lean Workflow app the release times by around 60 % reduce and the SLA compliance by around 25 percentage points with full transparency for Finance and Audit.
Below you will find Three realistic workflow app exampleswhich you can reproduce directly: Procurement approvals, Discount releases and Change request releases. Each example shows how Roles & rights, escalation, SLA timer and audit logs work in practice.
What "good" means for approval workflows
Before we dive into the examples, the building blocks that any solid release logic should contain should be clear:
- Roles & Rights (RBAC): Applicant, Approver(s), Finance/Ops, Auditor (read-only). Each role only sees and does what it is supposed to.
- SLA timer: Start on receipt of the task, end on approval/rejection. Automatic escalation if exceeded.
- Escalation: Time-based (inactivity) and risk-based (amount, category, margin).
- Audit log: Unchangeable history - who, what, when, with which comment or attachment.
- Notifications: In-app tasks + Slack/Teams reminders; email only as a fallback, not as a backbone.
- Release matrix: Rules by amount, category, customer group, risk or margin.
- Data quality: Mandatory fields, validations and intelligent defaults minimize rework.
Workflow app example 1: Procurement approvals (Purchase Request → PO)
Use case: Employees submit a procurement request (PR) for equipment, services or software. Approvals vary according to amount and category. After the last approval, a purchase order (PO) is automatically generated in the ERP.
Roles & rights
- Applicant: Create/edit PR until submission, view own applications, attach offers.
- Team management: Release up to €5,000, can request or comment on changes.
- Department management: Release from € 5,001 to € 25,000.
- Finance: Release over € 25,000; checks cost center, budget and supplier.
- Procurement: Creates order in ERP, marks delivery as completed, closes process.
- Auditor: Read-only rights for all data records and logs.
Release matrix (example)
Amount (EUR) | Release(s) | SLA (working hours) |
0-5.000 | Team leader | 16 h |
5.001-25.000 | Team management → Department management | 24 h per level |
>25.000 | Team management → Finance | 24 h + 32 h |
Core data fields
- Header: Applicant, department, cost center, supplier, requirement date
- Items: Description, quantity, unit price, total
- Documents: Offer PDF, service description
- Metadata: Category (CapEx/OpEx), budget code, internal notes
Procedure
- Creation & validation: Applicant fills out form; inline checks mandatory fields and totals.
- Submission → Trigger: App locks the request and forwards it to the team leader. SLA timer starts.
- Approval/rejection/modification:
- Release: Routing according to matrix.
- Change: Request returned to creator (all changes logged).
- Rejection: Reason required; notification to applicant.
- Last release → Webhook:
- Event PR.Approved triggers ERP API.
- PO is generated, confirmation is saved in the data record.
- Status & Notes: Applicant sees live status ("Waiting for Finance", "Approved", "PO #... created"). Slack reminder 2 h before SLA end.
- Close & Archive: Procurement confirms delivery, Finance makes final booking.
Escalation
- If a release > SLA lasts, automatic assignment to deputy + Slack channel alert.
- Amounts > 25 k € or CapEx categoryFinance always final instance.
Audit log
- Each step (submitted, released, returned, changed, escalated) with timestamp, user, old/new values and comment.
Example event
{
"event": "PR.Approved",
"prId": "PR-2025-0193",
"approvedBy": "maria.wagner",
"total": 18490.00,
"currency": "EUR",
"costCenter": "CC-410",
"nextAction": "CreatePO",
"attachments": ["angebot_acme_18490.pdf"]
}
Result
- Release time: days → hours (- 60 %).
- SLA fidelity: + 25 percentage points through timer + auto-escalation.
- E-mail volume: - 80-90 %.
Workflow app example 2: Discount approvals (Sales → Finance/Management)
Use case: A sales employee requests a discount in order to close a deal. Approvals depend on the discount, deal size and margin. Goal: quick decisions without loss of control.
Roles & rights
- Sales (applicant): Submit discount request from CRM, view decision.
- Sales Manager: Release up to 10 % or 20 k € deal value.
- Finance: Margin check, release of 10-20 %.
- Commercial Director / Management: Release > 20 % or special cases.
- Auditor: Read only.
Release matrix
Discount % | Deal size (EUR) | Release path | SLA |
≤ 10 % | any | Sales Manager | 8 h |
10-20 % | ≤ 50 k | Sales Manager → Finance | 8 h + 16 h |
> 20 % | any | Sales Manager → Finance → Commercial Dir. | 8 h + 16 h + 24 h |
Core data fields
- CRM link, product mix, list price vs. net price, discount %, planned closing date
- Margin (automatically calculated from COGS/list)
- Justification & win plan (competitors, time frame, strategy)
Procedure
- Application: Sales creates application directly in the CRM (embedded app or deep link).
- Validation: No sending without margin calculation or mandatory fields.
- Routing: App assigns releases according to matrix; SLA timer starts for each stage.
- Parallel testing: Finance checks margin while Sales Manager prepares decision.
- Decision: Approval / rejection / counter offer (e.g. 15 % instead of 18 %).
- Sync: After final approval, the discount is automatically updated in the CRM offer.
- Archive: Decision note is saved for audit and pricing reviews.
Escalation
- When Closing date < 48 hPriority flag; SLA halved.
- When Margin < limitblockade or mandatory override by management with justification.
Audit log
- Original price, requested discount, approved discount, responsible persons, comments ("Matched competitor X; 1 year prepaid").
Result
- Release time: ≤ 10 % discount on the same day, 10-20 % overnight, > 20 % within 72 h.
- Consistency: Central matrix instead of individual decisions.
- Turnover rate: Faster decisions without loss of margin.
Workflow app example 3: Change requests (scope, quantity, deadlines)
Use case: Changes to scope, quantities or deadlines become necessary during a project or order. Goal: Maintaining margins and deadlines without customer frustration.
Roles & rights
- Applicant (PM/Ops): Create change request, add details & effects.
- Operations: Checks feasibility and schedule.
- Finance/PMO: Checks costs and budget.
- Customer (optional): External release or e-signature.
- Executive Sponsor: Only with high impact.
Categories & Rules
Category | Impact | Approval path | SLA |
Minor | No budget/date change | Ops | 8 h |
Moderate | < 10 % budget or < 1 week | Ops → Finance | 8 h + 16 h |
Major | ≥ 10 % budget or ≥ 1 week | Ops → Finance → Exec + Customer | 8 h + 24 h + 24 h |
Core data fields
- Original order, description, reason, risk
- Impact analysis (budget/clocking) calculated automatically
- Attachments: new SoW, updated schedule
Procedure
- Initiation: Applicant selects category; app calculates impact.
- Ops exam: Feasibility & new dates.
- Finance: Budget, accounting plan, margin.
- Customer: E-sign or documented consent.
- Implementation: Webhook updates ERP/PM tool; baselines adjusted.
- Close: Versioning and storage of the final data.
Escalation
- At Major > 24 h inactivity: Alert to sponsor + project channel.
- If customer waiting time > 72 h: Reminder to account team.
Audit log
- Versioned history of scope, budget, deadlines, with customer signature.
- Who accepted which compromises and when.
Result
- Decision time: - 60 %.
- Customer transparency: Clear approvals prevent scope creep.
- Financial control: Margin remains stable thanks to controlled releases.
Reusable patterns in all three workflows
- Roles & rights: Minimalist roles, no multiple writers. Changes only with justification.
- SLA timer: Start/stop on task handover; visual timer; escalation before expiry.
- Escalation: Time and risk-based; automatic delegation in the event of absence.
- Audit logs: Readable, differentiated, exportable (CSV/PDF).
- Integration strategy: First Slack/Teams visibility, then ERP/CRM sync.
Implementation - Checklist
Data model:
- Entities: Request, Approval Task, Comment, Attachment
- Fields: Applicant, department, amount/discount/effect, status, SLA times
Automations:
- Trigger: on submit, on approve, on reject, on breach
- Webhooks: *Approved, *Rejected, *.escalated
UX:
- One step per screen, mandatory fields at the front, policies as context panel
- "Request change" button, which releases the form again
Security & Compliance:
- RBAC + data partitioning by cost center or region
- Unchangeable audit log, retention and export policy
KPI measurement:
- Processing time per step and overall
- SLA compliance per role
- Rework rate
- Email volume vs. in-app tasks
Measuring (and proving) success
A dashboard from day 1:
- Release time (P50/P90): Target - 60 %
- SLA fidelity: Target + 25 percentage points
- First-pass rate: Data quality & rule clarity
- Escalation rate: should decrease with maturity
Check weekly in the first month, then monthly with Procurement, Sales & Finance.
Conclusion
These Workflow app examples - Procurement, discounts and change requests - replace chaotic email chains and fragile Excel lists with clear roles, plannable timers and traceable audit trails. Start with your existing matrix and SLAs, digitize them step by step, and give teams a central interfaceto submit and approve applications and make progress. The effect is measurable: Release times - 60 %, SLA loyalty + 25 percentage pointsand significantly fewer surprises for Audit and Finance.
Arrange a free, no-obligation consultation with our team.
EN 
DE 
FR 
ES