From 00c7ec2533e1439e086c0772785b86bd9ce0e80d Mon Sep 17 00:00:00 2001 From: Adedayo Okunade <136774858+okunadea@users.noreply.github.com> Date: Mon, 14 Sep 2026 12:51:57 +0100 Subject: [PATCH 1/2] Update SCAL.page.md NBRS-4886 Remove 2-4 week SCAL timeframe --- guides/Training-guide-BARS/Home/Assure/Assure/SCAL.page.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/guides/Training-guide-BARS/Home/Assure/Assure/SCAL.page.md b/guides/Training-guide-BARS/Home/Assure/Assure/SCAL.page.md index 40a44623..66e2267e 100644 --- a/guides/Training-guide-BARS/Home/Assure/Assure/SCAL.page.md +++ b/guides/Training-guide-BARS/Home/Assure/Assure/SCAL.page.md @@ -14,7 +14,7 @@ Request for an **Account Manager** to be set up by sending an email to the BaRS When planning a project to build a BaRS solution, the inclusion of assurance must exist from the outset. -The process of being assured via the SCAL can take between 2-4 weeks (average), from the point of the first complete submission. This allows some time in any plan for resubmissions after review by the Solution Assurance team. +The process of being assured via the SCAL can vary depending on the completeness and quality of the first submission, requests for further information, and any required resumbmissions review by the Solution Assurance team. Sufficient time should therefore be included in any project plan for the assurance process. It is advised the SCAL requirements are reviewed after reading the implementation guidance. The two combined will help build a backlog of requirements for the anticipated solution. For example, there is implementation guidance for {{pagelink:core-EHFailureScenarios-1.1.3, text:error handling}} while the SCAL highlights the expectation for logging and auditing of errors. From f52fb3592bd20c4387e2baef8b171a554e0179d6 Mon Sep 17 00:00:00 2001 From: Adedayo Okunade <136774858+okunadea@users.noreply.github.com> Date: Mon, 14 Sep 2026 13:15:25 +0100 Subject: [PATCH 2/2] Update SCAL.page.md NBRS-4886 Correct assurance guidance wording --- guides/Training-guide-BARS/Home/Assure/Assure/SCAL.page.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/guides/Training-guide-BARS/Home/Assure/Assure/SCAL.page.md b/guides/Training-guide-BARS/Home/Assure/Assure/SCAL.page.md index 66e2267e..5aeb97a1 100644 --- a/guides/Training-guide-BARS/Home/Assure/Assure/SCAL.page.md +++ b/guides/Training-guide-BARS/Home/Assure/Assure/SCAL.page.md @@ -14,7 +14,7 @@ Request for an **Account Manager** to be set up by sending an email to the BaRS When planning a project to build a BaRS solution, the inclusion of assurance must exist from the outset. -The process of being assured via the SCAL can vary depending on the completeness and quality of the first submission, requests for further information, and any required resumbmissions review by the Solution Assurance team. Sufficient time should therefore be included in any project plan for the assurance process. +The process of being assured via the SCAL can vary depending on the completeness and quality of the first submission, requests for further information, and any required resumbmissions after review by the Solution Assurance team. Sufficient time should therefore be included in any project plan for the assurance process. It is advised the SCAL requirements are reviewed after reading the implementation guidance. The two combined will help build a backlog of requirements for the anticipated solution. For example, there is implementation guidance for {{pagelink:core-EHFailureScenarios-1.1.3, text:error handling}} while the SCAL highlights the expectation for logging and auditing of errors.