Exception Queue Setup Guide (Google Sheets / Excel)

A spreadsheet-based exception queue is the fastest way to start tracking AI automation failures without buying software. This guide shows you exactly how to build one that actually works.

You'll create a functional exception tracking system in under 30 minutes. No coding required. Just a spreadsheet, some formulas, and clear ownership rules.

This approach handles 80% of exception management needs for firms running up to 50 automation workflows. When you outgrow it, you'll have the data and process discipline to justify a proper ticketing system.

• Google Sheets (free) or Excel with Microsoft 365 (for automation features)
• 30 minutes of uninterrupted setup time
• One person designated as the exception queue owner

That's it. No integrations, no API keys, no vendor contracts.

Open a new Google Sheet or Excel workbook. Name it "AI Exception Queue - [Your Firm Name]".

Create these exact column headers in row 1:

A: Exception ID - Auto-generated unique identifier
B: Timestamp - When the exception was logged
C: Workflow Name - Which automation failed
D: Error Type - Category of failure
E: Description - What went wrong
F: Severity - P0 (critical), P1 (high), P2 (medium), P3 (low)
G: Status - New, Assigned, In Progress, Resolved, Closed
H: Assigned To - Email address of owner
I: Due Date - Target resolution date
J: Resolution Notes - What fixed it
K: Time to Resolve - Hours from creation to closure

Format row 1 as bold with a light gray background. Freeze this row (View > Freeze > 1 row).

Set column widths: A=100px, B=150px, C=200px, D=150px, E=300px, F=80px, G=120px, H=180px, I=100px, J=300px, K=100px.

Exception ID (Column A):
In cell A2, enter: =IF(B2="","","EXC-"&TEXT(ROW()-1,"0000"))
This creates IDs like EXC-0001, EXC-0002, etc. Copy down 500 rows.

Timestamp (Column B):
Leave blank for manual entry, or use a form (see Step 4) to auto-populate.

Time to Resolve (Column K):
In cell K2, enter: =IF(AND(B2<>"",G2="Closed"),(J2-B2)*24,"")
This calculates hours between timestamp and resolution. Assumes you log resolution time in column J. Copy down 500 rows.

Select the entire Status column (G2:G500). Apply these rules:

New - Red fill, white text
Assigned - Orange fill, black text
In Progress - Yellow fill, black text
Resolved - Light green fill, black text
Closed - Dark green fill, white text

Select the Severity column (F2:F500). Apply these rules:

P0 - Dark red fill, white text
P1 - Red fill, white text
P2 - Yellow fill, black text
P3 - Light gray fill, black text

Select the Due Date column (I2:I500). Apply this custom formula rule:
=AND(I2<TODAY(), G2<>"Closed", G2<>"Resolved")
Format: Red fill, white text. This highlights overdue exceptions.

In Google Sheets, go to Tools > Create a new form. This generates a form that writes directly to your sheet.

Add these form fields:

1. Workflow Name (Short answer, required)
2. Error Type (Dropdown: Data Quality Issue, API

   API

   Click to read the full definition in our AI & Automation Glossary.

   Failure, Logic Error, Timeout, Permission Error, Other)
3. Description (Paragraph, required)
4. Severity (Dropdown: P0, P1, P2, P3)
5. Supporting Evidence (File upload - screenshots, logs)

In form settings, enable "Collect email addresses" so you know who reported it.

Link this form in your Slack workspace, email signature, or automation failure notifications. Anyone can report an exception without touching the spreadsheet.

The form responses populate a second sheet. Use this formula in your main Exception Queue sheet to pull data:

In B2: ='Form Responses 1'!A2 (timestamp)
In C2: ='Form Responses 1'!C2 (workflow name)
And so on for each field.

For Google Sheets:

Go to Tools > Notification rules. Set up two rules:

1. New Exception Alert: "Notify me when... a user submits a form" - sends to queue owner immediately
2. Daily Digest: "Notify me at... [time] with... a daily digest of changes" - sends summary of all updates

For Excel with Microsoft 365:

Use Power Automate (included with M365):

1. Create a new flow: "When a new row is added"
2. Add action: "Send an email (V2)"
3. To: Your queue owner's email
4. Subject: New Exception: [Workflow Name]
5. Body: Include Exception ID, Severity, Description

Set up a second flow for overdue reminders:

1. Trigger: "Recurrence" (daily at 9 AM)
2. Condition: Check if Due Date < Today AND Status ≠ Closed
3. Action: Send email to Assigned To address

Create a second sheet tab named "Dashboard". This is your at-a-glance view.

Exception Count by Status:
Use COUNTIF formulas:
TOKEN_6
TOKEN_7
Continue for all statuses.

Average Time to Resolve:
TOKEN_8

Exceptions by Severity:
TOKEN_9
Continue for P1, P2, P3.

Top 5 Failing Workflows:
Use a pivot table. Insert > Pivot table. Rows: Workflow Name. Values: COUNTA of Exception ID. Sort descending. Show top 5.

Overdue Exceptions:
Create a filtered view showing only rows where Due Date < TODAY() and Status ≠ Closed.

Format this dashboard with large, bold numbers. Use sparklines or simple bar charts if you want visuals.

Document this directly in a third sheet tab named "Process Guide":

When an exception is logged:

1. Queue owner reviews within 2 hours (4 hours for P2/P3)
2. Owner assigns to appropriate team member based on workflow type
3. Owner sets due date: P0 = same day, P1 = 24 hours, P2 = 3 days, P3 = 1 week
4. Assigned person updates Status to "In Progress" when they start work
5. Assigned person logs resolution steps in Resolution Notes
6. Assigned person changes Status to "Resolved" when fixed
7. Queue owner verifies fix and changes Status to "Closed"

Escalation rules:

• P0 exceptions not assigned within 1 hour: Escalate to operations director
• Any exception overdue by 2+ days: Escalate to managing partner
• Same workflow failing 3+ times in one week: Schedule root cause analysis meeting

Write these rules in plain language. Add a column for "Owner" next to each step.

Daily standup (5 minutes):
Review Dashboard tab. Call out any new P0/P1 exceptions and confirm ownership.

Weekly review (15 minutes):
Review Top 5 Failing Workflows. Identify patterns. Schedule deeper investigation for workflows with 5+ exceptions.

Monthly analysis (30 minutes):
Calculate exception rate (total exceptions / total automation runs). Track trend over time. Review average time to resolve. Identify training needs based on error types.

Add these meetings to your calendar now. Assign a facilitator. Exception queues only work if someone actually looks at them.

Move to a dedicated ticketing system (Jira, Linear, ClickUp) when you hit any of these thresholds:

• 100+ exceptions per month
• 5+ people need to assign/resolve exceptions
• You need approval workflows (manager sign-off before closing)
• You want integration with monitoring tools (Zapier, Make, n8n)
• You need audit trails for compliance (SOC 2, ISO 27001)

Until then, this spreadsheet handles everything. The firms I work with typically run this setup for 6-12 months before outgrowing it.

New Exception Notification:

Subject: [P0/P1/P2/P3] New Exception - [Workflow Name]

Exception ID: [Auto-filled]
Workflow: [Auto-filled]
Error Type: [Auto-filled]
Description: [Auto-filled]

This exception has been assigned to you. Due date: [Auto-filled]

View full details: [Link to spreadsheet]

Overdue Exception Reminder:

Subject: Overdue Exception - [Exception ID]

You have an overdue exception assigned to you:

Exception ID: [Auto-filled]
Workflow: [Auto-filled]
Due Date: [Auto-filled] (now [X] days overdue)

Please update the status or escalate if you need help.

View details: [Link to spreadsheet]

Not assigning an owner. Someone must check this daily. Put it in one person's job description.

Skipping the form. If people have to open the spreadsheet to log exceptions, they won't do it. The form removes friction.

No due dates. Exceptions without deadlines never get resolved. Set them automatically based on severity.

Treating all exceptions equally. P0 means "client-facing failure, fix now." P3 means "annoying but not urgent." Use severity correctly.

Not reviewing resolved exceptions. The Resolution Notes column is your knowledge base. Read it monthly to prevent repeat failures.

This spreadsheet is not a permanent solution. It's a proof of concept that buys you 6-12 months to demonstrate ROI before investing in real tooling. Use that time to build the discipline and data that makes a proper exception management system worth the cost.