Offer (Consultation)

The consultation checklist is the second of three checklist phases in Reonic. It attaches to the offer and is the digital consultation record your consultants fill during the on-site visit, also usable in the Reonic Mobile App while standing in the customer's house. This page also covers the cross-cutting setup steps for all three Settings > Checklists phases.

Who this is for

Admins configuring consultation templates for the whole workspace (and shaping qualification + site-documentation templates from the same Settings area), and account managers running consultations on-site.

What checklists are for in Reonic

Checklists in Reonic capture structured data along the entire project process. They split into three phases, each phase appears exactly where it belongs in the system:

• Qualification, on the request. For telephone or written lead qualification. See Lead (Qualification).
• Consultation, on the offer. The classic consultation record for the on-site appointment (also usable in the Reonic Mobile App). This page.
• Site documentation, on the installation. For complete documentation of the assembly process, Mobile App compatible. See Site documentation (Installation).

A single project carries up to three independent checklists across its lifecycle, one per phase. The same building blocks power all three, so once you know how to author one, you know how to author them all. Checklists work the same way for your commercial projects. Commercial templates are kept separate from the residential ones, and the authoring experience is identical on both.

Set up a checklist (any phase)

The setup path is the same regardless of which phase you're working in.

1. Open Settings > Checklists.
2. Open the page for the phase you want to edit: Qualification, Consulting, or Site documentation. (The consultation checklist lives under the Consulting page.)
3. Build the template from blocks (see Building blocks below). You can insert any number of elements between existing rows.
4. Per element, decide whether it's required. Required elements must be filled in before the checklist can be marked complete.
5. Save. New projects created from this point forward use the updated template; in-flight projects keep their current version. See Site documentation (Installation) for the per-project update path.

Pro tip: Each phase has its own template. Editing the Consultation template doesn't change Qualification or Site documentation. If your team's process uses the same questions across phases, author them in each phase separately.

Building blocks

Every checklist is built from the same set of element types, the template just configures different elements for different phases:

• Description text, hints for the person executing (e.g. "Ask about existing heating contract before discussing heat-pump scope"). Read-only.
• Checklist, tickable points. Standard checkbox items.
• Selection, single-choice options. Display as radio buttons, or as a dropdown when the option list is long.
• Images, photo requests, optionally with example images stored on the element (e.g. what the existing heating's nameplate should look like).
• Free text, single-line (for values like consumption or date) or multi-line (for longer notes).
• Signature field, for formal confirmations (e.g. customer agreement to the consultation outcome). You choose who signs: the user, the customer, or another party.

Choose from this fixed set of building blocks when you author a template.

Image element settings

Per image element, you can configure:

• Allow images, PDFs, or both.
• Bulk upload (multiple files at once) or single upload.
• Store example images the user sees before capturing, useful for "here's what the existing heating's nameplate should look like."

Adapt checklists to your internal processes

Each installer company keeps its own checklist templates in its own workspace, so you can encode your own consultation process. Two layers of adaptation:

Workspace-wide template edits

Edit the template in Settings > Checklists and every new project picks up the change.

1. Open Settings > Checklists.
2. Open the page for the phase you want to adapt (Qualification / Consulting / Site documentation).
3. Add, remove, or reorder elements to match your team's process, e.g. add a "Customer signed consultation summary" signature element if your sales process ends with a sign-off, or insert a "Existing PV system" selection if you want consultants to flag retrofit opportunities.
4. Save. New projects from this point forward use the updated template; in-flight projects keep their existing version.

This is the right path when the change reflects your company's standard process and should apply going forward.

Note: Some templates are locked against edits. If a template won't let you edit it, contact Reonic support.

Per-project customisation

For one-off projects with unusual requirements (a commercial roof needing extra steps, a customer-specific signature flow), an admin can customise the checklist on a single project without changing the template.

1. Open the project in the Portal.
2. Open the checklist view.
3. Use the per-project edit affordances to add, rename, or remove elements. All the same building blocks are available.
4. Save. The change applies only to this project; the template is untouched.

Per-project customisation opts the project out of automatic template-refresh: once customised, the project keeps its own checklist and later template updates stay with the template. Use per-project customisation for exceptions; promote recurring exceptions into the template itself.

Generate a template with AI

If you have an existing checklist (a PDF, an image of a paper form, a CSV from another tool), the AI checklist builder can bootstrap a template from it.

1. Open the checklist editor for the phase you want.
2. Click the AI button (sparkles icon, splash CTA when the template is empty, floating sidebar button when content already exists).
3. Drop your source file(s) into the import form and optionally describe what you need in the prompt (e.g. "Heat-pump consultation checklist with all key assembly steps, German labels").
4. Submit. The AI streams a complete template live, you'll see segments and items appear progressively in the preview.
5. Accept and import. The generated block is appended to your editor without overwriting existing segments.
6. Click Save in the editor to persist the imported block. The block lives in form state until you save, so save before you leave the page.

Pro tip: Use AI generation as a starting point, then trim. AI-generated checklists tend to be over-comprehensive; an installer's time is better spent on a focused 15-item list than a sprawling 40-item one. Write a specific prompt: name the language ("German labels") and the structure you want ("separate segments for pre-installation, installation, commissioning") for cleaner output.

Note: Save the imported block before navigating away or closing the tab, since it lives in form state until you click Save. Work in one browser tab at a time when using the AI builder on a checklist, as two tabs on the same checklist can overwrite each other.

Note: The AI builder is available to admin users. Account managers and field workers use the standard building blocks to author templates. To turn on the AI builder for your workspace, contact Reonic support.

Things to know

• One template per phase, separate from the others. Editing the Consultation template doesn't change Qualification or Site documentation, author each phase separately.
• Template edits apply forward, not retroactively. In-flight projects keep their existing version. To pull a template update onto an existing project, use the per-project update path on Site documentation (Installation).
• A template update preserves what's already filled in. When you pull a template update onto an in-flight project, the filled-in values carry over: freetext, selections, attachments, marked-irrelevant flags, and captured signatures are all preserved. A merge does not force your customer to re-sign.
• Required elements gate completion. A checklist can be marked complete once every required element is filled. Mark elements required when they're load-bearing for downstream pricing, planning, or compliance.
• Per-project customisation breaks the auto-refresh link. Once a project's checklist is per-project customised, it keeps its own version and later template updates stay with the template. Use customisation sparingly for one-off exceptions; promote recurring patterns into the template.
• AI generation is admin-only. The AI builder is available to admin-or-above. The generated block is appended to your editor and persists after you click Save in the editor.
• Consultation checklists are Mobile App compatible. Your consultants can fill the consultation checklist directly on the Reonic Mobile App during the on-site appointment, with all the same building blocks (photos, signatures, freetext).

Related

• Lead (Qualification), the qualification checklist on the request.
• Site documentation (Installation), the site-documentation checklist on the installation + how to re-merge a template update onto an in-flight project.
• Checklists overview, the three phases at a glance.

Need help?

• Step-by-step questions about this flow → contact your Reonic account manager.
• Feature requests / something missing → drop a note to your account manager.
• Bug reports → include a screenshot + the URL where it happened in your support email.

Last updated on August 4, 2026