> For the complete documentation index, see [llms.txt](https://docs.bluepro.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bluepro.ai/scheduling-and-jobs/scheduling-and-jobs.md). # Scheduling & Jobs Plan and dispatch work **Plan the work and get it done.** Book appointments, dispatch the right technician, run jobs from the field, and keep every deal moving through your pipeline — so the office and the field always see the same, up-to-date picture. **What you'll find here** * **Scheduling Appointments & Dispatching** — booking, calendar views, and the map (web) * **Setting Up Your Calendar & Availability** — hours, durations, and what powers online booking * **Appointments & Closing Out Work** — a technician's day, start to close-out (mobile) * **Working a Job from Start to Finish** — the job record and its lifecycle (web) * **Customizing Your Pipelines & Stages** — tailor stages and automate the steps between them > 💡 **Key idea:** Jobs move through **pipeline stages** as you work — book → complete → invoice → get paid — and most of that advancement happens automatically. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.bluepro.ai/scheduling-and-jobs/scheduling-and-jobs.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.