Pilot service · Institutional research & reporting offices

SSMS-to-Quarto Automated Report Refresh

If someone on your team reruns the same SQL Server queries every month or term and pastes the results into a document, we can turn one of those reports into a parameterized Quarto report. It refreshes on a schedule, runs documented checks, and waits for a named reviewer before anything is shared.

Request a scoped pilot

Pilot inquiries only. The fee is quoted after a scoping conversation; nothing is purchased from this page.

Who this is for

Offices that produce the same report on a schedule from SQL Server data, for example:

The usual pattern: run saved queries in SQL Server Management Studio, copy results into Excel or Word, reformat the tables, check them against last period by eye, and repeat. The work is careful and repetitive, and it often lives in one person's head.

If SSRS or Power BI already meets the need, keep using it. This pilot is for a narrative or print-ready report that those tools aren't handling well today.

What the pilot covers

One data source, read-only
A single SQL Server database, ideally through a view that returns only the fields the report needs. Your IT team provisions a read-only account; we never need write access.
One recurring report
The report you already produce, rebuilt in Quarto so it renders to HTML, Word, or PDF from versioned SQL and code.
Up to three parameter variants
For example, all campuses plus two individual campuses, or three cohorts. Parameters are bound by the database driver and checked against an allowlist, never pasted into SQL text.
Release checks and a review step
Each refresh confirms the period exists, totals reconcile with an independent count, and change from the prior period stays within a threshold you set. Small cells are suppressed using your institution's rule. A failed check marks the report HOLD, and a named person approves before distribution.
Scheduling and handoff
A script your team runs on a schedule in your environment (for example, Windows Task Scheduler), plus a runbook for running, checking, and fixing a refresh by hand.

This describes the proposed pilot structure. A written scope confirms the report, variants, checks, environment, and fee before any work begins.

Deliverables

Report code

  • Versioned SQL files
  • A parameterized Quarto (.qmd) report
  • Rendered outputs for each variant

Checks

  • Coverage and reconciliation checks
  • Prior-period change threshold
  • Small-cell and complementary suppression

Operations

  • Schedule script and setup notes
  • Manual runbook and failure steps
  • A walkthrough with the report owner

See a sample built on invented data

Synthetic demo

We built a small version of this workflow against a synthetic enrollment database (no real students or institutions). It renders three campus variants of a term summary, suppresses small cells, and marks the report HOLD when a check fails.

To test it, we compared each variant's totals with answers computed separately from the generated data, without using the report's SQL. All three variants matched. We also confirmed that a missing reporting period produces a HOLD report and that an unknown campus parameter stops the render.

Open the sample report (all campuses) →

The sample shows what the output can look like. It is not a client deliverable, and it says nothing about time saved on your report; we would measure that on your report during a pilot.

How a pilot would run

  1. Scoping call. Pick one report, its audience, variants, and how often it runs. Confirm whether SSRS or Power BI already covers it.
  2. Define the metrics. Use a past approved report as the reference, including your suppression rule and change threshold.
  3. Build. Write the SQL and Quarto report against a copy, a test database, or synthetic data until access is approved.
  4. Reconcile. Run two reporting periods side by side with the approved versions; the data owner signs off on any differences.
  5. Schedule and hand off. Set up the scheduled refresh in your environment and walk your team through the runbook.

Before the pilot starts, we ask you to time one manual refresh, so you can compare it with the new process yourself.

Limitations

Common questions

Do we need to buy software?

Quarto, R, and Python are free and open source. The Microsoft ODBC driver for SQL Server is a free download. You need a machine or server that can reach the database on a schedule.

We already use SSRS or Power BI. Is this a replacement?

No. Keep the dashboards that work. This fits a recurring written or print-ready report, especially one that combines tables with narrative and is still assembled by hand.

Do you need student-level data?

Usually not. The report can read an aggregated view that your team creates, so the service account sees only the totals the report needs.

What does a pilot cost?

We quote a fixed fee after scoping, based on the report's complexity, number of variants, and your environment. The inquiry below doesn't commit you to anything.

What output formats are possible?

Quarto renders HTML, Word, and PDF from the same source. We agree on formats and an accessibility review during scoping.

Request a scoped pilot

Tell us about one report you refresh by hand. We will reply about fit, access requirements, and a quote.

How is it produced today? Select all that apply.

Your inquiry is processed through Resend, emailed to report-refresh@statisticalsolutions.org, and followed by a confirmation email to you. It does not subscribe you to a mailing list or start a purchase. Please don't include student-level or other confidential data. Privacy policy.

Prefer to talk first? Book a free 30-minute consult →

← Back to research support services