Where to find it | Sidebar → Admin → Corrections |
Who can see the queue | Admins and above |
Who can submit a flag | Anyone with drill-down access, from the page where they saw the problem |
How fresh is it? | Live |
What it's for
Signal displays numbers that originate in systems it doesn't control. When someone spots a wrong one — a client's revenue looks inflated, a department is mislabelled, outsourcing costs are missing — this gives them a structured path instead of a scattered Slack message, and gives admins one accountable queue.
Corrections never changes a financial number. It's a workflow and an audit trail. The actual fix happens in the source system, and marking a flag Resolved is a person attesting that it was handled.
How to report something
You don't need to come here to raise a flag. On the page where you saw the problem — for example a Summary drill-down — click the small flag icon next to the row. It pre-fills the client and the value on screen.
A good report has four things:
Field | What to put |
Field | Which number is wrong: Revenue, Outsource Costs, Gross Profit, Division, Department or Other |
Month | Which month you were looking at |
Current and expected value | What it showed, and what you believe it should be |
Reason | Why you believe that — this is the field that makes it actionable |
What you'll see on the queue
Three tabs with counts — Pending, Reviewed, Resolved.
The queue table — client, field, department, month, status, who submitted it and when.
Expand any row for the full detail: current and expected value, the reason, who reviewed it, reviewer notes, and when it was resolved.
A search box across client, department, reason and submitter.
Actions for admins — Review with a note, Resolve, and Delete for pending flags only.
How to use it
Work the pending queue. Corrections is the Admin section's landing page. Scan Pending, expand each flag to read the reason, then either Review with a note ("confirmed with finance, correction pending upstream"), resolve it if it's trivially answered, or delete it if it's a duplicate.
Close the loop. Once the underlying data is corrected at source and flows back into Signal, return to the Reviewed tab and click Resolve. That timestamp is the record that reported issues actually get fixed rather than just acknowledged.
Check whether a number is trustworthy. Before presenting a client's financials, search the queue for that client. Open flags disputing those months are a reason to caveat the review — or delay it.
Spot systemic problems. When the same field or the same client keeps reappearing, that's an upstream process problem, not a one-off. Escalate the pipeline, not the row.
The status workflow
Pending → Reviewed → Resolved. There's no reopen.
Pending — submitted, not yet triaged
Reviewed — an admin has acknowledged it, typically meaning it's being investigated or handed to finance
Resolved — closed, with a timestamp
The exact meaning of Reviewed versus Resolved is a team convention rather than something Signal enforces. Agree it with your team.
Good to know
Nobody is notified when you submit a flag. There's no email and no Slack message. The form's promise that finance will review it depends on admins checking the queue. If your issue is urgent, follow up directly as well as flagging it.
Flags are claims, not verified facts. Nothing checks the values you typed against the real figure, and nothing verifies the upstream fix landed before someone marks it Resolved. That's on the honour system.
The client field is free text. There's no picker, so spelling varies and flags aren't reliably linked to client records. Be consistent with names if you want to find them again.
"Current Value" is a snapshot, not a live figure. If it no longer matches what Signal shows, that divergence is often exactly the sign that the fix landed.
Only pending flags can be deleted. Reviewed and resolved ones can't be removed, so the audit trail can't be erased.
A leadership-access user without admin access can read the queue but sees no actions. That's expected.
Employee-data flags are informally supported. The form says "client or employee" and division and department are flaggable, but the underlying record is client-shaped. Whether people-data issues should route through here is a team decision.
Common questions
What is this page? A data-quality queue. People report numbers that look wrong; admins work them Pending → Reviewed → Resolved. It never changes financial data.
Can I flag something if I'm not an admin? Yes — use the flag icon on the page where you saw it. Only viewing and triaging the queue needs admin access. Standard-access users can't, because they don't have drill-downs.
Does flagging fix the number automatically? No. The fix happens in the source system. Once it lands and flows back, an admin marks the flag resolved. Signal doesn't verify it.
Does finance get notified? No. See "Good to know" — follow up directly if it's urgent.
What's the difference between Reviewed and Resolved? Mechanically: acknowledged versus closed with a timestamp. The operational meaning is your team's convention.
Can I delete a flag I submitted by mistake? Ask an admin, while it's still pending. Reviewed and resolved flags can't be deleted.
Why doesn't "Current Value" match what Signal shows now? It's a text snapshot from when it was flagged. A difference often means the fix landed.
Does resolving a correction change any numbers? No. It's purely a reporting and audit workflow.
Related
Where the numbers come from — check this before flagging; two numbers can legitimately differ
Summary — the main place flags get raised
Getting help — who to contact for everything else
Admin Tools — the rest of the back office