Ngenaire Docs

Report Templates

Report Templates let you author a reusable report layout once and render it on demand against a project's live data. A template is a body of text with placeholders for project values; when you render it, those placeholders are filled in from the current project.

Location: /report-templates (sidebar: Report Templates).

Report Templates are scoped to a project — the templates you see are the ones created for the project you currently have selected.

Report Templates vs. other template features

There are three template-style features; don't confuse them:

  • Report Templates (this page) — a text body you author by hand, with placeholders, that you render against a project to produce a report.
  • AI Report Builder — generates a template from an uploaded sample document and fills it with AI, with markdown / DOCX / PDF downloads. See AI Report Builder.
  • Document Templates — an organization-wide library of reusable document structures, under Define. See Document Templates.

If you want AI to build and populate the report for you, use the AI Report Builder. Use this page when you want full manual control over the report's body.

What a template defines

  • Name — what the template is for.
  • Description — an optional short note.
  • Body — the report text, with placeholders for project values and simple loops over project content (for example, a section that lists every requirement).
  • Output formatMarkdown, HTML, or Text.
  • Parameter schema — an optional JSON object declaring extra parameters you can pass in at render time.

Create a template

  1. Select the project you want the template to belong to.
  2. Click New template.
  3. Enter a Name and an optional Description.
  4. Write the Body. A starter body is pre-filled to show the placeholder and loop syntax.
  5. Choose the Output format (Markdown, HTML, or Text).
  6. (Optional) Provide a Parameter schema as JSON for any extra render-time values.
  7. Click Save.

Render a template

  1. On a template card, click the render / play action.
  2. (Optional) Supply any render parameters as JSON.
  3. The rendered output appears in a preview, populated from the project's current data.
  4. Download the result; the file type matches the template's output format (.md, .html, or .txt).

Edit or delete

  • Edit — open a template, change its name, description, body, format, or parameter schema, then save.
  • Delete — remove a template you no longer need. This cannot be undone.

Permissions

  • Members with project edit rights can create, edit, and delete templates.
  • Viewers can see and render templates but cannot author them.

Tips

  • Name templates after the deliverable, not the project, so the intent is clear.
  • Use loops for lists. A short loop in the body keeps a requirements or risk table in sync with the project automatically every time you render.
  • Render often. Because the output is built from live project data, re-rendering always reflects the latest state.

Related