--- title: "Understanding Multi-Visit Snow Services" slug: "understanding-multi-visit-snow-services" description: "Learn how Multi-visit keeps seasonal snow work tickets open across storms for shared crew time, materials, subcontractor expenses, and scheduled billing." updated: 2026-11-13T19:46:19Z published: 2026-11-13T19:46:19Z canonical: "guide.youraspire.com/understanding-multi-visit-snow-services" --- > ## Documentation Index > Fetch the complete documentation index at: https://guide.youraspire.com/llms.txt > Use this file to discover all available pages before exploring further. # Understanding Multi-Visit Snow Services ## Overview **Multi-visit** helps you run one work ticket across many visits. It allows you to keep a single ticket open for a whole season while crews or subs report time to it after every storm, so you can sell seasonal snow contracts without creating, completing, and invoicing a new ticket for every push. ### Things to know - **Multi-visit** is a setting on the catalog service in **Administration > Estimating > Service Catalog**. It isn't on the estimate, so you can't turn it on from the **Service Details** screen. - Seasonal (Fixed Payment) snow services need **Multi-visit**. Per Service and T&M snow services shouldn't use it. - Crews and subs can't complete a Multi-visit work ticket in Aspire Mobile. Someone in the office completes it at the end of the season, or at the end of each month if you use monthly tickets. - On a seasonal service, **Multi-visit** is required before you can add a subcontractor auto expense. Because the seasonal ticket stays open, those expenses don't generate on completion. Instead, you generate them for a time period with **Trigger Auto Expense Creation**. - If you sell the same work more than one way, create a separate service for each invoice type so each one can carry the right **Multi-visit** setting. ## Requirements - To turn **Multi-visit** on or off for a service, users must have the *System Admin* permission, or the *Branch Admin* permission with **Enhance Branch Admin Security** turned on. Branch administrators can only edit services for the branches they have access to. ## How it works A normal work ticket covers one occurrence of a service: the crew does the work, completes the ticket, and the ticket moves on to approval or invoicing. A Multi-visit ticket doesn't end after one visit. It collects time, materials, and costs from every visit until someone in the office completes it. ### Rules - **When a service is marked Multi-visit** → crew leaders can finish a day's work on its ticket in Aspire Mobile, including any forms on the service, without putting the ticket into **Complete** status. - **When a crew or sub reports a visit to a Multi-visit ticket** → the time and materials post to the same ticket, which stays open for the next storm. - **When a Multi-visit service has a subcontractor auto expense** → you generate purchase receipt recommendations for a time period from the **Work Tickets** screen with **Bulk Actions > Trigger Auto Expense Creation**, instead of waiting for the ticket to complete. - **When the invoice type is Fixed Payment and the catalog service isn't marked Multi-visit** → **Add Subcontractor Expenses** doesn't display when you select the three-dot (⋮) icon on the **Service Details** screen, so you can't add an auto expense to that service. - **When you schedule visits in bulk from the Schedule an Event screen** → visits created from Multi-visit tickets use the service’s Per Visit Hours for their length on the schedule. Per Visit Hours is 0 unless you enter a value, so visits get zero hours by default. Aspire uses Per Visit Hours instead of the ticket’s total hours, which would be too long for a single visit. - **When a Multi-visit service is in the Snow division** → the **Service Details** screen on the estimate displays two extra fields: **Per Visit Hours**, which sets how long each scheduled visit takes on the schedule, and **Per Visit Materials Qty**, which sets the default material quantities crews see when they add materials from Aspire Mobile, Time Entry, or the Subcontractor Portal. - **When a seasonal service is limited by visit count** → each visit to the Multi-visit ticket counts toward the limit, unless the visit is marked **Ignore Multi Visit Service Limit**. ### Components involved - **Service Catalog** → where **Multi-visit** is set on the service. - **Service Details** screen on the estimate → where the invoice type, occurrences, **Per Visit Hours**, visit limits, and auto expenses are set for the opportunity service. - **Schedule Board** → where visits to the ticket are scheduled for each event. - **Aspire Mobile** and the **Subcontractor Portal** → where crews and subs report each visit. - **Time Entry** and the **Work Tickets** module → where the office completes the ticket. ### Key terms | Term | Meaning | | --- | --- | | Multi-visit | A service setting that lets crews or subs report many visits to one work ticket without completing it. | | Visit | One trip to the property, scheduled on the Schedule Board. A Multi-visit ticket can have many visits. | | Per Visit Hours | A field on the estimate's **Service Details** screen, available for Multi-visit services in the Snow division, that sets how long each visit takes on the schedule. | ## Workflow / lifecycle A seasonal Multi-visit ticket moves through these stages: ![Diagram comparing seasonal tickets, which stay open all season, with per occurrence and T&M tickets, which are created for each event.](https://cdn.document360.io/5942a8d7-f3b1-4919-bdfa-d477d8498fe3/Images/Documentation/Snow_Work_Ticket_Lifecycle_Nov2026.png?sv=2026-02-06&spr=https&st=2026-11-15T01%3A07%3A14Z&se=2026-11-15T02%3A07%3A14Z&sr=c&sp=r&sig=6CMuLpOabs8Tv5e%2FjSKLKyPq8Xs7XRzepxYtD53vUQ0%3D) - **Created** → Aspire creates the ticket when the opportunity is won. With one occurrence, you get one ticket for the season. With one occurrence per month, you get one ticket for each snow month. - **Open** → for each storm, a visit is scheduled or pulled, and crews or subs report their time and materials to the same ticket. After each visit, the ticket stays open. - **Completed by the office** → at the end of the season, or at month end for monthly tickets, someone in the office completes the ticket from the work ticket or in Time Entry. - **Pending Approval** (if the service is marked **Requires Approval**) → the ticket waits for review before it's closed out. Approval is optional for seasonal services. > [!CAUTION] > **Caution:** When you accept time on a Fixed Payment ticket in Time Entry, leave **Complete** cleared. Selecting it completes the ticket, and clearing it later doesn’t uncomplete it. If that happens, uncomplete the ticket so it can take time from later storms. Billing for a seasonal service runs on the payment schedule in the estimate, not on ticket completion, so your customer is invoiced on schedule while the ticket stays open. ## Behavior notes / exceptions - **Per Service and T&M services marked Multi-visit** — crews can't complete these tickets in Aspire Mobile, so each one sits open until the office completes it. That delays approval and invoicing after every event. Clear **Multi-visit** on these services. - **Seasonal ticket completed too early** — if someone completes a seasonal ticket before the season ends, it can't take time from later storms. Uncomplete it to reopen it. - **Changing the setting on an existing service** — **Multi-visit** is read from the catalog service. When you turn it on, existing estimates and work tickets for that service update too, so you don’t need a contract change. - **Several routes visiting one property** — if more than one route visits a property for the same event and you want it counted once, mark the extra visits **Ignore Multi Visit Service Limit**. Visits created from an ignored visit are ignored too. - **Visits past midnight** — a visit that starts before midnight and runs past it counts as one visit toward a visit limit. - **Non-snow uses** — **Multi-visit** isn't limited to snow. Some companies use it for growing community (developing HOA) contracts, with one ticket covering a month of visits. ## How this displays in Aspire - In the Service Catalog, the **Multi-visit** checkbox displays on the **Service** screen. - On the estimate, **Per Visit Hours** and **Per Visit Materials Qty** display on the **Service Details** screen only for Multi-visit services in the Snow division. ![Service Details screen for a Multi-Visit snow service with Per Visit Hours and Per Visit Materials Qty highlighted.](https://cdn.document360.io/5942a8d7-f3b1-4919-bdfa-d477d8498fe3/Images/Documentation/Snow_Multi_Visit_Per_Visit_Fields_on_Estimate_Oct2026.png?sv=2026-02-06&spr=https&st=2026-11-15T01%3A07%3A14Z&se=2026-11-15T02%3A07%3A14Z&sr=c&sp=r&sig=6CMuLpOabs8Tv5e%2FjSKLKyPq8Xs7XRzepxYtD53vUQ0%3D) - On the Schedule Board, each storm's visit displays as its own placard, all tied to the same work ticket. - In Aspire Mobile, crew leaders can finish their work and forms for the visit, but the ticket isn't set to **Complete**. ## Why this matters Multi-visit is the setting that makes seasonal snow work in Aspire. Without it, a season-long ticket either gets completed after the first storm or blocks subcontractor payouts until spring. Set it right in the Service Catalog before you estimate, and your seasonal tickets, visit limits, and auto expenses behave the way your contracts expect. ## Troubleshooting For help with common Multi-visit problems, such as crews who can't complete a ticket, visit [Snow Troubleshooting](/docs/snow-troubleshooting). ## Related articles - [Snow Season Overview](/docs/snow) - [Setting Up Snow Services](/docs/snow-season-setup) - [Structuring Snow Opportunities](/docs/structuring-snow-opportunities) - [Scheduling a Snow Event](/docs/video-snow-scheduling-scheduling-an-event) - [Snow Troubleshooting](/docs/snow-troubleshooting)