The Recommendation Framework is HEPO's software for generating and managing proposed responses to cultural readings. It connects signals, conditions, templates, and scopes to a recommendation that a responsible person can inspect, acknowledge, act on, or dismiss.

The proposals come from the organization's configured rules and the platform's readings. Consultants can help design those rules; the running framework generates the instances. Each instance retains the basis on which it surfaced and the history of the response.

What happens after a reading needs attention?

Consider the team reviewing reliable handoffs. The reading has declined across the agreed period. A configured rule can recognize the relevant condition and create a proposal to review the practice or organize development.

The owner examines the rule, its scope, and the supporting evidence. A changed workload or an unsuitable threshold may call for further investigation. If development is appropriate, the owner can choose a response and connect it to a programme. The recommendation does not make that decision on their behalf.

That gives the organization a record of more than an alert: what was proposed, why, who responded, what they chose, and what happened afterwards.

How the proposal is generated

Signal definitions cover culture-index values and movement, containment-related conditions, campaign participation and milestones, and flourishing measures. The available signal and its configuration must fit the question being asked.

The starting rule examples include cross-trait divergence, a reversal persisting across periods, and a paired condition involving a falling trait reading and accelerating decay. These are examples of configurable conditions. A rule firing means its condition was met; the meaning of that condition still needs examination.

Inspect why it appeared

The rule view exposes the expression and the associated template, scope, delivery profile, priority, and validity. A recipient should be able to follow the proposal back through the reading to relevant evidence, within the permissions of their role.

Recommendation types provide a vocabulary for different responses: guidance, warning, encouragement, correction, learning, mentorship, policy, and escalation. Urgency and validity help distinguish what needs timely attention from what has become stale.

Delivery profiles describe in-app, email, push, and digest channels, with frequency, limits, and cooldowns. These are configuration choices for implementation; the existence of a channel option does not mean every deployment has connected it.

Keep the decision and its history visible

An instance can move from pending to acknowledged, in progress, and completed. It may instead be dismissed with a reason or expire when its validity ends.

Dismissal is a useful outcome when the recipient has context the triggering rule did not capture. Recording that reason helps the organization review whether the scope, condition, or proposed response should change. Acknowledging a recommendation is not the same as approving a programme or completing the proposed work.

People decisions remain human decisions. A recommendation can inform a development choice without becoming an automatic promotion decision, disciplinary action, or judgment of personal worth. The trust boundary →

Review what followed

The impact record can hold the earlier score, the later score, their difference, and an indication of detected behavior change. Together with the response history, this lets an owner examine whether the expected pattern moved after action.

The comparison is evidence for review, not proof that the recommendation caused the change. Other events, changing evidence coverage, and the timing of the review can matter. An unchanged reading is also useful: it may prompt the organization to examine the response, its implementation, or the rule that proposed it.

This information contributes to the wider Flourish & Wellbeing review and the next cycle of evaluation. Retuning remains governed work, rather than an assumption that the software automatically knows the right intervention.

Configure the response with the people responsible

The organization owns the rulebook, recipients, and decision responsibilities. Consultants help review starting templates and shape conditions that fit the operation. Implementers connect signals and configure delivery, validity, and access. The delivery partner supports the cycle from initial configuration through review of completed responses.

When the chosen response calls for structured development, Achievement Campaigns & Programmes give it milestones, participation, and progress. Other recommendation types can lead to other responsible actions; every proposal need not become a campaign.

Next: Achievement Campaigns & Programmes → · Return to the Culture Index →

Tell us what should happen when a reading needs attention.