Feedback
One report about a system, kept as it arrived, routed to the system's base by its key.
One Feedback row is one submission about one system: a bug, an improvement, a suggestion or a question, typed ops:Feedback. It is kept whole as it arrived, before and after triage. Systems Central is its System of Record. The system’s own base shows a synced copy filtered by System Key, so reporters write from where they work and the team triages here.
What a row is
On 2026-10-28 the table has 16 rows. 14 have System Key Operations and link KPIs & OKRs. They were moved here on 2026-09-17 from the legacy Operations base, which is not one of our systems, and their page names refer to that base. One has System Key CRM and no System link, so its Key Check shows ⚠ no system linked. One row is almost empty: no name, key or system. Lifecycle Status: 11 Completed, 3 On Hold, 2 Proposed.
Fields
What was reported (keep as received)
| Field | Type | Meaning |
|---|---|---|
| Name | Text, primary | Title the reporter gave; rename only to fix a typo |
| System Key | Single select | Routing key: one option per System Sync Key |
| Interface | Text | Page or screen where the reporter saw it |
| Category | Single select | Bug, Improvement, Suggestion, Question |
| Description | Long text | The original text; never add to it |
| Evidence | Attachments | Files as received |
| Evidence (File Link) | URL | A link to evidence; the column has no description yet |
| Source Root Cause | Long text | The cause the reporter gave, before investigation |
| Notify Reporter | Checkbox | The reporter asked to hear back |
| Reporter (Membership) | Link → Membership (mirror) | Who reported it |
| Created By | Created by | The account that typed the row |
Triage and answer
| Field | Type | Meaning |
|---|---|---|
| System | Link → System | The system it is about; must match System Key |
| Accountable | Link → Membership (mirror) | Who answers for resolving it; usually the system’s Maintainer |
| Lifecycle Status | Single select | Draft, Proposed, Active, On Hold, Completed, Cancelled, Archived |
| Priority | Single select | Urgent, High, Medium, Low |
| Due Date | Date | Response deadline promised to the reporter |
| Triage | Long text | Triage answers, one name = value per line |
| Resolution Plan | Long text | Action, owner and date |
| Solution Kind | Multiple select | Interface Change, Table Change, Automation Change, Airtable Limitation |
| Estimated Effort | Duration | Estimate made at triage |
| Resolved Date | Date | Day the change went live or the answer was sent |
| Response | Long text | The answer the reporter reads; crosses the sync |
| Reporter Follow-up | Long text | What the reporter added later; crosses the sync |
| Tags | Links → Tags (mirror) | Optional labels |
Record comments stay in the base where they were written. Response and Reporter Follow-up are the only replies that cross the sync.
Computed
| Field | Calculation |
|---|---|
| Is Open | 0 when Lifecycle Status is Completed, Cancelled or Archived; otherwise 1 |
| Is Overdue | 1 when open and Due Date is before today |
| Open Since | Creation time while open; blank when closed |
| Sync Key (from System) | Lookup of the linked System’s Sync Key |
| Key Check | ⚠ key mismatch when System Key ≠ Sync Key (from System); ⚠ no system linked when System Key is set and System is blank; otherwise blank |
| Reporter (Organization) | Business Unit of Reporter (Membership) |
| Reporter (Name), Accountable (Name) | Broken: they look up Member (Name), which the Membership mirror no longer has |
A row with no System Key and no System passes Key Check, so an empty row is not flagged.
Rules
- Kept whole. Name, Description, Evidence and Source Root Cause stay as received (rule “Submissions are kept whole as they arrived”).
- Key and link agree. Key Check is blank on every routed row (rule “Feedback’s system key matches its linked system”).
- One system, one reporter, one accountable. The links accept several records; link exactly one.
- The System field description says an automation fills System from System Key. No such automation runs. Link it by hand.
Example
A fictitious report: Name Visit list shows cancelled visits, System Key Field Service, Category Bug, Description as typed, Lifecycle Status Proposed; after triage System Field Service, Accountable the maintainer, Priority High, Due Date two days out, Resolution Plan and Response filled.