# Messaging and team standards

FICTIONAL WORKSHOP SOURCE. These are invented Halden standards for this exercise. They aren't Enhesa's approved voice or operating policy.

## Positioning and audience

Halden Monitor helps compliance managers see regulatory changes relevant to their sites, with interpretation and references they can examine. For the Reports module, lead with producing a report that can be shared with colleagues. The primary user is a compliance team manager. Analysts help prepare the evidence; site managers and the operations director receive the output. Those roles need different levels of detail.

The positioning should explain the job and the supported capability. Avoid promising that a product purchase removes the need for professional judgement. Customer concerns can guide which benefit to explain, but a concern isn't evidence of product performance. 

## Voice and claims

Write in British English. Use short, concrete sentences and familiar language such as site, change, source, report and review. Say what the product does and state useful limits. Avoid sweeping claims about transformation or effortless work. 

Two expressions are prohibited: real-time updates and guaranteed compliance. The feed updates once every 24 hours, and responsibility for compliance stays with the customer. Avoid equivalent claims such as instant changes or keeps you compliant. Prefer a factual description of the update frequency and the information supplied.

Don't invent performance improvements, customer quotations, prices, release dates or regulatory interpretations. Quotes must match the supplied interview and be labelled fictional. A marketing suggestion isn't an approved product fact, however confidently somebody phrased it in a meeting.

## Evidence and review

For each factual product claim, record the source filename and section in a claims table beneath the draft. Separate facts from interpretations and suggestions. An unknown should be written as not supplied, with a question for its owner. Cite the underlying source even when working from the mini-brain summary.

Product marketing reviews positioning and voice. The product manager checks capabilities and availability. Legal reviews regulatory or legal claims. Marketing operations reviews reporting definitions and calculations. This workshop produces drafts and a proposed review route; it doesn't simulate actual organisational sign-off.

## Learning and reuse

When someone corrects a draft, record the correction and its reason. Propose the relevant context update, let a person review it, then save a dated change-log entry. Keep the original source intact so another person can trace the change. A new customer request belongs in evidence until a product source confirms a capability change.