Keypup

Function: <code>BUSINESS_HOURS</code>

Syntax: <code>BUSINESS_HOURS(datetime_start, datetime_end, [timezone="UTC"], [hour_start="09:00"], [hour_end="17:00"], [weekday_start=1], [weekday_end=5])</code>

Description: Return a decimal number representing the business hours elapsed between two datetime values.

Full days of work are accounted for based on specified working hours (<code>8</code> for the default range <code>09:00</code> to <code>17:00</code>), not based on the 24h clock day.

Two business days will be equal to <code>16</code> hours when using the default <code>09:00</code> to <code>17:00</code> working hours. If you change the working hours to be from <code>06:00</code> till <code>22:00</code> (16-hour day), then this duration becomes <code>32</code> hours.

The range of days worked within the week is specified using the <code>ISO8601</code> standard, where Monday is <code>1</code> and Sunday is <code>7</code>.

The list of supported timezones is specified below.

<code>BUSINESS_HOURS("2013-06-24T13:30:00", "2013-06-25T18:29:00")</code> returns <code>11.5</code>

<code>BUSINESS_HOURS("2013-06-24T13:30:00", "2013-06-25T18:29:00", "CET")</code> returns <code>10.5</code>. With CET, the clock is moved one hour forward compared to UTC, so fewer work hours are accounted for on the first day.

<code>BUSINESS_HOURS("2013-06-24T11:00:00", "2013-06-24T15:00:00")</code> returns <code>4</code> (same day, half-shift)

<code>BUSINESS_HOURS("2013-06-24T13:35:00", "2013-06-25T18:29:00", "CET", "10:00", "16:00", 2, 4)</code> returns <code>6.0</code>. The first day is ignored since it's a Monday and we've explicitly specified that the week goes from Tuesday (<code>2</code>) to Thursday (<code>4</code>). The second day goes from <code>10:00</code> till <code>18:29</code>, which is equivalent to <code>10:00</code> till <code>16:00</code> since the hours beyond the shift are ignored, thus the <code>6.0</code> value.

<code>BUSINESS_HOURS("2013-06-24T13:35:00", "2013-07-25T18:29:00", "CET", "10:00", "14:00")</code> returns <code>92.0</code>. The first day is ignored because in <code>CET</code>, the "from" datetime starts after the shift's end (<code>14:00</code>). The last day is accounted in full since it ends after the shift's end. Then all weekdays between the two datetimes get accounted for. Each weekday is equivalent to <code>4</code> hours since the working hours are set from <code>10:00</code> till <code>14:00</code>.

- <code>BUSINESS_HOURS("2013-06-24T13:30:00", "2013-06-25T18:29:00")</code> returns <code>11.5</code>
- <code>BUSINESS_HOURS("2013-06-24T13:30:00", "2013-06-25T18:29:00", "CET")</code> returns <code>10.5</code>. With CET, the clock is moved one hour forward compared to UTC, so fewer work hours are accounted for on the first day.
- <code>BUSINESS_HOURS("2013-06-24T11:00:00", "2013-06-24T15:00:00")</code> returns <code>4</code> (same day, half-shift)
- <code>BUSINESS_HOURS("2013-06-24T13:35:00", "2013-06-25T18:29:00", "CET", "10:00", "16:00", 2, 4)</code> returns <code>6.0</code>. The first day is ignored since it's a Monday and we've explicitly specified that the week goes from Tuesday (<code>2</code>) to Thursday (<code>4</code>). The second day goes from <code>10:00</code> till <code>18:29</code>, which is equivalent to <code>10:00</code> till <code>16:00</code> since the hours beyond the shift are ignored, thus the <code>6.0</code> value.
- <code>BUSINESS_HOURS("2013-06-24T13:35:00", "2013-07-25T18:29:00", "CET", "10:00", "14:00")</code> returns <code>92.0</code>. The first day is ignored because in <code>CET</code>, the "from" datetime starts after the shift's end (<code>14:00</code>). The last day is accounted in full since it ends after the shift's end. Then all weekdays between the two datetimes get accounted for. Each weekday is equivalent to <code>4</code> hours since the working hours are set from <code>10:00</code> till <code>14:00</code>.

Below is the list of timezone abbreviations supported by <code>timezone</code> argument:

<code>ACST, ADT, AEST, AKDT, AST, AWST, BST, CAT, CDT, CEST, CET, CST, ChST, EAT, EDT, EEST, EET, EST, GMT, HDT, HKT, HST, IDT, IST, JST, KST, MDT, MSK, MST, NDT, NZST, PDT, PKT, PST, SAST, SST, UTC, WAT, WEST, WIB, WIT, WITA</code> ​

For a complete list of all supported "named" timezones (e.g. <code>Europe/Amsterdam</code>), see <a href="https://docs.keypup.io/en/articles/11705324-supported-timezones">the following help article</a>.

BUSINESS_HOURS

Find answers and get help from Intercom Support and Community Experts

This site employs cookies and other technologies that we and our third party vendors use to monitor and record personal information about you and your interactions with the site (including content viewed, cursor movements, screen recordings, and chat contents) for the purposes described in our Cookie Policy. By continuing to visit our site, you agree to our {websiteTermsLink}, {privacyPolicyLink} and {cookiePolicyLink}.

This site uses cookies and similar technologies ("cookies") as strictly necessary for site operation. We and our partners also would like to set additional cookies to enable site performance analytics, functionality, advertising and social media features. See our {cookiePolicyLink} for details. You can change your cookie preferences in our Cookie Settings.

We use cookies to make our site work and also for analytics and advertising purposes. You can enable or disable optional cookies as desired. See our {cookiePolicyLink} for more details.

Advertising cookies are set by our advertising partners to collect information about your use of the site, our communications, and other online services over time and with different browsers and devices. They use this information to show you ads online that they think will interest you and measure the ads' performance. Social media cookies are set by social media platforms to enable you to share content on those platforms, and are capable of tracking information about your activity across other online services for use as described in their privacy policies.

These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.

These cookies are necessary for the website to function and cannot be switched off in our systems.

These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site.

You have the right to opt out of the sale of your personal information. See our {cookiePolicyLink} for more details about how we use your data.

Your Privacy Choices

We use cookies to enhance your experience. You can customize your cookie preferences below. See our {cookiePolicyLink} for more details.

Cookie Settings

Link, Press control-option-right-arrow to exit

Empty Help Center

Uh oh. That page doesn’t exist.

Disappointed

Neutral

Smiley

Thinking...

Searching through sources...

Analyzing...

Tickets submitted through the messenger or by a support agent in your conversation will appear here.