If you’re talking about fixed payment tickets, I don’t think so. You can look at the Work Ticket Transaction Report to get a better idea. This has been an issue of mine for a while now. The visits number can be deceiving. It would be great if you could have an “as-needed” fixed payment ticket that doesn’t need to be invoiced and then you just use that ticket for each occurrence. 

I actually put an idea into the portal if you would like to vote on it: https://feedback.youraspire.com/ideas/WAP-I-6584

We are struggling with this topic this year, as we had many of our limited seasonal contracts reach their limited visits this year. It was terribly painful to count visits, as yes, the visit count is not always accurate.

I don’t have anything helpful to add, other than I did vote for your idea in the portal ​@snow_jones !  

How are other companies setting up limited seasonal work? Would it work to set them up with the number of tickets that are included in the price? How do we ensure they use a new ticket every time?

​@ericasarat Thanks for the vote! 

You could set them up with the correct number of services. It is difficult to ensure that they use a new ticket every time. The same goes for any per inch (per service) tickets though. What I usually do is after a storm I create a work ticket view of all the tickets you want to check and then clock into every one to ensure there’s only one clock in and that the ticket wasn’t used multiple times. I think the work ticket transaction report comes in handy here as well once you get all of the filters set up but I usually just got to the ticket itself. 

I would work with your CSM and see if Travis (I think) can join a meeting with you to review. He’s the go to Aspire guy for snow.