# Home Front fiber field-sales working templates

Published October 21, 2026. These are blank, manual working tools. They contain no customer data, production benchmarks, preset results, promised staffing or carrier integration. Agree the fields, access and definitions with the actual provider and commercial owners before using them for a live program.

## Scope worksheet

CSV: https://www.homefrontsolutionsllc.com/downloads/fiber-field-sales-rfp-scope-template.csv

Canonical guide: https://www.homefrontsolutionsllc.com/insights/fiber-field-sales-rfp-scope-of-work-template/

Use one row per procurement requirement. Complete buyer requirements before comparing proposals.

- `requirement_id`: stable internal reference for this scope line.
- `scope_area`: operating category, such as authority, people, offer, systems, reporting or closeout.
- `buyer_requirement`: the buyer's requested work and boundaries.
- `provider_dependency`: information, approval, access or capacity the provider must supply.
- `proposed_partner_deliverable`: the vendor's concrete response, including exceptions.
- `acceptance_evidence`: observable record or demonstration used to assess the deliverable.
- `accountable_role`: the role responsible for this line; agree the named owner separately.
- `commercial_treatment`: included work, separate charges, pay-event treatment or an unresolved commercial question.
- `open_question`: what still needs an answer; exclude customer details.
- `decision_status`: an agreed review status, such as draft, clarification needed or approved. A worksheet status is not a signed agreement.
- `review_date`: next review date, using an agreed date format.

## Territory-release log

CSV: https://www.homefrontsolutionsllc.com/downloads/fiber-territory-release-log-template.csv

Canonical guide: https://www.homefrontsolutionsllc.com/insights/fiber-territory-release-change-control-template/

Use one row per release or change event. Preserve prior rows instead of overwriting authorization history. This is a cohort-level release log, not an address-level serviceability dataset.

- `event_id` and `prior_event_id`: this event and the earlier event it changes, if any.
- `internal_cohort_id`: approved internal identifier for the address set, not customer contact or account information.
- `source_version`: the provider qualification source/version supporting the event.
- `release_version`: the operating instruction version issued to the field.
- `requested_state`: agreed route state. Suggested distinctions are draft, released, hold, withdrawn and superseded; map them to existing provider codes where appropriate.
- `reason`: confirmed reason for the event, or a clearly marked unresolved question.
- `effective_at` and `time_zone`: when the change begins to apply. Use an unambiguous timestamp and time zone.
- `provider_owner_role` and `field_owner_role`: who authorizes the event and who makes it operational.
- `approved_at` and `acknowledged_at`: approval and receipt evidence; a published message alone does not show acknowledgment.
- `evidence_reference`: approved internal record reference with restricted access. Do not include secret access tokens or public customer links.
- `next_action` and `next_review_at`: follow-up responsibility and review time.

## Order-to-install tracker

CSV: https://www.homefrontsolutionsllc.com/downloads/fiber-order-install-tracker-template.csv

Canonical guide: https://www.homefrontsolutionsllc.com/insights/fiber-order-to-install-reconciliation-template/

Use one row per internal order record in a current operating snapshot. Agree whether reporting counts orders, service locations or another unit. Preserve controlled snapshot history; this blank CSV is not a complete event audit system.

Use internal order IDs in shared trackers and exclude customer contact, account and payment data. Keep any necessary identity lookup in the approved system. Restrict completed files and evidence to authorized program users.

- `internal_order_id`: approved internal record reference.
- `related_internal_order_id` and `relationship_type`: duplicate, correction or replacement relationship, where confirmed. Do not count or pay the same outcome twice.
- `cohort_id` and `territory_release_version`: the selling cohort and field authorization relevant to the record.
- `submitted_at`: source-supported submission time.
- `provider_status`: current provider-confirmed status; do not replace it with a field estimate.
- `provider_accepted_at`, `appointment_at`, `provider_completed_at`, `provider_cancelled_at`: confirmed stage timestamps when applicable. Leave unknown or inapplicable values blank rather than inventing a time.
- `provider_reason_code`: confirmed provider code, not an assumed root cause.
- `field_status`: field snapshot kept separately so a disagreement stays visible.
- `source_system` and `source_checked_at`: where and when the provider status was verified.
- `as_of_at` and `time_zone`: the reporting observation time and agreed time zone.
- `exception_opened_at`, `exception_owner_role`, `next_action`, `next_review_at`: responsibility for an unresolved issue.
- `commercial_review_status`: review under the written pay event. A completed install is not automatically payable unless the agreement says so.

Proposed metrics to agree before use:

- Acceptance rate: provider-accepted records divided by submitted records in the same defined cohort and counting unit.
- Observed completion rate: confirmed completed records divided by accepted records in that cohort, with its age and as-of date disclosed.
- Mature-cohort completion rate: confirmed completions divided by accepted records meeting a pre-agreed observation rule. Disclose exclusions and do not present it as the full-cohort rate.
- Open-exception age: as-of time minus confirmed exception-open time, using consistent time zones.
- When a denominator is zero, report not available rather than a calculated percentage. Never silently remove unresolved records to improve a result.

## Reuse and credit

You may copy, adapt and share these Home Front-authored blank templates and their checklist definitions for internal operations or educational resources with clear credit to Home Front Solutions and a link to the relevant canonical guide above. This permission excludes third-party content, provider marks and logos. It does not imply a provider endorsement or authorize use of customer data. When sharing an adapted version, identify your changes rather than presenting them as Home Front's original method.

## Contact and applications

Business program review: https://www.homefrontsolutionsllc.com/contact/?category=Fiber%20Internet

Call us: (336) 420-9379

Existing local, travel and blitz recruiting hub: https://www.homefrontsolutionsllc.com/jobs/1099-field-sales/