Skip to main content

Report Forge Glossary

Report Forge glossary terms

Core concepts

TermDefinition
BlueprintThe master template that defines a reporting process. A blueprint specifies sections, fields, outputs, and workflow rules. Blueprints are reused across reporting periods.
EditionA single reporting cycle instance created from a blueprint. An edition captures data for one period (e.g., April 2025 Monthly Progress). Multiple editions can be created from one blueprint.
OutputA designed report layout that presents edition data. One blueprint can have multiple outputs (e.g., an executive PDF and a detailed Excel).
SectionA named grouping of fields within a blueprint. A section can be single-entry (one set of values per edition) or repeating (multiple rows per edition, like an activity list).
FieldA named data input within a section. Fields have a type (text, number, date, select, etc.) and optional validation.
ComponentA visual or content element placed in an output canvas: table, chart, KPI card, Gantt, image, text box, slicer, button, etc.
CanvasThe design surface in the Output Designer where components are placed and arranged.
WellA binding slot within a component's Build panel. Dragging a field into a well binds that data dimension to the component.
AggregationThe mathematical operation applied to a numeric field in a component well: Sum, Average, Count, Min, Max, etc.
ParameterA runtime-selectable value exposed to the report consumer or template engine (e.g., Reporting Period, Project Code). Parameters appear in filters and text using {ParameterName} syntax.
Calculated fieldA named expression evaluated from existing fields. Appears in the field list with an fx badge and can be bound in component wells.
Scope (filter)The reach of a filter rule: Visual (one component), Page (all components on the page), or Report (all components in all pages).
Scope (slicer)Whether a slicer's selection affects the current page only or all pages in the output.
Data connectionA configured link to a data source (OptiPlan, SQL Server, Excel, SharePoint) that supplies rows to blueprint sections.
Field mappingThe configuration that maps source data columns to blueprint section fields.
PreviewRendering the output canvas against a selected edition's data in the Output Designer, without generating a final output.
Publish (output)Making an output available for report generation from editions. Published outputs are locked from further edits.
Publish (blueprint)Making a blueprint available for edition creation. Published blueprints expose their structure to contributors.

Components

TermDefinition
TableA component displaying tabular data with optional grouping, subtotals, conditional formatting, and in-cell visuals.
MatrixA pivot-table component with row and column groups and aggregated value cells.
ChartStandard chart types: bar, line, area, pie, donut, scatter, histogram.
Combo chartA chart with two Y axes, one rendered as bars and one as a line on the same plot.
Advanced chartsSpecialist chart types: waterfall, treemap, funnel, decomposition tree, box plot, scatter-bubble, MTA, resource profile.
GanttA horizontal bar schedule chart showing activities, baselines, dependencies, and critical path.
KPI cardA compact visual showing one or more key performance indicators with optional trend, comparison, sparkline, or progress bar.
Cash flow curveAn S-curve or periodic bar chart for cumulative and periodic cost or progress data.
Earned value chartA chart for EV/PV/AC and CPI/SPI trend visualisation.
SlicerAn interactive filter control (dropdown, list, date range, etc.) for the report consumer to filter components.
ButtonA clickable element with an action (navigate page, drill through, navigate URL, filter, back).
SubreportA component that embeds another blueprint's output inside the parent output, with parameter mapping.
MapA geospatial component displaying point, cluster, heatmap, or polygon data on a basemap.
MTAMilestone Trend Analysis. A chart plotting forecast milestone dates across reporting periods to show schedule drift.

Reporting workflow terms

TermDefinition
ContributorA user assigned to enter data into an edition's sections.
ReviewerA user assigned to review submitted edition data and raise or resolve comments.
Review commentA comment raised against a specific field or row during the review process.
DraftEdition status: created but not yet submitted for review.
SubmittedEdition status: data submitted by the contributor; awaiting reviewer action.
Changes requestedEdition status: reviewer has returned the edition with comments for the contributor to address.
ApprovedEdition status: edition data has been reviewed and approved. Outputs can be generated.
ClosedEdition status: the report has been finalised and distributed. No further changes permitted.
RAGRed / Amber / Green status indicator. Used in conditional formatting and KPI cards to indicate performance against thresholds.
Data dateThe schedule as-of date for the edition. All schedule calculations are evaluated as of this date.
Reporting periodThe date range covered by the edition (e.g., 1 April 2025 to 30 April 2025).