Things to Consider

A things_to_consider field renders a list of risks, trade-offs, and caveats relevant to the recommended advice. It is one of the five rich content types in AdviceDocs and is generated by a Stage 5 LLM step that reads each recommendation and returns 1–3 considerations per item, flattened into a single bulleted list.

How to write the placeholder

Use a regular {{ field_name }}. The classifier looks at the field description, not the name — so make sure the description asks for considerations, risks, or caveats.

Things-to-consider placeholders

{{ things_to_consider }}
{{ portfolio_things_to_consider }}
{{ risks_and_trade_offs }}

What the classifier looks for

Descriptions like “List the things the client should consider before accepting this advice,” “Outline the risks and trade-offs,” or “Caveats and warnings about the recommended approach” will reliably classify a field as things_to_consider.

What renders at fill time

The placeholder is replaced with a structured list of blocks — usually a single bulleted list, but headings and paragraphs can also be returned when the example document uses them. The Stage 5 LLM:

Reads each recommendation in the template.
Generates 1–3 considerations per recommendation.
Flattens them into a single list, adapted to the client’s situation.
Styles them according to the linked example document.

Configuration after upload

Open the gear icon next to the template name to access the template-level generation settings. Pick an example document for things to consider — the sections in that document drive bullet style, length, and tone.

There is no per-field modal for this type. All things-to-consider fields on the template share the same example document.

Common pitfalls

Don't reuse the same field name as a recommendation

If both recommendation and things_to_consider share similar descriptions, the classifier may misroute. Keep the description focused on risks / considerations / trade-offs to push the LLM toward the correct type.

Empty list when there are no recommendations

Things to consider are derived per-recommendation. If the template has no recommendation fields, or none have been classified, this field renders empty.

Override the type manually if needed

You can force things_to_consider from the field configuration UI. Useful when the description is genuinely ambiguous between content / things_to_consider / benefits.

Syntax to copy

Generic things to consider

{{ things_to_consider }}

Topic-specific things to consider

{{ portfolio_things_to_consider }}
{{ insurance_things_to_consider }}
{{ super_things_to_consider }}

As part of a loop

{% for rec in recommendations %}
{{ rec.things_to_consider }}
{% endfor %}