Business lens demos/biz-01-status-onepager.html Fictional data ← all artifacts
Weekly status · steering committee

Project Lighthouse: week 24

week ending Fri 12 Jun 2026 · billing platform modernisation

ABC Corp is a fictional company. Every name, number and date is invented. This is a reference artifact generated with an LLM coding agent; the brief that produces it is at the bottom of this page.

AMBER Wave-2 migration started two days late and the decommission sign-off has moved by a week. The go-live date is still held.

Milestones

Done 10 Apr Discovery done · 10 Apr Done 2 May Vendor selection done · 2 May Done 29 May Pilot: wave 1 done · 29 May In progress, due 26 Jun Wave-2 migration in progress · due 26 Jun At risk, 17 Jul Decommission sign-off at risk · 17 Jul Planned, 28 Aug Go-live, all regions planned · 28 Aug today
done in progress at risk planned

Budget

€1.94M spent of €4.20M total · plan-to-date €2.10M (marker) · €0.16M under plan

Top 3 risks

SeverityRiskOwnerMitigation
HIGH Duplicate customer records in wave-2 source data could corrupt billing history on migration. S. de Wit Dedupe script run before each batch; manual review of flagged records; batch 3 gated on a clean report.
MED Vendor API rate limits during peak migration windows may stretch the wave-2 schedule. R. Okafor Night-window batching agreed with vendor; throughput test scheduled 16 Jun.
MED Key subject-matter experts on leave through July, so decommission review capacity is thin. A. Kowalczyk Review sessions front-loaded to June; deputy reviewers named for each area.

What changed since last week

  • Wave-1 reconciliation closed with zero open discrepancies.
  • Wave-2 migration started two days late (environment access delays).
  • Decommission sign-off moved from 10 Jul to 17 Jul to fit the legal review cycle.
  • Go-live (28 Aug) unchanged. Buffer reduced from 3 weeks to 2.

Next week's focus

  • Complete wave-2 batches 3 and 4 of 5, with a data-quality gate before each.
  • Submit the decommission plan to the change board.
  • Dry-run the rollback procedure for wave 2 in the staging environment.

Decision needed this week

Approve front-loading decommission reviews into June so the sign-off can hold at 17 Jul. Without sign-off cover, the 2-week go-live buffer is at risk. Owner: A. Kowalczyk · needed by Fri 19 Jun.

Confidence in the 28 Aug go-live: MEDIUM — held on the current plan, but contingent on a clean wave-2 data-quality run and change-board approval first pass.

How this was made: the brief, how to reproduce it, and an honesty note

The brief

Here are my raw status notes for this week: [paste your notes].

Create a complete single-file HTML status one-pager for the project:
overall RAG status with a one-line reason, a milestone timeline showing
done / in progress / at risk, budget spent vs plan as a simple bar,
top 3 risks with owners and mitigations, what changed since last week,
and next week's focus. Use only inline CSS and SVG. No external
libraries, no images. It must print cleanly on one A4 page.

How to reproduce

Paste the brief into any capable LLM: GPT, Claude, Gemini, Grok, DeepSeek, or the assistant your company provides. Iterate a few rounds on layout and content until it reads well. Save the final answer as a .html file and open it in any browser. Expect similar output, not identical: every model has its own taste, and that is fine.

Honesty note

This reference artifact was built with Claude Code, an LLM coding agent, over several iterations. Treat it as the bar to aim for, not as a guaranteed first answer. All data on this page is fictional.

Next artifact Decisions and actions tracker →
vishalshah.app