Key concepts and the mental model#

Most Reportworq concepts fall into place once one idea clicks. That idea is the single most important thing a new user has to get.

A report is a template that makes outputs#

Do not think of a report as an output. Think of it as a template that creates outputs.

A finished PDF or a sent email is a result. In Reportworq, the report is the thing that produces those results, over and over. It is a reusable asset with levers built in: parameters, variables, queries, formatting, messaging, and distribution rules. Pull those levers, and one report can generate hundreds or thousands of personalized outputs.

Different parts of the same source workbook do different jobs. Some parts exist to build the output file. Some exist only to build a rich email message. Others make distribution decisions, and others exist to collect data back into the planning system. The report becomes a specification for how information should flow through the organization.

This is where new users most often get stuck: they keep thinking of a report as a document rather than a reusable system. Once you build one solid master template that Reportworq can slice, personalize, and repeat, you stop maintaining a separate file per audience, and that is the moment the product pays off.

The terms that follow#

Everything else is a name for one of the levers on that template.

• Report (distribution job). The unit an author builds in the Job Editor. Internally it is a distribution job: a single runnable, schedulable object that binds source content, parameters, optional bursting, output formats, and delivery targets together. "Report" and "job" are the same thing seen from two angles, the author's asset and the thing that runs.

• Source file and worksheet. The Excel workbook (or PowerPoint template) the report renders, and the specific sheets it outputs, in order. The source file is where your existing Excel work lives, Reportworq automates it rather than replacing it. See Choose the source workbook and worksheets.

• Parameter. A named input that drives the report. Change a parameter such as period, store, or cost center, and the formulas in the source workbook recalculate to that value. Parameterizing a report is what lets one template serve every audience. See Parameterize a report.

• Bursting, replication, and burst sets. Bursting is the outcome: many personalized outputs from one job, one per value, each going to its own recipient. One cost-center job becomes one packet per cost-center owner.

  Two words describe how you get there, and they are not interchangeable. Replication is a parameter with several values fanning the output out by itself; set the parameter's replication mode and you are done. A burst set is the separate Bursting step, unlocked by flagging a parameter Burstable, which gives you per-file control over the values and the recipients.

  You do not need Burstable to produce many outputs. A multi-value parameter is already replicating. Flag Burstable only when you want the Bursting step itself. See What bursting is and when you need it.

• Distribution. The output formats a job produces (PDF, Excel, PowerPoint, CSV, and more) and the destinations it delivers them to (email, network folder, SharePoint, Slack, Teams, and others). One job can produce several formats to several places at once. See Distribution overview.

• Workspace. The governed content space a report lives in, its own folder tree, items, contacts, and security. The Workspace is also the home screen you browse. A server can host more than one workspace.

  Most organizations need only one. Folder-level security handles separating teams inside a single workspace, which is simpler to run than several. The clearest reason to add a second is credentials: a workspace holds its own data-source connections, so when two groups must reach the same system under different credentials, giving each its own workspace is the way to do it. Splitting purely to separate content is usually better served by folders.

• Contribution. The reverse direction. A contribution campaign turns a report into an input form, hands it to the people who own the numbers, collects what they enter, routes it for approval where you need one, and writes the approved values back to the planning system. The pieces are the campaign (the round of collection), the form each contributor fills in, and the approval step that gates the write-back. Reporting sends information out; contribution brings it back in, through the same security and the same audit trail. See Contribution overview.

• AI context. Reportworq's AI answers from the reports you have already built and approved, rather than querying your systems directly. That keeps answers traceable to something a person signed off, and keeps a user's AI access identical to their normal access. An author steers it per report with an AI profile, which tells the AI what the report means and how to talk about it. This is the steering wheel that stops answers drifting. See Create an AI Profile for a report and AI in Reportworq.

The value loop#

These pieces serve one repeating cycle: an author defines a report once, Reportworq generates it (on demand or on a schedule) by refreshing the data and rendering each output, and then distributes the results to where people work. Because the report is defined once and reused, the authoring effort carries over to every future run. The full arc, from authoring through monitoring, is walked through in The report lifecycle.

Where to go next#

• See the arc in action in The report lifecycle.
• Build your first report in Your first report, end to end.
• Look up any term in the Glossary.