Issue & Grievance Tracker

Plan a complaint log for conduct issues, internal grievances and workplace problems. The skill starts with a dated complaint, severity and triage owner. It adds a linked disciplinary case only when the process needs one.

The skill separates advice, review, conversion and build requests before producing artifacts. Advice receives a short recommendation and an offer of a relevant build. An explicit build request proceeds once essential missing facts are resolved. It asks one question at a time, reuses answers already supplied and stops when further answers would not change the deliverable. Unknown information remains unknown rather than receiving invented values.

Use it for a grievance tracker, workplace complaint log, code of conduct case or anonymous complaint box. Establish triage, investigation ownership, service-level timing and confidentiality first.

It does not investigate, adjudicate or notify anyone. Privacy, legal and disciplinary cases require a qualified human reviewer before action; the template records the process. The skill does not calculate payroll, tax, leave balances or KPIs. Automation, reminders and synchronization require an integration layer. Legal, tax and HR review is required before templates drive real decisions.

The workflow moves from complaint raised to triage, investigation, action and closure. Its 19 fields cover Issue Title, Issue Type, Raised By, Anonymous, Against (Person or Team), Department, Date Raised, Related Policy, Severity, Description and Assigned To. Investigation Notes, Action Taken, Linked Disciplinary Case, Resolution Date, Days Open, Confidential, Status and Issue ID complete the record. Resolution Date may be absent before resolution or without a verified source and must not be invented. Issue types include Conduct, Harassment, Discrimination, Safety, Pay, Workplace and Other. Severity ranges from Low to Critical; confidentiality from Public to Highly Restricted. Statuses are Logged, Under Review, Investigating, Resolved, Escalated and Closed. Linked Disciplinary Case is the relation field.

Requested artifacts can include CSV, SQL DDL, JSON Schema, Notion property mappings or an Excel workbook. The formats derive from one field list: CSV and JSON retain matching display names, while SQL uses normalized identifiers. Dates retain date types, money retains currency types and cross-table references retain relation types. Select options are a starting set that can be renamed to match the business.

One SQL example is:

CREATE INDEX idx_issue_grievance_tracker_status ON issue_grievance_tracker (status);

Templates are empty by default. Example rows are produced only on request and remain obviously synthetic. Sensitive identifiers should not be repeated unnecessarily during a requested review. Machine-readable data stays separate from explanatory prose and any material validation failures. Excel-compatible CSV uses UTF-8 with a byte order mark and accompanying guidance about number, date and currency columns. An XLSX workbook is a separate requested output rather than a renamed CSV.

The Notion output routes to notion-manual-import for CSV, property mappings, import steps and verification. Manual mappings require no connection. Requested live workspace changes require actual tool access, a verified target and authorization. Imported columns may initially be Text and need their mapped property types applied. Relation links resolve after both relevant databases are imported. A static mapping alone does not establish a completed workspace change.