Skip to main content

Weekly Power-User Operating Routine

The best Blast Audit teams do not wait for blocked runs or end-of-week cleanup. They use a short weekly routine across the add-in and dashboard to keep OCR healthy, templates reusable, and admin work under control.

Written by William Karkegi
Updated over 2 weeks ago

The best Blast Audit teams do not wait for blocked runs or end-of-week cleanup. They use a short weekly routine across the add-in and dashboard to keep OCR healthy, templates reusable, and admin work under control.

Who this is for

  • Power users in the Excel add-in

  • Team leads who own quality and adoption

  • Workspace admins reviewing usage, seats, and exports

Before you begin

  • You may still see Copilot Audit in a few older labels.

  • Add-in work happens in Excel. Dashboard work needs admin access.

  • If you do not have dashboard access, you can still follow the add-in parts of this routine.

How to do it

  1. Monday: check the dashboard.

Open Usage and review Feature engagement, Team momentum, and Adoption overview.

Then open Users to review pending invites and access gaps.

If seats are tight, check Billing and Seat management.

  1. Before matching work: clear the OCR backlog.

In Documents, scan OCR Status for anything still in Processing or Not Started.

Use Re-run OCR before those files hit a real engagement.

  1. Midweek: run matching in a controlled way.

Open Document Matching.

Start with My Templates or Company templates when possible.

For higher-quality runs, prefer Use document folders or Choose specific documents over All documents.

  1. Save good setups while they are fresh.

If a run worked well, save it with Save matching template and give it a clear name.

This keeps mapping and matching rules consistent across jobs.

  1. Review evidence workflows.

Use Documents or the viewer to spot missing snips.

If the Restore badge appears, handle it early.

Use Compare for revision checks and Form Extraction for repeated form-like documents.

  1. Friday: do admin cleanup.

Open dashboard Document Matching to review template run counts and sharing status.

Open Data exports if your team needs CSV outputs or scheduled reporting.

Clean up stale invites, seat pressure, and recurring blockers before the next week starts.

  1. Escalate only what survived the routine.

If the same error still appears after OCR cleanup, document scoping, and template review, send a support request with a support escalation packet instead of letting the issue roll forward.

Expected result

  • OCR issues are caught before matching day

  • Teams reuse templates instead of rebuilding mappings each week

  • Seat and invite problems are handled before they block new users

  • Exports and admin follow-up happen on a predictable cadence

Avoid this

  • Matching everything against All documents by default

  • Letting OCR stay in Processing until a live review is due

  • Saving messy templates and reusing them everywhere

  • Ignoring pending invites until seats run out

  • Waiting until Friday night to gather support details

If it still doesn't work

  • Keep only the minimum routine: dashboard check on Monday, OCR check before runs, and support prep on Friday

  • If one step always creates noise, simplify it before automating it

  • Use a support escalation packet for any blocker that repeats week after week

Read next

  • Read the Usage Dashboard

  • Invite Members and Assign Roles

  • Folder Strategy for Clean Matching

  • Save and Reuse Matching Templates

  • Fix "No Matches" or Low Confidence

  • Fix Seats and Invite CSV Errors

  • Build a Support Escalation Packet

Did this answer your question?