How to Create a Blueprint
A blueprint defines the structure of a reporting process: its sections, fields, editions, and outputs. Creating a well-structured blueprint is the foundation of every report in Report Forge.

Before you start
- You need the Blueprint Author or Admin role in your organisation.
- Plan the report structure: what sections does this report need? What fields are required in each section? Who fills in data and who reviews it?
- Identify the output format: will reports be exported as PDF, Excel, Word, or all three?
Step 1: Open the Blueprint Library
- Navigate to Report Forge from the main navigation.
- Select the Blueprints tab.
- Click + New Blueprint.
Step 2: Set blueprint properties
| Field | Description |
|---|---|
| Name | The internal name of the blueprint. This appears in the blueprint library and edition creation. |
| Display name | The name shown on report covers and in the report viewer. |
| Description | A short summary of the report's purpose. Shown in the library when selecting a blueprint. |
| Category | Group the blueprint by type (e.g., Monthly Progress, Handover, Safety). |
| Icon / color | Visual identifier in the library. |
| Version | Starting version label (default: 1.0). |
Click Create to open the blueprint designer.
Step 3: Add sections
Sections organise related data within the report. Each section holds fields and has settings controlling how data is entered and displayed.
- In the Blueprint Designer, click + Add Section.
- Enter the Section name (e.g., "Executive Summary", "Schedule Overview", "Cost Performance").
- Set the Section type:
- Single entry — one set of field values per edition (for summary data).
- Repeating rows — multiple rows per edition (for activity lists, issue registers, etc.).
- Optionally set a Description to guide contributors on what to enter.
- Click Save section.
Step 4: Add fields to each section
- Select the section you want to add fields to.
- Click + Add Field.
- Configure the field:
| Property | Options |
|---|---|
| Field name | Internal identifier used in output bindings. |
| Display label | Label shown to contributors and in outputs. |
| Field type | Text, Number, Currency, Percentage, Date, Single select, Multi-select, File upload, Rich text, Calculated. |
| Required | Whether the field must be filled before the edition can be submitted. |
| Placeholder | Hint text shown in the input field. |
| Validation | Min/max for numbers; date range for dates; character limit for text. |
| Default value | Pre-populated value when a new edition is created. |
| Conditional visibility | Show/hide this field based on the value of another field. |
- Click Save field.
- Repeat for all fields in the section, then repeat steps 1–4 for each additional section.
Step 5: Configure field order and grouping
Drag fields within a section to reorder them. Use Group to visually cluster related fields under a subheading within the section.
Step 6: Set up section permissions (optional)
For each section, set which roles can view or edit it:
- Open the section → Permissions.
- Assign Edit access to the roles responsible for filling in data.
- Assign View access to roles that review but do not edit.
Step 7: Add outputs
An output is the report layout that presents edition data. One blueprint can have multiple outputs (e.g., an executive summary PDF and a detailed Excel export).
- In the blueprint, click Outputs → + New Output.
- Name the output (e.g., "Monthly Progress Report \u2014 PDF").
- The Output Designer opens \u2014 see How to Build an Output for the full design workflow.
Step 8: Review and publish the blueprint
- Click Preview to open the blueprint in preview mode and confirm the section/field structure.
- Click Publish blueprint when the structure is finalised.
- Published blueprints can be used to create editions.
Publishing a blueprint does not lock it forever. You can unpublish, edit, and republish. Existing editions created from earlier versions are not affected by re-published changes unless you increment the version.