Establishing secure connection…Loading editor…Preparing document…

Support Resolutions Document

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

SUPPORT RESOLUTIONS DOCUMENT

Supporting Organization:    Recipient Organization:

Resolution Date:

WHEREAS

WHEREAS, the Supporting Organization has reviewed the objectives and scope of the Recipient Organization's proposed program, project, or initiative described as: ; and

WHEREAS, the Board or authorized body of the Supporting Organization finds that providing the support set forth in this resolution is in the best interest of the Supporting Organization and consistent with its charter, policies, and applicable law; and

WHEREAS, the Supporting Organization desires to set forth the terms, conditions, and authority for providing such support and, where applicable, to authorize designated officers to take actions necessary to implement this resolution.

RESOLVED

NOW, THEREFORE, BE IT RESOLVED that the Supporting Organization hereby expresses formal support for the Recipient Organization's program described above and authorizes the provision of support on the terms and conditions set forth in this Support Resolutions Document.

FURTHER RESOLVED that the Supporting Organization authorizes the expenditure or commitment of funds and other resources in accordance with the Payment Terms section below, subject to appropriation, budget approval, and any conditions set forth herein.

SCOPE OF SUPPORT

PAYMENT TERMS

Late Payment Fee:    or Flat Late Fee: per overdue invoice or as otherwise agreed.

TERM AND TERMINATION

Term Commencement Date:    Term Expiration Date:

Either party may terminate this Support Resolutions Document for material breach if such breach is not cured within the termination notice period following written notice. Termination shall not relieve either party of obligations accrued prior to termination.

CONFIDENTIALITY

The parties acknowledge that in the course of performance they may exchange Confidential Information. "Confidential Information" means non-public information disclosed in tangible form or clearly identified as confidential. Each party shall (i) use Confidential Information only for purposes of performing its obligations under this resolution, (ii) restrict disclosure to employees, contractors, or agents with a need to know who are bound by confidentiality obligations at least as protective as those contained herein, and (iii) take reasonable steps to protect such information from unauthorized disclosure.

Confidentiality obligations shall not apply to information that (a) is or becomes public without breach of this Agreement, (b) was rightfully in the receiving party's possession prior to disclosure, (c) is independently developed by the receiving party, or (d) is required to be disclosed by law, provided the disclosing party gives prompt notice to the other and cooperates regarding any protective order or confidential treatment.

GOVERNING LAW

This Support Resolutions Document shall be governed by and construed in accordance with the laws of the State of , without regard to its conflicts of law principles.

ENTIRE AGREEMENT

This Support Resolutions Document, together with any exhibits or attachments expressly incorporated herein, constitutes the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior and contemporaneous understandings, proposals, and communications, whether written or oral. Any amendment or modification must be in writing and signed by authorized representatives of both parties.

CERTIFICATION

I hereby certify that the foregoing resolution was duly adopted by the Supporting Organization's Board or authorized governing body in accordance with the Supporting Organization's governing documents and applicable law on the date set forth above and that the persons signing below are authorized to execute this resolution on behalf of their respective organizations.

Supporting Organization Representative:

By:

Date:

Recipient Organization Representative:

By:

Date:

Enter text✕

What the Support Resolutions Document Is and When it Applies

A Support Resolutions Document records the facts, actions and final determination for a customer or internal support incident, creating a clear record of issues reported, troubleshooting steps taken, responsible parties, and the final resolution. It supports accountability, dispute resolution, service-level agreement (SLA) tracking, and regulatory compliance when incidents affect protected data or contractual obligations. Use it to document technical fixes, service credits, refunds, escalation steps, communications, and sign-offs needed to close a support case formally.

Why a Clear Support Resolutions Document Matters

A precise Support Resolutions Document reduces ambiguity, protects the organization in disputes, and establishes an auditable record for compliance and internal reviews.

Why a Clear Support Resolutions Document Matters

Teams That Typically Prepare or Sign This Document

Common stakeholders who create, review, or rely on Support Resolutions Documents.

  • Customer support and technical teams who draft incident summaries and capture remediation details for each case.
  • Customer success and account management teams who document service credits, client communications, and acceptance of resolution.
  • Legal, compliance, and procurement teams who review records when incidents touch contracts, regulated data, or warranty claims.

Assigning clear ownership and sign-off authority ensures the document is complete and enforceable.

Step-by-Step: Completing a Support Resolutions Document

Follow these sequential steps to prepare, approve, and file the completed document.

  • 01
    Open Case: Record case ID and reporter details immediately.
  • 02
    Investigate: Document diagnostics, logs, and reproductions.
  • 03
    Remediate: Describe fixes, patches, or configuration changes.
  • 04
    Close and Sign: Capture approver signature and retention instructions.

Core Elements to Include in a Professional Support Resolutions Document

A well-structured document contains standard sections so reviewers can quickly verify the timeline, responsibility, and final outcome.

Header

Case ID, customer or system name, priority level, and initial intake date so the file is immediately identifiable across systems and audits.

Timeline

Chronological log of events with timestamps, actions taken, and persons involved to demonstrate responsiveness and procedural adherence.

Root Cause

Concise explanation of the primary cause, supporting evidence (logs, traces), and whether the cause is recurring or isolated.

Corrective Actions

Detailed list of fixes applied, code or configuration changes, mitigation steps, and any follow-up tasks assigned for preventing recurrence.

Customer Impact

Document affected users, data exposure (if any), service degradation, and any contractual remedies such as credits or refunds.

Sign-off

Approval block with signer name, role, signature method, and date to formally close the case and trigger retention workflows.

Essential Data and Compliance Information to Capture

PII/PHI exposure: Indicate if personal or health data was involved.
Regulatory tags: Flag HIPAA, FERPA, PCI, or other applicable regimes.
Encryption status: Note whether data at rest/in transit was encrypted.
Audit trail: Record timestamps, IP addresses, and actions.
Notices sent: Document any breach or customer notifications.
Follow-up tasks: List required remediation and owners.

Common Preparation Errors to Avoid

  • Incomplete timelines that lack timestamps or omit who performed each action, which undermines auditability and SLA verification.
  • Using vague language like 'issue fixed' without describing technical actions, code changes, or the method used to validate the fix.
  • Missing signatory authority or unsigned close blocks, which can leave the resolution non-binding for contractual or legal disputes.
  • Failing to flag regulated data exposure (PHI/PCI) or to follow breach-notification protocols, increasing legal and financial risk.

Risks and Potential Consequences of Inaccurate Records

Compliance fines: HIPAA penalties for mishandled PHI.
Contract breach: Service credit or indemnity obligations.
Liability exposure: Customer claims for damages.
Operational loss: Repeat incidents from incomplete fixes.
Evidence gaps: Weakened defense in disputes or audits.
Reputational harm: Customer churn and public complaints.

Where to File or Send the Completed Support Resolutions Document

Use predefined routing so the document reaches all required teams and is stored according to retention and access policies.

  • Internal Repository: Store in your ticketing or document management system.
  • Customer Attachments: Send finalized copy to the customer contact if required.
  • Legal Hold: Escalate to Legal if litigation risk exists.
  • Audit Archive: Move to long-term retention storage per policy.

Configuring an Online Workflow for This Document

Configure fields, routing, and retention rules in your eSignature or DMS platform to standardize completion and storage.

Field Configuration
Signature Block Require signer name, role, and date fields
Authentication Email link or SMS code; add KBA for higher assurance
Routing Auto-route to support lead, account manager, then legal
Retention Tag Apply retention label and export to archive

Technical and Integration Considerations for eSubmission

Ensure your chosen platform supports the authentication, audit, and retention needs required for this document.

  • Formats: PDF, DOCX, and PDF/A supported
  • Integrations: Connectors for CRM and cloud storage
  • Security: AES-256 at rest; TLS 1.2/1.3 in transit

Integrate with ticketing, cloud storage, and legal systems to automate routing, retention, and audit evidence capture.

eSignature Vendor Comparison for Support Resolutions Documents

Compare baseline pricing and core features for common eSignature vendors. signNow appears first to maintain consistent vendor ordering.

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 trial, no CC No No No No
Bulk Send Yes Yes Yes Yes No
Audit Trail Yes Yes Yes Yes Yes
HIPAA Compliant Yes (BAA) Yes Yes No No

Who Can Sign and Authorize a Support Resolutions Document

Support Manager

The support manager or team lead typically approves technical accuracy and confirms remediation steps; their signature attests that troubleshooting met internal standards and that follow-up items are assigned.

Legal Counsel

When incidents implicate regulatory exposure or contractual remedies, legal counsel reviews and signs to confirm that notifications and mitigation steps satisfy compliance and contractual obligations.

Typical Timelines and Processing Expectations

While policies vary by organization, use these common internal deadlines as baseline expectations for case handling and closure.

Acknowledgement Time:

Acknowledge receipt within 24 hours of the report.

Initial Response:

Provide initial troubleshooting within 48–72 hours for standard incidents.

Resolution Target:

Aim to resolve or escalate within 5 business days.

Customer Confirmation:

Obtain customer acceptance or sign-off within 10 business days after resolution.

Legal Escalation:

Escalate to Legal immediately if potential regulatory or material financial impact exists.

Frequently Asked Questions About Support Resolutions Documents

Answers to common questions about signing, notarization, retention, and what to do when data or compliance issues arise.


Need help? Contact support

be ready to get more
Join over 28 million airSlate SignNow users