L2L Changelog

Description

Search this Space

Recently updated content

July 2026 Changelog

7.08.26

Updates to Execution AI

Execution AI has officially expanded its footprint—you can now access its powerful insights right from the Homepage as well as within the Operator Portal. To better support high-volume operations, we have drastically scaled our capacity, increasing the maximum number of dispatches available for review to 10,000. Additionally, we’ve supercharged the Operator Portal with two brand-new production solvers: a Line Pulse Check to monitor real-time operational health, and a Shift Handover solver. https://support.leading2lean.com/articles/3968524927-l2l-execution-ai?lang=en

Metrics - OEE

We have updated the OEE calculation logic within L2L Dispatch to strictly align with the industry-standard formula: Availability × Performance × Quality = OEE. Previously, production pitches missing an Ideal Cycle Time (ICT) during line downtime were excluded from the final OEE score, which often hid actual downtime and caused reporting discrepancies. These pitches are now included with a natural Performance score of zero, providing perfectly reconciled metrics across all dashboards, though you may notice a downward historical adjustment on lines with heavy downtime. Read more here: https://support.leading2lean.com/articles/6033827735-oee-metric-update-july-2026

Mobile App Update

We are excited to roll out a major stability update to the L2L Dispatch Mobile App, featuring a rebuilt native wrapper designed to eliminate crashes and improve overall performance. This update delivers critical floor-ready enhancements, including reliable push notifications, streamlined photo capture for dispatches and checklists, and robust biometric sign-in persistence. The release is rolling out automatically as an in-place update through your device's app store or mobile device management (MDM) system.

Smart Skills

Smart Skills operators will now see proactive warning badges in-app, alongside timely email and push notifications 30 days and 7 days before a skill expires. Admins can also easily track and filter upcoming expirations directly within the Smart Skills matrix to seamlessly plan team re-certifications.

7.02.26
Improved Line Check-In Flexibility

The check-in window has been renamed from “Check In Additional Users” to “Check In Users.” The logged-in user is still selected by default, but you can now remove yourself from the list before saving.

Supervisors and operators can check in team members or relief workers without being forced to check themselves in at the same time, keeping your labor tracking data clean and accurate.

Smart Skills Navigation

Previously, operators had to repeatedly click "Back" through every single completed learning activity to exit. The back button will now cleanly take you directly back to the main Skill Overview, making it much faster to navigate your skills matrix.

In-App Notifications for Expired Smart Skills

You will now receive direct in-app notifications when a skill has expired. Tapping an expired skill notification will now take you directly to the relevant skill page so you can take action immediately.

Improved Currency Formatting

Added a new Currency format setting allowing you to choose between standard Decimal mark (1,234.56) and Decimal comma (1.234,56) formats. This ensures cost fields across the platform accurately reflect your preferred regional locale preferences (e.g., US vs. Euro formatting).

June 2026 Changelog

6.22.26 Set Demand On Changeover Now surpasses the 14 day limit

Production

Added the ability to set demand on a changeover beyond the previous 14-day limit, so sites with long production orders can plan demand further out.

6.17.26 Intra-Site Spares Transfer

Spares

We’ve introduced a Transfer operation to easily move part quantities between bin locations within the same site.

You can now move parts directly from one bin location to another via a secure, dedicated dialog box on the part detail page.

This eliminates the need to manually edit multiple individual bin-location rows. The new process automatically updates on-hand totals, validates available stock to prevent over-transfers, and creates a clear, paired audit trail for the movement.

Open

Open

6.10.26 Team Learning Journeys in Smart Skills

Team Learning Journeys make it easy to create and manage learning paths for entire groups of employees who share the same job title. Trainers can now configure skill order and target completion timelines once, then automatically apply them to current and future team members, ensuring everyone receives a consistent onboarding and development experience. This reduces manual setup effort and helps keep learning journeys up to date as teams grow.

Reports

We have redesigned the Dispatch History report filter form, grouping its fields into six themed, collapsible cards to help you find and apply filters faster. If you prefer the original format, a quick toggle lets you instantly switch back to the legacy single-column list view. Your existing saved reports, exported data files, and backend query speeds remain completely unchanged.

Open

Notifications Bell Icon

The Notification Center is now a convenient slide-out overlay that opens directly from the bell icon, allowing you to check your notifications instantly without losing your place or leaving your current screen.

6.9.26 One-Off Dispatch Estimated Hours

We’ve introduced an Estimated Hours field for single-instance, one-off dispatches. Planners can now set and edit decimal hour values inline directly from the dispatch detail page or right on the planner card.

One-off dispatches will no longer render as disproportionately large blocks, keeping your timeline clean and accurate. This helps support additional precision to further balance technician loads without skewing capacity data.

6.05.26 Product Attributes API & Product Order Import Updates

Product Attributes API

We’ve added new API endpoints to help you automate and manage your custom product tags and labels without using the UI. This makes it easy to sync bulk product data directly from external systems like SAP.

• Add Attributes: Programmatically assign custom tags to specific products using the /api/1.0/productcomponents/add_product_attributes endpoint.

• Remove Attributes: Cleanly strip tags from products using the /api/1.0/productcomponents/remove_product_attributes endpoint.

Note: This functionality mirrors our existing Machine Attributes API.

Product Order Import Updates

Re-importing matching IDs now correctly updates existing orders instead of creating duplicates.

The Line Code Assigned and Status fields will successfully update upon re-import.

Status updates are automatically bypassed for active orders currently in Changeover, Work In Progress, Paused, On Hold, Clean Up, or Completed status.

6.04.26 Pause Button Site Property Setting for Product Orders

There is a new site property setting, "Enable the 'Pause' Status for Build Sequences", that allows Sites to restrict operators from using the Pause status on Build Sequences.

This addresses an issue where pausing and resuming a product order would reactivate all future pitches (including intentionally unscheduled ones, such as weekends and holidays), overwriting carefully planned schedules.

Sites that rely on manually unscheduled future pitches (e.g., holidays, weekends) should consider disabling the Pause option in the UI to prevent accidental schedule disruption and using On Hold instead.

Note: Pausing via the API is unaffected by this setting.

6.2.26 Platform Webhook Payload Type (Swipeguide)

Platform admins can now select the Payload type for platform-level webhooks, enabling full compatibility and easier setup with Microsoft Teams workflows.

May 2026 Changelog

5.27.26 Assessor Role, Assessment Criteria per Skill Level, Skill-Based Matrix (Swipeguide)

Assessor Role: A new Skill Assessor permission level has been introduced, giving more flexibility in managing skill evaluations without granting full admin access. Assessors can create and manage Skills, Learning Activities, Skill Profiles, and Job Titles; be assigned to Skill Profiles to evaluate team members; and receive email notifications when users request skill assessments.

Assessment Criteria per Skill Level: Trainers can now define unique assessment criteria for each skill level, giving assessors and operators clearer, more relevant guidance during evaluations. Assessors can view level-specific criteria in the assessment drawer, and operators can see the skill requirements for their role during self-assessment.

Skill-Based Matrix: Trainers and assessors now have a dedicated Skill Overview tab in the Skills Matrix. This view shows all skills with pending assessments by default, with filters for status, tag, and team, plus search and clear status indicators (Approved, Expiring, Gap).

05.22.26 Require Sub Asset Selection at Dispatch Complete/Close

Dispatch Type configuration now includes a second sub asset enforcement option: “Sub asset must be selected to close a dispatch.” This works independently of the existing open-time requirement, so admins can enforce sub asset selection at open, close, or both.

When close-time enforcement is enabled, dispatchers cannot close or complete a dispatch without a sub asset selected — the field will be marked as required, and the close action will be blocked until a selection is made.

Note: Dispatches on machines with no configured sub assets are automatically exempt from this validation, ensuring auto-launched and API-created dispatches are never blocked.

5.21.26 Disable Manual Completion for Auto-Created Dispatches

To prevent downtime tracking gaps caused by prematurely closing integration-managed dispatches, you can now disable manual completion for auto-generated dispatches.

A new setting is available within Dispatch Type settings that allows you to disable the “Complete” button for dispatches automatically created via the API (e.g., from Ignition integrations).

When enabled, operators can still edit all required and mandatory fields, but the “Complete” button will remain unavailable. The dispatch can only be completed automatically by the integration itself.

If an operator hovers over the disabled button, a tooltip will clearly explain that the dispatch is auto-generated and managed by an external integration.

This restriction only applies to dispatches created by the API. Manually created dispatches (such as standard assistance or safety dispatches) remain unaffected and can still be completed by operators.

This functionality is supported across both Dispatch Classic and the Dispatch Portal.

5.19.26 Improved Skill Acknowledgement Experience on the Operator Portal

On sites that don’t require a username/password for check-in, viewing another clocked-in user’s skills on the Operator Portal now behaves more clearly.

Previously, clicking another user’s skill indicator could make it seem as though you were able to acknowledge their skills, but it would silently do nothing because you must be logged in as that user to acknowledge their skills.

With this update, when you view another user’s skills, you’ll see a clear message explaining that you must be logged in as that user to acknowledge their skills. Your own acknowledgement workflow remains unchanged.

5.15.26 Add Comments to a Pitch Without Updating Actuals

You can now save a comment on a pitch without entering production counts. Previously, the pitch dialog required actuals to be entered before a comment could be saved. With this update, operators can quickly log notes or document events mid-hour without affecting reported counts or scrap — simply type a comment and save.

Note: If actuals are entered below the target/demand, a comment is still required (existing behavior unchanged).

5.7.26 Standard Work Documents Display in the Operator Portal

We have updated the logic for the Operator Portal to ensure only fully configured Standard Work documents, those with a complete schedule and setup, are displayed. As a result, you may notice that certain documents previously visible now only appear once their requirements are finalized, ensuring operators see only the most relevant and actionable tasks.

5.1.2026 GDPR Compliance on User Setup for Images

As part of GDPR compliance for our European customers, we’ve added a new site setting where deactivating a user will automatically delete their profile image and clear their contact info (email, phone, SMS email). Includes a one-time bulk cleanup option to apply the rule to already-inactive users. Please reach out to Support if you’d like this enabled for your site.

April 2026 Changelog

4.28.26 Update to the new Dispatch UI

We've improved the Dispatch UI with clearer, more user-friendly error messages and now highlight any required fields that are missed during creation—making it faster and easier to get things right the first time.

We've also fixed a mobile issue where the keyboard could cover dropdown selections, improving the overall experience on smaller screens.

4.27.26 Calendar Updates and Quick Authentication

Maintenance Planning Calendars

To provide a more integrated maintenance planning experience, we've updated our core calendars to a unified backbone. Users will notice more consistent filtering options and minor UI refinements across the Work Order, Scheduler, Resource, Production, and Resource Shifts Calendars, laying the groundwork for future data overlays.

Quick Authentication

To streamline workflows on shared devices, we've introduced a Quick Authentication option for checklists. This feature is designed for environments that prioritize operational speed for high-frequency "sign-offs." Instead of typing a username and password, users can simply select their name from a pre-defined list to authenticate their work.

4.24.26 New Dispatch UI & API Documentation Fix

Dispatch

The New Dispatch dialog has been redesigned for mobile and tablet devices (however you'll notice the difference on a desktop too!) to ensure action buttons remain accessible and visible even when the on-screen keyboard is active. Key updates include:

• A full-screen layout with a pinned header and footer.

• Optimized dropdown selectors that feature search icons and improved text truncation for faster navigation on smaller screens.

API

We've updated the API documentation for the params_use_codes parameter in the Documents add, modify, and list_bycategory methods to correctly reflect that a value of 0 uses IDs and 1 uses codes.

4.15.26 L2L Execution AI Sliding Content & Additional Microphone Speech-to-Text Capabilities

L2L Execution AI Sliding Content

We've improved the L2L Execution AI interface to provide a more seamless multitasking experience. Previously, navigating the Execution AI panel could overlay your active workspace. With this update, we have introduced Sliding Content functionality. Now, the AI interface slides alongside your data rather than covering it, so you can still see your existing content and interact with data at the same time the AI chat is open.

Go Hands-Free with Expanded Speech-to-Text!

You can now use speech-to-text in the following locations:

• Dispatch portal (description and notes)

• Checklists (long input answers and comments/notes field)

Simply tap the microphone where available to dictate your notes and keep your workflow moving.

4.10.26 Quick Fix Functionality for Non-Production Customers & L2L Execution AI Solver Management Administrator Custom/Saved Solver Sharing

Quick Fix Functionality for Non-Production Customers

We've expanded the Quick Fix / Operator Fix functionality to support customers/sites that do not have the Production Module enabled. You can now configure these shortcuts directly within Dispatch Settings. Once configured, the Quick Fix option will be available on the Role-Based Home Page for faster issue resolution and data entry.

How to Configure: Navigate to your Dispatch Settings and define the following defaults:

• Default Dispatch Type: Select the type to be used for Quick Fixes.

• Default Trade: Assign the standard trade associated with these quick-response actions.

L2L Execution AI Solver Management — Custom/Saved Solver Sharing

System Manager Administrators can now manage and share custom/saved AI Solvers to targeted roles & pages.

• Accessible under the Setup menu for System Manager Administrators.

• Share custom or saved solvers across your site by selecting specific Role Access & defining which Pages a shared solver can be viewed.

4.8.26 Checklist "Require identity confirmation before answering" now extends to SSO/SAML authenticated users

We've updated the "Require identity confirmation before answering" checklist setting to support SSO/SAML authentication.

• What's changed: Users can now verify their identity via SSO/SAML in addition to standard username/password credentials.

• How it works: When enabled, users are prompted to confirm their identity before the first question. This records the specific user for the audit trail without logging them out of their active session.

• User Experience: Depending on your site configuration, users will either see an option to verify via username/password or by selecting Authenticate with SSO when required on a checklist.

4.7.26 Exports on Reports now include all columns in the UI; Ideal Cycle Time is now available on the Build Sequence level; & new AI features in Chat

Reports

We have updated several of our production reports to ensure that the data you see in your web browser matches exactly what you get when you click "Export". We've specifically addressed:

• Raw Pitch Report

• Production Summary Report (Daily & Weekly)

• Product Order Groups (in Production menu)

Production

You can now define an Ideal Cycle Time directly on a Build Sequence. Ideal Cycle Time is now included:

• On the Build Sequence create and edit pages.

• As a field in the sync_order_details API

Execution AI Chat Updates

• Users can now tap a microphone icon and dictate instead of typing when responding to Execution AI follow-up questions.

• Resizable history panel, tooltips on long conversation titles, ability to star, rename, and hide conversations.

4.3.26 User Export Enhancements

To streamline the auditing process and provide better visibility into user permissions, we have added three new columns to the User Export:

• Trade: View the specific trade assigned to each user.

• Resource Site Access: Identify which sites a user has resource access to.

• Admin Security Settings: Quickly confirm administrative security configurations.

These additions eliminate the need to manually check individual user profiles, making it easier for administrators to perform site access audits.

4.2.26 Sub Asset Notifications

You can now configure specific notifications for Sub Assets. This allows for more granular tracking and faster response times for specific components of your equipment.

How to set it up:

1. Navigate to your notification configuration.

2. Select Machine as the notification Type.

3. In the new Sub Asset dropdown menu, search for and select the specific sub asset(s) for your notification.

4.1.26 Enhanced Trade Assignment Visibility

To improve administrative efficiency and visibility, we have updated the Trade detail page to provide a clearer view of user assignments. This update eliminates the need to cross-reference multiple screens to manage your workforce.

• "Users with this Trade" Dropdown: A new multi-select dropdown is now available directly on the Trade detail view.

• Direct Management: Administrators can now add or remove users from a specific trade directly within this view.

March 2026 Changelog

3.31.26 L2L Execution AI Chat History & Expand/Collapse Fullscreen View

Enhanced L2L Execution AI Experience

We've updated L2L Execution AI to make managing your data-driven conversations more intuitive and flexible.

• Chat History: Your AI conversations are now automatically saved. Use the Show History option in the panel menu to revisit previous analyses or pick up right where you left off. To return to the standard chat view, open the same menu and select Hide History.

• Expand/Collapse Fullscreen Mode: Need a better view of your insights? You can now expand the chat interface using the Fullscreen icon in the upper-right corner of the panel.

3.27.26 Cycle-Based PM Estimated Due Dates, Schedule Dispatch Auto Close Behavior Configuration, & Revert Dispatch Status Dot Indicator

Cycle-Based PM Estimated Due Dates

We have added a built-in prediction engine so planners can estimate when the next cycle-based PM is due without relying on third-party software. With enough historical PM data (2+ completions), the system automatically forecasts future cycle-based PM dates in the calendar based on actual machine usage patterns within L2L.

Schedule Dispatch Auto Close Behavior Configuration

Admins can configure auto-closure settings when creating/editing scheduled events on the New/Edit Scheduler screen.

• Default behavior: Auto-close new dispatch

• New option: Keep new dispatch open — newer dispatches can remain visible and completable until manually closed or the configured time expires.

Revert Dispatch Status Dot Indicator

By changing the UI to be a dot next to the Dispatch status, we received reports that this may be slowing down the ability to quickly get information from the Dispatch list screen. We have reverted to having the color pill fully surround the Dispatch Status instead of the circle next to the status.

3.24.26 Improved Dispatch Status Sorting

To make finding the right status quicker and more intuitive, the Dispatch Status dropdown is now automatically sorted in alphabetical order.

3.20.26 Dispatch Type Setting to require sub asset to create new dispatch & Dispatch Status Dot Indicator

Dispatch Type Setting: Sub Asset must be selected to open a Dispatch

We have introduced a new dispatch type configuration setting to help teams ensure data accuracy and asset tracking. Administrators can now require that a Sub Asset be selected before a dispatch can be created or saved.

• A "Sub Asset must be selected to open a DISPATCH" toggle is now available within the Create Dispatch Settings section of the Dispatch Type configuration screen.

• When this setting is enabled, the Sub Asset dropdown becomes a required field. The system will prevent the Dispatch from being created or saved until a selection is made.

• The Sub Asset field will be visually marked with a required indicator (such as an asterisk) whenever the setting is active.

• This requirement is enforced across the platform, applying to both the New Dispatch modal and the Edit Dispatch screen.

New Dispatch Status Indicators

We have replaced the large, colorful status with a simplified dot indicator system. By moving to a dot indicator, we've established a clear hierarchy where the Dispatch Type is the dominant identifier, allowing the status text to be more readable and less distracting. This reduces visual clutter across the list view.

Note: This is not a configurable setting.

3.19.26 Dispatch Search Performance Improvements

Optimized Dispatch Search Performance

We've optimized how the search bar handles data to ensure the Dispatch Portal remains fast and responsive, even for sites with massive amounts of historical data.

• Text-based searches in the Dispatch Portal now default to the last 30 days of records.

• If your search results are being limited by this timeframe, a small information (ⓘ) icon will appear inside the search box explaining the limit.

• The 30-day limit is automatically lifted whenever you have an active filter (such as Area, Trade, or Status) applied.

Reliable Direct Links to Dispatches

When using "Open in Portal" links or redirecting from the classic view, the system now targets the specific Dispatch Number directly. Upon loading, the matching row will automatically expand so you can get straight to work.

L2L Admins can adjust the default search window (30, 60, 90 days, or No Limit) upon request within Site Properties.

3.18.26 Dispatch Portal Impact Display & Admins can Group all Reject Limits failures into one Dispatch

Enhanced Impact Visibility on Dispatch Portal

Dispatch Impact can now be displayed directly on the Dispatch Portal. The system will automatically surface this information when users sort by Impact. There is also a setting in the View Options to show Impact even when not sorting by Impact.

Consolidated Reject Limit Dispatches for Checklists

Checklist Administrators now have more granular control over how reject failures are handled, reducing notification fatigue and streamlining technician workflows.

• Consolidated Reject Dispatches: Admins can now configure checklists to group all Numeric Checklist Task Reject Limit failures/violations into a single Dispatch upon completion.

• Per-Checklist Configuration: This behavior is toggleable at the individual checklist level. Admins can choose between the traditional multi-dispatch behavior or the new single-dispatch consolidation.

3.17.26 Enhanced Dispatch Watch Notifications & Settings

You can now receive Dispatch Watch status change notifications through your preferred communication channels.

• Multi-Channel Support: Receive notifications on channels you already use, such as Email and WhatsApp.

• Customizable Settings: A new Watch notifications dropdown has been added to your notification settings, allowing you to define exactly how you want to receive updates for dispatches you are watching.

• Stay Informed Anywhere: Notifications are sent based on your personal preferences so you can stay up to date on your mobile device or desktop without needing to reference the Notification Center.

How to Enable: Navigate to your Notification Settings → Locate the Dispatch Watch section → Select your preferred delivery channels (Email, SMS, Web Browser, Web App, or WhatsApp).

3.13.26 Product Names on the Operator Portal

Production

You can now view full product descriptions directly within the Operator Portal. The Pitch Details and Current Order widget (product orders) will show the code along with the description for the Product. No more jumping back and forth between tabs to figure out what product you need.

3.5.26 Filter by Dispatch Questions on The Dispatch Portal

Dispatch Portal

We've added a new Dispatch Questions filter to the Dispatch Portal, allowing teams to use questions as a first-class operational tool for filtering and organizing work—enabling more flexible workflow.

3.4.26 Event Shadowing for Cycle Based PMs

Scheduler

You can now configure cycle-based PM schedules to shadow other cycle-based PMs on the same asset—automatically pulling forward related PMs within a defined threshold into the same maintenance window.

Dispatch Watch Update

You will no longer be automatically put on the Dispatch Watch list for notifications if you've made an edit or a comment on the Dispatch.

February 2026 Changelog

2.26.26 Dispatch Portal Machine Filter & Dispatch Answers on the Dispatch History Report

Dispatch Portal

You can now filter by Machine on the Dispatch Portal! The previous 'machine' filter for critical machines is now a checkbox at the bottom of the filter page.

Reports

The Dispatch History Report now includes a dropdown for Dispatch Answers. First, choose the Dispatch Question and then the Answers dropdown will appear. Free text answers will always appear in your results.

2.19.26 Subassets now have their own dropdown when creating a New Dispatch

Dispatch

We've separated Subassets from the Machines dropdown when creating a New Dispatch. We'll continue this trend in other places where you find the two combined in the coming weeks.

2.18.26 New Share Button on Dispatch Portal, Spares Permission Change & Report Update

Dispatch Portal

We've added a Share button on the Dispatch Portal! When you share a link, recipients will see the same filtered view that's on your screen—making it easier to align on specific dispatches without additional instructions.

Reports

The Dispatch History Report now defaults to displaying 100 dispatches. This update makes it easier to use Insights. Note: this change applies to every visit to Dispatch History, even if you are not actively using Insights.

Spares

We've updated permissions within the Spares Queue. Going forward, only users with Spares Admin permissions can use the "Close All Spares" action.

2.17.26 Tooling API can now Update Statuses

API

You can now change the status of Tooling via the /api/1.0/tooling/ endpoint.

2.13.26 Updates to the Labor Efficiency Standard Time Metric

Production

The Labor Efficiency (Standard Time) metric is now using Planned Non-Production Minutes instead of Planned Downtime Minutes in the Labor Minutes calculation. This aligns the metric with the reallocation tool and eliminates the need for customers to launch Dispatches to account for non-production events.

What changed: Labor Minutes = Actual Labor Time – (Operator Count × Planned Non-Production Time)

2.12.26 Dispatch Portal Filter Display

Dispatch Portal Filter

The Dispatch Portal filter will now open in a right-hand side panel instead of appearing as a centered overlay.

2.10.26 AI on the Dispatch Portal & chat functionality, Lineside Display Efficiency Fix, and new field for Spares API

Spares

Spares now has a 'Reject' status. When 'reject' is selected in the queue, we remove the spares but do not decrement them. The Reject status can be seen on the Dispatch Portal, as well as Classic Dispatch.

API

• The Add Scrap Detail API now has a new field to submit comments.

• Spares Synchronized method and GET APIs now have a Reject status.

AI

• The AI Insights Lens is now available on the Dispatch Portal (restricted to the 15 dispatches listed in that view).

• The AI Lenses now have chat functionality! Ask follow-ups like "How much downtime did these code reds cause?" or "What's the priority here?" without needing to create a custom Lens.

Dashboards

We've released an update to our Lineside Display dashboard for the efficiency metric: Efficiency will be calculated by adding the actuals of the current pitch and all past pitches, and dividing it by the sum of past pitch demand plus the demand of the current shift based on time elapsed.

2.4.26 New Filter on the Dispatch History Report

Reports

The Dispatch History Report now has a field to filter by Dispatch Questions. You'll see only dispatches that have a response for that question.

2.2.26 Add Predicted Machine Occurrences to the Scheduler Calendar via API

API

The API now accepts predicted scheduled dates from external condition monitoring systems (e.g., Vimana) for cycle-based PM occurrences. These occurrences will display on the scheduler and resource calendars using the predicted date.

January 2026 Changelog

1.30.26 A Clearer Name for a Broader Tool: Dispatch Portal

We're excited to officially share that Technician Portal has been renamed to Dispatch Portal. With this release, the new name is now live across the platform.

Over time, it became clear that Technician Portal didn't fully reflect how the product is actually used. The portal supports dispatchers, supervisors, planners, operators, and technicians alike—making it a shared workspace, not a technician-only tool. Dispatch Portal better represents that broader audience and purpose.

1.27.26 Insights in your language

Insights

Dispatch Insights will now respond in the user's preferred language by default.

1.26.26 Dispatch Watch

Dispatch

Dispatch Watch allows users to watch or unwatch individual dispatches so they receive notifications to the notification center when key updates occur. This helps technicians and managers quickly stay informed without having to manually check dispatch details.

Note: The only notifications you'll currently receive using Dispatch Watch are for status changes and assignments.

1.26.26 Record Details/Batch Details API Update

API

The record_details and record_details_batch endpoints now support identifying a build sequence directly. In addition to productcode or product_autodetect, you can now provide either buildsequence_id or buildsequence_externalid. When a build sequence is specified, the API will use it to register actuals and scrap counts.

1.21.26 Document Sharing to Specific Sites

Documents

If you are one of multiple locations within the same company that use L2L, you now have the ability to share documents across specific sites (provided all of those sites are on the same server). Click into a document on your site and you'll see a section called 'Share Document.' Choose All Sites (Global Sharing), or select specific individual sites from the available dropdown.

1.20.26 New Dispatch Type Setting to Require Description

Dispatch

You can now enable a setting on Dispatch Types that requires a description when creating a Dispatch, ensuring clearer context on why the Dispatch was submitted.

1.19.26 Admins can search Teams in the Skills Matrix (Swipeguide)

Admins can now use a search field to filter by Teams on the Skills Matrix.

1.12.26 Failure Pattern Analysis Lens is now

available

AI Lenses

The Failure Pattern Analysis Lens is now available on the Machine landing page, Machine History, and Dispatch History. This lens helps technicians quickly understand recent work and enables maintenance managers to identify recurring failure patterns—reducing downtime and speeding up repairs.

1.8.26 AI Lenses now use 100 Dispatches!

AI Lenses

Our analysis lenses now pull in 100 dispatches instead of just 25. You may need to change your view to 100+ in order for the lens to correctly utilize the data on the page.

1.2.26 Warn End User that their Checklist Response will Trigger a Dispatch

Document Center

Document Center Admins can now enable a warning in Document Settings that appears when a checklist response will trigger a Dispatch. This is especially helpful for checklists with numeric inputs, where an end user may accidentally enter an incorrect value. With auto-save enabled, Dispatches previously launched immediately—this warning helps prevent unintended launches before the response is finalized.