Fiber order-to-install reconciliation: a worksheet for accountable field sales
Reconcile fiber field orders against provider-confirmed installations, open exceptions and corrections. Includes a blank tracker and metric definitions.
Order-to-install accountability starts with a record that both field operations and the provider can reconcile. A rep's submission is not yet an accepted order, an appointment is not a completed installation, and an installation does not automatically establish the commercial payment event. This worksheet helps an ISP and its field partner connect those stages using internal IDs, source timestamps and a defined observation date. It complements the pilot scorecard: the scorecard defines what to measure, while this tracker shows which records support the count and which still need action.
Choose the counting unit before importing records
Agree whether the analysis counts orders, unique service locations, accounts or another unit. A household can have multiple submissions, and a corrected order can receive a new reference. Without a written rule, the field team can count both while the provider reports one installation. Keep the source IDs and the relationship between a replaced and replacement record; do not erase the history to make totals match.
The blank CSV uses one row per internal order record for a current operating snapshot. It includes a related-record field for duplicate or replacement references. Preserve the provider's order history or a separate controlled snapshot history rather than treating the latest CSV as a complete audit log. Before reporting, resolve how multiple rows contribute to the agreed counting unit.
Keep stage, evidence and owner together
A status without a source and timestamp is difficult to verify. Keep the provider's current status beside the field's last recorded status so differences remain visible. Record the source-system check time and the person or role responsible for resolving a disagreement. Do not label a customer cancelled because a note says no answer, or installed because the appointment date passed.
| Stage | Evidence to use | Do not substitute |
|---|---|---|
| Submitted | The approved order process returned a submission reference. | A conversation, lead or intention to order. |
| Accepted | The provider source confirms acceptance under the agreed definition. | A field record marked sold. |
| Scheduled | The provider source records a confirmed appointment under the program's rules. | A requested date or an assumed installation window. |
| Completed | The agreed provider source confirms the installation or activation event being measured. | An elapsed appointment or a representative's estimate. |
| Cancelled or rejected | The source status and reason are confirmed; any dispute has a named owner. | An aging order with no updated source evidence. |
| Commercially payable | The written pay event and reconciliation requirements are met. | Any upstream stage that the contract does not make payable. |
Reconcile in a repeatable sequence
Start with the agreed selling cohort and an explicit as-of timestamp. Import only the records permitted for this analysis. Check missing IDs, repeated IDs and replacement links before grouping by status. Then compare the field snapshot to the provider source, identify changes and assign unresolved differences. Publish totals only after the counting rules have been applied consistently.
Use internal order IDs in shared trackers and exclude customer contact, account and payment data. Resolve identity details inside the approved provider or CRM system. The public template is a blank working tool; it does not connect to a carrier system or authorize a new export. Restrict the completed tracker and any evidence links to the people who need them for the program.
- Confirm the cohort, counting unit, source systems and as-of time.
- Check missing, duplicate and replaced order references.
- Reconcile acceptance, appointment and completion to the provider source.
- Assign each mismatch a reason, owner, next action and review date.
- Record corrections without silently rewriting prior published snapshots.
- Separate operational completion from the written commercial pay event.
Do not mix selling-period volume with installation maturity
Orders accepted yesterday have had less time to complete than orders accepted several weeks earlier. Show the selling cohort and observation date together. Agree how long orders need to be observed for the decision being made, based on the actual provider process. Do not declare recent orders failed merely because they have not reached their appointment, and do not remove unresolved older orders to improve a completion rate.
The table below gives proposed calculations. The provider and buyer should approve the denominator and exclusions in writing. If an exclusion is allowed, report its count and reason alongside the result. Return not available when the denominator is zero; a zero denominator does not produce a meaningful percentage.
| Measure | Proposed calculation | State with the number |
|---|---|---|
| Acceptance rate | Provider-accepted records divided by submitted records in the agreed cohort. | Counting unit, duplicate treatment and source check time. |
| Observed completion rate | Provider-confirmed completed records divided by accepted records in that same cohort. | As-of date, cohort age and outstanding statuses. |
| Mature-cohort completion rate | Confirmed completions divided by accepted records meeting the pre-agreed observation rule. | Maturity rule and all exclusions; do not treat it as the full-cohort rate. |
| Open-exception age | As-of time minus the time the unresolved exception was opened. | Time zone, owner, next action and whether the cause is confirmed. |
Separate the customer's next action from the root-cause investigation
A customer who needs an installation update should not wait for a weekly attribution debate. Give the immediate customer task to the agreed owner, while a separate reason field identifies what is known about the delay. Useful categories can include qualification mismatch, incomplete information, scheduling, access, customer request, duplicate or source disagreement. Use an unknown category when the evidence does not support a cause.
At the review, look for repeated patterns across confirmed reasons. A high order count with many unresolved scheduling records may need a capacity or handoff fix. A rise in provider rejection may require offer, eligibility or order-entry review. The tracker helps direct the investigation; a correlation in one snapshot is not proof of fault or a universal agency performance benchmark.
Preserve corrections and close the commercial loop
When a provider corrects a status, keep the old snapshot, the corrected value, the source check time and the reason where available. Link any replacement reference so the same customer outcome is not counted or paid twice. A commercial dispute should point to the written pay event, authoritative evidence and exception process rather than an unqualified sales total.
After the selling period ends, assign ownership for orders still awaiting completion, customer issues and later permitted adjustments. Confirm when the cohort is considered closed and how a correction after closeout is handled. The public worksheet proposes the fields; it does not change a provider agreement or promise zero fallout.
Review the reporting handoff with Home Front
Bring a redacted description of your order stages, source systems, desired commercial event and current reporting gap. Home Front can discuss how a scoped field program connects territory, order quality, Dooriax workflow where agreed and provider-confirmed installation outcomes. Call us at (336) 420-9379 or use the existing business inquiry below. Access, integration work, staffing and deliverables are confirmed for the actual engagement.
Representatives looking for work should use the nationwide hiring hub rather than this provider worksheet. The existing application covers local, travel and blitz preferences for in-person, commission-only 1099 roles; written assignment terms control the territory, dates, compensation and expenses.
Sources and disclosure
This is an original Home Front operations template. It contains no actual customer records, measured conversion rates or promised installation outcomes. Definitions should be agreed with the provider and commercial owners for the specific program. A provider's authoritative record controls the reported outcome.
Related fiber operations guides
Use this fiber D2D pilot scorecard to define readiness, coverage, accepted orders, completed installs, fallout, complaints, and exit criteria.
A practical operating model for fiber serviceability, territory release, order quality, installation handoffs, exceptions and reporting.
Release fiber sales territories with versioned address cohorts, clear holds, assignment owners and change history. Includes a blank release worksheet.