Agree what a useful evaluation must prove

This is a discussion checklist, not a certification, contractual service commitment or promise of every requested integration. Use synthetic or authorized data initially; arrange appropriate handling before sharing live customer files.

1. Name the project decision

   Choose the workflow stage: a customer proposal, a CAPEX/RESCO comparison, a fixed-table terrain study, or a reviewed handoff. Identify the designer, commercial reviewer, owner and person accepting the result.

2. Agree the input evidence

   For commercial work, identify supported interval data, bill quality, tariff dates, meter direction and CT/PT basis, pricing and ownership assumptions. For terrain, establish coordinates, vertical basis, units, control coverage, independent checkpoints and equipment geometry.

3. Choose the actual receiving files

   List the proposal, report, BOM, SLD, DXF or workbook the next person needs. Open supported outputs in that person's tools and reconcile equipment IDs, units, quantities, revision and missing-output warnings. Scope new exchange formats separately.

4. Set acceptance before comparing results

   Agree purpose-specific tolerances and independent references with qualified reviewers. Record table and panel counts, terrain detail, hardware, timings and failure recovery. A scene that renders does not by itself establish large-project capacity or numerical accuracy.

   Keep direct-sunlight screening separate from annual energy. Civil quantities, structure, drainage, electrical code and geotechnical acceptance require their own appropriate evidence.

5. Review access, revisions and data handling

   Inspect organization membership, roles, review history, deliberate support access and supported retention/recovery controls. Confirm provider and entitlement conditions for the workflows being evaluated.

   Record requirements such as SSO, multi-site reporting, certifications, contractual support or recovery terms for assessment. Existing role controls do not imply those requirements are already met. Read the implemented security overview and privacy notice.

6. Record the result and the next scope

   Keep the input/version basis, discrepancies, rejected outputs and reviewer decision together. Decide whether the tested stage is useful and identify one next improvement. Agree any live rollout and support responsibilities explicitly.

Explore the installer example · Explore the commercial and terrain examples

Use your browser's Print command to save this checklist for the evaluation discussion.