advicedocs

Recommendation

A recommendation field renders long-form, structured advice content at the placeholder location. It is one of the five rich content types in AdviceDocs. Unlike simple fields, the value is a list of structured blocks (headings, paragraphs, lists, tables) and is generated by a dedicated Stage 4 LLM step that reads the template’s advice summary and an example document.

How to write a recommendation placeholder

Write a regular {{ field_name }} placeholder. There is no special syntax. The field name doesn’t have to contain “recommendation” — the type is decided post-parse by an LLM that reads the field’s description.

Recommendation placeholders
{{ recommendation }}
{{ portfolio_recommendation }}
{{ insurance_recommendation }}

The classifier reads the description, not the name

For a field to be classified as a recommendation, write a description that asks for advice content — for example, “Detail the recommendations from the advice summary” or “Recommended insurance strategy with sums insured.” Without a clear description, AdviceDocs will fall back to text.

What renders at fill time

At document-fill time the placeholder is replaced with a sequence of structured blocks:

  • Headings — section labels at h2 / h3 level.
  • Paragraphs — multi-line prose with bold / italic runs.
  • Lists — bulleted or numbered.
  • Tables — structured comparisons.

The blocks come from a Stage 4 LLM that:

  1. Parses the linked example document into sections.
  2. Matches each item in the advice summary to the closest section.
  3. Generates new blocks per recommendation, adapted to the client’s data.

Configuration after upload

Recommendation fields don’t use the per-field configuration modal. Instead, open the gear icon next to the template name to launch the template-level generation settings. There you can:

  • Pick an example document — a Setting file whose recommendation sections drive tone, structure, and section ordering for every recommendation in the template.
  • Pick an advice summary instruction — the source of truth for what is being recommended.

These settings are template-wide; changing them updates how every recommendation field on the template is generated.

Common pitfalls

Vague descriptions stay as text

A field named recommendation with no description (or a description like “the recommendation”) is too thin for the classifier. Write a description that explicitly asks for advice content — reference the advice summary, the recommendations being made, or the format you expect.

Document references override classification

If the description starts with an @ reference (e.g. @AdviceSummary), the field is treated as a non-dependent document anchor and will not be classified as a recommendation. Reword the description as a prose instruction to keep it in the rich content pipeline.

Manual override is supported

You can force a field to be a recommendation regardless of name and description by selecting the type in the field configuration UI. This sets is_field_type_manual = true and prevents the classifier from changing it later.

Syntax to copy

Generic recommendation
{{ recommendation }}
Topic-specific recommendations
{{ portfolio_recommendation }}
{{ insurance_recommendation }}
{{ super_contribution_recommendation }}
Recommendation inside a loop
{% for rec in recommendations %}
  {{ rec.recommendation }}
{% endfor %}