Missing or incorrect location details

Verify and update the GPS coordinates and pole/vault ID before submission. Incomplete location data commonly causes delayed dispatch and unnecessary travel costs; include a photo with a visible nearby landmark when possible.

Signature or approval errors

If an approver cannot sign, confirm their email and authentication method. Ensure consent to electronic records and that the signing platform supports the required authentication level for your jurisdiction.

Attachments fail to upload

Check file size and format limits; convert large OTDR traces or raw logs to PDF or compressed archives. Retry on a stable connection or upload from Wi‑Fi if mobile data is unstable.

Need to amend a submitted report

Create an addendum referencing the original Incident ID and clearly state changes. Do not overwrite the original entry; maintain an auditable change history with timestamps and editor identity.

When notarization is required

Obtain notarization for easements, legal attestations, or consent forms when local rules demand it. Consider Remote Online Notarization where accepted to avoid travel delays.

Retention and access questions

Store signed reports in a secure system with role‑based access. Follow your organization’s retention policy and regulatory obligations to ensure records are available for audits or disputes.

FTTC Issues Report

This template is fully customizable. Edit the text, fill out the fields, and send it for signature. Give it a try!

FTTC ISSUES REPORT & SERVICE AGREEMENT

Report No.: Report Date:

Parties

Client Name: Service Provider Name:

WHEREAS

WHEREAS, Client Name: operates premises and requires reliable FTTC (Fiber to the Curb) connectivity for business operations; and

WHEREAS, Service Provider Name: is engaged in the provision of telecommunications installation, monitoring, and remediation services; and

WHEREAS, Client has reported FTTC infrastructure or service degradation and the parties desire to document the reported issues, the agreed scope of remediation, payment terms, and related obligations.

Scope of Work

Service Provider shall investigate, diagnose, and remediate the reported FTTC issues at the location specified below, performing the tasks described and using personnel and equipment consistent with industry standards. The Scope of Work includes but is not limited to identification of physical fiber faults, testing of distribution point units, verification of drop and customer premises equipment, and coordination with upstream carriers where required.

Detailed Scope (describe tasks and deliverables):

Payment Terms

Client agrees to pay Service Provider for the services described in the Scope of Work in accordance with the following terms.

Contract Amount (USD): Payment Schedule: Late Payment Fee:

Term and Termination

This Agreement shall commence on Start Date: and shall continue until End Date: unless earlier terminated as provided herein. Either party may terminate this Agreement for convenience upon written notice delivered at least days prior to the effective date of termination. Termination for material breach shall be effective after thirty (30) days' written notice and failure to cure by the breaching party.

Confidentiality

Each party shall treat as confidential all information disclosed by the other party that is designated as confidential or that reasonably should be understood to be confidential given the nature of the information and the circumstances of disclosure. Confidential information shall not include information that is publicly available through no fault of the receiving party, already known by the receiving party without obligation of confidentiality, independently developed, or rightfully obtained from a third party without restriction. The receiving party will use confidential information only to perform its obligations under this Agreement and will not disclose it except to those employees, contractors, or professional advisers who need to know and who are bound to confidentiality obligations at least as protective as those herein. Upon termination or request, confidential materials shall be returned or destroyed.

Governing Law

This Agreement shall be governed by and construed in accordance with the laws of the State of , without regard to its conflict of law principles. Exclusive venue for any dispute arising under this Agreement shall lie in the state or federal courts located within that state.

Entire Agreement

This Agreement, including any attachments and written change orders executed by both parties, constitutes the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior and contemporaneous agreements, proposals, representations, and understandings, whether written or oral. No modification shall be binding unless in writing and signed by duly authorized representatives of both parties.

FTTC ISSUE REPORT DETAILS

Impacted Location (address): Contact Person: Contact Phone / Email: ISP / Carrier: Circuit / Equipment ID(s):

Severity: Critical (service outage) Major (degraded performance) Minor (intermittent)

Incident Date: Incident Time:

Incident Description: Immediate Actions Taken: Recommended Remediation / Next Steps: Estimated Downtime (hours): Attachments / Supporting IDs (list):

Acknowledgement

By signing below, each party represents and warrants that it is duly authorized to enter into this Agreement, that the information provided in this report is true and accurate to the best of its knowledge, and that it will cooperate in good faith to resolve the reported FTTC issues in accordance with the Scope of Work and Payment Terms set forth above.

Client - Printed Name:

By:

Date:

Service Provider - Printed Name:

By:

Date:

What the FTTC Issues Report Is and when it’s used

The FTTC Issues Report is a standardized technical record used to document faults, performance degradations, and installation issues for Fiber‑to‑the‑Curb deployments. It captures incident details, precise site location, equipment identifiers, impact on subscribers, and mitigation steps. The report supports internal triage, contractor coordination, permit reviews, and regulatory filings where required. Use it to preserve an auditable history of events, approvals, and corrective actions from detection through final closure, ensuring consistent handoffs between field crews, engineering teams, and municipal stakeholders.

Why a consistent FTTC Issues Report matters

A well‑structured report speeds diagnosis, reduces repeat site visits, and creates an auditable trail for regulatory compliance and warranty claims. It clarifies responsibilities and preserves evidence needed for dispute resolution and performance metrics.

Primary users and stakeholders who complete the report

The FTTC Issues Report is completed by personnel across field operations, project management, and regulatory teams to ensure consistent documentation.

Field technicians and installers documenting fault details, photos, and immediate mitigation steps for handoff.
Project managers and supervisors tracking repeated failures, contractor performance, and remedy timelines.
Municipal or utility permitting staff and compliance officers receiving evidence for permits, easements, or regulatory notifications.

Accurate completion helps operations, compliance, and customer care teams act on incidents quickly and maintain contractual and regulatory records.

Representative roles who sign or approve reports

Field Technician

A technician on site records the incident narrative, equipment serials, test results, photos, and temporary repairs. The technician documents immediate safety concerns and recommends next steps for escalation to engineering or contractor teams.

Project Manager

A project manager reviews submitted reports, assigns remediation tasks, coordinates permits or third‑party contractors, and updates stakeholders on timelines and costs. The manager signs off on closure once all corrective actions are complete and validated.

Essential fields every FTTC Issues Report should include

Incident ID: Unique alphanumeric identifier

Reporter: Name and contact

Location: Address or GPS coordinates

Equipment ID: Serial or tag number

Severity: Outage/Degradation level

Attachments: Photos and test logs

Filling out the FTTC Issues Report — step by step

Follow these steps to complete a clear, actionable report that supports fast triage and compliant recordkeeping.

01

1. Record ID: Assign a unique incident identifier
02

2. Capture location: Enter full address and GPS coordinates
03

3. Log symptoms: Describe observed failure and affected services
04

4. Attach evidence: Include photos, OTDR traces, and test files

Core sections to include in a professional FTTC Issues Report

A thorough report is divided into clear sections that make engineering review, contractor assignment, and regulatory follow up efficient.

Summary

Concise incident description with time discovered, short impact statement, and immediate safety notes to orient reviewers quickly.

Location Details

Precise address, GPS coordinates, nearest pole or vault ID, and any access constraints for crews and inspectors.

Equipment

List affected OLT/ONTs, fiber cable IDs, splice IDs, and serial numbers to tie reports to asset inventory.

Testing

Include OTDR traces, insertion loss values, split ratios, and any modem or service test results supporting diagnosis.

Mitigation

Document temporary repairs, traffic reroutes, customer notifications, and contractor work orders issued.

Closure Plan

Define remaining actions, owners, parts required, estimated completion date, and verification steps for final sign‑off.

How to configure an online FTTC Issues Report workflow

Map fields to routing rules, required attachments, and escalation paths when setting up a digital form for field use.

Field	Configuration
Incident Type	Drop‑down required
Priority	Auto‑set by impact
Attachments	Photo + OTDR required
Escalation	Auto‑email to PM

Typical submission and routing flow for the report

A clear routing model ensures reports reach the right teams without manual intervention or misplacement.

Capture: Technician completes form in the field app
Validate: System checks required fields and attachments
Route: Triage team receives ticket automatically
Assign: Work assigned to contractor or crew

Technical and integration considerations for eSubmission

Choose a platform that supports mobile capture, secure storage, and integrations with asset and ticketing systems.

File formats: PDF, DOCX, CSV
Integrations: NetSuite, Salesforce, Procore
Authentication: Email, SMS, SSO

Common timelines and response expectations

Define SLA targets and regulatory timelines clearly so report authors and responders are aligned on required actions.

Initial report:

Within 24 hours of detection

Triage response:

Initial acknowledgement within 4 hours

Temporary mitigation:

Implement within 48 hours for critical outages

Permitting actions:

Begin within 7–14 days where permits are required

Final closure:

Complete verification within 30 days

Key milestones from detection to closure

Track these sequential stages to measure progress and identify bottlenecks in incident handling.

01

Detection and Logging

Issue is discovered and a report record is created by the field or monitoring system.

02

Triage and Assignment

Triage team reviews details, sets priority, and assigns remediation tasks to crews or contractors.

03

Repair and Verification

Technician executes repairs and performs tests to confirm service restoration.

04

Closure and Documentation

Project manager validates results, closes the ticket, and archives the report for retention.

Common mistakes to avoid when preparing the report

Incomplete location details that force return site visits and delay repairs, such as missing GPS coordinates or pole numbers.
Omitting test artifacts like OTDR traces or modem logs, which prevents engineering from verifying root cause remotely.
Using inconsistent equipment identifiers or shorthand that do not match inventory systems, causing spare part delivery errors.
Failing to note public‑safety or traffic control requirements, which can stop contractors from accessing sites on schedule.

Consequences of incorrect or late reports

Service Impact: Extended outages

Regulatory Risk: Permit violations

Contractual Penalty: SLA fines

Safety Hazard: Increased liability

Invoice Delays: Payment disputes

Data Loss: Missing audit trail

eSignature vendor pricing snapshot for FTTC Issues Report workflows

Compare basic pricing and compliance attributes to select a secure eSignature provider for report routing and approvals. Do not rely solely on price; verify plan features before purchase.

	signNow	DocuSign	Adobe Sign	PandaDoc	HelloSign
Starting Price	$8/user/mo	$15/user/mo	$14/user/mo	$19/user/mo	$15/user/mo
Free Trial	7‑day free trial	Varies by vendor	Varies by vendor	Varies by vendor	Varies by vendor
Bulk Send	Yes	Yes	Yes	Yes	Limited
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes	Yes	Yes	No	No
Envelope Cap	No cap	100 envelopes/user/year	Varies by plan	Varies by plan	Varies by plan

Frequently asked questions when completing or submitting an FTTC Issues Report

Answers to common issues encountered during report completion, submission, eSigning, and record retention.

Need help? Contact support

Missing or incorrect location details
Verify and update the GPS coordinates and pole/vault ID before submission. Incomplete location data commonly causes delayed dispatch and unnecessary travel costs; include a photo with a visible nearby landmark when possible.
Signature or approval errors
If an approver cannot sign, confirm their email and authentication method. Ensure consent to electronic records and that the signing platform supports the required authentication level for your jurisdiction.
Attachments fail to upload
Check file size and format limits; convert large OTDR traces or raw logs to PDF or compressed archives. Retry on a stable connection or upload from Wi‑Fi if mobile data is unstable.
Need to amend a submitted report
Create an addendum referencing the original Incident ID and clearly state changes. Do not overwrite the original entry; maintain an auditable change history with timestamps and editor identity.
When notarization is required
Obtain notarization for easements, legal attestations, or consent forms when local rules demand it. Consider Remote Online Notarization where accepted to avoid travel delays.
Retention and access questions
Store signed reports in a secure system with role‑based access. Follow your organization’s retention policy and regulatory obligations to ensure records are available for audits or disputes.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now