Skip to content

CUSTOM REPORTS

Ask your submissions a question.

Group by an answer, a detail or a month, count and total what matters, filter to the slice you care about — then send it out as Excel or a branded PDF. No chart library to learn: the widget list is short, and each one tells you when it is the right choice.

See pricing

START HERE

You already have a report. This is the one above it.

THE FLOOR — AUTOMATIC

Every form keeps its own

The moment a form is live its report exists — submissions over time, completion rate, where people drop off. Nothing to configure, nothing to build. Most people never need more than this.

THE CEILING — YOURS

When the summary is not the question

“How many upgrade requests per region last quarter, excluding the cancelled ones?” is not a completion rate. That is a report you build once, save, and re-run whenever you want the current answer. The builder for it is on Business and Enterprise.

HOW IT WORKS

Three choices, then it is a report.

  1. 01

    Group by

    Group by an answer, by a submission detail, or by a time bucket — the dropdown you built last week, or the month it came in. Add a second dimension and one report answers referrals by clinic and by month. Every group becomes a row.

  2. 02

    Measure

    Count submissions, total a number field, average one — and add more than one, so the headline figure and the detail behind it sit in the same report. A count can be narrowed to only the responses you mean, which is how you count upgrade requests rather than submissions. Pick from what your fields actually support, so a measure can never be invalid.

  3. 03

    Filter

    Narrow to the slice that matters. Date range, status, any answer value. Save it, and re-run it whenever you want it fresh.

WHAT THAT LOOKS LIKE IN PRACTICE

Group by Region — measure count of submissions and average response time, where Status is Upgrade requested and Submitted is in the last 90 days

WHAT YOU CAN PUT ON IT

A canvas, not a fixed template.

Drag a widget in, size it, put it where you want it. The report is yours, and it looks the same on screen, in the PDF and to whoever you send it to.

Number

One measure’s total, large. The figure you’d quote in a meeting.

Bars

Compares groups by length. The easiest comparison to read, and the safe default.

Line

A trend across the groups in order. Best when the axis is time.

Area

A line with the space beneath it filled. Emphasises volume rather than rate.

Stacked bar

Each group’s share of the whole, as one bar. Lengths compare more accurately than angles, so this reads better than a pie.

Pie

Each group’s share of the whole. Best at three or four groups; harder to read past that.

Doughnut

A pie with the middle out. Same reading, a little easier on the eye.

Progress

One measure against a target you set. A meter, which reads better than a two-slice pie.

Comparison

Two measures side by side. Needs a second measure before it becomes available.

Table

Every group and every measure, as text. The one widget a screen reader can read completely.

Every widget reads the same saved definition, so changing a filter updates the whole page at once rather than once per widget.

THE PART NOBODY ELSE CAN DO

Group by a code. Show the name.

Your form collects a branch code, because that is what the respondent knows. Your report needs the branch name, the region and the manager — and those live in your database, not in the submission. With a data connection, the report reads both and joins them.

WHAT THE FORM COLLECTED

branch_code · BR-4471

status · Upgrade requested

submitted · 14 Aug

WHAT THE REPORT SHOWS

Northgate Retail · North West

Manager · from your database

17 requests · this quarter

Nobody has to maintain a lookup sheet, and nobody has to paste a branch list into the form for the report’s benefit. It reads what you already keep.

THE HONEST PART

What it does not do.

A page like this is easy to write without limits. Here are ours.

One form at a time
A report is built on a single form’s submissions. Combining several forms into one report is not something you can do today.
Measures are a closed list
Count, total, average and the rest — picked from what your fields support. There is no formula language, which is why a measure can never be invalid or silently wrong.
It is not a wall dashboard
A saved report runs over every response each time you open it, so the numbers are current and there is nothing to remember to refresh. What it will not do is sit on a screen in the corner of the office updating itself.
The join needs a connection
Pulling names, regions or anything else out of your own database requires a data connection, which is a separate add-on.

PRICING

On Business and Enterprise.

The custom report builder is included on Business and on Enterprise. It is not available on Free, Solo or Team.

BusinessEnterprise

TRY IT

Build one on a form you already have.

Pick a field to group by and see what comes back. If the answer is not useful in about a minute, it was never the right question.

Start free