Home / How It Works
How It Works: One Request, Start to Finished
This page walks a single request through the route — from the moment it is submitted to the moment the work it represents is finished and on the record. The example is a purchase request, but the same five stages apply to approvals, onboarding, claims, and document-driven decisions.
Arrival: the request becomes a tracked item
An operations lead submits a purchase request through a portal — MaxxLaunch™ on the MaxxLogix platform — at 9:04 a.m. Because the request arrives through a form, it lands as structured data: what is being bought, from whom, for how much, and why. Arrival is intake: the request is captured the moment it lands, given an identity, and placed on its route.
Nothing waits in an inbox, and nothing depends on the right person happening to see an email. From this point on, the request's location and status are always known.
Routing: the rules choose the path
Outcome Workflows™ reads the request and applies the rules your process runs on. The amount puts it on the two-approval path. The department sends the first approval to the cost-centre owner. The category adds a compliance check that other purchases skip. Nobody forwards anything; the route is chosen by rule, the moment the request arrives.
Change the rules and the route changes — visibly, in one place, for every request that follows. That is the difference between a process and a habit.
Approvals: decisions become queue tasks
The first approval arrives in the cost-centre owner's queue in Outcome Workspace™ — not as an email, but as a task holding the request, its data, and its history. She reviews it in context and approves with a single action, recorded with her name and a timestamp. The request moves on instantly; no reply-all, no forwarded attachment, no version confusion.
If the task had sat untouched, the route itself would have reminded her — and escalated after the threshold your rules set. Stalls are visible because the platform is watching the clock, not because someone complains.
Exception: the judgement call is escalated
The second approval hits a snag: the quoted total on the attached supplier document does not match the amount on the request — a discrepancy N-Way Match™ flagged when the document was checked against the request data. The rules cannot settle which figure is right, so the workflow does not guess. It escalates the exception to the finance lead, with the request, the document, and the specific mismatch in front of him.
He confirms the quoted figure, corrects the request, and approves — one decision, made with full context, recorded like every other step. The route resumes exactly where it paused.
Outcome: the finish is recorded, not assumed
With the last approval in place, the request is fulfilled and the outcome — what got done with it — is written to the record: who approved it, what was flagged and how it was resolved, and how long each stage took. The purchase is no longer a thread; it is an auditable piece of finished work.
That record is the point. It is what Outcome Analytics™ reports on: volumes by request type, exception rates, stage-by-stage cycle times, and the outcomes each process produces. Improvement stops being a guess, because the route keeps its own evidence.
The other front door: documents
Not everything arrives as a form. A contract, an invoice, or an application arrives as a document — read and validated by MaxxOwl™ SI on the MaxxLogix platform — and its data joins the same route at the same stages: routed by rule, approved as tasks, escalated on exception, recorded as an outcome. Documents and data, one route.
Same route, every kind of work
Every process your operation runs on can be walked through the same five stages. The rules, thresholds, and approvers change from process to process; the route doesn't. That consistency is what makes the outcomes comparable — and what makes a platform different from a pile of point tools.
Put your requests on a route
The stages above run on MaxxLogix — Outcome Workflows™, Outcome Workspace™, and the rest of the platform, with capacity published in SI Units and no surprise overages. See it at maxxlogix.com.
Visit MaxxLogix