Skip to main content

Continuous

Last year's decision, reviewed.

A separate case: KYC for Relationship Managers, from last year's decision to a new one.

Start here

The question

What has changed since our last decision?

What this answers

Show the earlier decision, today's evidence, and the new decision, with last year's report unchanged.

Fictional example About these examples

Northgate Bank, its people, and its records are fictional, and nothing here runs in a live account. AI drafts and a person decides: nothing is saved, assigned, published, or executed by AI. Training records show completion and scores; Salalem does not rate anyone's proficiency.

The FY26 cycle is closed

Last year's reason comes first.

The FY26 cycle closed on 2026-06-30. Last year's report kept the Train decision, its reason, and the date.

Needs cycles and closed reports

What Salalem connects

Last year's report kept the decision, its reason, and the date; the program link lives on the need, not in the report.

Northgate Bank

FY26 report | KYC decision

Fictional example

Record date
2026-06-30
Responsible person
Robin
Record status
Saved at cycle close

Earlier decision

Earlier decision
Train
Decided 2026-06-20
Saved reason
We will cover the outstanding KYC requirement through the role program.
As written in FY26
Open the FY26 need

Supporting records

Fictional example

FY26 need

KYC for Relationship Managers

Decided 2026-06-20

Linked program

Relationship Manager Excellence Program

Linked 2026-06-21, before closing on 2026-06-30

The need shows the program Robin linked.

What this answers

Last year's reasoning, as it was

Same people, same requirement

Compare the same 24 people over time.

Of the same 24 Relationship Managers, 12 had met the KYC requirement by 2026-06-15 and 18 by 2026-09-14. New joiners are kept apart.

Needs comparison

What Salalem connects

Both readings use the same people and requirement.

Northgate Bank

KYC | Two readings

Fictional example

Record date
2026-09-14
Responsible person
Robin
Record status
Evidence compared

New review

2026-09-14

Earlier reading
12 of 24 met
2026-06-15
Later reading
18 of 24 met
2026-09-14
New Relationship Managers
4 people
Joined after 2026-06-15 | Not compared
Check the comparison

Supporting records

Fictional example

Compared group

24 Relationship Managers

Both readings

Existing program

Relationship Manager Excellence Program

Checked 2026-09-14 | Still covers KYC

These numbers show completion progress. They do not show that the program caused it, or a return on investment.

What this answers

A fair comparison

Robin keeps the program

Already covered, with the program linked.

Robin records Already covered and links the existing program to the FY27 need. The team follows up with the 6 people still outstanding.

Needs cycles and decisions

What Salalem connects

Recording a decision and linking a program are separate steps.

Northgate Bank

FY27 decision | FY26 report

Fictional example

Record date
2026-09-15
Responsible person
Robin
Record status
Decision recorded

New review

New decision
Already covered
2026-09-15
Reason
Keep the program; follow up with the 6 outstanding.
No new content
Program link
Relationship Manager Excellence Program
Linked 2026-09-15
FY26 report
Unchanged
Reopened after the decision
Reopen the FY26 report

Supporting records

Fictional example

Earlier decision

Train

Decided 2026-06-20

Saved reason

We will cover the outstanding KYC requirement through the role program.

As written in FY26

The FY26 decision and date read as before.

What this answers

A new decision; last year's report intact

A complete answer

The new decision keeps its history.

Bring one earlier decision and newer evidence.

Book a demo

Related scope

What changes

The work becomes a regular review.

What has changed since our last decision?

All maturity scenarios

The L&D maturity story