Report Forge Key Concepts
Report Forge uses a small set of reporting objects. Learning these terms makes the rest of the product easier to understand.
| Term | Meaning |
|---|---|
| Blueprint | The reusable report structure. It defines sections, fields, rules, and the shape of a repeatable reporting process. |
| Section | A logical part of the report, such as progress, commercial status, risks, actions, or lookahead. |
| Field definition | A question, metric, text area, date, number, status, file, or other input expected inside a section. |
| Edition | A reporting cycle created from a blueprint, often tied to a week, month, project phase, or stakeholder update. |
| Entry | The actual information entered into a field for a specific edition. |
| Output | The designed report layout used to present edition data as a polished report. |
| Review history | Comments, review decisions, changes, and evidence preserved during the reporting cycle. |
How the objects connect
A blueprint defines what should be collected. An edition captures the current reporting period. An output presents the edition as a stakeholder-ready package.