Establishing secure connection…Loading editor…Preparing document…

Business Services Atlassian

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

BUSINESS SERVICES ATLASSIAN

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

WHEREAS

WHEREAS, Service Provider is duly qualified and experienced in providing consulting, configuration, administration, and integration services for Atlassian products and related business process services as set forth in this Agreement;

WHEREAS, Client desires to engage Service Provider to perform the services described in the Scope of Work and Service Provider is willing to perform such services under the terms and conditions set forth herein; and

WHEREAS, the Parties intend that the services be delivered in a professional manner consistent with industry standards and that confidential information exchanged in the course of performance be protected as provided below.

SCOPE OF WORK

Service Provider will provide business services related to Atlassian products, including but not limited to: system assessment, configuration, workflow design, plugin selection and installation, user training, migration support, and ongoing administrative support as further detailed below. Specific deliverables, milestones, and acceptance criteria shall be as set forth in the Scope of Work field.

PAYMENT TERMS

In consideration for the services, Client shall pay Service Provider the fees set forth below. Fees are exclusive of applicable taxes unless otherwise stated. All payments shall be made in U.S. dollars unless the Parties agree otherwise in writing.

Service Provider may suspend performance if undisputed invoices remain unpaid after the stated payment period, provided Service Provider gives Client at least five (5) business days' prior written notice and an opportunity to cure.

TERM AND TERMINATION

This Agreement commences on Commencement Date: and, unless earlier terminated in accordance with this Agreement, continues until End Date: .

Either Party may terminate this Agreement for convenience upon providing written notice to the other Party at least Notice Period (days): days prior to the intended termination date. Either Party may terminate for material breach if the breaching Party fails to cure the breach within Cure Period (days): 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. Sections concerning Confidentiality, Indemnification, Limitation of Liability, and Governing Law shall survive termination.

CONFIDENTIALITY

For purposes of this Agreement, "Confidential Information" means non-public information disclosed by a 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, including business processes, configuration details, implementation plans, and access credentials. Confidential Information does not include information that: (a) is or becomes publicly available through no fault of the receiving Party; (b) was rightfully known to the receiving Party prior to disclosure; (c) is received from a third party without breach of an obligation of confidentiality; or (d) is independently developed without use of the disclosing Party's Confidential Information.

The receiving Party shall use the same degree of care to protect Confidential Information as it uses to protect its own confidential information, but with no less than reasonable care. The receiving Party shall not use Confidential Information for any purpose other than performance under this Agreement and shall not disclose Confidential Information to third parties except to employees, contractors, or advisors who have a need to know and who are bound by confidentiality obligations at least as protective as those in this Agreement. Confidentiality obligations shall continue for Confidentiality Duration (years): years following termination or expiration of this Agreement.

INTELLECTUAL PROPERTY AND DATA

Unless otherwise agreed in writing, Service Provider retains ownership of tools, methods, templates, and pre-existing intellectual property used to perform the services. Deliverables specifically developed for Client under this Agreement will be owned by Client upon full payment, subject to Service Provider's retained rights in pre-existing materials and third-party components. Client grants Service Provider a limited, revocable license to access Client systems and Atlassian instances solely to perform the services described herein.

Each Party shall comply with applicable data protection laws in handling personal data. Service Provider shall process personal data only in accordance with Client's documented instructions and for the purposes of performing the services under this Agreement.

LIMITATION OF LIABILITY

EXCEPT FOR LIABILITY RESULTING FROM A PARTY'S WILLFUL MISCONDUCT OR GROSS NEGLIGENCE, IN NO EVENT SHALL EITHER PARTY'S AGGREGATE LIABILITY ARISING OUT OF OR RELATED TO THIS AGREEMENT EXCEED THE TOTAL AMOUNTS PAID OR PAYABLE BY CLIENT TO SERVICE PROVIDER UNDER THIS AGREEMENT IN THE SIX (6) MONTHS PRECEDING THE EVENT GIVING RISE TO LIABILITY. THIS LIMITATION APPLIES TO ALL THEORIES OF LIABILITY, INCLUDING CONTRACT, TORT, AND STRICT LIABILITY.

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 rules. The Parties expressly submit to the exclusive jurisdiction of the state and federal courts located within that state for resolution of disputes.

ENTIRE AGREEMENT

This Agreement, including all schedules and attachments executed by the Parties, constitutes the entire agreement between the Parties with respect to the subject matter hereof and supersedes all prior and contemporaneous agreements, proposals, statements of work, and communications, whether written or oral. No amendment to this Agreement shall be effective unless in writing and signed by authorized representatives of both Parties.

NOTICES AND CONTACTS

ADDITIONAL ACKNOWLEDGMENTS

The Parties acknowledge that the performance of services may require elevated access to Client's Atlassian instances and related systems. Client authorizes such access subject to the minimum principle of privileges and the security measures described below. Service Provider will document any required credentials and return or destroy such credentials upon completion of services.

By signing below, each Party represents and warrants that it has full power and authority to enter into this Agreement and to perform its obligations hereunder.

Service Provider (Print Name):

By:

Date:

Client (Print Name):

By:

Date:

Enter text✕

What the Business Services Atlassian document covers

The Business Services Atlassian is a standardized service agreement used to document the scope, deliverables, pricing, timelines, and responsibilities for professional services related to Atlassian products and integrations. It typically combines a statement of work, service levels, change management and data handling provisions that govern vendor and client interactions. The template is intended for commercial use between businesses, and when executed electronically it must meet the ESIGN and applicable state UETA/ESRA criteria to be legally binding across most U.S. jurisdictions.

Why a clear Business Services Atlassian matters

A well-structured Business Services Atlassian clarifies obligations, reduces disputes, and speeds onboarding. Clear terms on scope, SLAs, data security, and change orders cut rework and provide a defensible record if performance or payment issues arise under ESIGN and contract law.

Why a clear Business Services Atlassian matters

Typical teams and roles that complete this document

The Business Services Atlassian is used by cross-functional teams that manage procuring, delivering, and approving Atlassian-related services.

  • Procurement and sourcing teams managing vendor selection and contract terms.
  • IT and platform teams responsible for deployment, configuration, and integrations.
  • Legal and compliance reviewers overseeing terms, data handling, and risk allocation.

Stakeholders from procurement to operations use the executed agreement to manage delivery, invoicing, and compliance throughout the engagement.

Who typically signs and approves the agreement

Jordan Lee, Procurement Manager

Jordan evaluates vendor terms, negotiates pricing and payment schedules, and ensures the contract aligns with company procurement policies. They coordinate internal approvals and confirm that scope and deliverables match the purchase requisition.

Ava Patel, General Counsel

Ava reviews indemnities, warranty language, data protection clauses, and termination rights. She confirms enforceability under applicable state law and advises on any statutory requirements affecting eSigning or retention.

Core components to include in a professional agreement

A complete Business Services Atlassian combines technical, commercial, and legal elements so both parties have a clear operating playbook throughout the engagement.

Scope of Work

Describe services in measurable terms: deliverables, milestones, acceptance criteria, and excluded tasks. Precise scope prevents scope creep and supports change order routing and invoicing.

Service Levels

Define response and resolution targets, uptime commitments, and remedies for missed SLAs. Include reporting frequency and escalation points to make performance measurable and auditable.

Fees and Payment

State rates, billing cadence, accepted payment methods, expense reimbursement rules, and late payment interest. Specify invoicing requirements and any retainers or milestone-based payments.

Term and Termination

Specify the initial term, renewal mechanics, termination for convenience and cause, notice periods, and post-termination transition obligations for data and access.

Data Security and Privacy

List applicable data classifications, security controls, incident notification timelines, and compliance obligations such as HIPAA when relevant. Address data return or deletion at contract end.

Change Management

Set a formal process for scope changes, approval authority, pricing adjustments, and schedule impacts. Attach a change order template to record agreed modifications.

Step-by-step: complete and execute the agreement

Follow these sequential steps to prepare, review, and finalize the Business Services Atlassian with electronic signatures.

  • 01
    Prepare Document: Populate fields and attach exhibits.
  • 02
    Internal Review: Legal and procurement review terms.
  • 03
    Send for Signature: Assign signing order and send.
  • 04
    Record and Store: Save executed copy and audit trail.

Typical electronic signing workflow

Electronic execution follows a predictable flow; each step creates an auditable record to support enforceability and retention requirements.

  • Upload: Add final draft and attachments.
  • Place Fields: Insert signature, initial, and date fields.
  • Authenticate: Choose email, SMS, or stronger verification.
  • Complete: Signer executes and receives completed copy.

Recommended online workflow settings

Standardize settings to ensure consistent routing, authentication, and recordkeeping for service agreements.

Field Configuration
Signing Order Role-based sequential signing
Authentication Email verification plus optional SMS OTP
Templates Save vetted clause sets as reusable templates
Integrations Connect to Jira, Confluence, Slack for automation

Technical formats and integration needs

Ensure the document platform supports required file types, APIs, and identity checks before sending for signature.

  • File Formats: PDF, DOCX, and editable templates
  • Authentication: Email, SMS OTP, or stronger methods
  • Integrations: Salesforce, NetSuite, Google Workspace

Security and compliance checkpoints

Encryption: TLS 1.2/1.3; AES-256
Audit Trail: Timestamps and IP logs
Certifications: SOC 2 Type II; ISO 27001
HIPAA: BAA required for PHI
21 CFR Part 11: Support for FDA records
Accessibility: WCAG 2.0 Level AA

Comparing eSignature vendor pricing and limits

A concise vendor comparison focused on entry pricing, trial availability, bulk send capability, audit trail presence, and envelope limits where applicable.

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 plan Varies by plan Varies by plan Varies by plan
Bulk Send Yes (Business Premium) Yes Yes Yes No
Audit Trail Yes Yes Yes Yes Yes
Envelope Cap No cap 100 envelopes/user/year No cap No cap No cap

Key dates commonly tracked in the agreement

List contractual dates explicitly to avoid ambiguity about when obligations begin, payments are due, and renewal or termination windows close.

Effective Date:

Enter MM/DD/YYYY; triggers obligations and timelines.

Service Commencement:

Start within specified days after effective date.

Payment Due:

Net 30 or other agreed payment term from invoice date.

Renewal Notice:

Typically 30 to 90 days prior to renewal date.

Deliverable Deadlines:

Specify milestone dates and acceptance windows.

Common preparation mistakes to avoid

  • Using vague scope language that creates disagreement about deliverables and billing.
  • Entering inconsistent legal names or signatory titles that delay payment and tax reporting.
  • Omitting data handling or security clauses for regulated data such as PHI or financial records.
  • Failing to define change order process, causing disputes when requirements shift.

Short list of legal and financial risks

Breach Damages: Contract damages and reputational harm
Late Payment: Interest, collection costs
Tax Penalties: Backup withholding or IRS fines
I-9 Violations: Civil fines for paperwork errors
HIPAA Fines: Potential enforcement penalties
Information Return Penalties: See IRC §6721 for fines

Real-world examples using an eSigned template

Practical examples show how standard clauses and eSigning reduce turnaround and support compliance in live engagements.

Optica Ventures (COO)

When onboarding recurring service work we used a standard template and eSign to reduce back-and-forth.

  • The interface remained simple for clients.
  • The result was faster acceptance and fewer execution errors, enabling consistent invoicing and clearer scope control across projects.

Martin Properties (Founder)

For property platform integrations we deployed a single agreement template and electronic signing.

  • Mobile signing enabled field approvals.
  • This allowed responsive project starts, preserved audit trails for vendor changes, and improved compliance when multiple stakeholders signed remotely.

Frequently asked questions and common issues

Answers to common legal, technical, and administrative questions about preparing, executing, and storing the Business Services Atlassian.


Need help? Contact support

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