MAP · APPLY · EXPLAIN · DEMONSTRATION CASE STUDY

PO Allocator Lens™

Convert repeated allocation decisions into a transparent rule-led review workflow.

Open live demo Watch walkthrough See the workflow

Open order-line exportworkflow input

Check eligibility and priorityworkflow input

Apply capacity and sequencing rulesworkflow input

PROCESS
LENS™rules · checks · exceptions

Proposed PO allocation for eligible linescontrolled outcome

Reason attached to each allocationcontrolled outcome

Conflicts and unallocated lines separatedcontrolled outcome

Local workflowDesigned to run with controlled files in the browser.

Exception firstReview what needs judgement instead of every line.

Representative exampleIllustrative data and narrative, not a client claim.

ANONYMISED WORKFLOW CASE STUDY

The allocation rules worked — but too much of the process lived in one person’s head.

Situation: A recurring allocation process required incoming lines to be checked against supplier, location, product and order information before the correct reference could be selected.

Before: The decision sequence was understood through experience, notes and repeated searching rather than one controlled rule set. Covering the task during absence meant asking the usual owner or reconstructing the logic again.

What changed: The decision sequence was turned into visible business rules. The Lens proposes an allocation only when the conditions are clear, records the reason and sends conflicts or ambiguous lines to review.

Result: Routine allocations become a short controlled review while judgement stays with the user where the rules do not produce one safe answer.

Anonymised operational working pattern. Organisation names, people, locations, internal system names and identifying details are intentionally excluded. Any value figures elsewhere on this page are illustrative unless explicitly stated as validated.

BeforeRepeated searching before each allocation could continue.

DependencyKey rule knowledge concentrated with an experienced user.

Controlled changeTransparent recommendation with the reason shown.

ExceptionsConflicting or incomplete lines remain for human review.

THE OPERATIONAL CHALLENGE

How the work happens before the Lens

Order lines are allocated using priorities, date rules, capacity limits and fallback decisions that may be stored in spreadsheets, notes or experienced people’s heads. Manual allocation can vary by person and workload.

Open order-line exportCurrent manual step

Check eligibility and priorityCurrent manual step

Apply capacity and sequencing rulesCurrent manual step

Resolve conflicts and prepare outputCurrent manual step

THE HIDDEN BUSINESS LOGIC

The real value sits in the rules

The Lens is built around agreed conditions, tolerances and actions — not around a prettier spreadsheet.

If a line is ineligible → Exclude with reason

Apply agreed priority before fallback logic

Respect date, quantity and capacity constraints

If no valid allocation exists → Review required

Keep the rule reason beside every proposed result

THE CONTROLLED WORKFLOW

From raw input to action-ready output

1Load order lines

2Validate required fields

3Apply rule sequence

4Propose allocation

5Separate conflicts

6Export controlled result

WHAT THE USER SEES

Clear outcomes with the source detail preserved

Proposed PO allocation for eligible lines

Reason attached to each allocation

Conflicts and unallocated lines separated

Ready-to-use output after human approval

REPRESENTATIVE DEMONSTRATION RESULT

A result that can be explained, reviewed and exported

Figures and labels below describe the demonstration workflow and must be replaced or validated before being presented as a client result.

Visiblerule sequence

Separatedconflicts

Traceableallocation reason

WHAT THE CONTROLLED WORKFLOW CHANGES

Better control, earlier visibility and less dependence on memory

The value is not only that the task becomes faster. The workflow becomes easier to cover, explain, review and improve.

01Consistent sequenceSupplier, location and product rules are applied in the agreed order.

02Reason is visibleEvery proposed PO includes the rule or condition that produced it.

03Absence is manageableThe workflow can continue when the usual coordinator is unavailable.

04Less downstream reworkIncorrect allocations are reduced before they reach later operational or finance steps.

ILLUSTRATIVE VALUE MODEL

The routine decision becomes a short, traceable review.

The illustrative saving counts only the time released from repeated allocation work. Avoided downstream corrections are additional value.

152 hoursillustrative annual capacity released

£2,730illustrative annual labour value

Assumptions used

1 person
5 runs per week
45 minutes before
10 minutes after
£18/hour
52 weeks

Illustrative only. The final baseline is confirmed during a Process Scan using the client’s actual frequency, time, people and cost.

Historic value: Because the selected rule and allocation reason are stored with the result, older decisions can be reviewed and explained without relying on memory or reconstructing the original conversation.

BOUNDARIES AND TRUST

What this demonstration does — and does not assume

Demonstration workflow; final rules require client approval

No source-system write-back by default

Capacity and fallback logic remain configurable

Human approval remains part of the controlled workflow

Have a similar manual workflow?

Describe it in plain English and see the first-pass opportunity.

Check your process