What if a signer is unavailable?

If an authorized signer is unavailable, use an alternative signatory only if prior written delegation exists. Document the delegation and retain supporting approval records to avoid enforceability disputes.

Can this be signed electronically?

Yes — most Business Use Tunnel records may be executed electronically under the ESIGN Act (15 U.S.C. ch. 96) and UETA where adopted; confirm exceptions such as certain court orders or testamentary instruments do not apply.

Is notarization required?

Notarization is required for some instruments depending on state and content. For access-only authorizations notarization is uncommon but recommended when evidence of voluntary authorization is critical.

How should technical controls be specified?

List exact ports, IP ranges, authentication methods, and session logging responsibilities. Vague phrasing increases operational risk and complicates incident investigations.

What about retention and audits?

Retain executed records per your retention policy and applicable law; HIPAA-covered records require six years (45 CFR §164.530(j)), IRS-related records at least three years (IRC §6501(a)).

How to revoke access early?

Document revocation in writing, record the time and acting authority, perform immediate technical deprovisioning, and preserve the revocation record for audit and legal defense.

Business Use Tunnel

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

BUSINESS USE TUNNEL AGREEMENT

This Business Use Tunnel Agreement (the "Agreement") is made as of between Owner Name: and Licensee Name: .

Owner Address Licensee Address

RECITALS

WHEREAS, Owner is the legal owner or controlling licensee of the subterranean tunnel and associated accessways described in Exhibit A and suitable for the commercial uses set forth herein (the "Tunnel"); and

WHEREAS, Licensee desires to obtain a non-exclusive right to use the Tunnel for business purposes set forth in this Agreement, and Owner is willing to grant such right subject to the terms, conditions, and restrictions contained herein.

WHEREAS, the parties intend to allocate responsibilities for safety, maintenance, insurance, and payment as set forth in this Agreement.

SCOPE OF WORK

Licensee shall be authorized to use the Tunnel solely for the business purposes described below and in accordance with the restrictions and specifications set forth by Owner. Any expansion of use or structural alteration requires prior written consent from Owner.

Detailed Description of Permitted Use and Work to be Performed

PAYMENT TERMS

As consideration for the rights granted herein, Licensee shall pay Owner the amounts and according to the schedule set forth below. All payments shall be made in lawful currency and are exclusive of any taxes for which Licensee is responsible.

Usage Fee — Amount Payment Schedule / Invoicing Payment Due (Net Days) Late Fee / Interest

TERM AND TERMINATION

The term of this Agreement shall commence on and shall continue until unless earlier terminated in accordance with this Section.

Either party may terminate this Agreement for convenience upon written notice to the other party delivered not less than days prior to the effective termination date. Termination for cause may be immediate where the non‑breaching party provides written notice of a material breach and the breaching party fails to cure such breach within thirty (30) days of receipt of such notice.

CONFIDENTIALITY

Each party acknowledges that, in the course of performance, it may receive confidential or proprietary information of the other party. "Confidential Information" shall include technical data, business plans, customer lists, financial information, and other information reasonably understood to be confidential. Each receiving party shall: (a) hold Confidential Information in strict confidence; (b) not disclose Confidential Information to third parties except as expressly permitted in writing; and (c) use Confidential Information only for the performance of this Agreement. Confidentiality obligations shall survive termination of this Agreement for a period of three (3) years, except that trade secrets shall remain protected for as long as they qualify as trade secrets under applicable law.

INSURANCE, SAFETY, AND INDEMNIFICATION

Licensee shall, at its expense, maintain commercial general liability insurance and any other insurance reasonably required by Owner covering its operations within the Tunnel. Licensee shall comply with all applicable safety laws, codes, and Owner's reasonable operational and access rules. Licensee shall indemnify and hold Owner harmless from and against all claims, losses, liabilities, and expenses arising from Licensee's use of the Tunnel, except to the extent caused by Owner's gross negligence or willful misconduct.

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 laws principles. Venue for any dispute arising out of this Agreement shall lie in the state or federal courts located in that state.

ENTIRE AGREEMENT

This Agreement, together with any exhibits or attachments expressly incorporated herein, constitutes the entire agreement between the parties with respect to the subject matter and supersedes all prior negotiations, representations, and agreements, whether written or oral. No amendment or modification of this Agreement shall be effective unless in writing and signed by both parties.

ADDITIONAL PROVISIONS

If any provision of this Agreement is held invalid or unenforceable, the remaining provisions shall remain in full force and effect. Neither party may assign its rights or obligations under this Agreement without the prior written consent of the other, except that Owner may assign this Agreement to a successor in interest to the Tunnel.

Owner

Printed Name:

By:

Date:

Licensee

Printed Name:

By:

Date:

What the Business Use Tunnel document is and when it applies

The Business Use Tunnel is a formal authorization and documentation template used to record permission, responsibilities, and technical or access parameters when a business entity grants another party use of a controlled resource or service. Typical applications include authorizing network or VPN tunnels for vendor access, permitting temporary use of shared physical infrastructure, or documenting internal cross-departmental access for specific projects. The document captures parties, scope, duration, security requirements, and any special conditions so that obligations are clear and auditable for compliance and operational review.

Why a clear Business Use Tunnel record matters

A concise, well-completed Business Use Tunnel reduces operational risk by defining scope, access limits, and accountability; it supports audits, incident response, and contractual compliance without replacing standalone service agreements or technical change controls.

Who typically completes or signs this form

The Business Use Tunnel is completed by administrators, project sponsors, or contract managers who control resource access and by third parties or internal users receiving permission.

IT and Network Administrators — document technical access, ports, and duration for change control and audits.
Procurement or Contract Managers — ensure commercial terms and liability clauses align with supplier agreements.
Project Sponsors or Department Heads — authorize access tied to a specific business purpose or timeframe.

Signatures usually come from an authorized representative of the granting party and an authorized recipient, with IT and security teams copied for operational handoff.

Core sections to include in a professional Business Use Tunnel

A complete Business Use Tunnel template groups the agreement into discrete sections so reviewers can quickly confirm authority, scope, security controls, and expiration. Use consistent headings and a short summary at the top to speed review and routing.

Parties

Full legal names and contact information for the granting entity, the recipient, and any third-party administrators.

Scope

Precise description of the tunnel's purpose, allowed activities, systems or networks accessible, and any excluded uses.

Duration

Effective date and expiration or review date, plus renewal or automatic-expiry conditions.

Security Controls

Authentication method, encryption requirements, permitted IP ranges, multi-factor needs, and monitoring or logging obligations.

Responsibilities

Operational duties, incident reporting procedures, liability allocation, and who performs deprovisioning.

Signature & Audit

Signatory authority, date fields, and space for notarization or witness details when required.

Step-by-step: completing and approving a Business Use Tunnel

Follow these steps in order to create, review, and finalize a Business Use Tunnel with clear approvals and operational handoff.

01

Draft: Populate parties, scope, dates, and controls in the template.
02

Security Review: Submit to IT/security for technical validation and required controls.
03

Legal/Procurement Review: Confirm liability, indemnity, and commercial terms if third parties are involved.
04

Sign and Record: Collect signatures and save the executed copy in the document retention system.

Where to send the document and how routing typically works

A clear routing path ensures approvals and technical actions occur in the right sequence; combine document routing with ticketed change requests for the operational handoff.

Initiator: Uploads and completes the draft; assigns reviewers and signers.
Security Team: Validates controls, approves on technical grounds, and logs the change.
Legal / Procurement: Reviews third-party terms and approves contractual language where applicable.
IT Operations: Implements tunnel, records configuration, and confirms deprovisioning schedule.

How to configure an online workflow for the Business Use Tunnel

Set up a reproducible, auditable workflow with clear reviewer order, required fields, and authentication to reduce errors and speed approvals.

Field	Configuration
Required Fields	Grantor, Grantee, Scope, Effective/Expiration Dates
Review Order	Security → Legal/Procurement → IT Operations → Signatories
Signer Authentication	Email + optional SMS or two-factor for high-risk access
Audit Trail	Enable full timestamping, IP logging, and certificate-of-completion

Digital signing and technical integration considerations

Ensure the selected service supports exportable audit reports, long-term storage formats (PDF/A), and, where required, HIPAA or 21 CFR Part 11 controls.

Integrations: Salesforce, Microsoft 365, NetSuite, Google Workspace, Box, Procore
File Types: PDF, Word DOCX, HTML; preserve form fields and metadata
Authentication: Email, SMS, KBA, or advanced 2FA for higher-assurance signers

Typical timelines and processing expectations

Establish realistic internal SLAs for review, technical implementation, and deprovisioning to reduce lingering access and audit exceptions.

Internal Review SLA:

3–5 business days for security review

Legal/Procurement Review:

5–10 business days when third-party terms apply

Technical Implementation:

1–3 business days after approvals

Deprovisioning Window:

Immediate automated removal on expiration or within 24 hours

Document Retention Start:

Retention measured from Effective Date

Key milestones from request to closure

These numbered milestones track the lifecycle so stakeholders know where bottlenecks commonly occur.

01

1. Request Submitted

Requester completes template and assigns reviewers.

02

2. Security Clearance

Technical team approves scope and required controls.

03

3. Contract Review

Legal or procurement confirms third-party obligations as needed.

04

4. Implementation

IT implements tunnel and confirms connectivity.

Common mistakes to avoid when preparing the form

Vague scope descriptions that leave systems unintentionally accessible.
Missing or expired authorization dates causing unauthorized access.
No clear deprovisioning instructions or automated expiry.
Failing to involve security teams before signatures are collected.

Risks and potential consequences of incorrect or incomplete forms

Operational Risk: Unauthorized access or data exposure leading to breaches.

Compliance Risk: Regulatory exposure if protected data is accessed without proper controls.

Contractual Liability: Breach of vendor agreements or indemnity obligations.

Financial Penalties: Fines or remediation costs tied to data incidents or noncompliance.

Audit Findings: Negative audit outcomes and required corrective actions.

Operational Delay: Project hold-ups from incomplete approvals or unclear responsibilities.

Real-world examples of Business Use Tunnel scenarios

These condensed case narratives show how the template is adapted for different operational needs.

Vendor Remote Maintenance

A healthcare provider authorized a vendor to use a VPN for scheduled maintenance

Access limited to maintenance windows and monitored by security
The executed document included a HIPAA addendum, MFA requirement, and certificate of completion for audit trails.

Temporary Cross-Department Access

A finance project required short-term access to billing systems by procurement

Permissions scoped to specific data and removed after 14 days
The record specified responsibilities, logging, and automatic deprovisioning at expiration.

Typical signatories and their roles

IT Director

Signs to confirm technical feasibility and to accept responsibility for implementing security controls and deprovisioning at expiration. This party documents change tickets and operational handoff to IT operations.

Contracting Officer

Signs to confirm commercial and legal authority to grant access under existing agreements, ensuring indemnity, insurance, and liability terms are satisfied for third-party engagements.

Required information fields and security details to capture

Grantor Details: Legal name

Grantee Details: Legal name

Access Scope: Systems/IPs

Authentication: MFA/KBA

Encryption: Transport cipher

Audit Trail: Logging retention

Comparing eSignature vendor pricing and basic features for Business Use Tunnel workflows

Vendor pricing models and feature caps affect total cost and operational fit for high-volume tunnel authorization workflows; signNow is listed first per comparative format.

	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	No	No	Yes, limited	Yes, limited
Bulk Send	Yes	Yes	Yes	Yes	No
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes	Yes	Yes	No	No

Practical tips to reduce risk and speed approvals

Adopt consistent formatting and automated checks to cut review cycles and reduce rework when issuing a Business Use Tunnel.

Use Templates

Maintain an approved template with required fields locked to prevent omission and accelerate review.

Automate Approvals

Route automatically by role with conditional fields to ensure security and legal review when third parties are involved.

Record Everything

Store executed documents with audit trails and change tickets to support incident response and audits.

Review Periodically

Schedule periodic reviews for recurring tunnels to confirm necessity and compliance with updated controls.

Frequently asked questions about completing and managing Business Use Tunnel records

Answers below address common completion errors, signing concerns, and preservation of evidence for audits and compliance.

Need help? Contact support

What if a signer is unavailable?
If an authorized signer is unavailable, use an alternative signatory only if prior written delegation exists. Document the delegation and retain supporting approval records to avoid enforceability disputes.
Can this be signed electronically?
Yes — most Business Use Tunnel records may be executed electronically under the ESIGN Act (15 U.S.C. ch. 96) and UETA where adopted; confirm exceptions such as certain court orders or testamentary instruments do not apply.
Is notarization required?
Notarization is required for some instruments depending on state and content. For access-only authorizations notarization is uncommon but recommended when evidence of voluntary authorization is critical.
How should technical controls be specified?
List exact ports, IP ranges, authentication methods, and session logging responsibilities. Vague phrasing increases operational risk and complicates incident investigations.
What about retention and audits?
Retain executed records per your retention policy and applicable law; HIPAA-covered records require six years (45 CFR §164.530(j)), IRS-related records at least three years (IRC §6501(a)).
How to revoke access early?
Document revocation in writing, record the time and acting authority, perform immediate technical deprovisioning, and preserve the revocation record for audit and legal defense.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now