00
Create Recognition

Recognition that costssomething to give.

hero.subtitle

01
The gesture

One-tap-like-a-post, value-tagged.

Inside Connect, recognition is a first-class action. Type `/recognize @colleague for #integrity` in any thread, or use the wizard. Four fields, structured the same way every time.

  1. 01
    Choose a colleague
    Pick the person whose effort deserves to be seen.
  2. 02
    Select a Company Value
    Tie the recognition to one of your defined Values. The tag is what feeds the live KPI.
  3. 03
    Write a short note
    A personal line that stays in the feed. Optional, but it raises the signal.
  4. 04
    Attach points
    A point value usable in the Rewards Store. Bounded by the cap stack at submit time.
Recognition · new entry
Recognizing
Sara Al-Qahtani
Design · 3-year tenure
Company Value
ExcellenceTeamworkInitiativeIntegrity
Your message

"Sara, your coordination during the Q1 launch was exceptional. You kept the team aligned under pressure."

Points
This week: 250 of 500 remaining in your weekly cap
+250
Draft saved automatically
Ready to send
02
Submit-time fairness

Five-layer cap stack, at write time.

Every recognition is a write into the recognition graph. Wudd applies five fairness checks before the row is persisted. A breach returns `abort(422)` to the caller, the recognition is rejected at the request layer, not reconciled later. Caps are how points stay precious like money.

  1. 01
    Per-giver weekly cap
    A finite weekly recognition budget per sender, so the act of recognizing carries a real opportunity cost.
  2. 02
    Per-receiver monthly cap
    A monthly ceiling on what any one employee can accumulate, so a single favored receiver cannot saturate the signal.
  3. 03
    Per-value monthly cap (overridable)
    A ceiling on how much can be loaded onto a single Company Value in a month, keeps every value alive in the data.
  4. 04
    Per-receiver daily cap on manual recognition
    A daily floor against same-day burst behavior.
  5. 05
    Value-level period caps with per-receiver sub-caps
    Per-Value, per-period limits with sub-caps per receiver so cross-team patterns are detectable in the data.

On top of the five layers, the Gini-coefficient concentration check across Recognition Equity, Culture Momentum, and Team Stability widgets watches for the patterns the per-row caps cannot catch.

03
Why this matters

Precious recognition becomes management data.

A recognition that costs nothing to give produces noise. A recognition that names a Company Value, carries a message, attaches a finite reward, and is rejected at the cap layer when the budget is gone, that produces structured data. The same data the Strategy module reads to advance Key Results, the same data the Promotion Engine pillar review reads, the same data the Recognition Equity widget reads to flag concentration.

Next

Recognition that holds its weight.

Create Recognition is included in every Wudd plan, starting at Silver.