# Contractor Website Requirements Worksheet

Use this worksheet before requesting a website proposal. Short, specific answers are more useful than polished marketing copy. This file is provided by Battle Bound Branding without an email gate.

Guide: https://battleboundbranding.com/resources/contractor-website-planning-guide

## 1. Business foundation

- Best-fit customer:
- Priority job types:
- Jobs that are not a fit:
- Real service area and travel limits:
- Business hours:
- Emergency or after-hours availability:
- Expected response time:
- Primary website action (call, estimate request, booking, or another action):
- What makes an inquiry qualified:

## 2. Page requirements

Mark each page as required, later, or not needed. Add the customer question the page must answer.

| Page | Required / Later / No | Customer question or business job |
| --- | --- | --- |
| Homepage | | |
| Service overview | | |
| Priority service page 1 | | |
| Priority service page 2 | | |
| Priority service page 3 | | |
| About / team | | |
| Projects / gallery | | |
| Reviews / proof | | |
| Service area | | |
| Selected city or location pages | | |
| Contact / request estimate | | |
| Financing | | |
| Warranties | | |
| Careers | | |
| Privacy / legal | | |

## 3. Homepage first screen

- Plain-language service statement:
- Customer type:
- Geography:
- Primary call to action:
- Secondary contact path:
- One or two verified trust signals:
- Real hero image available? If not, who will create it?

## 4. Priority services

For each priority service, record:

- Customer problem or goal:
- Jobs included:
- Jobs excluded:
- What changes the scope or price:
- Delivery or estimate process:
- Relevant project proof:
- Relevant review or credential:
- Common questions:
- Best next action:

Repeat this section for each service that may need its own page.

## 5. Service-area plan

- Cities, ZIP codes, counties, or other areas actually served:
- Areas not served:
- Travel fees, limits, or scheduling differences:
- Staffed customer-facing locations:
- Address that should be public:
- Address that should remain hidden for a service-area business:
- Locations with enough distinct information and proof for a useful page:
- Business Profile owner and manager access:

Do not invent offices, local teams, projects, or customer outcomes.

## 6. Trust and content assets

- [ ] Business name, phone, email, hours, and service details confirmed
- [ ] Logo source files and brand colors collected
- [ ] Crew and owner portraits collected
- [ ] Branded vehicle and jobsite photos collected
- [ ] Before-and-after pairs collected from the same angle
- [ ] Project notes and publication approvals recorded
- [ ] Customer reviews retained with source records
- [ ] Licenses and insurance claims verified
- [ ] Warranties and guarantees reviewed for exact terms
- [ ] Memberships, certifications, and manufacturer relationships verified
- [ ] Privacy-sensitive visual details reviewed
- [ ] Original high-resolution files stored in a company-controlled account

Missing proof or assets:

Owner and due date for each missing item:

## 7. Quote form and lead flow

- Primary form purpose:
- Required fields and why each is needed:
- Optional fields and why they help:
- File uploads, limits, and handling:
- Consent or disclosure requirements to review:
- Spam and abuse controls:
- Success message and response expectation:
- Error handling and fallback contact path:
- Durable lead-record destination:
- Notification recipients:
- Lead owner:
- Missed-notification recovery path:

Map the flow:

`Visitor action → validation → durable record → confirmation → assignment → follow-up → status → next action`

## 8. Measurement plan

| Action | Event or record | What it means | Important limitation | Owner |
| --- | --- | --- | --- | --- |
| Phone-link click | | | Does not prove a connected call | |
| Form success | | | Does not prove a qualified lead | |
| Estimate scheduled | | | Requires CRM or scheduling reconciliation | |
| Qualified inquiry | | | Requires an agreed definition | |
| Won / lost job | | | Requires consistent status updates | |

- Analytics account owner:
- Search Console account owner:
- Call-tracking owner and number-portability plan:
- Recording disclosure and retention requirements to review:
- Internal and test traffic plan:
- Production test inquiry procedure:

## 9. CRM and follow-up

- Source of truth for leads:
- Required lead fields:
- Pipeline stages:
- Owner at each stage:
- Expected next action at each stage:
- Automations to add:
- Human approval or escalation points:
- Retry and failure behavior:
- Manual fallback:
- Export and offboarding procedure:

## 10. Accessibility, performance, and security

- [ ] Navigation and form can be completed by keyboard
- [ ] Focus is visible and not hidden behind sticky controls
- [ ] Form controls have visible labels, instructions, and useful errors
- [ ] Mobile, zoom, contrast, reduced motion, and touch targets are reviewed
- [ ] Images are responsive, compressed, and given useful alternative text
- [ ] Third-party scripts and fonts are justified
- [ ] LCP, INP, and CLS are measured on production pages
- [ ] HTTPS and secure headers are reviewed
- [ ] Input is validated on the server
- [ ] Secrets remain server-side
- [ ] Access follows least-privilege rules
- [ ] Dependencies, backups, monitoring, logging, and recovery are assigned

## 11. Ownership and handoff

Record the company owner and any agency access for each system.

| Asset or account | Company owner | Agency role | Billing owner | Recovery method documented? |
| --- | --- | --- | --- | --- |
| Domain registrar | | | | |
| DNS | | | | |
| Hosting / deployment | | | | |
| Source-code repository | | | | |
| Analytics / tag manager | | | | |
| Search Console | | | | |
| Business Profile | | | | |
| CRM / lead store | | | | |
| Call tracking | | | | |
| Scheduling / payments | | | | |
| Original photos and files | | | | |

- Maintenance owner after launch:
- Content owner after launch:
- Lead-response owner after launch:
- Backup and recovery owner:
- Support scope and exclusions:
- Source files and documentation required at handoff:
- Vendor termination and export terms:

## 12. Launch acceptance

- [ ] Final copy, claims, photos, and business details approved
- [ ] Placeholder content removed
- [ ] Navigation, phone links, forms, uploads, scheduling, and payments tested
- [ ] Success, error, duplicate, invalid, and failed-notification paths tested
- [ ] Mobile and desktop production views reviewed
- [ ] Keyboard, focus, labels, contrast, zoom, and reduced motion checked
- [ ] Titles, descriptions, headings, canonicals, redirects, and internal links checked
- [ ] Structured data, sitemap, robots rules, and index settings verified
- [ ] Production analytics, call routing, source data, and test leads verified
- [ ] CRM owner, statuses, next actions, and fallback paths confirmed
- [ ] Account inventory, backups, monitoring, documentation, and handoff accepted
- [ ] Post-launch review date scheduled

## 13. Questions for an agency

1. Who owns the domain, hosting, source code, analytics, business profiles, and connected accounts?
2. Who writes and approves the content? What inputs and proof are required from us?
3. What is included in accessibility, performance, security, SEO, and production testing?
4. How are forms stored, routed, protected, and recovered if notifications fail?
5. How are calls, forms, qualified leads, and booked work distinguished in reporting?
6. What CRM or automation work is included, and what happens when an integration fails?
7. What source files, documentation, credentials, and training are included at handoff?
8. What maintenance is required, who performs it, and what is excluded?
9. How are change requests, licenses, third-party fees, and termination handled?
10. Which claims or results can the agency support with evidence, and which outcomes cannot be guaranteed?

## 14. Decision record

- Project owner:
- Decision makers:
- Target launch window and reason:
- Budget planning range:
- Known dependencies:
- Known legal, regulatory, accessibility, or data requirements to review with qualified professionals:
- Definition of done:
- Next action:
- Owner:
- Due date:

---

Battle Bound Branding provides this worksheet as an educational planning resource. It is not legal, compliance, security, or accessibility certification advice, and it does not promise rankings, leads, revenue, or conversion results.