Buyer decision guide
Motorized Shade Site Commissioning Acceptance Checklist
Record installed opening, mechanical operation, commands, feedback, exceptions, retests and release status without pre-filling a PASS.
Quick Answer
Commissioning acceptance records the installed result at the actual opening. Start with the released configuration and any bench-test baseline, then verify mechanical operation and only the functions applicable to the selected control path. Use PASS, FAIL, NOT_TESTED or NOT_APPLICABLE. Record exceptions, owners and retests before the named authority releases that scope.
Bench Test and Site Commissioning Are Different
| Record | Where / purpose | Does not prove |
|---|---|---|
| A27 bench record | Representative hardware before site repetition | Installation, field wiring, final grouping or site network behavior |
| Site commissioning dossier | Installed opening under field power/control conditions | Long-term performance, unrelated openings or functions not tested |
| Handover index | Transfers accepted records and ownership | That every open issue is closed unless listed as such |
Site Commissioning Acceptance Dossier
| Domain | Record | Result field |
|---|---|---|
| Identity | Opening ID, approved configuration, installed motor/controller/version | PASS/FAIL/NOT_TESTED/NOT_APPLICABLE |
| Mechanical | Mounting, unobstructed travel and applicable stops/limits | Observed result and exception |
| Local command | Open, close, stop and local fallback where applicable | Expected / observed |
| Group / preset / scene | Only functions in the approved selected path | Expected / observed |
| Feedback / central control | Only documented interface and feedback expectations | Expected / observed |
| Network-dependent operation | Defined onsite/remote path and applicable failure behavior | Expected / observed |
| Release | Open issue, retest reference, responsible party and authority | Held / partial / accepted per signed record |
Use Status Words Precisely
PASS
Observed result meets the agreed criterion for this configuration and revision.
FAIL
Observed result does not meet it; record owner and corrective/retest reference.
NOT_TESTED
No evidence was collected. It is not a pass.
NOT_APPLICABLE
Function is outside the approved configuration; include the reason.
Exception and Retest Loop
- Record the field condition and exact opening.
- Separate mechanical, power, interface, programming and network observations.
- Assign the issue to the responsible project party; do not diagnose from status alone.
- Reference the corrected revision or action.
- Retest only affected criteria and preserve prior results.
- Release only the scope named by the acceptance authority.
Download the Site Acceptance Record
Download Site Commissioning Acceptance Dossier (XLSX)
All result cells default to NOT_TESTED or blank. No PASS is pre-filled. The workbook separates openings, issues and retests.
For coordination across pre-wire, installation, commissioning and handover, use the Pre-Wire & Commissioning Checklist. Record results only after the actual check.
What Saiwenna Can Review
| Buyer provides | Saiwenna reviews | Output |
|---|---|---|
| Released equipment/configuration and opening IDs | Supplied-scope identity and documentation | Identity discrepancies and required evidence |
| Expected functions and bench reference | Model/interface boundaries | Applicable-function questions |
| Field results, photos and issue log | Observed symptom against supplied scope | Technical information for responsible-party review; not blanket site approval |
Send a Reviewable Brief
Send opening/configuration list, approved functions, bench reference, field exceptions, retest owners and intended release authority.