Back

Feedback / correction / suggestion

Feedback is evidence when it is specific and traceable

A useful feedback path should preserve what was observed, where, when, why it matters, the supporting evidence, uncertainty, risk and suggested correction. REC-INT-014 provides a manual record, but this site does not currently collect it.

Correction feedback

Quote or identify the page/claim, state what appears wrong or outdated, attach/source the evidence, and suggest the smallest correction. Do not replace one unsupported claim with another.

Usability / accessibility feedback

Describe the device/context, task you were trying to complete, what blocked or confused you, and the observable result. Avoid assuming why the system behaved that way without evidence.

Suggestion / idea

Separate idea from requirement. State the problem, proposed change, intended user/value, risks, evidence or examples, and what would need to be tested. A suggestion does not become roadmap commitment merely because it is recorded.

Privacy before sharing

Remove credentials, secrets, private contact details, sensitive personal stories and unrelated third-party data from shared feedback. Use the minimum information needed to demonstrate the issue.

No receiver is promised here

The manual worksheet helps prepare a high-quality record. It is not a submission form, ticket system, complaint channel or guarantee that meUus will receive or respond to the note.

Reflection

Questions to sit with

  1. What did I observe rather than infer?
  2. What evidence would help another person reproduce or verify it?
  3. What is the smallest responsible correction?

One safe next action

Use the Feedback / Suggestion Record and keep it private until an authorized receiving path exists.