Current Scope and Limitations

This document sets out what Luminar Works does not do at launch, and the boundaries of what it does. It covers the modules available at launch — Luminar Core, Smart Planning, Multi-day Planning, and Size-Up. Capabilities described as coming later are on the Module Roadmap, and none of them is available yet.

Stating these boundaries plainly is deliberate: it is better to be clear about what Luminar Works does not yet do than to leave it to be discovered in the field.

Some limitations apply only during the Founding Fleet soft launch and lift at general launch — these are gathered in their own section below.

Platform scope at launch

Luminar Works is focused on planning and publishing at launch.

• There is no dispatch or real-time execution tracking at launch.
• A Luminar Works mobile app for agents — allowing published trips to be viewed and executed in the field — is coming soon after launch, and is not yet available.

Once a trip is published, it qualifies for export. The Export Trips call-to-action on the planning page — top right of the toolbar, next to Smart Planning — exports published trips to CSV, Excel, or PDF. Published trips can also be shared to the allocated Agent by email and WhatsApp. At general launch, the REST API additionally allows external systems to retrieve published trips. Luminar Works does not push data to external systems — retrieval is initiated from your side.

Founding Fleet soft launch limitations

These limitations apply during the Founding Fleet soft launch and are lifted at general launch:

• An account has a single Business Unit — there is no mechanism to create or select additional Business Units. Multiple Business Units are available at general launch.
• The REST API is not available during the soft launch. It becomes available at general launch. Getting data out during the soft launch is via individual trip export (CSV, Excel, or PDF) and sharing to the Agent by email or WhatsApp.

Business Unit limitations

• A Business Unit is assumed as the start and end location of a resource's trips. Resource-level start and end locations will be available with the Resource Operation module when it is released — it is not yet available.
• The free resource allocation applies to your first Business Unit only — resources in additional Business Units are charged per resource.

Planning horizon limitations

• Luminar Core plans a single day at a time.
• Planning across multiple days requires the Multi-day Planning module, and the horizon is capped at 7 continuous days.
• Overnight operating windows (a start time later than the end time, such as 20:00–06:00) express continuous overnight operation only with Multi-day Planning. Within a single-day horizon, such a window is interpreted as two windows in the day.

Trip limitations

• A trip is associated to exactly one primary resource and at most one secondary resource.
• A primary resource may have multiple trips, and each can have a different secondary resource assigned.
• A trip can be published without a secondary resource assigned.
• A trip can only be edited when the full date range it spans falls within the selected planning horizon. A trip that is not fully contained by the selected horizon is locked — it cannot be changed by that planning session, and the resource availability it consumes is still respected.
• A published trip cannot be edited. Unpublish the trip to return it to the Planned state before making changes.

Task limitations

• Tasks cannot be split. If a task's size exceeds the capacity of the largest available Asset, or its duration is longer than its service window, Luminar Works will not split it. For bulk orders, split the work into manageable sub-tasks before creating the tasks in Luminar Works.
• Tasks are independent — there are no dependencies between tasks at launch. Task ordering and dependencies will be available with the Task Pairing module when it is released.
• A task carries a single service window at launch. More than one window per Customer, Site, or task will be available with the Multiple Service Windows module when it is released.

Capacity limitations

• Luminar Core plans against one capacity dimension.
• Planning against up to three capacity dimensions requires the Size-Up module.
• Capacity applies to Capacity-Constrained Business Units only. In a Time-Constrained Business Unit, only service tasks are planned, and service tasks have no sizes — so Size-Up is not available to Time-Constrained Business Units.

Optimizer limitations

These apply when the Smart Planning module is active.

• The optimizer runs on demand, when the user chooses to trigger it — it does not run continuously in the background.
• The optimizer never breaks a hard constraint, and treats each Asset's capacity as a hard constraint — it will not build a trip that exceeds capacity.
• The optimizer does not split tasks to make an over-large task fit.
• When the optimizer cannot plan every task, the tasks that were not successfully planned are listed in a modal at the end of the run. A reason is not provided for why a task could not be planned — see the FAQ below for the common things to check.

Manual planning limitations

These apply to planning by hand on the Gantt, with or without Smart Planning.

• Manual planning can break constraints — for example, a task can be dragged onto a trip that exceeds an Asset's capacity. Constraint signals show when a plan has pushed past its limits, so this is visible while the trip is still in the Planned state. An over-capacity trip can be deliberately accepted and published, or adjusted until it fits.
• A user can manually force a trip to start or end outside a resource's operating window.
• A user can manually force a task onto a date outside its service window — this can happen when a multi-day horizon is selected that only partially overlaps the task's service window.
• Elements on the Gantt cannot be resized. The width of a Visit or any other element is derived from the underlying data and is not adjustable by dragging.
• Trips for a resource are sequential, not concurrent — a resource cannot be double-booked at any point on the timeline.
• Wait blocks are implemented by Smart Planning and cannot be dragged onto or off of the Gantt.

Data model limitations

• Hubs — a shared entrance serving multiple locations — are not available at launch.
• Items — the products or work actions that make up a task — are not available at launch. Task sizes are stated on the task rather than derived from its Items.
• Each entity carries a single operating window at launch (one start and end pair). Multiple availability windows will be available with a future module.

Users and roles limitations

• At launch, the user who creates the account is the Admin, with access to everything.
• A fuller roles model — with distinct roles, finer view and edit permissions, and Business Unit–level user association — is planned and not yet available.

Current scope and limitations FAQs

Can I track my trips in real time once they're out with the agent?
Not at launch. Luminar Works focuses on planning and publishing; real-time execution tracking arrives with the mobile app, which is coming soon after launch and is not yet available.

How do I get a published trip to my agent?
Use the Export Trips call-to-action on the planning page (top right, next to Smart Planning) to export published trips to CSV, Excel, or PDF. Published trips can also be shared to the allocated Agent by email and WhatsApp. At general launch, the REST API can also retrieve published trips into your own systems.

Can Luminar Works split a task that's too big for one resource?
No. Tasks are not split — if an order is too large for one trip, or longer than its service window allows, split it into sub-tasks before creating the tasks in Luminar Works.

Can I plan more than 7 days at once?
No. With Multi-day Planning the horizon is capped at 7 continuous days. Luminar Core plans a single day at a time.

Can I edit a trip I've already published?
No. A published trip cannot be edited — unpublish it to return it to the Planned state, make your changes, and publish again.

Why can't I edit a trip that's on the Gantt?
A trip can only be edited when the full date range it spans falls within the selected planning horizon. If the trip extends beyond the selected dates, it is locked for that session. Select a horizon that fully contains the trip to edit it.

Will the optimizer ever exceed a resource's capacity?
No. With Smart Planning, capacity is a hard constraint. An over-capacity trip can only arise from manual planning or from a change made after planning — and Luminar Works shows it clearly while the trip is still Planned.

Why didn't Smart Planning plan one of my tasks?
When the optimizer can't plan a task, it lists the task as unplanned at the end of the run but does not give a reason. Common things to check:

• Time window vs duration — is the task's service window long enough to contain its duration?
• Task window vs resource window — does the task's service window overlap with the operating window of a resource that could serve it?
• Size vs capacity — does the task's size exceed the Asset's capacity in any dimension (Size 1, Size 2, or Size 3)?
• Travel time and location — is the task so far from the resource's start point, on its own or in combination with the tasks already planned, that reaching it within the available windows isn't feasible?

Do I have to assign a secondary resource before I can publish?
No. A trip can be published with only its primary resource assigned.