T77 Fortnightly stream status update
Fortnightly stream status update
Where each of the four order-to-cash streams stands after the status window that closed on Wednesday, September 30, 2026, reported against one fixed structure: status, what moved, what is blocked, the next milestone and the decisions needed. A status that has not changed for two cycles is questioned, not accepted. Compiled by Tom Becker, PMO lead at Corbel Partners, for Robert Lang, chief operating officer at Thornbury Components, and Claire Dubois, engagement partner. Each stream lead submitted their own update. The next window closes Wednesday, October 14.
Sample template: the firm, people, clients and figures are fictional, and the embedded view holds synthetic sample records.
Stream status at a glance
| Stream | Status | Since the Sep 16 window | Next milestone | Update |
|---|---|---|---|---|
| Order entry and cutover | Order entry redesign v1.2 returned with changes: plant three test results came from an older build | Plant two cutover readiness, Oct 8 | In on time, complete | |
| Invoicing and credit | Credit limit policy decision at 23 days; two tax codes mapped to the wrong plant ledger | Invoicing design, Oct 16 | In on time, complete | |
| Collections | No change: the same status as Sep 16 | Collections workflow design, Oct 22 | Submitted, unchanged for two cycles | |
| Data and master data | Duplicate customer accounts down to 410 from 1,260 on Aug 15 | Customer master data cleanse, Oct 14 | In on time, complete |
Live example from the Dashboards app, shown with Thornbury Components' demo data. Block dates move forward each week, so they can differ from the sample dates on this page.
Collections has reported the same status for two cycles
The Collections update on Sep 30 repeats the Sep 16 update: dunning steps defined, draft call scripts written, dispute handoff to billing not reviewed. An unchanged status can mean the stream has stalled, not that nothing changed. Tom Becker asked the collections lead on Oct 1 to name the blocking item and has flagged the stream for the October steering pack. No answer has come back yet. Consequence: Collections workflow design (2 of 4 criteria, due Oct 22) cannot be accepted on time if the billing review has not started by Oct 14.
How the status colours are set
Green. On plan, with no blocked milestone and no decision older than 14 days.
Amber. A milestone is late or at risk and the stream has a plan and an owner for it.
Red. A milestone is blocked and the person who can unblock it has not yet acted.
The stream lead proposes the colour; the PMO lead questions it when the evidence in the update does not support it.
Streams in detail
What moved. Order entry redesign v1.2 went to Robert Lang on Sep 26 with four of five criteria evidenced. Claire Dubois held criterion 4 because the plant three test results came from an older build.
What is blocked. Plant two has not reported trained super users, so Plant two cutover readiness stands at 2 of 4 criteria. The report is needed before the cutover decision at steering on Oct 22. Plant three super user training starts only once the plant three cutover date is set.
Question from the PMO. Which plant two super users have finished training, and on what date? Awaiting the plant two manager.
Next. Plant three results from the current build as v1.3 by Oct 8. Owner: Tom Becker.
What moved. The invoice layout was approved on Sep 22, so Invoicing design stands at 1 of 4 criteria. Robert Lang named the finance director as owner of the credit limit decision on Sep 29, with a decision date of Oct 13.
What is blocked. Invoicing design waits on the credit limit policy decision, which has been open 23 days because finance and plant operations each assumed the other would own it. Tax code lookup configuration was sent back: two plant three orders returned the wrong code and finance withheld sign-off. Two tax codes sit on the wrong plant ledger, and Corbel owes the corrected mapping on Oct 5.
Why red. The unblocking decision has an owner now, but nothing is recorded yet.
Next. Decision recorded by Oct 13, three days before the Invoicing design due date on Oct 16.
What was reported. Dunning step table and draft call scripts are done. The dispute handoff to billing has not been reviewed with billing. Collections workflow design stands at 2 of 4 criteria at v0.6, due Oct 22. The text matches the Sep 16 update.
Question from the PMO. What is the blocking item, and who needs to act on it? Asked by Tom Becker on Oct 1, no answer yet.
Reading. The stream may be waiting on billing, or may have stalled. The evidence does not yet say which, so the status stays Amber rather than Green.
Next. Re-check at the Oct 14 window.
What moved. Duplicate customer accounts fell from 1,260 on Aug 15 to 410 on Sep 28, through merges at plants one and two. Data migration rehearsal was accepted on Sep 22 and Chart of accounts mapping on Sep 15.
Watch item. Plant three credit staff are still reviewing the duplicate list issued on Sep 24, so Customer master data cleanse stands at 2 of 4 criteria with a due date of Oct 14. Plant three data load rehearsal cannot start until the cleanse is accepted.
Why green. The cleanse is on its plan and the review has a named owner. It would turn Amber if the plant three list is not back by Oct 9.
Decisions waiting
Nine decisions are open. Each one shows the milestone it blocks and how long it has waited as of October 1.
| Decision | Owner | Raised | Age | Blocks | Needed by |
|---|---|---|---|---|---|
| Credit limit policy | Thornbury finance director | Sep 8 | 23 days | Invoicing design | Oct 13 |
| Plant three cutover date | Robert Lang | Sep 16 | 15 days | Plant three super user training | Steering, Oct 22 |
| Plant two cutover go or no-go | Robert Lang | Sep 22 | 9 days | Plant two cutover readiness | Steering, Oct 22 |
| Dispute handoff from collections to billing | Collections lead with the billing lead | Sep 16 | 15 days | Collections workflow design | Oct 14 |
| Finance sign-off on the corrected tax code table | Finance controller | Sep 28 | 3 days | Tax code lookup configuration | Oct 9 |
| Whether the August close counts for criterion 3 | Robert Lang | Sep 22 | 9 days | Month-end close procedure | Oct 14 |
| Plant three duplicate list: which accounts to merge | Plant three credit staff | Sep 24 | 7 days | Customer master data cleanse | Oct 9 |
| Whether plants one and two evidence satisfies criterion 3 | Robert Lang | Sep 30 | 1 day | Order entry redesign | Oct 8 |
| Owner of the training materials after handover | Thornbury plant operations lead | Sep 25 | 6 days | Training materials library | Oct 3 |
Live example from the Dashboards app, shown with Thornbury Components' demo data.
Milestones to the end of the October steering cycle
Bars run from the start of work to the due date in the milestone tracker. Red bars are blocked or overdue. The marker is the October steering meeting on Thursday, October 22, where the plant two and plant three cutover decisions are taken.
%%{init: {"gantt": {"useWidth": 920}}}%%
gantt
title Thornbury milestones, Sep 7 to Nov 13, 2026
dateFormat YYYY-MM-DD
axisFormat %b %d
section Order entry and cutover
Order entry redesign resubmission :crit, oe, 2026-09-28, 2026-10-08
Plant two cutover readiness :active, p2, 2026-09-14, 2026-10-08
Plant three super user training :p3, 2026-10-26, 2026-11-06
section Invoicing and credit
Credit limit decision :crit, cl, 2026-09-08, 2026-10-13
Tax code mapping fix :crit, tc, 2026-09-28, 2026-10-05
Invoicing design :active, inv, 2026-09-14, 2026-10-16
section Collections
Collections workflow design :active, col, 2026-09-07, 2026-10-22
section Data and master data
Customer master data cleanse :active, dm, 2026-09-07, 2026-10-14
Plant three data load rehearsal :dl, 2026-10-26, 2026-11-13
section Steering
October steering meeting :milestone, st, 2026-10-22, 0d
Milestones blocked or disputed
The view lists every milestone that is blocked by a requested change or a dispute, across Corbel's programs. Thornbury has three rows on it: Order entry redesign and Tax code lookup configuration with changes requested, and Month-end close procedure disputed.
Before you share this page with a client
This sample view holds milestones for several clients, including Northwick Insurance Group and Brennan & Shaw Distributors. Switch the embed to a view filtered to Thornbury Components before you send this page to Robert Lang or anyone at Thornbury.
Before the Oct 14 window closes
How to use this template
Compile one update per fortnightly window from each stream lead's own submission. Question any gap, and flag a stream whose status is unchanged for two cycles.
| Variable | Meaning | Required |
|---|---|---|
{{program.name}} | Program the update covers | Required |
{{window.close_date}} | Date the status window closed | Required |
{{stream.status_rows}} | Each stream with status, movement, next milestone and update state | Required |
{{stream.stale_list}} | Streams whose status is unchanged for two cycles | Required |
{{decision.open_rows}} | Open decisions with owner, raised date, age and the milestone blocked | Required |
{{milestone.dates}} | Milestone start and due dates for the timeline | Required |
{{window.next_date}} | Date the next status window closes | Optional |
If a required value is missing, show Needs review in its place and hold the update; never fill it with a guess. If a stream has not submitted, show Unavailable for that stream and do not carry forward its last status.
The live Dashboards blocks on this page show the Thornbury Components demo profile. Point each block at your own client's profile, or remove it, before you share the page. Filter the embedded view to the same client as well.