Analytics Request Intake

A single front door for data questions, a decision-first form, prioritisation and turnaround targets, a request desk rota and a searchable library of past answers, so asks stop getting lost or answered twice.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Then open the Marketplace in the app, search for Analytics Request Intake, and click Install. It goes into your own files, and works offline from then on.

What it installs.

1

Pillar

1

Area

50

Projects

202

Starter tasks

📊 Data & Analytics

Analytics Request Intake

Managing incoming data questions with a clear intake form, prioritisation, turnaround expectations and a record of past answers.

  1. Map of where data requests arrive today
  2. Open request backlog snapshot and clean-out
  3. Single front door for analytics requests
  4. Decision-first analytics request form
  5. Request types and size classes
  6. Choosing a request tracking tool
  7. Turnaround targets by request size
  8. Prioritisation rubric for data requests
  9. Request statuses and definition of done
  10. Searchable library of past answers
  11. Daily intake triage slot
  12. Weekly request prioritisation call
  13. Requester status updates and chaser reduction
  14. Monthly intake metrics review
  15. Answer library upkeep
  16. Weekly backlog grooming and ageing requests
  17. Quarterly demand review with department heads
  18. Requester feedback after delivery
  19. Register of repeat requests
  20. Request desk rota for analysts
  21. Clarifying conversation for vague requests
  22. Effort estimation for analytics requests
  23. Declining and redirecting requests gracefully
  24. Hypothesis-first scoping for larger analyses
  25. Guide for requesters on asking a good data question
  26. Standard close-out note for answered requests
  27. Check-the-library step before submitting
  28. Split between request work and planned analysis
  29. Analyst hour allowances for each department
  30. Fast lane for urgent and executive requests
  31. Intake automation for routing and replies
  32. Rules for raw data extract requests
  33. Cycle time study of thirty closed requests
  34. Converting oversized asks into scoped projects
  35. Launch of the new intake process
  36. Thirty-day intake pilot retrospective
  37. Planning season request surge
  38. Quarter-end reporting crunch plan
  39. Annual intake process review
  40. Request queue handover before a holiday period
  41. Solo analyst covering a whole company
  42. In-scope request list for a new data team
  43. Shared intake across embedded analysts
  44. Inheriting a request backlog after a reorg
  45. Request coordinator in a requesting team
  46. Request intake during a data platform migration
  47. Request volume forecast for analyst capacity
  48. Decision log of what answered requests changed
  49. Theme analysis of a year of requests
  50. Published catalogue of analytics services

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

Map of where data requests arrive today

This is a team plan, best installed into a shared workspace so everyone with a role in it can see and own their tasks. Before designing anything, find out how questions actually reach the data team: direct messages, email threads, comments on dashboards, asides at the end of meetings and the occasional ticket.

First tasks

  • Search your messages and inbox for data questions from the last two weeks
  • Ask each analyst to list the requests they took outside any queue
  • Tally requests by channel, requester and team in one sheet
  • Share the channel map with the team lead and agree the main finding

Open request backlog snapshot and clean-out

Most teams starting an intake process already carry an invisible backlog: half-finished pulls, promised follow-ups and asks nobody has said no to. Gathering every open request into one list, confirming which are still wanted and closing the rest gives the new process a clean starting line instead of a hidden debt. Expect around a third of old requests to be no longer needed once you ask.

First tasks

  • Ask each analyst to paste their open requests into a shared sheet
  • Add the requester, date asked and current state to each line
  • Message each requester to confirm which of their requests still matter
  • Close the unwanted requests with a one-line note to each requester
  • Assign a named owner to every request left open

Single front door for analytics requests

Requests that arrive through ten channels cannot be prioritised, counted or shared, so the first structural change is one place where every data question starts. It can be a shared chat channel, a ticket queue or a form feeding a board, but it must be one route, publicised, and faster for the requester than messaging an analyst directly. Pick the route requesters already use most and make it official.

First tasks

  • Pick the intake route that requesters already use most often
  • Set up the route so every request appears in one shared list
  • Write the polite redirect reply for requests that arrive elsewhere
  • Add a link to the front door on the team wiki and chat profiles

Make it yours.

Install Analytics Request Intake, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.