Skip to content
Back to Marketing
Marketing

Solar Case-Study Source Collection Workflow: Commissioning to Interview

Collect solar case-study sources from installed scope and commissioning to operating data, technical interpretation and an approved customer interview.

Arshia Jahangiri
3 min

Table of contents

A solar case-study source collection workflow helps a Canadian contractor assemble evidence before writing. Begin with the project record, then collect measured data, technical interpretation and the customer’s actual account. The output is an indexed source packet, not a finished success story.

Start at commissioning and handover

Identify the installed configuration, relevant completion milestones, test records and final scope. Keep the signed offer and later accepted changes so a writer can distinguish the original plan from the delivered work.

Assign a collection owner. Ask project contributors for the records they actually control, rather than inviting a marketer to reconstruct technical facts from memory. Use the existing project identifier across the source packet.

Collect sources in a traceable sequence

Collection step Source to obtain Check before use
1. Installed scope Final equipment list, layout and accepted changes. Does it describe the as-built project?
2. Delivery evidence Commissioning, approval and handover references. Which milestones do the records actually establish?
3. Operating data Original exports and relevant billing records for the proposed period. Are dates, units, gaps and account boundaries clear?
4. Context Known changes in occupancy, equipment, tariffs or building work. Which comparisons need qualification?
5. Technical interpretation Reviewer notes and reproducible calculations. Does the proposed statement follow from the sources?
6. Customer account Interview notes, exact quotations and permitted uses. Are recollection, measured fact and publication permission separated?

Give each source a reference, date, contributor and access restriction. Preserve original records alongside working extracts. Redact unnecessary identifiers in public materials without discarding the controlled evidence needed for review.

Interview after checking the file

Use the project record to ask specific questions: what concern led to the work, which decision changed the scope, what was disruptive, and what does the owner understand better now? Do not write praise and ask the customer to validate an invented quotation.

If memory conflicts with a record, retain the question and seek clarification. An experience can be reported as the person’s account without being converted into a verified technical result.

Work an incomplete-data example

In a fictional source packet, commissioning is documented but a monitoring gap affects the proposed operating period. Record the gap, the known cause if supported, and which statements remain possible. The packet may support installation and handover details without supporting a complete annual production claim.

The performance-claim guidance helps frame review of promotional results. Missing evidence should become a limit or an assigned enquiry, not a plausible number supplied by the writer.

Release a source packet to the writer

Include a claim/source/limitation index, unresolved questions, reviewed calculations and approved customer material. Follow meaningful-consent guidance for the proposed use and sharing.

Keep the collection task separate from the article brief and narrative outline. A later update should return to this packet so new claims can be traced to new evidence.

Share this article