Can this form be e-signed?

Yes. Electronic signatures meet U.S. legal standards under the ESIGN Act (15 U.S.C. ch. 96) and UETA where adopted; ensure intent, consent, attribution, and reliable record retention to satisfy 15 U.S.C. §7001 and state UETA rules.

What fields are critical for SLA claims?

Essential fields include incident ID, exact circuit identifier, timestamps, carrier case numbers, and attached diagnostics (traceroutes, logs). Quantify impact and preserve original files; incomplete records often result in denied SLA credit claims.

Are notarization or witnesses required?

Not typically. Standard incident reports do not require notarization or witnesses. If a signed affidavit or contractual attestation is needed, follow state notarization rules or Remote Online Notarization procedures where available and appropriate.

How long must I keep the form?

Retention depends on purpose: keep incident records during the active term plus at least three years for tax and billing evidence (IRC §6501(a)). Healthcare metadata must follow HIPAA six-year rule (45 CFR §164.530(j)). Consult counsel for state variations.

What happens if diagnostic files are missing?

Missing diagnostics may bar SLA credits, hinder root-cause analysis, and prolong outages; request carrier logs, reproduce tests ASAP, and document why files are unavailable to preserve evidentiary integrity.

Can signNow be used to collect signatures?

Yes. signNow supports legally binding eSignatures, audit trails, and HIPAA-compliant workflows (BAA required). Pricing starts at $8/user/month and includes templates and mobile apps; choose a plan that matches your volume and authentication needs.

Electronic Signature
Templates
Miscellaneous
Business WAN Issue Form

Business WAN Issue Form

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

BUSINESS WAN ISSUE FORM

Company Name:

Client Contact: Phone:

Site / Service Location

Account / Circuit Number: Reported Date: Reported Time:

Incident Summary

Affected Services and Equipment

Select affected items Edge Router Switch / LAN Leased Line / Circuit VPN / Tunnels Internet Breakout

Other affected equipment or identifiers

Impact and Severity

Severity (check one): Critical — complete outage or major business impact Major — significant degradation Minor — isolated or intermittent

Estimated impact (users, locations, services)

Troubleshooting Performed

Ticketing & Escalation

Ticket / Reference Number Assigned To Escalation Required Yes — escalate to NOC / Carrier / Provider

Escalation Notes

Desired Outcome / Service Request

Service Fee Estimate & Charge Authorization

Estimated Fee: Billing Account:

WHEREAS (Agreement Recitals)

WHEREAS, Client Name: requires remediation services for business wide area network issues; and

WHEREAS, Service Provider Name: has capabilities and agrees to provide the services described herein on the terms set forth below.

Scope of Work

The Service Provider will perform the following remediation, diagnostic, and repair services to restore WAN functionality and minimize business impact. The parties acknowledge that actions required may include coordination with third-party carriers, configuration changes, circuit testing, and on-site technician dispatch.

Payment Terms

Service Fee (if not covered by existing agreement): . Payment Schedule: . Late Fee:

Client authorizes Service Provider to bill the Billing Account noted above for authorized services and acknowledges responsibility for charges incurred in connection with the work described.

Term and Termination

Service Commencement Date: . Expected Completion Date: .

Either party may terminate this Statement of Work for material breach that remains uncured for following written notice. Termination does not relieve Client of obligation to pay for work performed through the effective date of termination.

Confidentiality

Each party will hold in confidence technical and business information marked or reasonably understood to be confidential and will not disclose such information except to employees, contractors, or third-party carriers as required to perform the services. Confidential information shall not include information that is publicly available or independently developed. The obligations set forth herein survive termination for a period of two (2) years unless otherwise required by law.

Governing Law

This Statement of Work and any dispute arising hereunder shall be governed by the laws of the State of without regard to conflict of law principles.

Entire Agreement

This document, together with any referenced master services agreement or order form executed by the parties, constitutes the entire agreement between the parties with respect to the subject matter and supersedes all prior or contemporaneous agreements, understandings, and communications, whether written or oral.

Acknowledgement

By signing below, the undersigned represent and warrant that they have the authority to bind their respective organization to the terms set forth in this form and any associated Statement of Work.

Service Provider:

By:

Date:

Client:

By:

Date:

What the Business WAN Issue Form Is and Why It Exists

Business WAN Issue Form is a standardized incident report used by organizations to document wide area network outages, performance degradations, and configuration faults. It captures identifying information (site, contact, circuit ID), technical diagnostics (latency, packet loss, traceroutes), timeline of events, actions taken, and impact on business services. Completed forms provide a consistent record for internal IT teams, third-party carriers, and vendors during troubleshooting and contractual escalation. The form supports versioned records for audits and service-level agreement (SLA) reviews and can be submitted electronically or as a printed attachment to ticketing systems.

Key Purposes and Practical Benefits

Standardizing incident reports reduces diagnostic delays and preserves forensic detail. A Business WAN Issue Form improves cross-team communication, speeds vendor escalations, and creates an auditable record for SLA claims and post-incident reviews while supporting electronic submission and reliable retention for compliance or billing disputes.

Who Typically Completes This Form

IT operations teams, network engineers, and carrier support staff typically complete the Business WAN Issue Form to document incidents and coordinate troubleshooting, repairs, and escalations.

Corporate IT: Logs site, circuit ID, impact, business services affected, and initial diagnostics.
Managed service providers: Collate carrier data, attach traceroutes, and manage ticket escalation workflows.
Vendors/carriers: Use form for outage validation, root cause analysis, and SLA credit processing.

Accurate, timely completion ensures effective vendor response and preserves documentation needed for SLA adjudication, billing corrections, and internal post-incident review.

Essential Sections to Include on a Professional Form

A professional Business WAN Issue Form groups information into incident details, contact points, circuit identifiers, diagnostics, actions taken, and escalation outcomes to streamline troubleshooting and records.

Incident ID

Assign a unique incident identifier and record the date and start time. Include incident severity level and affected business services to prioritize response and correlate tickets across systems.

Contact

Provide primary and secondary contact names, roles, phone numbers, and email addresses. Note on-call rotation and preferred contact window to speed real-time troubleshooting and reduce response latency during incidents.

Circuit Info

Record carrier name, circuit ID, service type, bandwidth, and physical demarcation. Include account or ticket numbers for the carrier to reduce back-and-forth during escalations and expedite validation steps.

Diagnostics

Attach timestamped traceroutes, ping statistics, latency/jitter measurements, packet loss figures, and relevant router/switch logs. Indicate measurement tools, endpoints tested, and test schedule for reproducibility.

Actions Taken

Document immediate mitigation steps, configuration changes, restart logs, and personnel actions with timestamps and responsible parties. Note temporary workarounds and dates for permanent remediation planning.

Escalation

Track escalation path, carrier or vendor case numbers, assigned engineers, expected response SLAs, and outcomes. Record any SLA credits requested and the supporting evidence attached to the claim.

Required Fields and Short Data Checklist

Site Identifier: Physical address and site code.

Circuit ID: Carrier-assigned circuit number.

Contact Details: Phone, email, role.

Incident Timeline: Start, detection, and resolution times.

Diagnostic Files: Traceroutes, pings, logs attached.

Impact Summary: Services affected and business impact.

Step-by-Step: Complete and Route the Form

Follow this sequence to complete and route the Business WAN Issue Form for efficient troubleshooting and escalation across internal and external teams.

01

Start Report: Fill incident ID, site, and start time.
02

Add Contacts: Enter primary and backup contact details.
03

Attach Diagnostics: Upload traceroutes, logs, and timestamps.
04

Route: Send to carrier, ticketing, and archive copies.

How to Configure an Online Template and Routing

Configure the online template fields and routing rules to match your ticketing system and carrier escalation procedures.

Field	Configuration
Required Fields and Validation Rules	Mark site, circuit, timestamps as required; add format checks.
Date and Time Formatting Rules	Enforce MM/DD/YYYY and timezone selection for all timestamps.
Automatic Routing and Escalation Rules	Auto-send to carrier, internal teams, and ticketing on submission.
Submitter Authentication, Logging, and Attribution	Require email or SMS OTP and capture IP, timestamp, and submitter name.

Typical Submission Flow From Detection to Closure

Typical submission flow describes detection, reporting, vendor escalation, mitigation, and closure with archival for audits.

Detect: Network monitoring alerts or user reports trigger form creation.
Report: Technician fills form and attaches diagnostics.
Escalate: Form routed to carrier with case numbers.
Close: Document resolution, verify service restoration, archive.

Technical Requirements for Electronic Submission and Storage

For electronic submission, confirm platform supports attachments, field validation, and audit trails before deployment to avoid data loss.

Formats: PDF and DOCX accepted for attachments.
Integrations: Ticketing, SIEM, and carrier portals.
Authentication: Email, SMS OTP, or SSO options.

Key Timelines and Deadlines to Observe

Timelines govern incident reporting, carrier SLA windows, documentation deadlines, and retention triggers for audits and billing disputes.

Initial Report Deadline:

Within 1 hour of detection when possible.

Carrier Notification Window:

As defined by carrier SLA; often 24 hours.

Diagnostic Submission Requirement:

Attach traceroutes and logs within 24 hours.

SLA Credit Request Timing:

Submit claim within carrier-specified claim window.

Record Retention Trigger:

Archive form per retention policy immediately after closure.

Common Mistakes to Avoid

Incomplete circuit identifiers slow carrier validation and can delay escalations; always include carrier name, exact circuit ID, account number, and physical demarcation to avoid lookup delays.
Missing timestamps and unsynchronized clocks on diagnostic logs make timeline reconstruction difficult; ensure all devices use NTP and include UTC timestamps for traceroutes and log exports.
Nonstandard file formats or excessively large attachments can block uploads; compress logs, use standard text or PDF formats, and confirm system file size limits before submission.
Ambiguous impact descriptions hinder prioritization; quantify affected users, revenue impact, or service degradation level rather than using vague terms like 'slow' or 'intermittent'.

Consequences of Incorrect or Incomplete Forms

SLA Denial: Incomplete evidence may forfeit credits.

Billing Errors: Incorrect circuit IDs cause misallocated charges.

Extended Downtime: Delays in escalation prolong outages.

Compliance Risk: HIPAA exposure if health data mishandled.

Forensic Gaps: Missing logs limit root cause analysis.

Contract Disputes: Poor documentation weakens legal positions.

eSignature Vendor Pricing and Feature Snapshot for Form Collection

Compare common vendor pricing and feature availability for eSignature options commonly used to collect and store Business WAN Issue Forms.

	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	No
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes	Yes	Yes	No	No

Frequently Asked Questions and Troubleshooting

Answers to frequent questions about completing, signing, and submitting the Business WAN Issue Form, including evidence requirements and retention guidance.

Need help? Contact support

Can this form be e-signed?
Yes. Electronic signatures meet U.S. legal standards under the ESIGN Act (15 U.S.C. ch. 96) and UETA where adopted; ensure intent, consent, attribution, and reliable record retention to satisfy 15 U.S.C. §7001 and state UETA rules.
What fields are critical for SLA claims?
Essential fields include incident ID, exact circuit identifier, timestamps, carrier case numbers, and attached diagnostics (traceroutes, logs). Quantify impact and preserve original files; incomplete records often result in denied SLA credit claims.
Are notarization or witnesses required?
Not typically. Standard incident reports do not require notarization or witnesses. If a signed affidavit or contractual attestation is needed, follow state notarization rules or Remote Online Notarization procedures where available and appropriate.
How long must I keep the form?
Retention depends on purpose: keep incident records during the active term plus at least three years for tax and billing evidence (IRC §6501(a)). Healthcare metadata must follow HIPAA six-year rule (45 CFR §164.530(j)). Consult counsel for state variations.
What happens if diagnostic files are missing?
Missing diagnostics may bar SLA credits, hinder root-cause analysis, and prolong outages; request carrier logs, reproduce tests ASAP, and document why files are unavailable to preserve evidentiary integrity.
Can signNow be used to collect signatures?
Yes. signNow supports legally binding eSignatures, audit trails, and HIPAA-compliant workflows (BAA required). Pricing starts at $8/user/month and includes templates and mobile apps; choose a plan that matches your volume and authentication needs.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now