Who should update the list?

Primary responsibility usually sits with Operations or an assigned owner; delegated teams provide changes. Establish a single owner to receive updates and schedule routine verifications to prevent drift.

How often must contacts be verified?

Verify critical contacts quarterly and perform a full review annually. Update the list within seven business days after any role or vendor change to keep incident response effective.

Can the list include private health contacts?

Yes, but if entries reference protected health information or PHI access, apply HIPAA controls and execute a Business Associate Agreement for vendors handling PHI.

Is an electronic signature acceptable?

Electronic signatures meet legal requirements under the ESIGN Act (15 U.S.C. ch. 96) and UETA where adopted, provided intent, consent, attribution, and retention are documented.

When is notarization required?

Most internal support lists do not require notarization. If the list includes legally enforceable authorizations or powers, consult state notary rules or counsel to determine requirements.

How do I revoke or replace the list?

Issue a new version with a later effective date and archive the older copy. Communicate changes to all stakeholders and retain prior versions per your retention policy for auditability.

Business Support List

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

BUSINESS SUPPORT LIST AND SERVICE AGREEMENT

This Business Support List and Service Agreement (the Agreement) is entered into as of by and between Client Name: with principal address: , and Service Provider Name: with principal address: .

WHEREAS

1. Client requires ongoing business support services, including but not limited to operational support, technical assistance, vendor coordination, and administrative functions, in order to maintain and grow Client's business operations.

2. Provider represents that it has the necessary personnel, expertise, and resources to perform the services set forth in this Agreement and is willing to supply such services to Client on the terms and conditions contained herein.

3. The parties desire to set forth in writing the scope, responsibilities, compensation, and other terms governing Provider's performance of the listed business support functions.

SCOPE OF WORK

Provider will perform the business support services and tasks specified in the Business Support List below (the Services). Provider shall perform the Services with reasonable skill, care, and in a professional manner consistent with industry standards.

Comprehensive Description of Services

BUSINESS SUPPORT LIST (ITEMIZED)

The parties agree that the following itemized tasks constitute the Services. Provider will maintain records of time and materials for each listed item and provide periodic status reports as set forth in this Agreement.

1. Support Item Title Description 2. Support Item Title Description 3. Support Item Title Description 4. Support Item Title Description

PAYMENT TERMS

In consideration for the Services, Client shall pay Provider as follows.

Service Fee (per period or flat) Billing Schedule Payment Due (days after invoice) Late Fee

Provider shall invoice Client in accordance with the Billing Schedule. Unless otherwise agreed in writing, payment is due by the Payment Due date. Any undisputed late payments shall accrue interest at the Late Fee rate specified above or the maximum rate permitted by law, whichever is lower.

TERM AND TERMINATION

This Agreement shall commence on Start Date: and shall continue until End Date: unless earlier terminated in accordance with this section.

Notice Period for Termination

Either party may terminate this Agreement for material breach by the other party if the breaching party fails to cure the breach within days after receipt of written notice specifying the breach. Termination shall not relieve Client of its obligation to pay for Services performed and expenses incurred through the effective date of termination.

CONFIDENTIALITY

"Confidential Information" means all non-public information disclosed by a party in connection with this Agreement, whether oral or in writing, that is designated as confidential or that reasonably should be understood to be confidential given the nature of the information. Each party shall (a) use Confidential Information only for performance or enforcement of this Agreement; (b) restrict disclosure to employees, contractors, and agents who have a need to know and who are bound by confidentiality obligations at least as protective as those herein; and (c) protect such information using at least the same degree of care it uses to protect its own confidential information, but no less than reasonable care.

Confidential Information does not include information that: (i) is or becomes publicly known without breach of this Agreement; (ii) was known to the receiving party prior to disclosure; (iii) is received from a third party without breach of an obligation of confidentiality; or (iv) is independently developed without use of the disclosing party's Confidential Information. A receiving party may disclose Confidential Information when required by law, provided it gives prompt notice to the disclosing party to seek a protective order or other remedy.

GOVERNING LAW

This Agreement shall be governed by and construed in accordance with the laws of the State of without regard to its conflicts of law principles. Venue for any dispute arising out of or relating to this Agreement shall lie in the state or federal courts located within that State.

LIMITATION OF LIABILITY & INDEMNIFICATION

Except for liability arising from a party's gross negligence or willful misconduct, neither party shall be liable to the other for incidental, consequential, special, or punitive damages. Each party shall indemnify and hold the other harmless from third-party claims arising from the indemnifying party's breach of this Agreement, negligent acts, or willful misconduct, subject to customary defenses.

ENTIRE AGREEMENT

This Agreement, including any Business Support List items and written appendices signed by the parties, constitutes the entire agreement between the parties regarding the subject matter hereof and supersedes all prior proposals, discussions, and agreements, whether oral or written. Any amendment or modification must be in writing and signed by authorized representatives of both parties.

CONTACTS FOR NOTICES AND SERVICE COORDINATION

Client Primary Contact Provider Primary Contact

The persons identified above are authorized to receive notices, approve work orders, and coordinate scheduling for the Services unless otherwise notified in writing.

Client Name:

By:

Date:

Service Provider:

By:

Date:

What a Business Support List Is and When it’s Used

A Business Support List is a structured record of internal and external contacts, responsibilities, and resources that a company uses to resolve operational, technical, legal, and customer issues. It typically identifies support teams, escalation steps, service-level targets, required access credentials, and related documentation links. Organizations use the list for onboarding, incident response, vendor coordination, and regulatory audits. Maintaining a clear, current Business Support List reduces confusion during incidents, ensures accountability across teams, and documents who is authorized to act for specific service categories.

Why a Clear Business Support List Matters

A concise Business Support List reduces downtime, clarifies escalation, and preserves audit trails for compliance. It helps satisfy internal SLAs and external obligations by documenting roles, response times, and handoff procedures in a single reference.

Teams and Roles That Rely on a Business Support List

Core users create and consult the Business Support List during operations, onboarding, incident handling, and audits.

IT and Engineering: Track on-call rotations, escalation contacts, system owners, and recovery procedures for technical incidents.
Customer Support and Operations: Use contacts and SLA targets to coordinate responses across teams and vendors.
Legal and Compliance: Maintain authorized signers, data-handling notes, and required notices for regulatory review.

Keep the list accessible to primary stakeholders and restricted for sensitive contacts; update it after staff or vendor changes.

Essential Elements of an Effective Business Support List

A professional Business Support List groups contacts by function, records escalation paths, and links required documents for quick access during events or routine operations.

Contact Details

Name, role, direct phone, email, time zone, and preferred contact method for each support person or vendor; include backup contacts.

Escalation Steps

Clear, ordered steps showing who to notify at each severity level, time thresholds for escalation, and who approves exceptions.

Service Levels

Document SLA targets, response and resolution timeframes, and penalties or credits tied to performance where applicable.

Access Instructions

Describe required credentials, privileged account owners, temporary access process, and any required approvals for system access.

Supporting Docs

Attach runbooks, vendor contracts, network diagrams, and authorization letters so responders have the right documents on hand.

Review Schedule

Specify review cadence, owner for updates, version history, and the date of last verification for compliance evidence.

Step-by-Step: Creating or Updating the Business Support List

Follow a repeatable workflow to collect, verify, and publish support contacts so the list stays accurate and actionable.

01

Collect: Gather contact and role data from team leads.
02

Verify: Confirm details with each person listed.
03

Approve: Obtain sign-off from designated approvers.
04

Publish: Distribute to stakeholders and archive previous versions.

Configuring an Online Workflow for Your Support List

Set up template fields, signer roles, and notifications to automate updates and approvals when the list changes.

Field	Configuration
Template	Create a reusable file with required fields pre-positioned.
Signers	Define approver roles and the order of approvals.
Authentication	Require email or SMS verification for approvers.
Notifications	Enable alerts on changes and scheduled review reminders.

Typical Digital Review and Distribution Flow

A simple digital workflow reduces coordination time: create, verify, approve, sign, and distribute with an audit trail for compliance.

Create: Populate the list template.
Verify: Contact entries are validated by owners.
Approve: Designated approvers sign or confirm changes.
Distribute: Publish to stakeholders and save a versioned copy.

Technical Considerations for eSubmission and Distribution

Choose a platform that supports fillable fields, role-based approvals, and secure distribution to internal teams.

File Formats: PDF, DOCX, and XLSX supported
Integrations: Connect with Google Workspace or Microsoft 365
Authentication: Email, SMS code, or SSO

Ensure the platform meets your security and retention requirements before publishing; verify integration points with ticketing and monitoring systems.

Recommended Deadlines and Update Cadence

Set clear deadlines for initial publication and routine verification to keep contact data current and reliable.

Initial Publication Deadline:

Complete and publish within project onboarding (typical: 30 days).

Change Notification Window:

Require updates within 7 business days of any staffing or vendor change.

Quarterly Verification:

Confirm key contacts and SLAs every 90 days.

Annual Review:

Perform a full audit and approve changes once per year.

Incident Postmortem Update:

Update the list within 10 business days after major incidents.

Key Milestones for List Approval and Publication

Track these milestones to manage approvals and maintain a clear version history for the Business Support List.

01

Draft Completion

Assemble data and draft the support list for review.

02

Stakeholder Review

Collect feedback from affected teams and legal/compliance.

03

Final Approval

Obtain sign-off from designated approvers.

04

Publication & Distribution

Publish to stakeholders and record the effective date.

Common Mistakes to Avoid When Preparing the List

Listing personal or unmonitored contact addresses that are inaccessible during incidents and delay response.
Failing to include backup contacts or escalation steps, which forces ad-hoc decisions under pressure.
Keeping the list in multiple, unsynchronized copies, causing teams to act on different versions.
Omitting access or credential notes; responders then lose time obtaining required permissions.

Risks and Consequences of an Inaccurate Support List

Operational Downtime: Longer outages and delayed recovery

Contract Breach: Missed SLAs can trigger credits or penalties

Regulatory Exposure: Noncompliance risks for regulated data

Data Breach Risk: Incorrect access procedures increase susceptibility

Customer Impact: Reputational harm and lost business

Audit Failure: Insufficient records for inspections

Key Security and Compliance Notes for Support Lists

Encryption: TLS 1.2/1.3 in transit and AES-256 at rest

Audit Trail: Record timestamps, IPs, and actions for each change

Access Controls: Role-based permissions and least-privilege model

MFA: Require multi-factor authentication for approvers

BAA: Use BAA where HIPAA-regulated contacts exist

Certifications: SOC 2 Type II and ISO 27001 demonstrate controls

Typical eSignature Pricing and Feature Comparison

Compare starting prices and core features across common eSignature providers; signNow appears first as a reference option for pricing context.

	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
Envelope Cap	No cap	100 envelopes/user/year	Varies by plan	Varies by plan	Varies by plan

Practical Examples from Organizations Using a Support List

These short case arcs illustrate how companies use a Business Support List to improve response and compliance in real scenarios.

Optica Ventures — Operations

Optica centralized contacts and runbooks for faster triage of investor requests and portfolio issues.

The new list removed ambiguity during handoffs.
The team reports simpler customer interactions and fewer escalations because responders always know who owns each task and how to reach backups, improving turnaround across routine and ad-hoc requests.

Martin Properties — Real Estate

Martin Properties consolidated leasing and maintenance contacts in one list for field teams.

Mobile access reduced site delays.
Staff can now close maintenance tickets and tenant requests faster; property managers cite improved compliance with inspection schedules and more timely vendor coordination after standardizing contact and escalation information.

Who Typically Signs or Approves the Support List

Operations Manager

The Operations Manager typically approves content related to service levels and on-call rosters. They confirm accuracy of technical contacts and accept responsibility for distribution and periodic review to ensure operational readiness.

General Counsel

The General Counsel or delegated compliance officer signs off on any legal or vendor authorization language. They verify that data-sharing notes, privacy considerations, and retention policies meet regulatory obligations.

Frequently Asked Questions About the Business Support List

Answers to common implementation and compliance questions about maintaining and using a Business Support List.

Need help? Contact support

Who should update the list?
Primary responsibility usually sits with Operations or an assigned owner; delegated teams provide changes. Establish a single owner to receive updates and schedule routine verifications to prevent drift.
How often must contacts be verified?
Verify critical contacts quarterly and perform a full review annually. Update the list within seven business days after any role or vendor change to keep incident response effective.
Can the list include private health contacts?
Yes, but if entries reference protected health information or PHI access, apply HIPAA controls and execute a Business Associate Agreement for vendors handling PHI.
Is an electronic signature acceptable?
Electronic signatures meet legal requirements under the ESIGN Act (15 U.S.C. ch. 96) and UETA where adopted, provided intent, consent, attribution, and retention are documented.
When is notarization required?
Most internal support lists do not require notarization. If the list includes legally enforceable authorizations or powers, consult state notary rules or counsel to determine requirements.
How do I revoke or replace the list?
Issue a new version with a later effective date and archive the older copy. Communicate changes to all stakeholders and retain prior versions per your retention policy for auditability.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now