> ## Documentation Index
> Fetch the complete documentation index at: https://docs.probaseapp.com/llms.txt
> Use this file to discover all available pages before exploring further.

# On-demand jobs

> Set up jobs with no fixed schedule, like snow removal or callbacks, and add visits only when the work is needed

# On-demand jobs

Some work doesn't happen on a calendar. You plow after it snows, or you go out when a customer calls. An **On demand** job is made for this kind of work. It has a Start Date and an optional End Date, but ProBase doesn't book any visits by itself. You add a visit when the job needs one, either one at a time or many at once with [Dispatch](https://docs.probaseapp.com/scheduling/dispatch.md).

> [!NOTE]
>
> On-demand jobs and Dispatch are rolling out gradually. If you don't see **On demand** in the Service Frequency list yet, it hasn't reached your account.

## Creating an on-demand job

**1. Start a new job**

Tap the **+** button and choose **New Job**, then pick the customer, property and service as usual. See [Creating jobs](https://docs.probaseapp.com/getting-started/creating-jobs.md).

**2. Pick On demand**

On the **When should this job be scheduled?** step, open **Service Frequency** and choose **On demand**. The helper reads *"No set schedule. Visits are created on demand when requested or dispatched."*

The step now asks only for a **Start Date**, an optional **End Date** and the crew. There's no visit day, start time or length, because no visit is booked yet. With no End Date, the job stays open until you cancel it.

The **Start Date** is filled in with tomorrow. A line under the field says which day you've picked, in words: **Starts today.**, **Starts tomorrow.** or a date such as **Starts Mon, Nov 9.** Check it before you go on, because a billing plan starts on that day.

![Choosing On demand on the Schedule step](https://mintcdn.com/lawnstarter/xiqN-4tb8EenJDbV/images/probase/on-demand/01-schedule-step-on-demand-430.png?fit=max\&auto=format\&n=xiqN-4tb8EenJDbV\&q=85\&s=6de2cc6f8806a6bb8640c724727a1eea)

**3. Choose how to bill it**

On-demand jobs skip the usual Pricing step and go straight to billing. See [Billing an on-demand job](#billing-an-on-demand-job) below.

**4. Confirm and create**

Review the summary and tap **Create**. The job is saved with no visits, and its page reads **On demand**.

![An on-demand job created](https://mintcdn.com/lawnstarter/AH7JTXBRALSk3HPW/images/probase/on-demand/02-created-on-demand-430.png?fit=max\&auto=format\&n=AH7JTXBRALSk3HPW\&q=85\&s=f9e946ce2c7810dee553bef9dd56edc7)

![The job page reads On demand](https://mintcdn.com/lawnstarter/xiqN-4tb8EenJDbV/images/probase/on-demand/03-job-page-on-demand-430.png?fit=max\&auto=format\&n=xiqN-4tb8EenJDbV\&q=85\&s=c48887acce294693707a601032025341)

You can also switch an existing job to On demand from **Change Schedule** on the job page. Its existing visits are kept.

### Using a custom service

If you pick **Custom service** instead of a service from your catalog, ProBase still needs a name for the job. When the job is already set to On demand (for example, when you start it from the [Dispatch](https://docs.probaseapp.com/scheduling/dispatch.md) explainer), the step after the service reads **Describe this job**. It asks for:

* **Service Name** (required), such as "Roof raking"
* **Description** (optional)
* **Industry**, if you work in more than one trade
* **Checklists**, if you want every visit of this job to carry one

There's no price on this step. You set what the customer pays on the billing steps that follow.

![Describe this job for a custom on-demand service](https://mintcdn.com/lawnstarter/aVQdJ8kU20oFDroJ/images/probase/on-demand/04-custom-on-demand-describe-this-job-430.png?fit=max\&auto=format\&n=aVQdJ8kU20oFDroJ\&q=85\&s=79d31dd4a69544769d9fe6666c42e71c)

Tap **Next** to go on to the Schedule step, where **Service Frequency** is already **On demand**, then choose how to bill the job. The confirmation shows the name and description you typed on its **Service** row.

![The confirmation for a custom on-demand job](https://mintcdn.com/lawnstarter/AH7JTXBRALSk3HPW/images/probase/on-demand/05-custom-on-demand-confirm-430.png?fit=max\&auto=format\&n=AH7JTXBRALSk3HPW\&q=85\&s=6909092df76dcf3fa62605ea32a21626)

Tap **Confirm and create job** to save it.

![The custom on-demand job created](https://mintcdn.com/lawnstarter/AH7JTXBRALSk3HPW/images/probase/on-demand/06-custom-on-demand-created-430.png?fit=max\&auto=format\&n=AH7JTXBRALSk3HPW\&q=85\&s=7f61e288a61dad5f768a64f9d82dc9c9)

A job made from a catalog service skips **Describe this job**, because its name comes from the service.

#### Changing a custom on-demand job before you create it

You can also start a custom job the usual way — fill in **What does it cost?** with a name and price — and then set **Service Frequency** to **On demand** on the Schedule step. Either way, once a custom job is On demand, the confirmation sends you back to **Describe this job** to change it:

* Tap **Edit** on the **Service** row to change the name or description.
* Tap **Edit** on the **Pricing** row — it opens **Describe this job** too, because an on-demand job's price lives on its billing.
* Tap **Edit** on the **Checklists** row to add or remove a checklist.

Everything you typed is still there. Make your change and tap **Next** to go straight back to the confirmation.

![Editing the Service row opens Describe this job](https://mintcdn.com/lawnstarter/-Kwg20M49HEdLC7A/images/probase/on-demand/09-custom-on-demand-edit-service-describe-this-job-430.png?fit=max\&auto=format\&n=-Kwg20M49HEdLC7A\&q=85\&s=bad5b479a9bb354857957f64a974fa1f)

![The confirmation shows the new name](https://mintcdn.com/lawnstarter/AH7JTXBRALSk3HPW/images/probase/on-demand/10-custom-on-demand-edited-service-confirm-430.png?fit=max\&auto=format\&n=AH7JTXBRALSk3HPW\&q=85\&s=ac3b1601e724955bc15503502c8a3624)

![Editing the Pricing row opens Describe this job](https://mintcdn.com/lawnstarter/-Kwg20M49HEdLC7A/images/probase/on-demand/07-custom-on-demand-edit-pricing-describe-this-job-430.png?fit=max\&auto=format\&n=-Kwg20M49HEdLC7A\&q=85\&s=fc7566bafd436a1afd725a35f9fa8bd0)

![Editing the Checklists row opens Describe this job](https://mintcdn.com/lawnstarter/vWwqJMY0BSiRui61/images/probase/on-demand/11-custom-on-demand-edit-checklists-describe-this-job-430.png?fit=max\&auto=format\&n=vWwqJMY0BSiRui61\&q=85\&s=2396d8a7fe9de1ad64607a69bbf65b2c)

To change what the customer pays, tap **Edit** on the **Billing** row. A job made from a catalog service works differently: its **Service** row lets you pick a different service, and its **Pricing** row opens the billing summary.

## Billing an on-demand job

The first billing question is **How do you want to bill this job?**

* **By the visit** — bill the customer after each completed visit. Best for per-push snow removal, callbacks or as-needed jobs.
* **Fixed rate or recurring plan** — bill a set amount on a regular schedule, such as monthly or seasonally. Best for seasonal contracts and maintenance plans. You then pick how often it bills.

Where season contracts have reached your account, a plan then asks **How is this plan structured?**: **Ongoing recurring** for a plan with no fixed end, or **Fixed term total** for one price over a set timeframe. See [Season contracts](https://docs.probaseapp.com/scheduling/contracts.md).

![How do you want to bill this job?](https://mintcdn.com/lawnstarter/vWwqJMY0BSiRui61/images/probase/on-demand-billing/01-how-to-bill-430.png?fit=max\&auto=format\&n=vWwqJMY0BSiRui61\&q=85\&s=a494193a1c72cc9366f078893fffbfe7)

Next comes **What does this customer pay?** Fill in the price and tax rate. You can also add a charge or a discount. The **Total (with tax)** updates as you type.

![What does this customer pay?](https://mintcdn.com/lawnstarter/623aOteOmCvXbX6U/images/probase/on-demand-billing/02-summary-by-the-visit-430.png?fit=max\&auto=format\&n=623aOteOmCvXbX6U\&q=85\&s=7fe9e75db938a81381a521dd8d7f01ef)

If the service already has its billing set up in your [service catalog](https://docs.probaseapp.com/getting-started/service-catalog.md#setting-up-billing-for-an-on-demand-service), this summary opens filled in. Tap **Edit billing** to change it for this job only.

A few things to know:

* **The price can be left blank.** The job shows **No price yet**. A visit on an unpriced by-the-visit job doesn't add a charge, but any other charges on the job still bill.
* **A discount applies once**, to the first invoice, and can't be more than that invoice.
* **Fix anything marked.** If you tap Next with a problem, the field is marked and the footer tells you how many fields need fixing.

![Fields that need fixing](https://mintcdn.com/lawnstarter/Sk_qbpRcTRpk0ONp/images/probase/on-demand-billing/03-summary-next-check-430.png?fit=max\&auto=format\&n=Sk_qbpRcTRpk0ONp\&q=85\&s=2c2afc6d7e304c3f6a355df5e02d63cb)

### Per-visit charge on a plan

A recurring plan can also add a fixed amount for each completed visit, for example "$125.00/month + $60.00 per visit". The field's note reads *Added to the invoice each time a visit is completed. For example, $125/month plus $60 per visit.* — the same note on the job's billing, the job's **Edit pricing** page and a quote line. The per-visit charge must be more than \$0. The job's total then reads **Total (subscription only)**, because per-visit charges are added and taxed on each invoice.

### When a plan bills

An on-demand plan bills from its first charge day through its End Date, and only while the job is open:

* If the Start Date is later than today, the first charge is on the Start Date. Otherwise it's the day you create the job.
* Later charges repeat from that first day, for example on the 1st of each month.
* The last charge is on or before the End Date.

For example, a plan sold on Oct 20 with a Start Date of Nov 1 and an End Date of Mar 15 bills on Nov 1, then on the 1st of each month, and last on Mar 1.

The **How this plan bills** note on the confirmation and the **Job created** screen says when the first charge is added. When the Start Date is later than today, it names that day, for example *"The first charge (\$125.00) is added on Nov 15."* Otherwise it says the charge is added now.

### Saving the billing to the service

If the service has no billing setup yet, the confirmation offers **Save this as \[service]'s billing for new jobs**. It starts checked. Leave it on and the next on-demand job for that service starts with the same billing. You need permission to edit services to see this box.

![Save the billing to the service](https://mintcdn.com/lawnstarter/AH7JTXBRALSk3HPW/images/probase/on-demand-billing/04-confirm-save-to-service-430.png?fit=max\&auto=format\&n=AH7JTXBRALSk3HPW\&q=85\&s=ed853662bf326e7209f53e483fa4c022)

## Snow Removal details

When an on-demand job uses a **Snow Removal** service, it carries two extra details:

* **Trigger depth** — how many inches of snow it takes before you go out. It fills in from the service's default, and you can change it on the confirmation (where it reads, for example, *2 in*) or later through **Change Schedule**. [Dispatch](https://docs.probaseapp.com/scheduling/dispatch.md) uses it to leave out jobs that aren't due yet.
* **Area treated** — the size of the area in square feet, under **Visit defaults** on the job page.

![Snow fields not set yet](https://mintcdn.com/lawnstarter/AH7JTXBRALSk3HPW/images/probase/on-demand-job-page/04-snow-fields-not-set-430.png?fit=max\&auto=format\&n=AH7JTXBRALSk3HPW\&q=85\&s=e5240a2fc495dffa354a44476498a64c)

![Snow fields set](https://mintcdn.com/lawnstarter/AH7JTXBRALSk3HPW/images/probase/on-demand-job-page/05-snow-fields-set-430.png?fit=max\&auto=format\&n=AH7JTXBRALSk3HPW\&q=85\&s=beca2196104eb699298271de650aa965)

## The job page

An on-demand job's page shows its price in words, such as "$75.00 per visit", "$125.00/month" or "$125.00/month + $60.00 per visit".

![The two-part price on the job page](https://mintcdn.com/lawnstarter/AH7JTXBRALSk3HPW/images/probase/on-demand-job-page/03-two-part-price-430.png?fit=max\&auto=format\&n=AH7JTXBRALSk3HPW\&q=85\&s=9b817e4047a9970a7636ab73cda349c4)

Wherever ProBase names how an on-demand job is billed, it uses the same words you picked when you set it up: **By the visit**, or **Ongoing recurring** followed by how often it bills, such as *Ongoing recurring · Monthly*. You see these words on the job's **Service plan** section, on the visit's **Details** tab, on the visit cards in your schedule and on the **Edit pricing** page.

On a plan with no per-visit charge, Service details offers **Add a per-visit charge**. It opens Change Pricing with the charge field ready. Use **Remove charge** to take it off again.

![Add a per-visit charge](https://mintcdn.com/lawnstarter/AH7JTXBRALSk3HPW/images/probase/on-demand-job-page/01-subscription-offers-a-charge-430.png?fit=max\&auto=format\&n=AH7JTXBRALSk3HPW\&q=85\&s=cbd5902b4787ed5dcee7ef664b37a4bb)

![A \$0 charge is refused](https://mintcdn.com/lawnstarter/HeJk4XosxNRK1SsZ/images/probase/on-demand-job-page/02-zero-charge-refused-430.png?fit=max\&auto=format\&n=HeJk4XosxNRK1SsZ\&q=85\&s=2b23a48c2af9eb95b4453295a05889a3)

A later price or charge only applies to visits completed after you change it.

## Adding visits

An on-demand job never books visits by itself. To add one:

* Use **Schedule a visit** on the job page for a single visit, or
* Use [Dispatch](https://docs.probaseapp.com/scheduling/dispatch.md) to add a visit to many jobs at once.

Visits added through Dispatch have no set time. They read **Anytime** on the visit page, the day view and the week view, and they sit at the top of the day. If you set a time on one, it stops being Anytime.

## When the End Date passes

An on-demand job closes by itself after its End Date ends in your business's time zone. When it closes:

* It reads **Completed** and stops billing.
* Visits booked after the End Date that nobody has started are cancelled.
* Visits on or before the End Date, and any visit someone already worked on, are kept.

![An ended job](https://mintcdn.com/lawnstarter/U-B6ePA8PoEShqel/images/probase/gw3409-reopen-at-end-date/01-ended-job.png?fit=max\&auto=format\&n=U-B6ePA8PoEShqel\&q=85\&s=1005127fd92499f04df52ed01ffb2373)

### Reopening an ended job

You can reopen a job that closed at its End Date. It continues the same plan: no new first charge, and the Start Date and billing day stay the same. Billing days that passed while the job was closed aren't charged.

* **Set a later End Date** through Change Schedule. Pick today or a later date, or clear it.

  ![Setting a later End Date](https://mintcdn.com/lawnstarter/U-B6ePA8PoEShqel/images/probase/gw3409-reopen-at-end-date/02-later-end-date.png?fit=max\&auto=format\&n=U-B6ePA8PoEShqel\&q=85\&s=ec947bbcb5b3c56f7078528d823b47ce)

  ![The job reopened](https://mintcdn.com/lawnstarter/U-B6ePA8PoEShqel/images/probase/gw3409-reopen-at-end-date/03-reopened.png?fit=max\&auto=format\&n=U-B6ePA8PoEShqel\&q=85\&s=b3ce57299e89c5ae52ff617afe40524d)

* **Schedule a visit.** The sheet tells you *"Scheduling this visit reopens the job until \[day]"* and what it will cost. The visit's day becomes the new End Date when it's later.

  ![The reopen sheet](https://mintcdn.com/lawnstarter/AbABdrIu95eqV7H0/images/probase/closed-jobs/06-reopen-sheet.png?fit=max\&auto=format\&n=AbABdrIu95eqV7H0\&q=85\&s=7a067026d62fa6821f8399363ac631c5)

* **Extend the season** for many ended jobs at once from Dispatch. See [Ended jobs](https://docs.probaseapp.com/scheduling/dispatch.md#ended-jobs-and-extend-the-season).

## Duplicating a job for next season

A job that closed at its End Date leads with **Duplicate job**, with **Schedule a visit** below it. **Duplicate job** is also in the job's **⋯** menu, next to **Cancel job**.

![A closed job leads with Duplicate job](https://mintcdn.com/lawnstarter/petJy3W1e9CxiFU_/images/probase/closed-jobs/01-closed-job-leads-with-duplicate.png?fit=max\&auto=format\&n=petJy3W1e9CxiFU_\&q=85\&s=eb906234edee9647a532d123cd942d5e)

![The closed job's More menu](https://mintcdn.com/lawnstarter/petJy3W1e9CxiFU_/images/probase/closed-jobs/02-closed-job-more.png?fit=max\&auto=format\&n=petJy3W1e9CxiFU_\&q=85\&s=135c18fa239d86a31555e3f701fd2911)

Duplicate job opens the New Job confirmation filled in from the old job: customer, property, service, billing, price, per-visit charge, tax, frequency, trigger depth, area treated, crew and visit time. Both dates move one year forward, and the **Schedule** row reads *"Dates moved forward one year from the earlier job."* Charges, discounts and visits are never copied.

* If the Start Date a year on has already passed, the copy starts **today** instead and keeps the moved End Date. The **Schedule** row adds *"Start Date set to today."*

  ![A duplicate starting today](https://mintcdn.com/lawnstarter/petJy3W1e9CxiFU_/images/probase/closed-jobs/06-duplicate-start-date-set-to-today.png?fit=max\&auto=format\&n=petJy3W1e9CxiFU_\&q=85\&s=2e1d969cb6d1edf76b10399aa385d4f6)
* If the End Date a year on has already passed too, or the earlier job had no End Date, neither date is filled in and you pick the Start Date yourself.

![The duplicate confirmation](https://mintcdn.com/lawnstarter/petJy3W1e9CxiFU_/images/probase/closed-jobs/03-duplicate-confirmation.png?fit=max\&auto=format\&n=petJy3W1e9CxiFU_\&q=85\&s=070b34485fc7195f6e099a520c5438ff)

Once the copy is created, the old job's button reads **View the new job**.

![View the new job](https://mintcdn.com/lawnstarter/petJy3W1e9CxiFU_/images/probase/closed-jobs/05-closed-job-view-the-new-job.png?fit=max\&auto=format\&n=petJy3W1e9CxiFU_\&q=85\&s=4763d75b3d88b2072ad9d2274a5a0a14)

### If another job overlaps

If the same customer already has an active job for the same service at that property, and the dates overlap, the confirmation asks what to do before you create the new one:

* **End the earlier job** the day before the new one starts (the default), or
* **Keep both running**.

![Choosing what to do with an overlapping job](https://mintcdn.com/lawnstarter/petJy3W1e9CxiFU_/images/probase/closed-jobs/04-duplicate-overlap-block.png?fit=max\&auto=format\&n=petJy3W1e9CxiFU_\&q=85\&s=2ea1bea064c22b9023ec2aeac116bb3d)

This check also appears in New Job when you create an overlapping job.

## Related pages

* [Dispatch](https://docs.probaseapp.com/scheduling/dispatch.md)
* [Season contracts](https://docs.probaseapp.com/scheduling/contracts.md)
* [Creating jobs](https://docs.probaseapp.com/getting-started/creating-jobs.md)
* [Service catalog](https://docs.probaseapp.com/getting-started/service-catalog.md)
* [One-time vs subscription billing](https://docs.probaseapp.com/billing/one-time-vs-subscription.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.