# Remote IT Before/After Report Template

Customer:
Date:
Package:
Machine:

## 1. Starting condition

- Reported issue:
- Storage status:
- Startup/app clutter:
- Browser/tool clutter:
- Backup status:
- Important folders/apps to avoid:

### Browser task baseline (when relevant)

Use non-sensitive aliases and setting names/status only. Do not retain private URLs, page contents, screenshots, passwords, or personal/regulated records. Blank fields are not evidence: write UNKNOWN, not observed, or not applicable with a reason. This evidence procedure does not change the purchased package, time box, terms, or exclusions.

- Task alias / exact observable symptom:
- Browser/version / profile alias / visible Windows version:
- Repeatable steps (no private content):
- Start/finish markers / observation method (seconds if observable; otherwise specific qualitative observation or UNKNOWN):
- Conditions to match: same page/workload alias, tab count, network connection, cache/warm-up state, background apps:
- Only intended difference: explicitly logged approved change being tested; other condition differences make pairs not comparable:
- Prior attempted fixes / result / approximate time / customer-reported vs observed:
- Restrictions / unknowns / safe eligibility:
- Agreed customer retest workflow / interruption to check:

## 2. Actions approved

- [ ] Storage review
- [ ] Startup app review
- [ ] Browser extension review
- [ ] Installed app review
- [ ] Downloads/Desktop organization recommendation
- [ ] AI starter setup
- [ ] Other:

These boxes approve review categories only, not every change. Obtain affirmative customer approval before each reversible change after explaining the prior setting, proposed change, reason, and rollback. If approval or safe rollback is unavailable, do not change it.

| Change ID | Prior setting | Proposed change / reason | Affirmative approval + time | Applied / declined / rolled back | Rollback steps / verification |
|---|---|---|---|---|---|
|  |  |  |  |  |  |

Record customer-approved rollback and observed restoration separately; unknown restoration is not success. Do not log sensitive setting values. Destructive deletion is not a reversible browser experiment; do not use it as one or disable security protections/bypass managed controls.

## 3. Changes made

| Area | Before | After | Notes |
|---|---|---|---|
| Storage |  |  |  |
| Startup |  |  |  |
| Browser |  |  |  |
| Apps |  |  |  |
| AI setup |  |  |  |

### Matched browser task observations

Run three trials before changes and three after using the agreed steps/markers/method. Retain failures and slower trials. Do not invent timing, average away regressions, or claim causal/durable gains. If conditions differ, write not comparable and explain; if a trial is missing, state why. Link applied/rolled-back change IDs; observations alone do not prove the suspected bottleneck caused the symptom.

- Applied/rolled-back change IDs / suspected bottleneck and evidence (or UNKNOWN):

| Trial | Before observation | After observation | Conditions matched? | Regression / interruption |
|---|---|---|---|---|
| 1 |  |  |  |  |
| 2 |  |  |  |  |
| 3 |  |  |  |  |

## 4. What was not touched

- 

## 5. Risks / recommendations

- Backup:
- Security:
- Hardware:
- Software:
- Follow-up:

## 6. Customer handoff

- Summary:
- What to do weekly/monthly:
- What to avoid:
- Recommended next service, if any:

- Approved rollback instructions handed off / observed verification / unverified restoration:
- Unresolved items / retained or rolled-back changes:
- Unknowns / missing or not-comparable observations:
- Out-of-scope items / stop reason / what was not performed:
- Next safe step / customer acknowledgment (no additional scope or unlimited follow-up implied):

## 7. Completion confirmation

Customer confirmed:

```text
Satisfied / needs follow-up / unresolved issue
```

### Browser task outcome (separate from satisfaction/payment)

- Customer retest: workflow attempted / original interruption absent or remains / regression / not completed and reason:
- Outcome: UNKNOWN / UNRESOLVED / STOPPED_OUT_OF_SCOPE / OBSERVED_IMPROVEMENT
- Evidence and limitations supporting selected outcome:

If multiple conditions apply, choose STOPPED_OUT_OF_SCOPE for a scope/time stop first, then UNKNOWN for insufficient evidence, then UNRESOLVED for measured failure. Preserve every reason; improvement is never the default.

Use OBSERVED_IMPROVEMENT only for a reproduced slowdown with all three matched pairs, at least two observably faster after trials, no task regression in any trial, and a customer retest completing the required workflow without the original interruption. Qualitative observations need explicit descriptions, not invented numbers. This is session-specific, not proof of causation, a durable fix, or a warranty. State if no change was made. Incomplete/non-comparable evidence or incomplete retest is UNKNOWN; remaining failure or failure to meet the improvement rule is UNRESOLVED. Excluded work or time-box exhaustion requiring further work is STOPPED_OUT_OF_SCOPE. Do not label these outcomes fixed. Report delivery/satisfaction/payment is not proof of improvement.