# Case Study Evidence Template

Collect this information during the project. Do not wait until launch, when screenshots, decisions, and baseline data may already be lost.

## Project identity

- Client or project name:
- Engagement type: real client / internal product / concept
- Industry and audience:
- Project dates:
- Battle Bound team and roles:
- Client approval to publish: yes / no / pending

## Overview

Describe the organization, audience, and scope in plain language.

## Before state

- What was observable before the work began?
- Which screenshots, analytics exports, search reports, or workflow records prove it?
- What should not be claimed because it was not measured?

## Challenge

- What prevented the desired action or outcome?
- Who experienced the problem?
- What constraints shaped the work?

## Goals

- Primary objective:
- Secondary objectives:
- Agreed success measures:
- Measurement owner and source:

## Process and decisions

For each major stage, record the decision, the reason, and the approval.

1. Discovery:
2. Strategy:
3. Design:
4. Implementation:
5. Testing:
6. Launch:
7. Follow-through:

## Technologies

List only technologies actually used on the project and explain what each one supported.

## Implementation

- Deliverables completed:
- Integrations connected:
- Content created or migrated:
- Tracking configured:
- Documentation or training delivered:

## Screenshots and artifacts

- Before screenshots:
- Approved designs:
- Desktop implementation:
- Mobile implementation:
- Workflow or dashboard screenshots:
- Launch evidence:

## Verified outcomes

For every number, record the source, date range, baseline, comparison period, and client approval.

- Metric:
- Baseline:
- Result:
- Source:
- Date range:
- Approved to publish:

If no verified outcome is available, state that clearly and omit the metric from public copy.

## Client feedback

- Verbatim quote with written permission:
- Accurate feedback summary if no verbatim quote exists:
- Date received:
- Approved attribution:

## Lessons learned

- What decision worked well?
- What would change next time?
- What should future clients know?
- Which lesson is supported by the project record rather than hindsight alone?

## Publication review

- [ ] Client identity and relationship labeled accurately
- [ ] Concept work cannot be mistaken for a real client
- [ ] Every metric has a source
- [ ] Quotes are verbatim and approved
- [ ] Confidential information removed
- [ ] Technology list verified
- [ ] Screenshots approved
- [ ] Links tested
- [ ] Final client approval recorded