The board looks stable until one change exposes three weak assumptions.
Manual crew-fit logic often depends on memory, not a visible reasoning layer. That is manageable until urgency strips the buffer out of the day.
Governed concept demo. Controlled conversations only.
Bring ranked allocation judgement into the moment pressure hits.
Helping businesses make better dispatch and workforce decisions under pressure. LiftIQ helps teams see ranked recommendations, visible hard blocks, and explainable score logic before a rushed assignment becomes a scramble.
Current stage: early product foundation. Read-heavy, write-light. No live integrations. No dispatch replacement claims.
What LiftIQ surfaces
Pressure concentrates where judgment is still manual.
The current LiftIQ demo shows how one overlay can rank options, hard-block missing requirements, and keep the reasoning visible when the board gets tight.
Crew fit
Ranked against job needs, access limits, and operator readiness.
Fatigue view
Monitor above 44 hours. Block above 48. Block below 10 hours rest.
Hard blocks
Missing required tickets and licences stay visible, not buried.
Built for dispatch pressure, not presentation theatre.
LiftIQ is being built to augment dispatchers, workforce planners, and operational leads. It is not presented as automated compliance software, mature AI, or a finished integration layer.
Why this matters
Most allocation risk is not dramatic. It is cumulative.
Late call-outs. Repeated crew assumptions. Ticket checks that happen too late. Fatigue that stays fragmented across the day. Each issue looks manageable on its own. Together they create scramble, delay, and avoidable decision noise.
Required tickets get discovered under pressure instead of before the call.
LiftIQ is being shaped to make missing mandatory requirements obvious, not easy to miss in a notes field or a hurried phone chain.
Hours and rest history stay fragmented when the day starts to move fast.
Fatigue exposure is operational, not theoretical. If the signal is unclear, the dispatcher carries the risk mentally.
What LiftIQ is
A read-first overlay for operational decisions that are still happening in memory, calls, and judgement.
The current governed demo is front-end only. It uses seeded data and rule-based logic to show how recommendation, review, and hard-block states could appear inside a serious operational workflow.
SmartRank
Weighted recommendation logic with an explainable score breakdown. Useful when multiple crew options look plausible at first glance.
FatigueGuard
Consistent rest and weekly-hours rules that surface monitor states and hard blocks before an unsafe option is treated as normal.
CredentialGate
Internal module name remains ComplianceAI, but the current truthful function is simple: visibly hard-block missing required credentials.
Swap preview
Replacement ranking logic for last-minute change scenarios, using the same seeded recommendation layer rather than invented automation.
How it fits
LiftIQ is being engineered to support the dispatcher, not step around them.
The current product direction is deliberate: read-heavy first, recommendation before automation, and explicit human review before any future write-back pathway is considered.
1
Read the operational context
Operator records, credentials, job requirements, site constraints, fleet availability, and fatigue inputs form the base layer when those sources eventually exist.
2
Rank, flag, and hard-block
LiftIQ applies recommendation rules and explicit gate rules. A useful option should be visible. An unsafe option should be visibly blocked.
3
Keep the reasoning visible
The score breakdown stays in view so dispatch and operations leads can judge the recommendation instead of being asked to trust a black box.
4
Move to integration later, not prematurely
Operational system access comes first if LiftIQ progresses. Any later Xero or MYOB alignment is planned phase-2 work, dependent on partner access and real field mapping.
"LiftIQ is being structured so it can later sit beside dispatch, workforce, and financial systems such as Xero and MYOB, but those pathways are planned architecture only until they are explicitly built and verified."
Planned direction only. Not currently supported.Current state
- Governed concept demo with deterministic seeded logic.
- Explainable scoring, hard blocks, and preview-only event logging.
- Suitable for tightly controlled design-partner conversations.
- Built to augment dispatch and operational decision-making.
Not yet
- No backend, no production permissions model, and no live integrations.
- No claim of automated compliance or regulatory reporting.
- No dispatch replacement workflow and no live write-back.
- No live Xero or MYOB connectivity, payroll logic, or invoice automation.
Current commercial motion
Start with a specific diagnostic or a controlled executive briefing.
The strongest LiftIQ movement architecture right now is simple. First: a Dispatch Blind-Spot Diagnostic for operations and dispatch leaders. Second: an executive design-partner briefing for operators who want to test pilot suitability without buying hype.