--- current-handbook.md +++ outputs/proposed-handbook.md @@ -2,12 +2,20 @@ Document ID: HB-REPORTS -Version: 1.4 -Source status: approved baseline in this fictional packet -Effective date: 2026-10-05 +Status: draft_pending_owner_review +base_version: 1.4 +Source status (baseline only): approved baseline in this fictional packet +Source effective date (baseline only): 2026-10-05 Document owner: owner-d01 -Snapshot: 2026-10-09T10:55:00+01:00 +Source snapshot (baseline only): 2026-10-09T10:55:00+01:00 +Human review: not performed +New approval date: none +New published version: none +New publication date: none +External application: not performed Audience: client-service employees with access to the relevant client workspace + +> Local proposal based on HB-REPORTS v1.4. The baseline remains the operational reference; this draft has not been reviewed, approved or published. Unchanged sections below retain baseline wording, including section 5's reference to the approved page. The proposed subsection requires owner review. ## 1. Purpose @@ -24,6 +32,15 @@ Do not send the report to the client until the assigned account owner has recorded written approval in the client workspace. A lack of reply is not approval. + +### 3.1 Submit a draft for approval — proposed + +1. Add the draft report to the client workspace. +2. Tag the assigned account owner there. +3. Wait for that owner's written approval in the client workspace before sending the report to the client. A lack of reply is not approval. + +Draft evidence: onboarding-qa.md, ONB-20261009-01, T02–T05 (N02/M01, elapsed 00:18–01:10), compared with current-handbook.md, HB-REPORTS v1.4, HB-REPORTS:approval-gate. Steps 1–2 are proposed from T03 and T05; step 3 restates the approved gate and is consistent with T03. No workspace URL, software-specific button or response time is specified in the supplied discussion (T05). + ## 4. Keep the review record