Jakub Hejl Products · Web · Operations
← Back to projects
Ticket FlowOperational automation

Ticket complete.
Without losing a quarter of a shift.

The tool builds an operational ticket from source validation through impact calculation to a ready attachment. The user receives a complete, traceable draft and focuses on the final review.

Try the demo ↗Why the project was built ↓
JavaScriptBrowser automationParallel processingXLSXWorkflow orchestration
GENERATED TICKETDEMO-2048
Ready for review ✓
01Source02Calculation03Attachment04Ticket
UnitUNIT-042
Total impactCZK 26,736
Item count24 pcs
Documentationevidence_demo.xlsx ✓
Automation prepared the supporting data and form.A person reviews and confirms →
≈ 25% of a shiftpreviously consumed by ticket administration
Several systemsreplaced by one guided workflow
1 reviewinstead of repeatedly copying the same data
More attentionfor operations, decisions and people
Why this project exists

Tickets were a supporting task.
Yet they held the work back.

The person responsible for operations spent a significant part of the shift assembling supporting data instead of managing operations.

First, the right records had to be found and checked for completeness. Then other sources had to be opened, every product value retrieved, the total impact calculated and everything written into a spreadsheet. Finally, the same identifiers, quantities and amounts were copied into a ticket form. A long chain of small steps repeated with every ticket.

BEFORE1 / 4 of a shift

Searching, copying, calculating and checking.

Administration set the pace of work and delayed tasks that needed a person on the floor.

AFTER1 workflow

The tool prepares everything. A person decides.

Data, calculations and attachments come together; the user handles exceptions and the final review.

VALUEtime back

Operations receive the attention that tickets used to consume.

The time saved can go to people, shift priorities and situations that cannot be automated.

From hours to minutes

What used to fill
a quarter of a shift.

01Collect supporting dataFind units, items and missing quantities

02Look up a valueOpen other sources and value each product

03Build evidenceCalculate impact and create a reviewable attachment

04Complete ticketPrefill the form and let a person confirm the conclusion

01 / SOURCE CHECK
UNIT-042 expected 1210 loaded
UNIT-117 expected 88 loaded ✓
UNIT-203 expected 66 loaded ✓
Exceptions are immediately visible without stopping the rest of the batch.
02 / VALUE LOOKUP
01020304
  • SKU-D41CZK 1,290verified
  • SKU-M08CZK 749cache
  • SKU-P72CZK 2,140verified
10 / 10 values retrieved in parallel
03 / EVIDENCE READY
IDQTYVALUETOTAL

SKU-D4141 290CZK 5,160

SKU-M088749CZK 5,992

SKU-P7262 140CZK 12,840

evidence_demo.xlsxCZK 26,736
04 / READY FOR HUMAN CHECK
TICKET / DEMO-2048Ready ✓
Unit
UNIT-042
Quantity
24 pcs
Impact
CZK 26,736
Attachment
attached ✓
Behind the time saving

Time saved through a better process.
It is a better way of working.

01 / Process redesign

I removed an entire chain of waiting, rather than automating a single button.

I mapped ticket creation from the first source row to the final form. Every system switch, manual calculation and repeated copy became part of one continuous workflow.

REMOVERepeated copying of the same details.CONNECTSource, values, calculation and form.KEEPHuman review before a decision.
02 / Reliable automation

A fast workflow needs to handle failure safely.

Each lookup has its own status and timeout. A cache speeds up repeated results, missing values are flagged and incomplete units are isolated. Users can see what needs attention instead of waiting for a silent error.

PARALLELmultiple values at onceTIMEOUTno endless waitingCACHEquick repeatWARNINGexceptions remain visible
03 / Human checkpoint

Automation saves time. Responsibility stays with people.

The tool creates the calculation, attachment and prefilled ticket from the same dataset. Before completion, it shows a summary and warnings and requires a final review. The user checks whether the conclusion makes sense instead of assembling the data.

✓ supporting data from the same source✓ impact remains traceable→ final human decision
Before & after

Same ticket.
A completely different working day.

Before: tickets consumed a quarter of a shift
25%of a shift lost
  1. 01Find source data
  2. 02Check quantities
  3. 03Look up values
  4. 04Create the calculation
  5. 05Copy into the form
  6. 06Attach supporting data
  • Operations wait while administration is assembled
  • The same data passes through people’s hands several times
  • Errors often appear only at the end
After: automation prepares, a person reviews
TIME RETURNED TO THE SHIFT+25%for operational work*
SOURCE→CALCULATION→ATTACHMENT→TICKET ✓

* compared with the original time spent on manual preparation

  • The workflow shows progress and exceptions
  • Calculation, attachment and form share the same data
  • People focus on review rather than copying
← MANUAL ADMINISTRATIONTIME FOR OPERATIONS →
↔
Project impact

The ticket is complete.
The shift can continue.

01

Less administration

A task that took roughly a quarter of a shift no longer requires its own manual project.

02

More time for people

Users can return to supporting the team, priorities and current operational problems.

03

Less room for copying errors

Supporting data, calculations and the ticket follow one data path.

04

Control remains clear

Automation prepares the work, while the final decision deliberately stays with a person.

Interactive demo

Try the workflow
that gives time back to the shift.

The demo simulates the real journey from source validation and parallel value retrieval to a ticket ready for human approval.

Try the demo ↗Back to projects