Your Department's Worst Day

Read the reconciliation pile Excel file. This is Accounting's month-end backlog.
Categorize each item: BLOCKING CLOSE (prevents financial close), VARIANCE (amounts differ between ledger and bank), MISSING EVIDENCE (audit trail incomplete), ROUTINE (standard entries pending posting).
For BLOCKING CLOSE items, draft a one-sentence resolution action with the responsible party.
Produce a triage report as a Word document (.docx) with:
- Executive summary with total unreconciled amount and close readiness %
- BLOCKING CLOSE items with resolution actions and owners
- VARIANCE items grouped by type (currency mismatch, decimal shift, timing difference)
- MISSING EVIDENCE items with the specific document or sign-off needed
- Pattern analysis: recurring reconciliation breaks across accounts or entities
- Recommendation on whether close deadline is achievable

Read the case pile Excel file. This is the Monday pre-arbitration and expiring cases backlog.
Categorize each case: DEADLINE CRITICAL (< 3 days to scheme deadline), EXPIRING SOON (< 7 days), EVIDENCE READY (can submit today), WAITING ON MERCHANT (evidence requested, not received), PRE-ARB ACTION (pre-arbitration response needed).
For DEADLINE CRITICAL cases, draft a one-sentence action plan including scheme portal and deadline date.
Produce a triage report as a Word document (.docx) with:
- Executive summary with case counts by scheme (Visa, Mastercard, AMEX) and urgency
- DEADLINE CRITICAL cases with action plans and scheme portal targets
- PRE-ARB ACTION cases with recommended accept/fight assessment
- Cases grouped by reason code category (Fraud, Consumer Dispute, Processing Error, Authorization)
- Pattern analysis: merchants generating repeat chargebacks or approaching VAMP/MATCH thresholds
- Recommendation for today's case processing order

Read the alert pile Excel file. These are screening alerts requiring review.
For each alert, categorize as: FALSE POSITIVE, NEEDS REVIEW, or ESCALATE.
Draft a one-sentence rationale for each categorization.
Produce a triage report as a Word document (.docx) with:
- Executive summary: counts by category
- ESCALATE items first with full rationale
- NEEDS REVIEW items with suggested next steps
- FALSE POSITIVE items grouped by dismissal reason
- Any cross-alert patterns (same merchant, same geography, same alert type)

Read the escalation pile Excel file. This is the Country Operations escalation backlog across all markets.
Categorize each item: REGULATORY RISK (compliance or legal deadline), MERCHANT OUTAGE (revenue-impacting), LOCAL APPROVAL NEEDED (pending country-specific sign-off), CENTRAL COORDINATION (requires HQ team input), ROUTINE LOCAL (standard local process).
For REGULATORY RISK items, draft a one-sentence action with the affected market and deadline.
Produce a triage report as a Word document (.docx) with:
- Executive summary with escalation counts by country (GB, ES, IT, PT, CZ, HU, IS)
- REGULATORY RISK items with market-specific deadlines and owners
- MERCHANT OUTAGE items with estimated revenue impact
- Escalations grouped by type (sales, onboarding, operations, compliance)
- Pattern analysis: countries or processes generating disproportionate escalations
- Recommendation on which markets need immediate Country Manager attention

Read the ticket pile Excel file. This is the weekend support backlog.
Categorize each ticket by urgency: URGENT (SLA breach risk), TODAY, THIS WEEK, NEEDS INFO.
For URGENT tickets, draft a one-sentence next step.
Produce a triage report as a Word document (.docx) with:
- Executive summary
- URGENT tickets with next steps
- Tickets grouped by category
- Repeat-issue patterns (3+ tickets for same root cause)
- Recommended FAQ articles to reduce future volume

Read the request pile Excel file. This is the Data team's ad-hoc request backlog.
Categorize each request: EXISTING DASHBOARD (answerable from current Tableau dashboards), QUICK QUERY (one-off Snowflake SQL, < 30 min), NEW MODEL NEEDED (requires DBT model or new data source), BLOCKED (upstream data quality issue or missing access), DUPLICATE (same question already answered).
For EXISTING DASHBOARD requests, draft a one-sentence response pointing to the specific dashboard.
Produce a triage report as a Word document (.docx) with:
- Executive summary with request counts by complexity and requesting department
- BLOCKED requests with the specific upstream issue preventing delivery
- NEW MODEL NEEDED items with estimated effort and dependencies
- DUPLICATE clusters for consolidation
- Pattern analysis: departments submitting repeat requests that should be self-serve dashboards
- Recommendation for this week's on-call rotation on-call priorities

Read the exception pile Excel file. This is Finance's settlement and correction backlog.
Categorize each item: UNRECONCILED (bank vs internal mismatch > 48 hrs), CORRECTION PENDING (four-eye approval needed), CURRENCY MISMATCH (FX or currency code discrepancy), SCHEME FORMAT ERROR (Visa/MC/AMEX file parsing issue), ROUTINE (within tolerance, auto-clear candidate).
For UNRECONCILED items, draft a one-sentence investigation step with the data source to check.
Produce a triage report as a Word document (.docx) with:
- Executive summary with total unreconciled value and correction queue depth
- UNRECONCILED items with investigation steps and age in days
- CORRECTION PENDING items with approval status (Pending Approval 1 / Pending Approval 2)
- Items grouped by scheme settlement source (Visa, Mastercard, AMEX)
- Pattern analysis: recurring discrepancy types (decimal shifts, timing gaps, duplicate postings)
- Recommendation on items to escalate via Jira vs resolve directly

Read the alert pile Excel file. This is the Fraud team's monitoring case backlog.
Categorize each alert: BLOCK IMMEDIATELY (high-severity score > 90 or BIN attack pattern), INVESTIGATE (suspicious pattern needing analyst review), FALSE POSITIVE LIKELY (matches known snooze patterns), THRESHOLD WARNING (merchant approaching VAMP/MATCH limits), DUPLICATE (same merchant, same rule, already open case).
For BLOCK IMMEDIATELY alerts, draft a one-sentence recommended action (block payouts, block account, or create ticket).
Produce a triage report as a Word document (.docx) with:
- Executive summary with alert counts by rule type and severity
- BLOCK IMMEDIATELY alerts with recommended actions
- THRESHOLD WARNING merchants with current ratio vs VAMP/MATCH limits
- Alerts grouped by detection mode (real-time, near real-time, batch)
- Pattern analysis: BIN attack clusters, velocity spikes, or coordinated fraud across merchants
- Recommendation for today's queue assignment priorities

Read the deal pile Excel file. This is the pipeline backlog.
Categorize each deal: HOT (ready to close), WARM (needs follow-up), STALE (no contact > 14 days), DATA ERROR (suspicious values).
For HOT deals, draft a call prep brief.
Produce a triage report as a Word document (.docx) with:
- Executive summary with total pipeline value by category
- HOT deals with call prep briefs
- STALE deals with recommended re-engagement approach
- DATA ERROR items for CRM cleanup

Read the ticket pile Excel file. This is the IT Helpdesk's JSM backlog.
Categorize each ticket: P1 INCIDENT (system outage or security issue), ACCESS URGENT (new joiner starting today/tomorrow), ROUTINE ACCESS (standard provisioning request), HARDWARE (equipment issue or replacement), MFA/PASSWORD (reset or lockout), LICENCE REQUEST (software approval needed).
For P1 INCIDENT tickets, draft a one-sentence impact assessment and escalation path.
Produce a triage report as a Word document (.docx) with:
- Executive summary with ticket counts by category and SLA status
- P1 INCIDENT items with impact assessment and escalation contacts
- ACCESS URGENT items with the new joiner's start date and department
- Tickets grouped by application (Okta, Zendesk, HubSpot, Jira, other)
- Pattern analysis: repeated MFA reset abuse, recurring hardware failures, or licence bottlenecks
- Recommendation for ticket assignment across today's support shift

Read the review pile Excel file. This is the contract review backlog.
Categorize each review: URGENT (deadline < 7 days), STANDARD, LOW RISK (template-based), NEEDS ESCALATION (non-standard terms).
For URGENT items, flag the specific clauses requiring attention.
Produce a triage report as a Word document (.docx) with:
- Executive summary
- URGENT reviews with clause-level flags
- NEEDS ESCALATION items with risk description
- Suggested prioritisation for this week

Read the delivery pile Excel file. This is the Supply Chain's terminal order and returns backlog.
Categorize each item: FAILED DELIVERY (courier attempted, merchant not available), OVERDUE (past expected delivery date), PREP NEEDED (device not yet prepared for dispatch), RETURN PENDING QA (returned device awaiting inspection), SWAP URGENT (merchant without working terminal), SCHEDULED (on track, no action needed).
For SWAP URGENT items, draft a one-sentence action with courier and expected resolution.
Produce a triage report as a Word document (.docx) with:
- Executive summary with counts by order type (new, swap, collection, return) and status
- SWAP URGENT and FAILED DELIVERY items with merchant impact and next steps
- OVERDUE items with days past expected date and courier tracking status
- Items grouped by country and delivery partner (DPD, local couriers)
- Pattern analysis: courier failure rates, country-specific delivery bottlenecks, QA backlogs
- Recommendation for today's dispatch and QA priorities

Read the content pile Excel file. This is Marketing's content production and campaign backlog.
Categorize each item: PAST DEADLINE (publication date missed), LAUNCHING SOON (going live within 48 hours, needs approval), IN PRODUCTION (on track, in creative pipeline), NEEDS LOCALISATION (English ready, translations pending), BLOCKED (waiting on Product, Legal, or stakeholder input), BACKLOG (no deadline pressure).
For PAST DEADLINE items, draft a one-sentence recovery plan with revised timeline.
Produce a triage report as a Word document (.docx) with:
- Executive summary with content counts by status and channel (blog, email, social, campaign asset)
- PAST DEADLINE items with recovery plans
- LAUNCHING SOON items with outstanding approval steps
- NEEDS LOCALISATION items grouped by target market and language
- Pattern analysis: bottlenecks in the 40-day campaign cycle (ideation, approval, localisation)
- Recommendation for this week's content priorities by channel

Read the application pile Excel file. This is the Onboarding team's merchant pipeline backlog.
Categorize each application: CDD BLOCKED (KYC/KYB pending > 14 days), DOCUMENT MISSING (merchant hasn't submitted required docs), TERMINAL PENDING (CDD cleared but no device assigned), ALMOST LIVE (all steps complete, awaiting first transaction), AT RISK (> 21 days in any single stage), ON TRACK (progressing normally).
For CDD BLOCKED applications, draft a one-sentence follow-up action with the specific blocker.
Produce a triage report as a Word document (.docx) with:
- Executive summary with pipeline counts by stage (Registration, KYC, CDD, Terminal, Activation)
- CDD BLOCKED and AT RISK applications with days stuck and specific blockers
- DOCUMENT MISSING applications with exactly which documents are outstanding
- Conversion funnel: application to first settlement with drop-off points
- Pattern analysis: lead sources with highest stall rates, CDD bottleneck causes
- Recommendation for follow-up priority and merchants needing escalation to Sales

Read the request pile Excel file. This is the operations request backlog.
Categorize each request: URGENT, ROUTINE, BLOCKED, DUPLICATE.
Flag any requests that appear to be related (same merchant, same issue type).
Produce a triage report as a Word document (.docx) with:
- Executive summary
- URGENT items with recommended actions
- BLOCKED items with what's needed to unblock
- DUPLICATE clusters for consolidation
- Automation failure patterns (bot failures followed by manual requests)

Read the partner pile Excel file. This is the Partnerships team's partner activity and commission backlog.
Categorize each item: COMMISSION DISPUTE (partner querying amount or clawback), UNDERPERFORMING (lead volume dropped > 30% vs prior period), INTEGRATION STUCK (technical onboarding stalled), NEW PARTNER SETUP (onboarding checklist incomplete), CLAWBACK REVIEW (cancelled merchant triggering commission recovery), HEALTHY (performing within expectations).
For COMMISSION DISPUTE items, draft a one-sentence summary of the discrepancy and data to verify.
Produce a triage report as a Word document (.docx) with:
- Executive summary with partner counts by status and total commission value at risk
- COMMISSION DISPUTE items with discrepancy details and verification steps
- UNDERPERFORMING partners with trend data and suggested re-engagement approach
- INTEGRATION STUCK partners with the specific technical blocker
- Pattern analysis: duplicate ISA payments across countries, clawback frequency by partner type
- Recommendation for this week's partner relationship priorities

Read the request pile Excel file. This is the People team's employee request backlog.
Categorize each request: NEW JOINER URGENT (start date within 5 days, setup incomplete), OFF-BOARDING (last day approaching, revocation needed), PAYROLL CRITICAL (affects next pay run), POLICY QUERY (employee question needing response), REVIEW CYCLE (performance review admin task), ROUTINE (standard HR process request).
For NEW JOINER URGENT items, draft a one-sentence checklist gap with the missing setup step.
Produce a triage report as a Word document (.docx) with:
- Executive summary with request counts by category and country
- NEW JOINER URGENT items with start dates and missing provisioning steps
- OFF-BOARDING items with last dates and security-critical access to revoke first
- PAYROLL CRITICAL items with pay run deadline
- Pattern analysis: recurring provisioning delays by department, overdue compliance training
- Recommendation for coordination needed with IT Helpdesk this week

Read the activation pile Excel file. This is Product Activation's non-transacting merchant backlog.
Categorize each merchant: KYC INCOMPLETE (CDD not cleared, can't transact), TERMINAL NOT DELIVERED (device pending logistics), TECHNICAL BLOCKER (setup issue preventing first transaction), DORMANT (onboarded > 30 days, no transaction, no known blocker), CAMPAIGN TARGET (good candidate for activation nudge), ACTIVATED (first transaction processed, remove from list).
For DORMANT merchants, draft a one-sentence outreach action with the suggested channel (SMS, email, phone).
Produce a triage report as a Word document (.docx) with:
- Executive summary with activation rate vs 90% KPI and counts by blocker type
- DORMANT merchants with days since onboarding and suggested outreach
- TECHNICAL BLOCKER merchants with the specific issue to resolve
- Merchants grouped by product type (POS vs E-commerce) and lead source
- Pattern analysis: drop-off points in the activation funnel, campaign conversion rates
- Recommendation for this week's activation campaign targeting

Read the backlog pile Excel file. This is the Product team's Jira backlog.
Categorize each ticket: BLOCKED (dependency or decision preventing progress), SPRINT CARRY-OVER (missed last sprint, needs re-prioritisation), STALE (no update > 14 days), BUG CRITICAL (user-facing defect), READY FOR SPRINT (groomed with acceptance criteria), NEEDS GROOMING (missing requirements or story points).
For BLOCKED tickets, draft a one-sentence unblock action identifying who owns the dependency.
Produce a triage report as a Word document (.docx) with:
- Executive summary with ticket counts by status and total story points at risk
- BLOCKED tickets with dependency owners and suggested unblock actions
- BUG CRITICAL items with severity and affected user segment
- SPRINT CARRY-OVER items with reason for slippage
- Pattern analysis: recurring blockers, teams causing dependencies, velocity trend
- Recommendation for next sprint planning priorities and tickets to descope

Read the escalation pile Excel file. This is Product Operations' Tier 2 escalation backlog from JSM.
Categorize each ticket: PRODUCT BUG (confirmed defect, needs engineering), PROCESS GAP (no runbook or help centre article exists), COMPLAINT (formal complaint requiring GDPR-compliant handling), MISROUTED (should have been resolved at Tier 1), RECURRING PATTERN (3+ instances of same issue), STANDARD RESOLUTION (known fix, can close today).
For PRODUCT BUG items, draft a one-sentence Jira summary for the engineering team.
Produce a triage report as a Word document (.docx) with:
- Executive summary with escalation counts by category and source team (CR, Sales)
- PRODUCT BUG items with Jira summaries ready for engineering handoff
- COMPLAINT items with compliance handling status and response deadline
- RECURRING PATTERN clusters with root cause hypothesis and suggested product fix
- Pattern analysis: help centre content gaps driving Tier 2 volume, misroute rate from Tier 1
- Recommendation for product feedback to share at next Product sync

Read the cancellation pile Excel file. This is the Retention team's incoming cancellation request backlog.
Categorize each request: HIGH VALUE SAVE (monthly volume > threshold, worth a retention call), SERVICE ISSUE (reason linked to support quality, not pricing), PRICE SENSITIVE (competitor offer or fee complaint), BUSINESS CLOSURE (genuine closure, not saveable -- route back to CR), EARLY WARNING (not yet cancelled but showing churn signals), ALREADY LOST (merchant already moved processing elsewhere).
For HIGH VALUE SAVE requests, draft a one-sentence save angle based on the merchant's likely real reason.
Produce a triage report as a Word document (.docx) with:
- Executive summary with cancellation count, total monthly volume at risk, and save opportunity %
- HIGH VALUE SAVE merchants with save-call prep notes and suggested approach
- SERVICE ISSUE cases with the specific service failure to acknowledge
- Cancellation reasons grouped by category (service, price, competitor, closure)
- Pattern analysis: churn signals appearing before formal cancellation, repricing history of churning merchants
- Recommendation for today's retention call priority order

Read the risk alert pile Excel file. This is the Risk team's merchant risk review backlog.
Categorize each alert: RESTRICT NOW (chargeback ratio exceeding VAMP/MATCH threshold), EDD REQUIRED (enhanced due diligence triggered), BEHAVIOUR MISMATCH (transaction pattern inconsistent with declared business type), THRESHOLD APPROACHING (within 20% of scheme limit), PERIODIC REVIEW (standard ongoing monitoring, no red flags), CLEARED (previously flagged, now within acceptable parameters).
For RESTRICT NOW alerts, draft a one-sentence recommended action (monitor, restrict, or block) with the specific threshold breached.
Produce a triage report as a Word document (.docx) with:
- Executive summary with alert counts by severity and scheme (Visa VAMP, Mastercard MATCH)
- RESTRICT NOW alerts with threshold data and recommended actions
- EDD REQUIRED cases with the trigger reason and documentation to request
- BEHAVIOUR MISMATCH merchants with declared vs actual transaction pattern comparison
- Pattern analysis: merchant categories generating repeat alerts, country-level risk concentration
- Recommendation for cases to discuss at the next CDD risk meeting

Read the scheme pile Excel file. This is Scheme Operations' bulletin actions and compliance backlog.
Categorize each item: MANDATE DEADLINE (scheme rule change with implementation date < 30 days), FEE DISCREPANCY (billed vs estimated variance > 5%), MCC NON-COMPLIANT (merchant category code mismatch), CLEARING ERROR (file parsing or format issue), BULLETIN REVIEW (new bulletin needs impact assessment), ROUTINE COMPLIANCE (standard periodic check).
For MANDATE DEADLINE items, draft a one-sentence impact summary with affected teams and implementation date.
Produce a triage report as a Word document (.docx) with:
- Executive summary with item counts by scheme (Visa, Mastercard, AMEX, UnionPay, Diners) and urgency
- MANDATE DEADLINE items with impact summaries and implementation timelines
- FEE DISCREPANCY items with variance amounts by scheme and fee type
- MCC NON-COMPLIANT merchants with current vs correct MCC assignment
- Pattern analysis: schemes generating most compliance work, recurring fee reconciliation breaks
- Recommendation for items to include in the next scheme business review

Read the treasury pile Excel file. This is Treasury's daily liquidity and safeguarding exception backlog.
Categorize each item: FUNDING SHORTFALL (settlement account below required balance), SAFEGUARDING BREACH (80/20 partner bank A/partner bank B split outside tolerance), FX EXPOSURE (currency position approaching volatility threshold), TRANSFER FAILED (automated sweep or manual transfer did not execute), BALANCE CORRECTION (minor adjustment needed), NORMAL (within all parameters).
For FUNDING SHORTFALL items, draft a one-sentence action with the amount needed and target bank account.
Produce a triage report as a Word document (.docx) with:
- Executive summary with total safeguarded balance, split ratio status, and exception count
- FUNDING SHORTFALL items with shortfall amounts and settlement deadlines
- FX EXPOSURE items with current position vs threshold by currency
- TRANSFER FAILED items with the failed sweep details and retry instructions
- Pattern analysis: currencies or bank partners generating repeat exceptions, timing patterns in sweep failures
- Recommendation on DCC currencies to consider disabling and transfers to prioritise today