> For the complete documentation index, see [llms.txt](https://docs.betterbuilding.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.betterbuilding.io/sign-up-and-plans/news-and-updates/2026/copying-a-schedule.md).

# Copying a  Schedule

New Feature

<figure><img src="https://2129322768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfKJnzF2TwHA3APPbiCpF%2Fuploads%2FFF86NqabPejDgc0EQ7xO%2FCopying_a_schedule%20(Small).png?alt=media&amp;token=bd9db160-c079-4a8f-9e89-66cd9a998054" alt=""><figcaption></figcaption></figure>

Schedules show up everywhere on the platform: occupants, lighting, equipment, infiltration, air conditioning, etc.&#x20;

Managing them is one of those tasks that isn't hard, just tedious. Few are confused by a schedule. Folks are just tired of rebuilding the same one five times in five different places.

A few months back we added something for exactly this problem: a copy and paste feature that lets you grab any schedule and reuse it wherever you need it.&#x20;

For example, say you're setting up an HVAC system. You could head to the HVAC tab, copy the schedule you want, then drop it straight onto a component like an air handling unit or an air terminal, no rebuilding required.

It's a small feature, but it saves you from a genuinely annoying bit of busywork. Worth digging into if you haven't already.


---

# 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.betterbuilding.io/sign-up-and-plans/news-and-updates/2026/copying-a-schedule.md?ask=<question>&goal=<user_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.
