Establishing secure connection…Loading editor…Preparing document…

AWS Customer Agreement

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

PROPOSED AWS AND NOTICE OF MEETING

Note: Employers use this form to inform employees of the proposed AWS. Seek legal counsel if you do not know the wage and hour rules. (Delete this note prior to use.)

1. Proposed AWS. An alternative workweek schedule (hereinafter, “AWS”) allows for shorter workweeks by allowing employees to work up to 10 hours per day, 40 hours per week, without incurring overtime. (hereinafter, “Company”) is proposing to institute the following AWS for the work unit.

Option 1, describe single schedule The AWS will consist of the following 10-hour days, Monday through Thursday:

Mon Tue Wed Thu Fri Sat Sun
Work Start Time 8:00 a.m. 8:00 a.m. 8:00 a.m. 8:00 a.m. OFF OFF OFF
Work End Time 7:00 p.m. 7:00 p.m. 7:00 p.m. 7:00 p.m.
Lunch 1 hour 1 hour 1 hour 1 hour
TOTAL WORK HOURS 10 10 10 10

Option 2 for Multiple Schedules Two work schedules will be offered in order to cover the operating hours of the business. of the employees must work the schedule while the remaining must work the schedule. Each employee may choose which schedule he or she would like to work. However, those employees with the most will get to choose their schedule first. If is the same between two or more employees, then shall be used to determine who gets to choose their schedule first. After all the positions in one of the schedules are full, the remaining employees will be assigned to the remaining unfilled schedule.

Mon Tue Wed Thu Fri Sat Sun
Work Start Time 8:00 a.m. 8:00 a.m. 8:00 a.m. 8:00 a.m. OFF OFF OFF
Work End Time 7:00 p.m. 7:00 p.m. 7:00 p.m. 7:00 p.m.
Lunch 1 hour 1 hour 1 hour 1 hour
TOTAL WORK HOURS 10 10 10 10

2. Mandatory Meeting. A mandatory meeting with , for which you will be paid to attend, shall be held on the following date to discuss the effects of the AWS on job conditions and benefits.



Location:

3. Secret Ballot. 14 days after the meeting, a vote by secret ballot shall take place on .

4. Written Agreement Required. If the AWS is elected, a written agreement consenting to an AWS must be voluntarily entered into between you and the employer.

5. Holiday Schedules. If a holiday falls on the employee’s normal workday, then the holiday will be observed and the employee will be given hours of holiday pay. If a holiday falls on the employee’s normal day off, then Option 1: no extra day off will be given and no holiday pay will be given. Option 2: a personal day off (with pay if the holiday was a paid holiday) will be given that the employee can use in the future. Option 3: the holiday (both paid and unpaid) will be observed on the employee’s normal workday that is closest to holiday and which is in the same workweek as the holiday so that the employee will get an extra day off (and paid hours if the holiday is a paid holiday) in honor of the holiday.

6. Vacation Accrual. If an employee on an AWS earns a week’s worth of vacation, he or she would have earned the same number of hours of vacation as any other employee with the same number of years of service. Employees who work and AWS and who do not work a full year earn a prorated amount of vacation based on the follow example: If an employee who works an AWS could earn 40 hours of vacation in a year, then that employee earns .20833 hours of vacation for each day worked, up to .8333 hours of vacation per week.

7. Other Fringe Benefits. Except as discussed above, the AWS shall not affect any other benefit offered by the Company.

8. Incomplete Shifts. When on occasion there is not enough regular work to keep the employee busy, the employee will be allowed to voluntarily go home early without completing his or her AWS shift. If an employee goes home early, he or she will not be paid for the un-worked hours. If an employee chooses to stay and complete his or her AWS shift, then the Company will provide the employee with odd jobs for the remainder of the shift. The wage rate for working odd jobs will be minimum wage.

9. Overtime. The AWS would affect overtime compensation as follows:

An overtime rate of compensation of no less than one and one-half times the regular rate of pay shall be paid for:

a) any work exceeding the regularly scheduled hours on a regularly scheduled workday established by the alternative workweek agreement (but not more than 12 hours);

b) any work in excess of 40 hours in a week

c) the first 8 hours of work on any day which is not a regularly scheduled workday established by the alternative workweek agreement.

An overtime rate of compensation of no less than double the regular rate of pay of the employee shall be paid for:

a) any work in excess of 12 hours per day;

b) for any work in excess of eight hours on any day which is not a regularly scheduled workday established by the alternative workweek agreement.

9. Makeup Time. An employee may substitute a day off for a whole workday on occasion to meet the personal needs of the employee without the payment of overtime. Employees cannot substitute part of a workday and make up the time on another workday or on a day off. The employee must substitute a whole workday for a day off.

10. Reasonable Accommodation.

The Company shall make a reasonable effort to find a work schedule not to exceed eight hours in a workday, in order to accommodate any affected employee who was eligible to vote in the election but who is unable to work the alternative schedule hours established as the result of that election. This reasonable accommodation only applies to current employees and does not apply to anyone hired after the date of the election.

The Company shall also explore any available reasonable alternative means of accommodating the religious belief or observance of an affected employee (whether hired before or after the election) that conflicts with an adopted AWS, in the manner provided by subdivision (j) of Section 12940 of the Government Code.

11. Petition for Revocation. After a lapse of 12 months and upon petition of at least one-third (1/3) of the affected employees, a new vote by secret ballot will be held. A 2/3 vote from at least two-thirds (2/3) of the affected employees will be required to reverse the AWS agreement.

12. At-Will Employment. NOTHING ABOUT THE AWS WILL CHANGE THE AT-WILL RELATIONSHIP BETWEEN THE COMPANY AND ITS EMPLOYEES. THE EMPLOYMENT RELATIONSHIP MAY END AT ANY TIME, WITH OR WITHOUT CAUSE, AT THE REQUEST OF THE EMPLOYEE OR THE COMPANY.

13. All Rights Reserved. All the rights of the Company under the rules of AB60, Labor Code §511, and the appropriate regulations adopted by the Industrial Welfare Commission are reserved and shall be followed.

If you have any questions, please contact .



Enter text

What the AWS Customer Agreement Is and Why It Matters

The AWS Customer Agreement is the contractual document that sets the legal relationship between a customer and Amazon Web Services for use of cloud services, billing, support, and intellectual property rights. It defines account responsibilities, payment and billing terms, data handling expectations, termination and suspension rights, and dispute resolution provisions. Organizations use it to establish commercial and compliance obligations for cloud deployment, to allocate risk and liability, and to document which service terms, service-level commitments, and acceptable use rules govern the account.

How the AWS Customer Agreement Protects Your Organization

The agreement clarifies payment and liability exposure, governs data controls and security responsibilities, and sets terms for service availability and dispute resolution under 15 U.S.C. §7001 (ESIGN) and applicable state law such as UETA where relevant.

How the AWS Customer Agreement Protects Your Organization

Who Typically Reviews and Signs the AWS Customer Agreement

Several internal roles commonly interact with and approve the AWS Customer Agreement; responsibilities vary by company size and procurement process.

  • Procurement and IT purchasing teams who verify pricing, procurement terms, and contract duration before account activation.
  • Legal and compliance teams who review liability, data processing provisions, and export controls for regulatory conformity.
  • Finance and billing contacts who confirm billing addresses, tax treatment, and payment methods for invoicing accuracy.

In larger organizations, signatures may require coordinated approval from procurement, legal, and finance; in small organizations a single authorized signer may suffice.

Common Signatory Roles

Procurement Director

Typically coordinates vendor selection, negotiates commercial terms and payment schedules, and ensures procurement rules are followed before the agreement is signed by an authorized representative.

General Counsel

Reviews risk allocation, indemnities, data protection language, and termination provisions; often approves nonstandard amendments and provides final sign-off for higher value or sensitive engagements.

Required Information and Key Fields to Provide

Legal Entity: Full registered business name
AWS Account ID: 12-digit account identifier
Billing Contact: Name, email, phone
Tax Identifier: EIN or SSN where required
Notice Email: Email for formal notices
Authorized Signer: Name and title

Immediate Risks of Incomplete or Incorrect Agreement Data

Tax Withholding: Backup withholding risk 24% if TIN missing
Billing Disputes: Late payment fees and service suspension
Regulatory Exposure: HIPAA noncompliance fines possible
Contractual Liability: Indemnity and limitation clauses enforceable
Account Suspension: Service may be suspended for breach
Tax Penalties: IRC §6721 penalties for reporting errors

Common Mistakes to Avoid When Preparing the Agreement

  • Using an informal or abbreviated legal name that does not match the company’s EIN or articles of organization, which can invalidate invoicing and tax reporting.
  • Failing to designate an authorized signer or providing a person without actual signature authority, resulting in unenforceable commitments or internal disputes.
  • Skipping the notice and billing contact fields or entering incorrect email addresses, which can block legal notices and delay dispute resolution.
  • Overlooking state-specific regulatory clauses or export-control language in the data-processing terms that affect cross-border service usage and compliance.

Step-by-Step: Completing the AWS Customer Agreement

Follow these sequential steps to fill the agreement accurately and reduce review cycles.

  • 01
    Gather documents: Collect EIN, articles, and proof of authority
  • 02
    Enter account info: Provide legal name, AWS account ID, billing contact
  • 03
    Confirm tax details: Attach W-9 when requested by payer
  • 04
    Authorize signature: Signer signs and dates with title

How the Agreement Is Processed After Completion

After the agreement is completed, it typically follows a short internal workflow before becoming effective and tied to the AWS account.

  • Submission: Send completed copy to AWS account team
  • Internal review: Legal or procurement confirms terms
  • Activation: Account features enabled per terms
  • Recordkeeping: Store executed agreement for retention

Configuring an Online Completion Workflow

Set up a simple digital workflow to collect signatures, preserve an audit trail, and automate notifications.

Field Configuration
Signature Field Require signer name, date, and title
Authentication Use email + SMS code for verification
Notifications Auto-send executed copy to parties
Audit Trail Capture IP, timestamp, and actions

Digital Signing and Technical Requirements

Choose a platform that supports legal e-signatures, audit trails, and the integrations your workflow needs.

  • Integrations: Salesforce, NetSuite, Microsoft 365 supported
  • File Formats: PDF, DOCX, and HTML accepted
  • Security: TLS in transit, AES-256 at rest

Ensure the selected provider supports required compliance frameworks (ESIGN, UETA, HIPAA BAA if applicable) and preserves an auditable certificate of completion.

Key Dates and Response Timelines to Note

Track these practical timelines related to agreement effectiveness, billing, and tax document handling.

Effective Date:

Date the signed agreement takes effect

Billing Cycle:

Monthly cycle begins per account billing settings

Dispute Notice Period:

Follow notice windows in the agreement

W-9 Provision:

Provide W-9 when requested by payer

Renewal Notice:

Provide any termination/renewal notice per clause

Typical Milestones from Negotiation to Activation

This sequential milestone overview shows common stages and where attention is most often required.

01

Negotiation

Finalize any nonstandard terms and rates

02

Execution

Obtain authorized signatures and dates

03

Account Activation

AWS links the signed agreement to the account

04

Ongoing Compliance

Monitor billing, security, and subcontractor usage

eSignature Vendor Comparison for Completing Agreements

A concise pricing and capability snapshot for common eSignature vendors; signNow is listed first per comparative format requirements.

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 Varies Varies

Electronic Signature vs Digital (PKI) Signature: Key Differences

Understand the technical and legal distinctions so you can choose the right form of signature for compliance needs.

Criteria Electronic Signature Digital Signature
Definition any electronic symbol pki-based cryptographic signature
Legal Basis esign/ueta acceptance same + certificate authority
Non-repudiation audit trail evidence cryptographic proof
Use Cases general contracts high-assurance, regulated records

Real-World Examples of Agreement Use

These customer examples show practical application of digital agreement workflows in business operations.

Optica Ventures (COO)

The interface is simple and easy-to-use for our team; more importantly, it is just as easy for our customers.

  • They reduced signature friction on vendor agreements.
  • As a result, execution time shortened and internal teams reported fewer follow-ups and cleaner audit trails for procurement.

Tech Data (CEO)

Tech Data uses airSlate SignNow to improve our internal and external customer service while increasing our speed to revenue.

  • The platform integrated with enterprise systems.
  • This integration let them automate billing attachments to executed agreements and accelerate invoice reconciliation across accounts.

Practical Tips for Accurate and Efficient Completion

Follow these practical recommendations to lower risk and shorten review cycles when completing the agreement.

Use consistent legal names and identifiers
Match the legal entity name and EIN exactly to tax and corporate records; consistency prevents withholding, tax reporting, and invoicing mismatches that can disrupt payments.
Designate a single billing contact
A centralized billing contact reduces missed invoices and accelerates dispute resolution by ensuring notices reach the right person quickly.
Retain an auditable eSigning trail
Capture timestamps, IP addresses, and authentication method so the signed agreement is defensible and reproducible for audits or dispute proceedings.
Limit custom redlines
Negotiate only high-impact clauses and attach a separate schedule for negotiated items to reduce legal review time and maintain standard service terms.

Frequently Asked Questions About the AWS Customer Agreement

Answers to common questions about enforceability, signatures, notarization, and recordkeeping for the AWS Customer Agreement.


Need help? Contact support

Explore Templates

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