KPI Gamification

A health check of how the user's company is using KPI Gamification: an overall adoption score, what is on track, what can improve, and what has not been started, with a suggested next step for each. It is a summary of counts and statuses only: it contains no team member names, scores, salaries or personal data. Every call reads the latest data, so run it again after the user has changed something. Use it when the user asks how their company is doing, what to set up next, or for an adoption or audit review.

audit_company

List the company's active gamecards (the KPI scorecards for each role): id, name, category, number of KPIs, whether an HR Kit already exists, and a link. Read-only. kpi_count counts every KPI on the card, including Attendance, Timing and Reports. Rows are sorted by name; created_at tells apart cards with the same name (use the most recent one unless the user says otherwise). Use it to find a gamecard id (needed by the HR Kit and SOP tools) or when the user asks what gamecards they have.

list_gamecards

Use this whenever the user asks to create or design a gamecard or KPI scorecard for a role. Check the design BEFORE saving it. Nothing is saved and it is free. Returns valid:true with a preview_id and a summary, or valid:false with errors (each has a path and a fix). The server never invents scoring details, so the caller must supply real slabs, checklist tasks, audit questions or productivity tasks. Rules: weightages total exactly 100; Attendance, Timing and Reports are categories (not KPI types), normally 10 points each; every other KPI is category "Core KPIs" with a kpi_type. MANDATORY on every card (the server rejects a card without them): Attendance, Timing and Reports (5 or 10 points each), an internal Management Audit (Audit-Feedback, type internal, 5 to 10 questions), a Checklist (5 to 15 specific tasks) and a To-Do List. Roles that serve outside customers also get an external feedback KPI (5 to 10 questions). The result can also carry "suggestions" and "warnings": the server's design advice for the card. Machine operators and other manufacturing roles use Productivity with productivity_type "cycle_time" (10 to 30 steps in seconds) named "... Cycle Time" instead of a Goal KPI for output. Desk roles use Productivity in minutes (10 to 30 tasks). Conversion uses two slabs, 80% and 70%. Goal Pro-Rata uses mqr_threshold 70. KPI and task names are plain ("Ticket Resolution", not "per ticket") and the word "Employee" is rejected in favour of "Team Member". The summary lists the KPIs in display order (Attendance, Timing, the other KPIs, Reports last) and gives each KPI a "type" label. The preview_id is what commit_gamecard saves.

preview_gamecard

Preview an HR Kit for one gamecard: job description, roles and responsibilities, skill matrix, assessment questions and standard practices. The server generates all of it from the gamecard with KPI Gamification's own generator, so you only choose the gamecard and optionally the role details and pay ranges. Nothing is saved. Returns valid:true with a preview_id and a summary, or valid:false with errors to fix. One kit per gamecard: if one exists you get a link to it instead. The preview_id is what commit_hr_kit saves.

preview_hr_kit

Check an HR policy before saving it as a DRAFT. You supply the company's policy choices (working days, leave rules, timing, salary deductions, probation and notice period, benefits); every value must be one of the listed options and the server tells you exactly what to fix. Nothing is saved. Leave allowance, weekly offs, holidays, permission hours and the per-day salary method are taken from the company's live settings when the PDF is made, so they are not accepted here. Only values the user chose should be supplied; the server does not fill in defaults. The preview_id is what commit_hr_policy saves.

preview_hr_policy

Preview a Standard Operating Procedure (SOP) built from the company's gamecards and HR Kits: purpose, scope, roles involved, process steps, escalation matrix, tools and annexures. Generated by the server; you choose the category, a title and which roles (gamecard_ids) it covers. Nothing is saved. Use category 'company-wide' for the Team Member handbook (leave gamecard_ids empty to cover every role); any other category needs at least one gamecard. Limitation: the process steps come from the app's standard template for the chosen category, not from the title, so this tool cannot write machine, safety, medical, chemical, construction or other technical procedures. The preview_id is what commit_sop saves.

preview_sop

Save the previewed HR Kit as a draft in the company (it keeps its HRK-year-number serial). It saves exactly what the preview showed. Call it only once the user has confirmed the preview. No PDF is generated: the user opens the link to review, edit and generate the PDF in KPI Gamification.

commit_hr_kit

Save the previewed HR policy as a DRAFT. It saves exactly what the preview showed, never overwrites an existing policy, and never publishes. Call it only once the user has confirmed the preview. The user opens the link to review, adjust and publish it in the HR Policy Studio (publishing generates the PDF).

commit_hr_policy

Save the previewed SOP as a draft in the company (it keeps its SOP-year-number serial). It saves exactly what the preview showed. Call it only once the user has confirmed the preview. No PDF is generated: the user opens the link to review, edit and generate the PDF.

commit_sop

Save a previewed gamecard to the user's company. It saves exactly what the preview showed; a changed design needs a new preview. Call it only once the user has confirmed the preview. Returns links to open the gamecard in KPI Gamification. The gamecard is saved as a template and is not assigned to anyone; assigning it is done in the app.

commit_gamecard