Everything that can move the date.
Risks, assumptions, issues, dependencies. One list, every line with a name and a day.
One migration, logged
The log on Monday 1 Feb. The risks came out of the pre-mortem at kickoff, 13 Jan.
Risks
Might happen, with the date that settles it.
-
R1
Ledgerline’s saved-card export arrives late, so 41,000 customers re-enter their cards.
- Odds / hit
- Medium / high
- Trigger
- No test export by Sat 6 Feb
- Owner
- Dana
- Status
- Watching.
-
R2
The Ledgerline contract auto-renews for a year because notice goes out late.
- Odds / hit
- Medium / high
- Trigger
- Signed notice not sent by Sat 30 Jan
- Owner
- Marco
- Status
- Triggered 30 Jan. Now I1.
-
R3
The rollback rehearsal fails, so we cut over with no way back.
- Odds / hit
- Low / high
- Trigger
- Rehearsal not clean by Sat 20 Feb
- Owner
- Priya
- Status
- Watching.
Assumptions
Believed, not checked, with the day you check.
-
A1
Notice must reach Ledgerline four weeks before the 1 Mar renewal: by Mon 1 Feb.
- Check by
- 20 Jan, clause 14
- Owner
- Marco
- Status
- Checked 19 Jan: true. Closed.
-
A2
We can refund pre-cutover payments through Ledgerline for 120 days after.
- Check by
- 10 Feb, in writing from Ledgerline
- Owner
- Marco
- Status
- Not checked yet.
-
A3
Our fraud rules port to Northpay unchanged.
- Check by
- 17 Feb, replay January in their sandbox
- Owner
- Jonas
- Status
- Not checked yet.
Issues
Happening now, with a decision and a deadline.
-
I1
Renewal notice unsigned; the CFO is away until 3 Feb. Was R2 until 30 Jan.
- Resolve by
- Mon 1 Feb, 17:00
- Owner
- Marco
- Decision
- Deputy CFO signs today
- Status
- Escalated Sat 30 Jan.
-
I2
3% of Northpay webhooks fail signature checks in staging.
- Resolve by
- 5 Feb
- Owner
- Jonas
- Status
- Clock skew suspected. Fix in review.
Dependencies
Owed by someone else, by name and date.
-
D1
Firewall rule letting the card vault reach Northpay.
- Owed by
- Sam Okafor, platform team
- Due
- 12 Feb
- Chased by
- Priya
- Status
- Ticket PLAT-412 accepted 27 Jan.
-
D2
Production keys and merchant ID.
- Owed by
- Elena Ruiz, Northpay onboarding
- Due
- 15 Feb
- Chased by
- Jonas
- Status
- On track.
The day R2 became I1
The trigger date passed with the notice unsigned. Marco closed the risk and opened an issue.
R2. The notice might go out late.
Settles on 30 Jan. Until then, Marco watches.
I1. The notice is unsigned.
Hard deadline Mon 1 Feb. It is also why Monday’s status goes red.
Believed, or owed?
Refunds keep working on Ledgerline.
Nobody promised it; Marco believes it. It needs a check date: 10 Feb.
The firewall rule.
Sam promised it. It needs his name, not “platform”, and his date: 12 Feb.
Can you find out yourself? Assumption. Must you wait for someone? Dependency.
One row
Same fields for all four letters.
- ID
- R, A, I or D, plus a number
- What
- [one sentence; a risk says what might happen]
- Owner
- [one person on your side]
- Date
- [trigger, check by, resolve by, or due]
- Odds / hit
- [low, medium, high], risks only
- Owed by
- [their name, their team], dependencies only
- Status
- [what happened last, with its date]
Read it every Monday. Any date behind you means the row changes: closed, or a new letter.
A row without a name and a date is not a log entry. It is a worry with a number.