Recognition & Rewards

Recognition & Rewards defines a lightweight record for celebrating employee excellence. Capture recognition when it happens and attach a category, then use a wall or summary and a monthly review to see what is being valued. A short entry at the event keeps capture manageable. The register retains the recognised employee, giver, message, date, category, points, reward type and visibility. It can describe a public or private recognition process, with the choice established from the business rather than assumed.

The default deliverable is a short recommendation. An explicit setup, build or conversion request produces artifacts after essential missing facts are resolved. Advice receives a direct answer, while a review works from the material provided. This keeps the size of the proposed setup tied to the requested outcome.

Use it when appreciation happens informally but is never recorded, or a kudos board and reward tracker need a shared structure. It does not deliver rewards, make payments or compute leave balances. Recording cash or time off does not authorize or fulfill the reward.

This is an empty-template workflow, not processing of real employee or customer records. Automation, reminders and synchronization require the separate integration layer. Sensitive decisions and adjustments require qualified human review before anything is acted on.

Establish spot versus monthly cadence and who can give recognition; points, gifts, cash or extra time off and the budget; public or private, team or company-wide and named or anonymous visibility; existing capture and audience; and whether a log, wall or reporting is wanted. Questions are asked one at a time, excluding anything already answered in earlier messages. Unknown facts stay unknown. Intent, confirmed facts, open questions and requested formats remain internal unless the user asks to inspect them; no missing answer is invented.

The field model includes Recognition Title (text); Category (select); Date (date); Department (text); Given By (text); Message (text); Month (text); Notes (long_text); Points Awarded (number); Rec-Rwd ID (id); Recognised Employee (text); Reward Type (select); Visibility (text); Year (text).

Category starts with Team, Individual, Department, Company, Values. Reward Type starts with Spot Award, Gift, Voucher, Cash, Time Off, Recognition.

Requested CSV, SQL DDL, JSON Schema and Notion mappings derive from one field list. Display names remain identical across CSV and JSON, and normalized SQL identifiers are documented. Relation fields keep their relational meaning, dates remain dates and money remains currency. Machine-readable data is separated from explanation, with validation failures and limitations reported separately.

One supplied SQL example is:

CREATE TABLE recognition_rewards (
  recognition_title VARCHAR(255),
  category VARCHAR(100) NOT NULL,
  date DATE NOT NULL,
  department VARCHAR(255),
  given_by VARCHAR(255),
  message VARCHAR(255),
  month VARCHAR(255),
  notes TEXT,
  points_awarded NUMERIC NOT NULL,
  rec_rwd_id SERIAL PRIMARY KEY,
  recognised_employee VARCHAR(255),
  reward_type VARCHAR(100) NOT NULL,
  visibility VARCHAR(255),
  year VARCHAR(255),
  created_at TIMESTAMP DEFAULT NOW(),
  updated_at TIMESTAMP DEFAULT NOW()
);

Excel-compatible CSV uses UTF-8 with a byte order mark. Because CSV has no column types, numeric, date and currency formatting is identified after the data. A CSV is not an .xlsx workbook; the latter is generated only when requested. Example rows require an explicit request and must be clearly synthetic. Sensitive identifiers are not unnecessarily repeated in a review, and generated templates remain empty.

Notion output goes to notion-manual-import for the CSV, property mapping, import steps and verification checklist. Manual mappings require no connection. Requested workspace changes require verified tool access, the actual target and authorization; a claimed connection is insufficient evidence. Notion relation columns resolve only after both databases have been imported. Select options are an initial vocabulary that can be renamed to match the business. people-directory supplies the related employee master record; notification-reminder-hub is the separate due-date reminder module. Personal identifiers and sensitive financial details stay out of generated templates.