How to Schedule Tableau Reports Around Business Calendars

Schedule the delivery for the business’s approved reporting dates, and configure the period shown in the report separately. Advanced Tableau Report Scheduler (ATRS) supports recurring frequencies and selected dates in a Custom Calendar, which can help when a finance close does not follow an ordinary weekly or monthly pattern.

Imagine finance requesting its performance pack on the fourth approved working day after month-end. It needs the completed month’s figures, with time to review them before the management meeting. Sending on the first of every month would be predictable, but it could still arrive before the books are ready.

A regular Tableau subscription may suit a straightforward recurring snapshot. The extra issue here is the company calendar: closures, approved close dates and occasional changes to the meeting timetable. ATRS can maintain those delivery choices alongside the report and its destination.

We’ll use a June performance pack to make the distinction concrete. Its delivery happens in July, while its figures remain June’s. A delay changes when the reader receives it; it should not silently turn it into July’s performance.

Before choosing a frequency, finance and the reporting owner need to agree what counts as a working day. That shared definition is more useful than a scheduling formula neither person can explain.

For this example, the company excludes weekends and is closed on Monday 5 July 2027. After June ends, the first four approved working days are 1, 2, 6 and 7 July. The June pack is therefore due on Wednesday 7 July.

The following cycle illustrates why one test month is not enough. With no additional closure in its first week, July’s fourth working day is Thursday 5 August. Those two dates show how the same business requirement can produce different positions within the calendar.

These are illustrative company dates, not a calendar your organization should adopt automatically. A headquarters closure may differ from a regional team’s working week. Finance needs to approve its own dates and the time zone in which the report is expected.

The purpose of a report also determines what a closure should do. A board pack might need to move earlier to allow reading time; a close report might have to wait until staff return. Skipping, advancing and delaying are different decisions. Selecting a custom date does not imply that every missed run automatically moves to another day.

Once the intended dates are written down, the scheduling choice is easier to evaluate. An ordinary Monday summary can keep its weekly recurrence, while the close pack uses the dates finance actually approved.

In ATRS, choose the recurrence that matches the agreed requirement, or create a named Custom Calendar and select the individual reporting dates. Apply it to the relevant report or package schedule, then inspect the next expected execution.

For finance, a name such as Finance Close Reporting 2027 makes the calendar’s purpose recognizable. The administrator should be able to show finance that the June pack is due on 7 July and the July pack on 5 August without opening unrelated schedules.

A shared calendar is useful when several outputs follow the same close. It also means a date change can affect more than the one pack somebody asked about. Review the schedules using it before applying an edit.

ATRS provides an Update Schedules action for distributing revised calendar information to the schedules that use it. Without that step, those schedules retain the old information. After a change, the next execution dates are the practical confirmation that the intended jobs received the revision.

Timing still sits alongside the reporting prerequisites. A 7 July calendar entry is not evidence that finance approved the close. If generation depends on that approval or a completed data update, the workflow needs that condition too.

A manual sample can prove the pack’s content and email delivery. It does not, by itself, prove that the recurring calendar is correct; the configured next run needs its own date review.

Suppose the June pack is delayed well beyond its intended July delivery. If someone generates it in August using a generic “previous month” selection, the resulting report could contain July instead of June. The file might arrive successfully and still answer the wrong question.

The requested reporting period therefore needs its own definition. For an ordinary monthly cycle, relative date logic may be appropriate. For a delayed run or correction, confirm the intended month or fiscal period explicitly before generating the pack.

The subject, report heading and filename should make that choice visible. “June performance pack” tells the reader what the figures describe, even if the message arrives later. Wording such as “approved close” should be used only when it accurately reflects the business state.

A package can contain several workbooks with different period logic. One may use calendar months, another a fiscal period. Compare their actual selections rather than assume a shared delivery date aligns them.

The year matters too. A January delivery can describe December of the previous year, and a fixed test date left in a schedule can keep producing an old month indefinitely. Inspect a second period during approval.

When finance requests a resend months later, establish whether it wants the original approved file or a fresh calculation incorporating corrections. That choice preserves the meaning of the request while allowing the delivery plan to change.

The calendar needs attention before its last selected date arrives. ATRS disables schedules using a custom calendar when that calendar ends. Adding more dates offers an option to re-enable affected schedules, so extending the list and checking the enabled state belong in the same review.

For finance, the next year’s close-calendar approval is a useful moment to do that work. The business owner approves the dates; the administrator updates the calendar, applies the revision to its schedules and checks the resulting future executions.

Review a few revealing dates: a month-end weekend, a closure, year-end and an irregular meeting. There is no need to generate every future report to understand whether those dates express the approved rule.

Then observe the first normal scheduled cycle. The pack should arrive at the agreed time, cover the intended month and leave the recipients enough time to read it. A technically punctual report arriving after the meeting would still miss the purpose of the calendar.

Keep the calendar’s owner and review deadline with its affected schedules. That gives a covering colleague a way to maintain the commitment when finance’s close process changes.

Use your own close dates and reporting periods to explore Tableau scheduling with ATRS, including the company closure or unusual month that an ordinary recurrence does not express.