Recurring analytics

Build shared dashboards for recurring decisions

Create dashboards that answer the same question every week. Use variables to parameterize views, schedule refreshes, and keep the SQL inspectable beside every chart.

Builder: Visual + SQL
Layout: 12-column grid
Variables: Typed parameters
Refresh: Manual + scheduled

Every team has questions that come back. Weekly revenue by segment. Monthly pipeline by region. Quarterly retention by cohort. The analysis is the same shape each time — the only things that change are the date range, the filter values, and the people in the room.

SyneHQ Dashboards turns those recurring questions into shared, parameterized dashboards. Build the query once with the visual builder or in SQL, configure the chart, drop it into a 12-column layout, and wire up variables so the next review is a matter of changing a dropdown — not rebuilding a spreadsheet.

From question to shared dashboard

A reporting dashboard starts as a question: "How did each segment perform this quarter?" In Dashboards, you answer it by building the query, seeing the result, and laying out the presentation — all in one workspace.

Start with the visual query builder. Pick the connection and table, select the columns you need (segment, revenue, quarter), add filters and sorting. The builder generates SQL you can inspect and edit at any point. When the query shape is right, configure a chart — choose bar, line, area, or another type, assign the X and Y fields, and set the title and colors.

The chart becomes a block in a dashboard. Add more chart blocks for related views — revenue by segment beside revenue by quarter, for example — and use Markdown blocks to record the review context: what the chart is answering, what caveats apply, when the data was last checked.

Blocks sit on a responsive 12-column grid. Move and resize them so the primary comparison is visible first and supporting context sits nearby. Layout changes persist, so the next person who opens the dashboard sees the same arrangement.

Dashboards / Q3 Revenue Review / Chart builderIllustrative interface

Chart preview

Revenue by segment — Q3

Bar chart

Dashboard layout — 12-column grid

Chart block

Revenue by segment

Chart block

Trend

Markdown block

Q3 review notes and source definitions

Sample configuration — no live data connection or query execution

The key property of this workflow is that the SQL stays visible beside the chart. A reviewer can check the query logic, not just the bars. When a number looks unexpected, the path from chart to SQL to source is one click, not a ticket to another team.

Parameterize for the next review

A dashboard built for one quarter becomes useful for every quarter when you add variables. Define a typed variable — "quarter" as a string, "region" as a string, "min_revenue" as a number — and map it to the SQL with template syntax: {{quarter}}, {{region}}.

Now the same dashboard answers the question for Q2 EMEA and Q3 North America without anyone editing the SQL. Change the variable value, refresh, and the charts update.

Refresh can be manual or automatic. Set an auto-refresh interval — every 30 minutes, every hour — for dashboards that need to stay current during a review window. Manual refresh is available when you want to deliberately recheck a result. The interval requests a refresh; actual timing depends on the configured connection and source availability.

Dashboard variables

Parameterize the view

quarter

Type: String

region

Type: String

EMEA

SQL mapping

SELECT segment, SUM(revenue)
FROM orders
WHERE quarter = {{quarter}}
  AND region = {{region}}
GROUP BY 1

Refresh schedule

Keep the dashboard current

Auto-refresh

Every 30 minutes

Interval requests a refresh. Actual timing depends on connection state and source availability.

Sharing

Team access

Share the dashboard with the team. Everyone uses the same query logic and layout — they change the variable values for their context.

Variables and refresh together mean a dashboard is not a snapshot. It is a reusable view that adapts to the context of the current review. Share it with a team, and the whole group works from the same query logic and the same layout — they just change the parameters.

For each chart, takeaways let you capture the observation from a specific review. Comments are available on chart blocks for discussion. These are aids for the review conversation, kept close to the data they reference.

Reporting patterns that save hours

The combination of visual building, SQL inspection, variables, and scheduled refresh supports several recurring reporting patterns:

Weekly revenue review

Build a dashboard with segment revenue, order volume, and average order value. Parameterize by week using a date variable. Each Monday, change the variable to the current week, refresh, and the team reviews the same three charts with fresh data. A Markdown block at the top records the agenda and any standing definitions (what counts as "completed," which segments are included).

Monthly pipeline report

Create charts for pipeline by stage, conversion rates, and average deal size. Use region and month variables so each regional lead sees their own view. The SQL is the same; the variables filter it. Schedule auto-refresh for the first business day of the month so the dashboard is ready before the meeting starts.

Quarterly board deck data

Board reporting often means exporting numbers from a dashboard into slides. Build the dashboard with the charts that will be presented: ARR growth, customer count, retention rate, expansion revenue. Use quarter and year variables. When the quarter closes, update the variables and export the charts. The SQL behind each chart is inspectable, so any question about methodology has an answer in the same workspace.

Ad-hoc investigation follow-up

Sometimes a weekly review surfaces a question that needs a deeper look. Start in Data Explorer or Quantum Lab to investigate, then promote the result to a dashboard chart when the question becomes recurring. The dashboard captures the promoted query, and the next review includes it automatically.

Keep the SQL inspectable

The common thread across these patterns is that the SQL never disappears behind the chart. Every dashboard block traces back to a query. Every variable maps to a SQL reference. Every refresh runs the same query with the current parameters.

This matters because reporting workflows break when the logic is opaque. A chart that shows a number without showing how it was computed is a chart that will eventually be wrong without anyone noticing. Dashboards keeps the path from question to SQL to chart to layout visible at every step.

Get started

Build and configure dashboards in Dashboards. For product guidance, read the visualization documentation. To explore your data before building a dashboard, start with Data Explorer or Quantum Lab.