Weekly Reports

Every Sunday evening, FastQuery posts a weekly report to each store’s newsfeed. It’s written for the whole team — a short briefing that surfaces the few things that need attention this week, not a ledger of everything that happened.

What’s in a report

Each report opens with a quick read of the week, then gets straight to the point:

• Needs Attention — the handful of items (at most five) that actually need the team this week, ranked by consequence: what it is, why it matters, and what happens if it slips.
• Routine movement — everything else, summarized in a few lines: tasks completed, counts in progress, backlog trend.
• Recommendations — suggested next moves where the week’s activity points to one.

Tasks and items mentioned in the report are tappable — tap one to open it right from the post.

The report is a starting point, not the full story. For anything you want to dig into, ask FastQuery in the chat — you can reference the report directly, like “the weekly report mentions a SKU shortage — show me that task and what’s been done on it.”

The executive summary

Alongside the store reports, an executive summary posts to the organization’s Headquarters feed, where admins and managers see it. It rolls the week up across all stores: how each location performed, patterns that span stores, and the items worth leadership follow-up.

A sample report

Here’s a real report from our demo store (in the app, the underlined items are tappable links to the actual tasks):

The fire-safety recert is down to its last item: the extinguisher pass and emergency-lighting test both closed this week, leaving only the Sentinel Fire Systems sprinkler/alarm certification — now 5 days overdue and blocked on the vendor. The Milwaukee M18 freight lands Friday and bay 3 isn’t yet clear for it.

Needs Attention

• Sprinkler & alarm annual certification is 5 days overdue and the only open piece of the annual recert. Per Hannah’s note, Sentinel is booked ~2 weeks out and nothing closes on our end until a tech shows. It needs escalation or a second vendor, since the recert stays open until it’s filed.
• Clear bay 3 for Milwaukee freight Friday is overdue with spring garden pallets still occupying the staging space. The Milwaukee freight (PO #MW-44218) arrives Friday ~8:30 and needs bay 3 staged; if it’s not cleared first, receiving backs up against the 10am paint truck.
• Investigate SKU 5033403 shortage (44 missing) is overdue and unstarted. Mango flagged 47 expected / 13 counted — well past the 10-unit threshold — so the gap needs tracing back through the April receiving PO before it hardens into the shrink line.
• Restock walk — paint aisle (7–9) is 1 day overdue at 40%; back-room pull and aisle 7 pegs are done, but the aisle 8 can slots and shelf-tag check remain ahead of the paint truck.
• Repeat shoplifting risk: Isabella turned away a teen (red Giants cap) attempting to pocket two utility knives. The follow-up to pull the front-door clip for the LP binder is open, so the desk has a photo if he returns.

Routine Movement

Six tasks completed this week, including the extinguisher inspection, emergency-lighting test, April P&L roll-up, and the returns-desk signage fix (7-day SO hold now matches policy).

Cycle counting is mid-round: PVC fittings, aisle 19 reached 10/13 (76%) with 11 SKUs counted this week, while the new Badger Floor Outs sits at 2/8. Bin-tag and price-tag audits across aisles 2, 19, 20, and plumbing are in progress. The garden endcap reset is at tear-down complete (40%).

Of the 5 overdue tasks, all saw movement or were created this week — there is no stale backlog carried from prior weeks.

Recommendations

• Escalate the sprinkler/alarm cert directly with Sentinel or line up a backup certifier; at the current pace the recert stays open past its due date regardless of internal effort.
• Clear bay 3 today so Friday’s freight and the 10am paint truck don’t collide at the dock.
• On the 1-1/4” full-port ball valve add: Daniel logged three contractor asks in a week — pull his SKU list and run the Eagle margin check before the next quarterly order.

The recert hinges on one vendor visit, and Friday’s freight depends on bay 3 being cleared first; both are worth resolving early in the week.

Ask FastQuery in the app chat to dig into anything here — you can reference this report.

Getting reports by email

The feed post is the primary copy, and reading it there needs no setup. If you also want reports in an inbox, an admin can add email recipients on the Integrations page under Weekly Reports: each facility has its own recipient list for the store report, and there’s a separate list for the executive summary. A facility with no recipients simply gets its report on the feed only.

Admins can also add additional guidance there — a short note on what your organization wants reports to emphasize (for example, “always call out compliance items first”). It shapes emphasis; the report’s structure and tone stay the same.

Good to know

• Quiet weeks stay quiet. A store with no meaningful activity that week gets no report post — the executive summary still posts and notes which stores were quiet.
• A report can occasionally arrive late. If generation hits a snag on Sunday night, the report is re-run and typically lands within a day, covering the same week. If the executive summary already went out before a late store report landed, it’s refreshed to include that store — the post on the Headquarters feed is updated in place, and email recipients get a new copy marked [corrected] in the subject.
• Reports can’t be edited. Like other system posts, they’re a record of what the AI reported. If a report gets something wrong, ask FastQuery about it in chat — the underlying tasks and data are the source of truth.