From Documents to Executed Actions. Post-Workshop Brief

A closed workshop at the Solar Quality Summit Europe 2026, co-organised by SolarPower Europe and Intersolar.

Workshop facilitators

<aside> 🐿️

Aevy — AI-powered unstructured information management for renewable energy assets

Gautier Moulin — [email protected] | aevy.io

</aside>

<aside> ☀️

SolarNotions OS — [Călin to add description]

Călin Sas — [Călin to add email] | solarnotions.com

</aside>

For Workshop Attendees

Thank you for joining us at SQS Europe 2026. Below you'll find everything we covered — the framework, a self-assessment scorecard, a best-practices cheat sheet, and the standards we referenced. Bookmark this page and come back to it when you're ready to act.

Didn't Attend? Here's What You Need to Know

<aside> 📌

In a 40-minute hands-on workshop, participants worked with realistic solar asset documents — commissioning reports, O&M contracts, SCADA exports, contractor emails — under time pressure. Two teams tackled two different scenarios:

Onboarding teams received a post-PAC handover document package and had to extract everything an operations team would need on day one.
Operations teams received a month of operational documents and had to produce a clear picture for the asset manager.

Afterwards, the teams compared outputs. The result was always the same: neither team produced what the next person in the chain actually needed. Critical items were missed, cross-references were overlooked, and the gap between "having documents" and "having operational intelligence" became physically visible on the table.

The workshop then introduced a four-layer framework — Extraction, Structuring + Cross-Referencing, Validation, and Orchestration — as a systematic way to close that gap. Everything below unpacks that framework and gives you tools to assess and improve your own operation.

</aside>

The Documentation-to-Action Framework

Everything in the workshop maps to four layers. If you remember one thing, remember this chain:

DOCUMENTS → [EXTRACTION] → STRUCTURED DATA → [CROSS-REFERENCING] → [VALIDATION] → INSIGHTS → [ORCHESTRATION] → ACTIONS
      ↑                                                                                                    ↓
      └──────────────────────────────────────── FEEDBACK LOOP ─────────────────────────────────────────────┘

The four layers — and the questions they answer

Layer	Question	In the exercise	In your real operation
1 — Extraction	What does this document contain?	You read the fragments and pulled out data (scissors)	Manually typing from PDFs into spreadsheets
2 — Structuring + Cross-Referencing	How does it relate to everything else?	You organised info on the A3 sheet and (hopefully) compared across documents	Normalising reports, linking equipment to warranties and history
3 — Validation	Can we trust this?	Blue post-its — "Does this match the SCADA data?"	Cross-checking contractor data against independent sources
4 — Orchestration	Who does what, by when, tracked where?	Yellow post-its — work orders with owners and deadlines	Auto-generated, assigned, tracked, and closed actions

The key insight from the exercise: documentation failures don't just create gaps in your own work. They create gaps for the next person in the chain — the operations team that inherits a bad handover, the asset manager who receives an unvalidated report, the buyer who can't verify compliance history.

Workshop facilitators

For Workshop Attendees

Didn't Attend? Here's What You Need to Know

The Documentation-to-Action Framework

The four layers — and the questions they answer

Where Documents Break in the PV Lifecycle