Auto Tours

Note: Auto Tours is a Beta feature. To have it enabled for your database, please reach out to LDARtools Support.

Auto Tours let you save a component query and a build schedule once — Chateau builds the matching tours automatically on that cadence. Instead of returning to the Schedule each period to select components and click Build New Tours, you configure it once and the tours appear on their own.

Auto Tours requires the Tours Management role.

The Auto Tours tab is located under Tours > Auto Tours. To create a new auto build, click + New auto build in the top-right corner of the grid.

Setting Up an Auto Build

The New Auto Build panel has four sections.

Auto Build Name

Enter a name for this auto build. The name appears in the Auto Tours list and is available as a template variable in the tour name (see Tour Generation below).

Build When

Configure when the auto build runs.

Next run is shown below the time field so you can confirm the first scheduled execution before saving.

Note: Build times are limited to 5:00 AM–8:00 PM (local) so the nightly rules engine has finished populating the schedule before a build runs. Inspections appear on the schedule on the first day of their period — run the build at the start of the period you want to build (e.g., the 1st for monthlies).

Query — which scheduled components to include

Define which components the build should pull into tours.

Query builder

Use Add Fields to Query to add filter conditions. Each condition specifies a field (Facility, LUnit, component type, etc.), an operator (Equals, Not Equals, etc.), and a value. Add multiple conditions to narrow the selection. You can also load a previously saved query using the Saved Queries dropdown, or save the current query for reuse with the save (heart) icon.

Due window

The due window controls which inspection requests are eligible for this build. Select the period that matches your build frequency:

• This Week
• This Month
• This Bimonthly Period
• This Quarter
• This Year

The preview line below the dropdown shows the exact date range the next build will use — for example: "At next run (Jun 29, 2026), pulls requests due Jun 1, 2026 – Jun 30, 2026 — anything due within the Month."

Preview

A live preview section shows what the build would produce if it ran right now against today's schedule:

• Components match — number of components matching the query that have a pending request in the due window
• Tours would be built — estimated number of tours based on your grouping settings
• LUnits represented — number of distinct Location Units in the matching results

The preview is illustrative — the live build runs against the schedule on its actual run date, so results will differ.

Tour Generation

Configure how tours are structured when the build runs.

Group by LUnit — when checked, components from different Location Units are placed on separate tours. Uncheck to allow components from multiple Location Units on the same tour.

Cap per tour — when checked, enter a maximum number of components per tour. When the matching components exceed the cap, Chateau creates multiple tours. When unchecked, all matching components go on a single tour per LUnit (or one tour total if not grouping by LUnit).

Note: Two groupings are always applied regardless of your cap setting:

• REN grouping — components sharing the same reference equipment number are kept together, which may cause a tour to slightly exceed the cap
• Detector-type separation — components that require different detector type combinations (for example, FID vs. PID for M21) are placed on separate tours. AVO components, which require no detector type, are not separated from other inspection types and may appear on the same tour as M21 or OGI components.

Tour Name

Define the naming pattern for tours generated by this build. Click the Insert links to add template variables into the name:

Example: {auto build name} — {date} — {lunit} #{n} produces "Auto Build — Jun 25 — FCCU #1"

Default technician

Optionally assign all tours from this build to a specific technician automatically. Leave as (unassigned) to create tours without a technician assignment.

Notifications

Configure who is notified after each build attempt. Three notification types are available — each can be toggled on or off independently:

• Notify when a run matches zero components — sends a notification when the query ran successfully but found no pending requests matching the filter
• Notify on every successful build — sends a notification each time tours are created
• Notify if the build fails — sends a notification if an error prevented the build from completing

Recipients — enter Chateau users or email addresses. Type a name to search existing users, or type an email address directly to add someone who does not have a Chateau account.

Saving and Running

Enabled toggle — at the top of the panel, new auto builds are enabled by default. Toggle off to create the build in a disabled state without it running on schedule.

Save — saves the auto build. It will run at the next scheduled occurrence based on the recurrence settings. If you created a weekly build on a Thursday set to run every Monday, it will first run the following Monday.

Save & run now — saves the auto build and immediately triggers a build against today's schedule.

Validation — if required fields are missing when you click Save, Chateau highlights what needs to be filled in (for example: "Tour name is required" or "At least one query condition is required"). A green toast notification confirms "Auto build saved" on success.

The Auto Tours Grid

After saving, the auto build appears as a row in the Auto Tours grid. The grid shows:

Two action buttons appear at the end of each row:

• Edit — opens the Edit Auto Build panel to modify any settings, or to delete the build
• Run now — immediately triggers the build outside of its normal schedule

How Auto Tours Builds

When an auto build fires, Chateau:

1. Runs the saved query against the current inspection schedule within the configured due window
2. Collects all components that match the query and have at least one pending inspection request
3. Groups them by Location Unit (if enabled) and applies the size cap
4. Applies REN grouping — related equipment is kept together
5. Applies detector-type separation — components with different detector type combinations (e.g., FID vs. PID) are placed on separate tours; AVO components (no detector required) are not separated from other inspection types and may appear on the same tour as M21 or OGI components
6. Names each tour using the configured template
7. Assigns tours to the default technician (if configured)
8. Sends notifications to all configured recipients

Built tours appear in the Current Tours tab alongside manually created tours and can be edited, reassigned, or deleted there like any other tour.

Note: Auto Tours does not apply DTM-based size defaults. Tour sizing is governed entirely by your configured cap. If you need DTM and non-DTM components on separate tours, create two auto builds with distinct query filters.