Skip to content
On this page
Our approachKeep people involved

Keep people involved where they truly matter

Automated preparation → Human decision → Automated execution

People should not be involved out of habit. They should step in where their participation genuinely adds value or is necessary because of the nature of the task.

A system can collect data, verify documents, calculate figures, retrieve information, prepare decision options and update business software. Yet some decisions require accountability, trust, expert judgement or an understanding of circumstances that cannot be captured reliably by fixed rules.

We do not try to remove people at any cost. Instead, we design workflows so employees participate only at meaningful decision points. The preparatory and follow-up steps remain automated wherever this is safe, technically feasible and authorized.

Why human participation matters

Standard operations can usually run without routine approval. However, when facts are missing, consequences are significant, interests conflict or something genuinely unusual occurs, an automated action may create more risk than value.

A reliable process must be able to stop, explain why it stopped and send the right person a prepared case file. The employee decides within their authority; the system then resumes the approved workflow.

Where people add value

Accountability and major decisions

System: Check policy, documents, thresholds and consequences.

Human: Make and own a justified exception decision.

Negotiation and trust

System: Prepare client history, commercial terms and options.

Human: Build trust and negotiate an acceptable agreement.

Ambiguous context

System: Gather evidence, surface contradictions.

Human: Interpret circumstances outside standard rules.

Genuinely exceptional events

System: Pause unsafe steps and create an actionable case.

Human: Choose an authorized, safe continuation.

Three human decision points

Choose a scenario. The system first completes everything it can automate, then hands over a specific question, documents and permitted options when needed. You can choose a course of action and see how the automated workflow continues.

  1. Event

    A request, enquiry or order.

  2. Automated preparation

    Collect documents and verify facts.

  3. Automation boundary

    Are the facts and authority sufficient?

  4. Human decision

    A specific question for the responsible person.

  5. Automated continuation

    Only the authorized next action.

Non-standard return: accountable judgement

A customer requests a return for order #1284, 47 days after delivery. The company uses a 30-day internal window for standard returns. The customer reports intermittent equipment faults, but a diagnostic report has not yet been provided.

The system identifies an exception, not an automatic rejection. Internal standard-return rules do not override any other contractual or legal rights that may apply.

Human choiceSystem continuation
Request diagnostic evidencePrepare a request and a follow-up task; status: Awaiting Information.
Approve an exception within authorityRecord the grounds and start the authorized inspection/return workflow, without faking a completed refund.
Decline with a reasonDraft the response, record the basis and the applicable escalation path, if any.
Key-account negotiation

A long-standing B2B customer wants to renew a 12-month contract and requests a 12% discount plus 45-day payment terms. The company authorizes standard offers of up to 5% discount and 14-day payment terms without additional approval.

CRM and calculation modules prepare transaction history, commercial figures and possible options. An AI assistant may draft proposals, but it must not promise terms beyond the employee’s authority.

Human choiceSystem continuation
Offer standard authorized termsDraft a proposal; do not assume the customer accepted it.
Request approval for an exceptionCreate an approval task; do not promise unapproved terms.
Prepare a different proposalGenerate a draft alternative for the manager to discuss personally.
Shipment discrepancy: context and expert judgement

An important customer is expecting 80 units of equipment. ERP lists product B-120, but scanning reveals labels reading B-102 on 12 packages. The other 68 units pass the automated comparison. The shipment is scheduled for the following day.

The system cannot conclude whether the issue is incorrect labeling or wrong physical products. Rather than ship potentially incorrect goods, it holds the disputed items and prepares a precise exception report.

Human choiceSystem continuation
Request a physical inspectionCreate inspection task; keep disputed units on hold.
Propose a partial shipmentPrepare a customer approval request for the 68 verified units; do not ship without authorization.
Pause the shipmentKeep the hold and prepare an incident notification and follow-up task.

How human involvement works

Human decisions are explicit, permission-controlled transitions within an otherwise automated workflow.

Standard, well-supported events can proceed automatically. When information is contradictory, an authority limit is reached or material exceptions arise, the process moves into a controlled waiting state. The responsible employee receives the question, evidence, source links and relevant choices. Once the decision is recorded, the system executes only the authorized next step.

Standard case

Verified facts and sufficient authority → automated action.

Significant exception

Prepared case file → human decision → authorized continuation.

No safe continuation

Await information or approval; the unsafe action remains blocked.

When a person is needed

  • Cost and reversibility of an error: greater consequences call for stronger controls.
  • Clarity of rules: reliable checks should run automatically, not through ritual approvals.
  • Authorization and accountability: workflows must respect assigned decision rights.
  • Ambiguity and missing evidence: uncertainty requires verification, not confident invention.
  • The value of personal contact: people are needed where outcomes depend on trust, understanding the other person and finding a mutually acceptable solution.

Technology and governance

Typical components include Python business rules, PostgreSQL, CRM/ERP integrations, APIs, task queues and role-based access controls. LLMs or machine-learning models may assist with extracting facts, retrieving documents and preparing drafts, but they do not replace an authorized human decision where one is required.

ComponentPurpose
Python / Business RulesValidation, calculations, routing and state changes.
CRM / ERP / APISource-of-truth data, documents and permitted business actions.
PostgreSQLCase states, decision reasons and audit history.
LLM / Semantic SearchExtract context, retrieve evidence and draft communications.
Role-based AccessVerify the decision-maker’s authority.
Task Manager / NotificationsAssignments, deadlines, escalation and follow-up.

Quality and safety

Each human decision point needs a designated owner, an explicit reason for escalation, an authorization boundary and an audit trail. A missing response or integration failure must never be treated as implicit approval. When safe continuation is impossible, the process remains on hold or stops cleanly.

Employees should not have to re-enter existing data, repeat automated checks or manually distribute the approved decision. The surrounding workflow remains automated.

Business value

Organizations do not have to choose between complete automation and universal manual control. Reliable, repeatable tasks run in software while qualified employees handle the exceptions and judgements where they add real value. This reduces unnecessary approvals, frees expert time and keeps important decisions accountable.

Meaningful measures include straight-through processing rate, justified handoffs to people, time to resolve exceptions, preventable errors and repeated manual work. The objective is not simply fewer human touches, but better process economics without losing quality or responsibility.

The final principle

First, eliminate unnecessary steps. Next, automate the necessary repeatable operations. Finally, preserve human participation where it truly adds value.

Remove unnecessary steps → Automate necessary operations → Preserve valuable human involvement

Discuss your workflow

Do your teams spend time on reviews and approvals even though most cases are routine? Share the process and we can identify what to eliminate, what to automate reliably, and where an accountable person is genuinely needed.