## TL;DR
A Juro 'template variable unresolved' with a smart field rendering blank means the variable behind the field has no value: the data source did not populate it, the counterparty skipped the question that feeds it, or the field was relinked to a different variable. Open the template, find which variable the smart field references, trace that variable to its source (integration field, questionnaire answer, or manual entry), supply the missing value, and regenerate the document. Blank output is the system telling you the data never arrived - not a rendering bug.

## The query
```text
Juro 'template variable unresolved'  -  the smart field renders blank in the sent contract
```

## Use this when
- A Juro smart field renders blank in the sent contract
- The template preview shows the value but the generated document does not
- The error or warning names a template variable as unresolved

## Not for
- Smart fields showing the wrong value - those resolved, just to bad data
- Whole-document generation failures - those fail before any field renders
- Formatting issues in populated fields - a presentation problem, not a data problem

## Steps
### 1. Identify the variable behind the blank field
In the template editor, select the blank smart field and read which variable it references. Smart fields are just views onto variables; the fix is always at the variable level, never in the field's formatting.
Expected output: the exact variable name the field depends on.

### 2. Trace the variable to its data source
Check where the variable gets its value: a connected integration field, an answer in the counterparty questionnaire, or a manual entry by your team. Open that source and confirm the value exists. The usual findings: the questionnaire question is optional and was skipped, or the integration field mapping broke.
Expected output: you can point at the source and see the value missing there.

### 3. Supply the missing value and regenerate
Provide the value at the source - answer the questionnaire question, fix the integration mapping, or enter it manually - then regenerate the document from the template. Editing the generated document directly does not fix the template, and the next generation will be blank again.
Expected output: the regenerated document shows the populated field.

### 4. Make the variable required or defaulted
If the variable is business-critical, mark its questionnaire question required or give the variable a sensible default in the template. Optional inputs feeding critical fields are how blank contracts ship.
Expected output: future documents cannot generate with this variable empty.

## Tool compatibility
Juro contract automation: template editor, smart fields, template variables, questionnaire, and integrations. Same behavior across Juro plans with templating.

## Variant phrasings
- Juro template variable unresolved smart field blank
- Juro smart field renders blank in sent contract
- Juro variable has no value document generation
- Juro questionnaire skipped question blank field

## Why it happens
Juro separates data (variables) from presentation (smart fields) so one variable can feed many places. When the data is missing, every field bound to it renders blank rather than failing generation - the document is still structurally valid, just incomplete. That leniency is useful for drafts but dangerous for sent contracts, which is why critical variables should be required, not optional.

## Edge cases / pitfalls
- A variable renamed in the template orphans every smart field bound to the old name - they go blank together.
- Integration mappings break silently when the source system renames a field; re-verify mappings after source-system changes.
- Preview can show cached values from a previous generation - always regenerate to test a fix.
- Conditional sections can hide the question that feeds the variable; the counterparty never sees it and the field goes blank.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_bBPvpClLTSAMnNfVh_ehnA