Deadline

A due date that knows about weekends, holidays, and the difference between them.

Give it a start date and a number of days. It returns the date the clock actually runs out, how many working days are left, and a sentence explaining how it got there. It renders a card, and it exposes every number it computed so you can draw your own.

It does not write anything. No status column, no stored due date, no reminder. It computes and reports; what that means is yours.

Why not just use DateAdd

DateAdd(start, 30, TimeUnit.Days) is wrong for most statutory and contractual clocks, and the three reasons stack up.

Weekends do not count. Thirty working days from 3 August is 14 September, not 2 September.

Holidays do not count either, so the answer depends on which months the window crosses. A thirty day clock starting in October crosses three federal holidays; the same clock starting in February crosses one. Same allowance, different date.

And a holiday is observed, not celebrated. Independence Day on a Saturday is observed on the Friday. The office is closed on the third, so the third is the day that does not count. An app that skips the fourth tells someone the office is open when it is shut.

The gap grows with the window. At thirty days it is usually about twelve. At a hundred and five working days from 17 August 2026 the naive answer is 30 November and the real one is 20 January, fifty one days later. Every one of them is a day somebody thought they had.

Properties

Input

Config

Card height is 236 expanded and 92 compact. The component sets it from Compact, so leave Height alone unless you are hiding sections individually.

Output

Events

What the card shows

Label and status pill across the top. The pill is a coloured dot and a word, not colour alone, so the state survives being printed and being read by somebody who cannot separate the hues.

The date, large, as Wed, Jan 20, 2027.

The countdown, in the unit the mode is counting: working days in business mode, calendar days in calendar mode. Overdue is always calendar days in both, because how late something is gets counted the way a person counts it.

The breakdown sentence. 105 working days from Aug 17 lands on Jan 20. 51 days skipped (7 holidays). This is the part that stops somebody rebuilding the calculation in a spreadsheet.

A progress bar, elapsed time over the whole span. Empty before the clock starts, full once it is overdue or complete.

Three tiles for the numbers the sentence refers to: work days remaining, skipped, holidays. A number somebody can point at settles an argument faster than a paragraph does.

Implementation details

No state at all. Every output derives from the inputs, so OnReset does nothing and the component draws correctly the moment it is pasted. There is no load step and no host wiring beyond passing the inputs.

The search is bounded. Adding N working days generates a window of candidate dates, keeps the working ones, and takes the Nth. The window is Days * 2 + 14, which is always enough because a five day week needs about 1.4 times the target and the extra fortnight covers a run of closures. Days is capped at 400, since an unbounded search is a hang rather than an error, and working day precision on a date two years out is false precision anyway.

The holiday table covers three years, the year of StartDate and the two either side, so a window crossing New Year still finds January's holidays. A 105 day clock from August reaches New Year's Day and MLK Day of the following year; a two year table would come back two days early and say nothing about why.

The observed rule is applied to the five fixed date holidays and the nth weekday computed for the rest. Independence Day 2026 falls on a Saturday, so the table carries Friday 3 July.

The progress bar measures elapsed over span, not remaining over allowance. The second one silently assumes the clock started today, and a start date three months out makes the fraction negative.

WorkDaysRemaining is not DaysRemaining. Three calendar days over a long weekend is zero working days. Showing the calendar count is how a deadline gets missed by somebody who was watching the countdown.

The working week is configurable. Sunday to Thursday is the working week across much of the Gulf. Hard coding Saturday and Sunday is what stops a component being usable outside the US, and it costs one Config key to avoid.

An empty holiday table is a sentinel, not Table(). An empty table literal has no columns, so anything reading HolidayDate off it fails to compile. The default carries one row dated 1900, and rows dated 1900 are treated as absent.

Use cases

When not to use it. If the clock runs in hours rather than days, or if the deadline is a fixed date somebody typed in, this is the wrong tool. It answers one question, and it is only interesting when the answer is not obvious.

SharePoint

Index DueDate. Filtering on a stored indexed date between two values is delegable at any list size; anything computed at render time is capped at your delegation limit and fails silently past it.

Recompute the stored date deliberately, in a Flow, when StartDate or DaysAllowed changes. Recomputing on every read means a holiday table correction quietly moves dates people are working to.

After you paste

Set Width by hand. A pasted component instance arrives at 600 regardless of what the YAML says. Height comes through intact.

Pass every Config key, even the ones you are leaving at their defaults. A Record input's Default does not reach a pasted instance, so the component Coalesces each key internally, and passing the full record is what a real host should look like.

The instance syntax is Control: CanvasComponent with a ComponentName sibling, not Control: cmpDeadline.

Try this

Set the start to 17 August 2026 with 105 days in working mode. The card reads Wed, Jan 20, 2027, 51 days skipped, 7 holidays, and the comparison panel shows DateAdd fifty one days short.

Switch to calendar days. The date moves back to 30 November, skipped drops to zero, and the holiday count drops to four, because the shorter window misses Christmas, New Year and MLK Day.

Pull the start back to 2 July and Independence Day appears in the list as Friday 3 July, not the fourth. That is the observed rule, and it is the detail most implementations get wrong.

To see the working week matter, use 26 July 2026 with 10 days. Monday to Friday gives Friday 7 August; Sunday to Thursday gives Sunday 9 August. Most starts give the same answer either way, since both weeks have five working days, so pick a start that lands on a weekend to see them separate.