Project Progress

status="ready" · 7 projects, 356 tasks, read on 6 Apr 2026. The headline is 58% — the largest-remainder split of all 356 tasks is 58 / 11 / 2 / 29, which adds to exactly 100. Atlas data migration is 62% done against a schedule line standing at 88%, so it is 26 points behind and the chip reads At risk; Billing rewrite holds 4 of the board's 6 blocked tasks; Design system v2 went past 27 Mar ten days ago; Partner API sandbox has no start date, so there is no line to judge it against. Point at any row — or focus the rail and press ↓ — and its caption swaps from owner and date to the counts and shares behind the bar.

Platform group · Q2 delivery board

58%

of all tasks done

7 projects · 356 tasks · 6 blocked · 1 overdue · 1 complete

Atlas data migration

62%

At risk

Elizabeth Metz · due Apr 17 · 11 days left

Billing rewrite

67%

Blocked

Denise Runte DVM · due Apr 10 · 4 days left

Mobile onboarding

40%

On track

Hugo Emard · due May 15 · 39 days left

Design system v2

83%

Overdue

Linwood Carter · due Mar 27 · 10 days late

Search relevance

0%

At risk

Faith Harber · due Jun 30 · 85 days left

SOC 2 evidence

100%

Complete

Bria Konopelski · due Apr 30 · 24 days left

Partner API sandbox

35%

No schedule

Brett Langosh · due May 8 · 32 days left

done207 · 58%in progress39 · 11%blocked6 · 2%not started104 · 29%schedule line

Point at a project — or focus the rail and use ↑ and ↓ — to break its bar into counts and shares.

Each bar is one project's tasks, split into done, in progress, blocked and not started; bare track is work nobody has started. The four shares are whole per cents apportioned by largest remainder, so they add to exactly 100 and a segment holding real work never prints 0%. The tick is the schedule line — where a straight run from the start day to the due day says the project should be today. Health is derived from those numbers, never supplied: unscoped when no tasks are counted, complete when nothing is open, overdue past the due day, blocked while any task is blocked, at risk more than 10 points behind the schedule line, on track otherwise, and no schedule when the dates do not describe a window to draw a line in — the row says which date broke. Days are counted between calendar days, so nothing here moves with a time zone or a daylight-saving change. Rows are in the order the board supplied them.

Project progress: Platform group · Q2 delivery board. 7 projects, 356 tasks in scope. 58% of all the work is done. Across the whole board that is 58% done, 11% in progress, 2% blocked, 29% not started — whole per cents apportioned by largest remainder, so the four add to exactly 100. Read on Apr 6, 2026. 1 overdue, 2 holding blocked work, 2 at risk, 1 complete. Next date on the board: Design system v2 on Mar 27, 2026, 10 days late. Rows are in the order the board supplied them. Every project is listed in the table below.

Every project on the board with its owner, its dates, the four counts and their shares, the completion figure, where the schedule line stands today, and the health worked out from them.
Project	Owner	Started	Due	Days left	Done	In progress	Blocked	Not started	Total	Complete	Schedule line	Health	Why
Atlas data migration	Elizabeth Metz	Jan 12, 2026	Apr 17, 2026	11 days left	48 (62%)	12 (15%)	0 (0%)	18 (23%)	78	62%	88%	At risk	26 points behind the schedule line · 11 days left
Billing rewrite	Denise Runte DVM	Feb 2, 2026	Apr 10, 2026	4 days left	31 (67%)	6 (13%)	4 (9%)	5 (11%)	46	67%	94%	Blocked	4 tasks blocked and not moving · 4 days left
Mobile onboarding	Hugo Emard	Mar 2, 2026	May 15, 2026	39 days left	24 (40%)	9 (15%)	0 (0%)	27 (45%)	60	40%	47%	On track	7 points behind, inside the 10-point band · 39 days left
Design system v2	Linwood Carter	Jan 5, 2026	Mar 27, 2026	10 days late	54 (83%)	3 (5%)	2 (3%)	6 (9%)	65	83%	100%	Overdue	10 days past Mar 27, 11 tasks still open, 2 blocked
Search relevance	Faith Harber	Mar 16, 2026	Jun 30, 2026	85 days left	0 (0%)	4 (10%)	0 (0%)	36 (90%)	40	0%	20%	At risk	20 points behind the schedule line · 85 days left
SOC 2 evidence	Bria Konopelski	Feb 16, 2026	Apr 30, 2026	24 days left	41 (100%)	0 (0%)	0 (0%)	0 (0%)	41	100%	67%	Complete	nothing left open, 24 days before the date
Partner API sandbox	Brett Langosh	not recorded	May 8, 2026	32 days left	9 (35%)	5 (19%)	0 (0%)	12 (46%)	26	35%	no schedule line	No schedule	no start date, so there is no schedule line to judge it against · 32 days left

status="empty" · a valid payload with no projects on it — told apart from "loading" and from "the board service didn't answer".

Project progress

Platform group · Q2 delivery board

No projects on this board yet

Each project becomes one bar split into done, in progress, blocked and not started, with its owner, its due date and a health chip worked out from those counts and the dates around them.

status="loading" · a headline block and four row silhouettes in the ready layout, so nothing jumps when the data lands. aria-hidden, plus an sr-only role=status; the pulse stops under prefers-reduced-motion and no timer is involved.

Project progress

Platform group · Q2 delivery board

status="error" · the fetch failed, and an empty rail would read as "no projects", which is a different fact. "Try again" appears only when onRetry is passed, and pressing it switches this card to ready.

Project progress

Platform group · Q2 delivery board

Couldn't load the board

The project source didn't respond, so nothing here is a picture of the work — an empty rail would read as “no projects”, which is a different fact.

Rounding edges, the reason this component apportions rather than rounds. Fleet telemetry is 1 blocked task in 500: plain rounding floors it to 0% and draws a bar claiming nothing is blocked, so it is lifted to 1% and the row prints 99 / 0 / 1 / 0. Ledger reconciliation is three equal thirds and prints 34 / 33 / 33, not the 33 / 33 / 33 that adds to 99. Quarter close is four exact quarters and needs no leftover at all. Vendor audit has nothing scoped, so its number is an em dash rather than NaN%. The board headline reads 97%, not 99% — three of its four parts are under half a per cent, and keeping each of them visible costs the largest part one point apiece.

Project progress · rounding edges

Four boards chosen to break percentage rounding

97%

of all tasks done

4 projects · 507 tasks · 3 blocked

Fleet telemetry

99%

Blocked

Jeanne Pouros · due Apr 24 · 18 days left

Ledger reconciliation

34%

Blocked

Vera Bergstrom · due Apr 13 · 7 days left

Quarter close checklist

25%

Blocked

Everett Willms · due Apr 20 · 14 days left

Vendor audit

—

Unscoped

Fanny Hyatt · due May 4 · 28 days left

done501 · 97%in progress2 · 1%blocked3 · 1%not started1 · 1%schedule line

Point at a project — or focus the rail and use ↑ and ↓ — to break its bar into counts and shares.

Each bar is one project's tasks, split into done, in progress, blocked and not started; bare track is work nobody has started. The four shares are whole per cents apportioned by largest remainder, so they add to exactly 100 and a segment holding real work never prints 0%. The tick is the schedule line — where a straight run from the start day to the due day says the project should be today. Health is derived from those numbers, never supplied: unscoped when no tasks are counted, complete when nothing is open, overdue past the due day, blocked while any task is blocked, at risk more than 10 points behind the schedule line, on track otherwise, and no schedule when the dates do not describe a window to draw a line in — the row says which date broke. Days are counted between calendar days, so nothing here moves with a time zone or a daylight-saving change. Rows are in the order the board supplied them.

Project progress · rounding edges: Four boards chosen to break percentage rounding. 4 projects, 507 tasks in scope. 97% of all the work is done. Across the whole board that is 97% done, 1% in progress, 1% blocked, 1% not started — whole per cents apportioned by largest remainder, so the four add to exactly 100. Read on Apr 6, 2026. 3 holding blocked work. Next date on the board: Ledger reconciliation on Apr 13, 2026, 7 days left. Rows are in the order the board supplied them. Every project is listed in the table below.

Every project on the board with its owner, its dates, the four counts and their shares, the completion figure, where the schedule line stands today, and the health worked out from them.
Project	Owner	Started	Due	Days left	Done	In progress	Blocked	Not started	Total	Complete	Schedule line	Health	Why
Fleet telemetry	Jeanne Pouros	Jan 5, 2026	Apr 24, 2026	18 days left	499 (99%)	0 (0%)	1 (1%)	0 (0%)	500	99%	83%	Blocked	1 task blocked and not moving · 18 days left
Ledger reconciliation	Vera Bergstrom	Mar 23, 2026	Apr 13, 2026	7 days left	1 (34%)	1 (33%)	1 (33%)	0 (0%)	3	34%	67%	Blocked	1 task blocked and not moving · 7 days left
Quarter close checklist	Everett Willms	Mar 30, 2026	Apr 20, 2026	14 days left	1 (25%)	1 (25%)	1 (25%)	1 (25%)	4	25%	33%	Blocked	1 task blocked and not moving · 14 days left
Vendor audit	Fanny Hyatt	Apr 6, 2026	May 4, 2026	28 days left	0	0	0	0	0	—	0%	Unscoped	no tasks scoped yet

Dates are calendar days, not instants. Read on 7 Mar 2026 with a due date of 9 Mar, this row says "2 days left" and "9 Mar" for every reader on earth — even though the gap spans the night United States clocks jump forward. Subtracting two local-midnight dates across that boundary gives 47 hours and prints "1 day left"; formatting a UTC-midnight date in local time prints "8 Mar" west of Greenwich.

Project progress · across a clock change

Read on 7 Mar; the gap spans the night US clocks jump forward

84%

of all tasks done

1 project · 45 tasks

Payments cutover

84%

On track

Aiden Bruen · due Mar 9 · 2 days left

done38 · 84%in progress4 · 9%blocked0 · 0%not started3 · 7%schedule line

Point at a project — or focus the rail and use ↑ and ↓ — to break its bar into counts and shares.

Each bar is one project's tasks, split into done, in progress, blocked and not started; bare track is work nobody has started. The four shares are whole per cents apportioned by largest remainder, so they add to exactly 100 and a segment holding real work never prints 0%. The tick is the schedule line — where a straight run from the start day to the due day says the project should be today. Health is derived from those numbers, never supplied: unscoped when no tasks are counted, complete when nothing is open, overdue past the due day, blocked while any task is blocked, at risk more than 10 points behind the schedule line, on track otherwise, and no schedule when the dates do not describe a window to draw a line in — the row says which date broke. Days are counted between calendar days, so nothing here moves with a time zone or a daylight-saving change. Rows are in the order the board supplied them.

Project progress · across a clock change: Read on 7 Mar; the gap spans the night US clocks jump forward. 1 project, 45 tasks in scope. 84% of all the work is done. Across the whole board that is 84% done, 9% in progress, 0% blocked, 7% not started — whole per cents apportioned by largest remainder, so the four add to exactly 100. Read on Mar 7, 2026. No project is overdue, blocked or at risk. Next date on the board: Payments cutover on Mar 9, 2026, 2 days left. Rows are in the order the board supplied them. Every project is listed in the table below.

Every project on the board with its owner, its dates, the four counts and their shares, the completion figure, where the schedule line stands today, and the health worked out from them.
Project	Owner	Started	Due	Days left	Done	In progress	Blocked	Not started	Total	Complete	Schedule line	Health	Why
Payments cutover	Aiden Bruen	Feb 16, 2026	Mar 9, 2026	2 days left	38 (84%)	4 (9%)	0 (0%)	3 (7%)	45	84%	90%	On track	6 points behind, inside the 10-point band · 2 days left

Three ways a schedule stops being a schedule, each named on the row instead of swallowed. Legacy import is due 31 February — a string that matches YYYY-MM-DD and is still not a day, so it is refused rather than rolled forward to 3 Mar. Ghost initiative starts and ends on the same day: a zero-width window, which is the divide-by-zero that turns a schedule line into Infinity%. Rescue plan is simply 35 days past 2 Mar, and reports that with 15 tasks still open and 4 of them blocked.

Project progress · unreadable schedules

Dates that do not describe a window

26%

of all tasks done

3 projects · 35 tasks · 4 blocked · 1 overdue

Legacy import

57%

No schedule

Latoya Fritsch · no readable due date

Ghost initiative

20%

No schedule

Luz Walker III · due May 1 · 25 days left

Rescue plan

17%

Overdue

Romaine Huel · due Mar 2 · 35 days late

done9 · 26%in progress3 · 9%blocked4 · 11%not started19 · 54%schedule line

Point at a project — or focus the rail and use ↑ and ↓ — to break its bar into counts and shares.

Each bar is one project's tasks, split into done, in progress, blocked and not started; bare track is work nobody has started. The four shares are whole per cents apportioned by largest remainder, so they add to exactly 100 and a segment holding real work never prints 0%. The tick is the schedule line — where a straight run from the start day to the due day says the project should be today. Health is derived from those numbers, never supplied: unscoped when no tasks are counted, complete when nothing is open, overdue past the due day, blocked while any task is blocked, at risk more than 10 points behind the schedule line, on track otherwise, and no schedule when the dates do not describe a window to draw a line in — the row says which date broke. Days are counted between calendar days, so nothing here moves with a time zone or a daylight-saving change. Rows are in the order the board supplied them.

Project progress · unreadable schedules: Dates that do not describe a window. 3 projects, 35 tasks in scope. 26% of all the work is done. Across the whole board that is 26% done, 9% in progress, 11% blocked, 54% not started — whole per cents apportioned by largest remainder, so the four add to exactly 100. Read on Apr 6, 2026. 1 overdue, 1 holding blocked work. Next date on the board: Rescue plan on Mar 2, 2026, 35 days late. Rows are in the order the board supplied them. Every project is listed in the table below.

Every project on the board with its owner, its dates, the four counts and their shares, the completion figure, where the schedule line stands today, and the health worked out from them.
Project	Owner	Started	Due	Days left	Done	In progress	Blocked	Not started	Total	Complete	Schedule line	Health	Why
Legacy import	Latoya Fritsch	Feb 2, 2026	unreadable	unknown	4 (57%)	1 (14%)	0 (0%)	2 (29%)	7	57%	no schedule line	No schedule	an unreadable due date, so there is no schedule line to judge it against
Ghost initiative	Luz Walker III	May 1, 2026	May 1, 2026	25 days left	2 (20%)	0 (0%)	0 (0%)	8 (80%)	10	20%	no schedule line	No schedule	a start date that is not before the due date, so there is no schedule line to judge it against · 25 days left
Rescue plan	Romaine Huel	Jan 2, 2026	Mar 2, 2026	35 days late	3 (17%)	2 (11%)	4 (22%)	9 (50%)	18	17%	100%	Overdue	35 days past Mar 2, 15 tasks still open, 4 blocked

Every project scoped to zero tasks. There is no whole to take a share of, so there is nothing to divide by: the headline is an em dash, every bar is bare track behind its schedule-line tick, and each chip reads Unscoped rather than pretending the board is 0% complete — a board nobody has broken down yet is not a board that is behind. The tick stays, because the calendar is running whether or not anyone has written the work down.

Project progress · nothing scoped

Kicked off, not yet broken down

—

of all tasks done

3 projects · 0 tasks

Q3 discovery

—

Unscoped

Trevor McClure · due Jul 31 · 116 days left

Partner pilot

—

Unscoped

Lowell Fisher · due Jun 15 · 70 days left

Compliance refresh

—

Unscoped

Lulu Bauch · due May 29 · 53 days left

done0 · 0%in progress0 · 0%blocked0 · 0%not started0 · 0%schedule line

Point at a project — or focus the rail and use ↑ and ↓ — to break its bar into counts and shares.

Each bar is one project's tasks, split into done, in progress, blocked and not started; bare track is work nobody has started. The four shares are whole per cents apportioned by largest remainder, so they add to exactly 100 and a segment holding real work never prints 0%. The tick is the schedule line — where a straight run from the start day to the due day says the project should be today. Health is derived from those numbers, never supplied: unscoped when no tasks are counted, complete when nothing is open, overdue past the due day, blocked while any task is blocked, at risk more than 10 points behind the schedule line, on track otherwise, and no schedule when the dates do not describe a window to draw a line in — the row says which date broke. Days are counted between calendar days, so nothing here moves with a time zone or a daylight-saving change. Rows are in the order the board supplied them.

Project progress · nothing scoped: Kicked off, not yet broken down. 3 projects, 0 tasks in scope. Nothing is scoped anywhere on the board, so there is no completion figure. Read on Apr 6, 2026. No project is overdue, blocked or at risk. Next date on the board: Compliance refresh on May 29, 2026, 53 days left. Rows are in the order the board supplied them. Every project is listed in the table below.

Every project on the board with its owner, its dates, the four counts and their shares, the completion figure, where the schedule line stands today, and the health worked out from them.
Project	Owner	Started	Due	Days left	Complete	Schedule line	Health	Why
Q3 discovery	Trevor McClure	Apr 1, 2026	Jul 31, 2026	116 days left	—	4%	Unscoped	no tasks scoped yet
Partner pilot	Lowell Fisher	Mar 16, 2026	Jun 15, 2026	70 days left	—	23%	Unscoped	no tasks scoped yet
Compliance refresh	Lulu Bauch	Apr 6, 2026	May 29, 2026	53 days left	—	0%	Unscoped	no tasks scoped yet

One project. The board headline and the row's own number are the same 57%, because apportioning 26 / 7 / 2 / 11 for the row and for the board runs the same rule over the same counts. Two blocked tasks, so the chip reads Blocked even though the project is 13 points behind rather than late.

Project progress · one project

A single stream of work

57%

of all tasks done

1 project · 46 tasks · 2 blocked

Checkout rewrite

57%

Blocked

Mr. Alfred Pfannerstill · due Apr 30 · 24 days left

done26 · 57%in progress7 · 15%blocked2 · 4%not started11 · 24%schedule line

Point at a project — or focus the rail and use ↑ and ↓ — to break its bar into counts and shares.

Each bar is one project's tasks, split into done, in progress, blocked and not started; bare track is work nobody has started. The four shares are whole per cents apportioned by largest remainder, so they add to exactly 100 and a segment holding real work never prints 0%. The tick is the schedule line — where a straight run from the start day to the due day says the project should be today. Health is derived from those numbers, never supplied: unscoped when no tasks are counted, complete when nothing is open, overdue past the due day, blocked while any task is blocked, at risk more than 10 points behind the schedule line, on track otherwise, and no schedule when the dates do not describe a window to draw a line in — the row says which date broke. Days are counted between calendar days, so nothing here moves with a time zone or a daylight-saving change. Rows are in the order the board supplied them.

Project progress · one project: A single stream of work. 1 project, 46 tasks in scope. 57% of all the work is done. Across the whole board that is 57% done, 15% in progress, 4% blocked, 24% not started — whole per cents apportioned by largest remainder, so the four add to exactly 100. Read on Apr 6, 2026. 1 holding blocked work. Next date on the board: Checkout rewrite on Apr 30, 2026, 24 days left. Rows are in the order the board supplied them. Every project is listed in the table below.

Every project on the board with its owner, its dates, the four counts and their shares, the completion figure, where the schedule line stands today, and the health worked out from them.
Project	Owner	Started	Due	Days left	Done	In progress	Blocked	Not started	Total	Complete	Schedule line	Health	Why
Checkout rewrite	Mr. Alfred Pfannerstill	Feb 9, 2026	Apr 30, 2026	24 days left	26 (57%)	7 (15%)	2 (4%)	11 (24%)	46	57%	70%	Blocked	2 tasks blocked and not moving · 24 days left

sort="risk" · the same seven projects as the first card, walked worst first: Design system v2 (overdue), Billing rewrite (blocked), Atlas data migration and Search relevance (at risk, nearer date first), Partner API sandbox (no schedule), Mobile onboarding (on track), SOC 2 evidence (complete). Every number is identical — only the order moves.

Project progress

Platform group · Q2 delivery board

58%

of all tasks done

7 projects · 356 tasks · 6 blocked · 1 overdue · 1 complete

Design system v2

83%

Overdue

Linwood Carter · due Mar 27 · 10 days late

Billing rewrite

67%

Blocked

Denise Runte DVM · due Apr 10 · 4 days left

Atlas data migration

62%

At risk

Elizabeth Metz · due Apr 17 · 11 days left

Search relevance

0%

At risk

Faith Harber · due Jun 30 · 85 days left

Partner API sandbox

35%

No schedule

Brett Langosh · due May 8 · 32 days left

Mobile onboarding

40%

On track

Hugo Emard · due May 15 · 39 days left

SOC 2 evidence

100%

Complete

Bria Konopelski · due Apr 30 · 24 days left

done207 · 58%in progress39 · 11%blocked6 · 2%not started104 · 29%schedule line

Point at a project — or focus the rail and use ↑ and ↓ — to break its bar into counts and shares.

Each bar is one project's tasks, split into done, in progress, blocked and not started; bare track is work nobody has started. The four shares are whole per cents apportioned by largest remainder, so they add to exactly 100 and a segment holding real work never prints 0%. The tick is the schedule line — where a straight run from the start day to the due day says the project should be today. Health is derived from those numbers, never supplied: unscoped when no tasks are counted, complete when nothing is open, overdue past the due day, blocked while any task is blocked, at risk more than 10 points behind the schedule line, on track otherwise, and no schedule when the dates do not describe a window to draw a line in — the row says which date broke. Days are counted between calendar days, so nothing here moves with a time zone or a daylight-saving change. Rows run worst first: overdue, blocked, at risk, unscoped, no schedule, on track, complete.

Project progress: Platform group · Q2 delivery board. 7 projects, 356 tasks in scope. 58% of all the work is done. Across the whole board that is 58% done, 11% in progress, 2% blocked, 29% not started — whole per cents apportioned by largest remainder, so the four add to exactly 100. Read on Apr 6, 2026. 1 overdue, 2 holding blocked work, 2 at risk, 1 complete. Next date on the board: Design system v2 on Mar 27, 2026, 10 days late. Rows run worst first: overdue, blocked, at risk, unscoped, no schedule, on track, complete. Every project is listed in the table below.

Every project on the board with its owner, its dates, the four counts and their shares, the completion figure, where the schedule line stands today, and the health worked out from them.
Project	Owner	Started	Due	Days left	Done	In progress	Blocked	Not started	Total	Complete	Schedule line	Health	Why
Design system v2	Linwood Carter	Jan 5, 2026	Mar 27, 2026	10 days late	54 (83%)	3 (5%)	2 (3%)	6 (9%)	65	83%	100%	Overdue	10 days past Mar 27, 11 tasks still open, 2 blocked
Billing rewrite	Denise Runte DVM	Feb 2, 2026	Apr 10, 2026	4 days left	31 (67%)	6 (13%)	4 (9%)	5 (11%)	46	67%	94%	Blocked	4 tasks blocked and not moving · 4 days left
Atlas data migration	Elizabeth Metz	Jan 12, 2026	Apr 17, 2026	11 days left	48 (62%)	12 (15%)	0 (0%)	18 (23%)	78	62%	88%	At risk	26 points behind the schedule line · 11 days left
Search relevance	Faith Harber	Mar 16, 2026	Jun 30, 2026	85 days left	0 (0%)	4 (10%)	0 (0%)	36 (90%)	40	0%	20%	At risk	20 points behind the schedule line · 85 days left
Partner API sandbox	Brett Langosh	not recorded	May 8, 2026	32 days left	9 (35%)	5 (19%)	0 (0%)	12 (46%)	26	35%	no schedule line	No schedule	no start date, so there is no schedule line to judge it against · 32 days left
Mobile onboarding	Hugo Emard	Mar 2, 2026	May 15, 2026	39 days left	24 (40%)	9 (15%)	0 (0%)	27 (45%)	60	40%	47%	On track	7 points behind, inside the 10-point band · 39 days left
SOC 2 evidence	Bria Konopelski	Feb 16, 2026	Apr 30, 2026	24 days left	41 (100%)	0 (0%)	0 (0%)	0 (0%)	41	100%	67%	Complete	nothing left open, 24 days before the date

Fourteen projects with names longer than the row will hold, showSummary off and the footnote dropped: names truncate rather than wrap, because a wrapped name would push its own bar down the card and make the rail reflow under the pointer. All fourteen rows are rendered — nothing is folded away.

Project progress · full portfolio

Fourteen streams, names longer than the row

Robust executive open architecture

58%

Overdue

Hadley Tremblay · due Mar 11 · 26 days late

Innovative reciprocal migration

61%

Overdue

Gloria Koch DDS · due Mar 28 · 9 days late

Customer-focused local utilisation

62%

Blocked

Moses Crooks · due Jun 11 · 66 days left

Customizable neutral archive

62%

On track

Elisabeth Wiegand · due Jun 5 · 60 days left

Customer-focused 24/7 encoding

44%

Blocked

Shelly DuBuque · due May 25 · 49 days left

Upgradable global collaboration

56%

Overdue

Erna Kuphal · due Apr 2 · 4 days late

Quality-focused needs-based knowledge user

32%

Overdue

Hubert Schamberger · due Mar 8 · 29 days late

Monitored content-based generative AI

80%

Blocked

Dr. Christian Shields · due Jun 6 · 61 days left

Total user-facing moderator

45%

Blocked

Dr. Matilda Barton · due Jun 15 · 70 days left

Monitored tertiary knowledge base

54%

Blocked

Hazle Altenwerth · due Jun 16 · 71 days left

Compatible client-driven leverage

59%

Blocked

Blake Mann · due Apr 17 · 11 days left

Stand-alone explicit ability

16%

Overdue

Diana Blanda · due Feb 25 · 40 days late

Grass-roots value-added methodology

84%

Blocked

Henry Prohaska · due Jun 8 · 63 days left

User-friendly local implementation

22%

Blocked

Sheldon Langosh V · due Jun 2 · 57 days left

done510 · 55%in progress83 · 9%blocked34 · 4%not started290 · 32%schedule line

Point at a project — or focus the rail and use ↑ and ↓ — to break its bar into counts and shares.

Project progress · full portfolio: Fourteen streams, names longer than the row. 14 projects, 917 tasks in scope. 55% of all the work is done. Across the whole board that is 55% done, 9% in progress, 4% blocked, 32% not started — whole per cents apportioned by largest remainder, so the four add to exactly 100. Read on Apr 6, 2026. 5 overdue, 13 holding blocked work. Next date on the board: Stand-alone explicit ability on Feb 25, 2026, 40 days late. Rows are in the order the board supplied them. Every project is listed in the table below.

Every project on the board with its owner, its dates, the four counts and their shares, the completion figure, where the schedule line stands today, and the health worked out from them.
Project	Owner	Started	Due	Days left	Done	In progress	Blocked	Not started	Total	Complete	Schedule line	Health	Why
Robust executive open architecture	Hadley Tremblay	Jan 6, 2026	Mar 11, 2026	26 days late	53 (58%)	12 (13%)	4 (4%)	23 (25%)	92	58%	100%	Overdue	26 days past Mar 11, 39 tasks still open, 4 blocked
Innovative reciprocal migration	Gloria Koch DDS	Jan 11, 2026	Mar 28, 2026	9 days late	48 (61%)	1 (1%)	2 (3%)	28 (35%)	79	61%	100%	Overdue	9 days past Mar 28, 31 tasks still open, 2 blocked
Customer-focused local utilisation	Moses Crooks	Jan 31, 2026	Jun 11, 2026	66 days left	38 (62%)	7 (11%)	2 (3%)	15 (24%)	62	62%	50%	Blocked	2 tasks blocked and not moving · 66 days left
Customizable neutral archive	Elisabeth Wiegand	Feb 9, 2026	Jun 5, 2026	60 days left	53 (62%)	7 (8%)	0 (0%)	25 (30%)	85	62%	48%	On track	14 points ahead of the schedule line · 60 days left
Customer-focused 24/7 encoding	Shelly DuBuque	Jan 24, 2026	May 25, 2026	49 days left	14 (44%)	0 (0%)	3 (9%)	15 (47%)	32	44%	60%	Blocked	3 tasks blocked and not moving · 49 days left
Upgradable global collaboration	Erna Kuphal	Jan 11, 2026	Apr 2, 2026	4 days late	57 (56%)	7 (7%)	3 (3%)	34 (34%)	101	56%	100%	Overdue	4 days past Apr 2, 44 tasks still open, 3 blocked
Quality-focused needs-based knowledge user	Hubert Schamberger	Jan 22, 2026	Mar 8, 2026	29 days late	13 (32%)	2 (5%)	4 (10%)	21 (53%)	40	32%	100%	Overdue	29 days past Mar 8, 27 tasks still open, 4 blocked
Monitored content-based generative AI	Dr. Christian Shields	Jan 12, 2026	Jun 6, 2026	61 days left	53 (80%)	10 (15%)	1 (2%)	2 (3%)	66	80%	58%	Blocked	1 task blocked and not moving · 61 days left
Total user-facing moderator	Dr. Matilda Barton	Jan 24, 2026	Jun 15, 2026	70 days left	29 (45%)	6 (9%)	1 (2%)	28 (44%)	64	45%	51%	Blocked	1 task blocked and not moving · 70 days left
Monitored tertiary knowledge base	Hazle Altenwerth	Feb 10, 2026	Jun 16, 2026	71 days left	41 (54%)	8 (10%)	2 (3%)	25 (33%)	76	54%	44%	Blocked	2 tasks blocked and not moving · 71 days left
Compatible client-driven leverage	Blake Mann	Jan 29, 2026	Apr 17, 2026	11 days left	47 (59%)	0 (0%)	3 (4%)	30 (37%)	80	59%	86%	Blocked	3 tasks blocked and not moving · 11 days left
Stand-alone explicit ability	Diana Blanda	Jan 21, 2026	Feb 25, 2026	40 days late	4 (16%)	5 (19%)	4 (15%)	13 (50%)	26	16%	100%	Overdue	40 days past Feb 25, 22 tasks still open, 4 blocked
Grass-roots value-added methodology	Henry Prohaska	Jan 26, 2026	Jun 8, 2026	63 days left	47 (84%)	6 (11%)	3 (5%)	0 (0%)	56	84%	53%	Blocked	3 tasks blocked and not moving · 63 days left
User-friendly local implementation	Sheldon Langosh V	Jan 19, 2026	Jun 2, 2026	57 days left	13 (22%)	12 (21%)	2 (4%)	31 (53%)	58	22%	57%	Blocked	2 tasks blocked and not moving · 57 days left