WINHOVEN · AUTOPILOT PILOT EVIDENCE MAP
Purpose: compare existing evidence and gaps across chosen working situations.
This is an original Winhoven planning aid, not a required Microsoft test suite.
It does not establish readiness, representative coverage or approval to run tests.

Intended first-day user task and expected outcome:
Deployment flow and mode (administrator-confirmed / unknown):
Flow confirmation source and date:
App set/configuration version or private reference:
Observation window:
Evidence owner and approved private support location:

STATE KEY
Applicability: Yes / No (record the reason) / Unknown
Evidence recorded = dated observation + traceable reference, NOT a pass.
Keep failed, partial or contradictory observations with their limitations.
Not yet tested = responsible owner confirms an applicable planned test was not performed.
Do not infer Not yet tested from an empty worksheet.
Unknown = applicability, execution or evidence availability is not confirmed.
Missing evidence is not a failure; nonapplicable is not a pass.

1. REMOTE STARTER
Question: What was observed from initial setup through the expected usable desktop on the intended remote connection? Separate user observation from the matching administrator report.
Applicable: Yes / No (reason) / Unknown
Evidence state: Evidence recorded / Not yet tested / Unknown
Expected outcome:
Actual observation and limitations (or Unknown):
Private evidence reference, time/time zone and relevant context:
Next evidence question:
Named owner or Owner unknown:
Next authorized read-only check or approval needed:

2. BRANCH STARTER
Question: Is there evidence for the intended branch path? Keep context privately. Do not assume remote results apply or infer a network cause from different results.
Applicable: Yes / No (reason) / Unknown
Evidence state: Evidence recorded / Not yet tested / Unknown
Expected outcome:
Actual observation and limitations (or Unknown):
Private evidence reference, time/time zone and relevant context:
Next evidence question:
Named owner or Owner unknown:
Next authorized read-only check or approval needed:

3. REQUIRED APPLICATION
Question: Which intended first-day task was observed working? Keep setup/reporting or detection evidence separate from application usability. Installed alone does not answer this question.
Applicable: Yes / No (reason) / Unknown
Evidence state: Evidence recorded / Not yet tested / Unknown
Expected outcome:
Actual observation and limitations (or Unknown):
Private evidence reference, time/time zone and relevant context:
Next evidence question:
Named owner or Owner unknown:
Next authorized read-only check or approval needed:

4. SUPPORT HANDOFF IF SETUP STOPS
Question: Is an existing contact/escalation path recorded, with an owner able to review the exact flow, stage, time and approved evidence? Do not force a failure, wipe, recover or bypass setup for this row.
Applicable: Yes / No (reason) / Unknown
Evidence state: Evidence recorded / Not yet tested / Unknown
Expected outcome:
Actual observation and limitations (or Unknown):
Private evidence reference, time/time zone and relevant context:
Next evidence question:
Named owner or Owner unknown:
Next authorized read-only check or approval needed:

SUPPORT-PATH NOTE
For a documentation-only support-path row, record an actual owner/path or mark Unknown.
No artificial execution test is required. Not yet tested only describes a planned rehearsal
when its responsible owner confirms that it has not been performed.

Keep identifiers, hardware hashes and raw logs in your approved private support workspace.
These four prompts are not exhaustive. Do not infer the deployment flow from ESP alone.
A new test requires its own authorization. No device, access, policy or deployment change
is authorized by this note.