Skip to main content

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.

Creating a blueprint 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

  1. Navigate to Report Forge from the main navigation.
  2. Select the Blueprints tab.
  3. Click + New Blueprint.

Step 2: Set blueprint properties

FieldDescription
NameThe internal name of the blueprint. This appears in the blueprint library and edition creation.
Display nameThe name shown on report covers and in the report viewer.
DescriptionA short summary of the report's purpose. Shown in the library when selecting a blueprint.
CategoryGroup the blueprint by type (e.g., Monthly Progress, Handover, Safety).
Icon / colorVisual identifier in the library.
VersionStarting 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.

  1. In the Blueprint Designer, click + Add Section.
  2. Enter the Section name (e.g., "Executive Summary", "Schedule Overview", "Cost Performance").
  3. 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.).
  4. Optionally set a Description to guide contributors on what to enter.
  5. Click Save section.

Step 4: Add fields to each section

  1. Select the section you want to add fields to.
  2. Click + Add Field.
  3. Configure the field:
PropertyOptions
Field nameInternal identifier used in output bindings.
Display labelLabel shown to contributors and in outputs.
Field typeText, Number, Currency, Percentage, Date, Single select, Multi-select, File upload, Rich text, Calculated.
RequiredWhether the field must be filled before the edition can be submitted.
PlaceholderHint text shown in the input field.
ValidationMin/max for numbers; date range for dates; character limit for text.
Default valuePre-populated value when a new edition is created.
Conditional visibilityShow/hide this field based on the value of another field.
  1. Click Save field.
  2. 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:

  1. Open the section → Permissions.
  2. Assign Edit access to the roles responsible for filling in data.
  3. 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).

  1. In the blueprint, click Outputs+ New Output.
  2. Name the output (e.g., "Monthly Progress Report \u2014 PDF").
  3. The Output Designer opens \u2014 see How to Build an Output for the full design workflow.

Step 8: Review and publish the blueprint

  1. Click Preview to open the blueprint in preview mode and confirm the section/field structure.
  2. Click Publish blueprint when the structure is finalised.
  3. Published blueprints can be used to create editions.
note

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.