Can the form be signed electronically?

Yes. Electronic signatures are generally valid under the federal ESIGN Act (15 U.S.C. §7001) and state UETA laws. Ensure the signer demonstrates intent and consent and retain an auditable record.

Who is authorized to sign the form?

Designate signers in policy—typically the manager, HR representative, and an IT approver. Use role-based authorization to ensure only authorized personnel approve reductions.

Is notarization ever required?

Not for routine access changes. Notarization is generally reserved for certain legal instruments (wills, powers of attorney, deeds). Confirm if your organization or jurisdiction demands extra authentication.

What if access was removed by mistake?

Open a restoration request tied to the original ticket. Record the corrective approval and timestamp. Preserve logs to show both the erroneous removal and the remediation.

How should signed forms be stored?

Store signed copies in a secure records system with immutable audit trails, exportable PDFs, and controlled access. Follow retention schedules applicable to your industry.

How long until billing reflects the change?

Billing timing depends on subscription terms and the effective date set on the form; adjustments commonly apply at the next billing cycle or prorate based on the effective date.

User Decrease Form

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

USER DECREASE FORM

Client Name: Provider Name: Account / Contract Number: Primary Contact Name:

Contact Email:

Contact Phone:

Recitals

WHEREAS, the parties identified above have entered into an agreement governing access to the Provider's systems and services for the account identified by Account / Contract Number: ; and

WHEREAS, Client desires to decrease the number of authorized user accounts, reassign licenses or otherwise remove specified user access, and Provider is willing to implement such reductions in accordance with the terms and any applicable fees or prorations set forth in this form and the governing agreement; and

WHEREAS, the parties wish to document the scope, effective date and financial adjustments associated with the requested user decrease, and to provide mutual authorization for Provider to take the actions described below.

Scope of Work

Provider shall perform the following actions in connection with the user decrease request, and shall take commercially reasonable steps to preserve Client data as set forth in the governing agreement. If any removal will materially affect service delivery, Provider will notify Client and await any required approvals specified by the governing agreement before deprovisioning.

Description of users to be removed (one per line: Full Name — Username/ID — Role — Last Active Date): Additional scope details / special instructions:

Payment Terms

The parties acknowledge that decreasing users may give rise to prorated credits, one-time administrative fees, or no adjustment, depending on the governing agreement and the timing of the decrease. Client elects the following financial adjustments and acknowledges Provider's right to offset outstanding charges.

Adjustment amount (if applicable): Proration or refund schedule: Late fee on outstanding balances:

Select refund or credit method (if an adjustment is due):

Apply credit to account balance Issue refund to payment method on file No refund; record as forfeited in accordance with agreement

Term and Termination

This User Decrease Form modifies the parties' existing service relationship with respect to the accounts and users identified herein and is effective as of the Effective Date set forth below, subject to the notice and cure provisions of the parties' governing agreement.

Requested effective date of decrease:

Agreement start date (if different):

Notice period required prior to deprovisioning (days): Cure period for disputed removals (days):

Confidentiality

Each party shall maintain the confidentiality of the other party’s non-public information disclosed in connection with this User Decrease Form. Provider shall treat any retained data associated with removed users in accordance with the data retention and deletion provisions of the governing agreement. Confidential information shall not be disclosed except as required by law or with the prior written consent of the disclosing party.

Governing Law

This User Decrease Form shall be governed by and construed in accordance with the laws of the jurisdiction specified in the parties' governing agreement. If no such jurisdiction is specified, the laws of the state of: shall apply, without regard to conflict-of-law principles.

Entire Agreement

This User Decrease Form, together with the parties' underlying service agreement and any exhibits referenced herein, constitutes the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior and contemporaneous communications and proposals, whether oral or written, relating to the same subject matter. No modification is effective unless in writing and signed by authorized representatives of both parties.

Authorizations and Certifications

The undersigned certifies that they are an authorized representative of the party for which they sign, that the information provided in this User Decrease Form is true and complete to the best of their knowledge, and that they have the authority to request the user decreases and any associated financial adjustments set forth herein.

Authorized representative name (if different from printed signer): Title / Position: Comments or special handling requests:

Client:

By:

Date:

Provider:

By:

Date:

What the User Decrease Form Is and when it's used

A User Decrease Form documents the removal or reduction of a user's access, allocation, or assigned resources within an account, subscription, or internal system. It records who requested the change, the user or license affected, the effective date, and any approvals or financial adjustments. Organizations use this form to ensure consistent offboarding, correct billing adjustments, and audit trails for access control. The completed form becomes an administrative record used by IT, HR, finance, and compliance teams to reconcile access lists and billing statements.

Why a well-prepared User Decrease Form matters

A clear, completed User Decrease Form reduces security risk, prevents billing errors, and creates a defensible audit trail for access changes. It formalizes approvals and timestamps effective dates so internal controls and cost allocation remain accurate.

Which teams typically complete or receive this form

Centralizing these roles on the form helps ensure the reduction is complete, reversible only by authorized processes, and supported by documentation.

IT administrators: Validate technical access removed and record system account changes with exact usernames and timestamps.
Human resources: Confirm employment status or role changes and maintain personnel records linked to the access change.
Finance or billing: Reconcile license, seat, or subscription reductions and adjust invoices or cost centers accordingly.

Essential parts of a professional User Decrease Form

A thorough form combines identification, change details, approvals, effective timing, billing impact, and an audit trail to support operational and compliance needs.

User ID

Record the unique account or username and any internal identifier used to locate the user in systems and logs, enabling precise deprovisioning.

Change Type

Specify whether the action is full removal, role downgrade, license reduction, or temporary suspension and include the reason for the change.

Effective Date

Provide the exact date and time the change should take effect; this controls billing proration and access termination timing.

Approvals

Capture manager and department head approvals with printed name, title, signature, and date to demonstrate authorization for audit purposes.

Billing Impact

Describe seat counts or subscription adjustments, any required refunds or proration, and the cost center to be credited or debited.

Audit Trail

Include a field for the person executing the change, execution timestamp, and any related ticket or change request IDs for traceability.

Required data elements at a glance

User Identifier: Username or employee ID

Requester: Name and department

Type of Change: Removal, downgrade, or suspension

Effective Date: MM/DD/YYYY

Approval: Manager name and signature

Related Ticket: Change request or ticket ID

Step-by-step: completing the User Decrease Form

Follow a consistent sequence to prevent access gaps and billing mistakes: identify, authorize, schedule, execute, and verify.

01

Identify record: Locate the exact user account and relevant identifiers before editing access.
02

Request approval: Collect manager and department approvals in writing or via an authorized electronic workflow.
03

Schedule change: Set an effective date and coordinate across IT and billing teams to align timing.
04

Execute and verify: Remove access, adjust billing, and confirm completion with a ticket closure or signed confirmation.

Configuring an online User Decrease workflow

Set up fields, approvals, and automated routing to avoid manual handoffs and missed steps.

Field Mapping	Map form fields to HR and directory attributes for automation
Approval Sequence	Define manager → IT → finance order with conditional routing
Notifications	Enable email/SMS triggers for pending and completed states
Execution Action	Connect automation to deprovisioning script or ticket action
Audit Log	Capture signer, timestamp, and ticket linkage automatically

Technical considerations for electronic completion and signatures

Ensure the selected solution provides tamper-evident records, retention controls, and exportable audit reports so the form supports compliance and internal review.

File formats: PDF and DOCX supported
Authentication: Email, SMS, or MFA options
Integrations: Connects to HR and ticketing systems

Typical routing: who sees the form and when

A standard routing model reduces delay and documents the authorization path from request to completion.

Requester submits: Manager or HR initiates the form with required fields completed
Manager approval: Direct manager reviews and signs to authorize the change
IT execution: IT removes access and records the execution timestamp
Finance reconciliation: Billing adjusts seat counts and posts any proration

Typical timelines and processing expectations

Establish internal SLAs to align access changes with payroll, billing cycles, and security reviews; those timelines depend on company policy.

Advance notice:

Submit at least 3–10 business days before the desired effective date

IT action window:

IT typically completes deprovisioning within 24–72 hours of approval

Billing alignment:

Adjustments often apply at the next billing cycle; confirm proration rules

Appeals period:

Allow 5–10 business days to review disputes or restoration requests

Record retention:

Store signed forms per retention policy immediately after completion

Key risks and consequences of incorrect or missing forms

Unauthorized access: Persistent access increases security breach risk

Billing errors: Overpayment or underbilling for seats

Compliance gaps: Failed audits or internal control exceptions

Data loss: Premature deletion can affect investigations

Operational delay: Missing approvals slow downstream workflows

Legal exposure: Contractual disputes over termination timing

Typical eSignature vendor pricing and capability snapshot

For organizations assessing electronic completion of User Decrease Forms, compare price, trial availability, bulk send, audit trail, HIPAA support, and envelope caps across vendors.

	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	Yes	Yes	Yes	No
Audit Trail	Yes	Yes	Yes	Yes	Yes
Envelope Cap	No cap	100 envelopes/user/year	Varies	Varies	Varies

Practical tips to complete the form accurately and quickly

Follow consistent naming, standard approval sequences, and automated verification to reduce errors and processing time.

Standardize identifiers

Use the canonical username or employee ID from HR and directory services to avoid mismatches when deprovisioning.

Require approvals

Enforce manager and IT approvals in a defined order so no single party can bypass controls.

Automate routing

Connect the form to ticketing and billing systems so execution updates are logged and invoices adjust automatically.

Keep an audit trail

Record who executed the change, the timestamp, and the related ticket to support audits and incident response.

Real-world examples of how organizations use this form

Two practical examples show typical uses across industries and how the form supports operational needs.

Real Estate — Martin Properties

Property manager removed a user to limit access after termination

Action triggered coordinated IT and billing updates
The completed form linked to the tenant file and billing proration, preventing a $1,200 overcharge and supporting audit evidence.

Healthcare — Fertility Centers of Illinois

Clinic updated staff access after role change to protect PHI

HR and IT approvals recorded before deprovisioning
The record preserved signatures and timestamps to meet HIPAA documentation and internal compliance checks.

Frequently asked questions about the User Decrease Form

Answers to common questions cover electronic validity, signature authority, timelines, and recovery steps for mistakenly removed access.

Need help? Contact support

Can the form be signed electronically?
Yes. Electronic signatures are generally valid under the federal ESIGN Act (15 U.S.C. §7001) and state UETA laws. Ensure the signer demonstrates intent and consent and retain an auditable record.
Who is authorized to sign the form?
Designate signers in policy—typically the manager, HR representative, and an IT approver. Use role-based authorization to ensure only authorized personnel approve reductions.
Is notarization ever required?
Not for routine access changes. Notarization is generally reserved for certain legal instruments (wills, powers of attorney, deeds). Confirm if your organization or jurisdiction demands extra authentication.
What if access was removed by mistake?
Open a restoration request tied to the original ticket. Record the corrective approval and timestamp. Preserve logs to show both the erroneous removal and the remediation.
How should signed forms be stored?
Store signed copies in a secure records system with immutable audit trails, exportable PDFs, and controlled access. Follow retention schedules applicable to your industry.
How long until billing reflects the change?
Billing timing depends on subscription terms and the effective date set on the form; adjustments commonly apply at the next billing cycle or prorate based on the effective date.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now