HCDI Lead Indexer

Chapter 11. From finding to action

HCDI platform rule (Unit 3.9); general professional knowledge. Submission drafts an English action for every score from 1 to 4, and records unevidenced indicators not evidenced. The Arabic is drafted only as a translation once the English is approved. Changing a score during review returns the assessment to draft. Each action carries a materiality (unless a rule set it), a response type, a timing, an accountable function and logged reasoning. The engagement team cannot approve an action. Approval is HCDI's. An expected outcome is what an action is hoped to achieve. It is not evidence that a gap has closed. Closure needs evidence of its own, and the Tracker records what the client says happened. Common Error. Treating a well-written action as if it were progress.

An action describes intended change#

Basis - general professional knowledge and editorial explanation. External references are identified explicitly; this section adds no HCDI rule.

A finding concerns evidence; an action concerns a future response. Expected benefits are hypotheses until supported by implementation and outcome evidence. The supplied public workflow is retained, but protected action classification and Context Engine mechanics are not reconstructed. A clear sentence cannot replace source-required approval.

Figure 3.11 An action describes intended change. Original conceptual illustration; arrows organise the discussion and do not establish a validated causal effect or a scoring procedure.

Original exercise L3 E11#

Basis - original fictional exercise. The organisation, events and any numbers are invented for learning. No HCDI result is assigned.

A management plan promises better delegation after a workshop. The client calls the issue verified closed when invitations are sent.

Question - Which stages have been conflated?

Worked answer: Part G, exercise L3 E11.