Can this agreement be e-signed?

Yes. Electronic signatures are generally enforceable under the federal ESIGN Act (15 U.S.C. §7001) and UETA in most states, provided the signature shows intent, consent, attribution, and the record can be retained and reproduced.

Is notarization required?

Typically no for a fob custody agreement, but some states or specific landlord/tenant contexts may require notarization; check state law or lease terms before omitting notarization.

Who must sign the agreement?

Both the issuing organization (authorized representative) and the holder should sign; an authorized signer demonstrates organizational consent and the holder demonstrates acceptance and attribution.

How do I cancel or revoke access?

Revocation is usually performed by the issuer (deactivating the fob) per the agreement's return and revocation clause; notify the holder in writing and document the deactivation in access logs.

What if the holder disputes a replacement fee?

Maintain the signed agreement, incident report, and any cost receipts. Clear, pre-agreed fees and documented loss reports strengthen enforceability and reduce dispute risk.

How should signed copies be stored?

Keep a tamper-evident signed PDF with an audit trail (timestamps, signer emails, IP) in secure records storage; for HIPAA-related contexts, enforce access controls and follow 45 CFR §164.530(j).

Electronic Signature
Templates
Miscellaneous
Miscellaneous Fob Holder Agreement

Miscellaneous Fob Holder Agreement

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

Miscellaneous Fob Holder Agreement

This Miscellaneous Fob Holder Agreement (the Agreement) is entered into as of Effective Date: by and between Issuer Name: and Holder Name: .

WHEREAS

WHEREAS, Issuer supplies electronic access devices (fobs) to authorized individuals for controlled access to the Premises located at Address: ; and

WHEREAS, Holder requires access to the Premises for legitimate business purposes and agrees to the terms and conditions set forth in this Agreement; and

WHEREAS, Issuer and Holder desire to set forth the rights, obligations, fees and return requirements related to issuance and use of the fob(s).

Scope of Work (Access and Responsibilities)

The Holder is granted non-exclusive, revocable limited access to the Premises only for the purposes described below. Access is subject to the rules and restrictions in this Agreement and any reasonable security procedures adopted by Issuer.

Detailed Access Scope and Holder Obligations

Fob Details

Number of Fobs Issued Fob Identification (IDs or Serial Numbers) Condition on Issue (notes)

Payment Terms

Holder shall pay the following amounts in consideration for issuance and maintenance of fob(s):

Deposit / Issuance Fee Payment Schedule (dates/methods) Replacement Fee for Lost/Damaged Fob Late Payment Fee

Term and Termination

This Agreement commences on Start Date: and will continue until End Date: , unless earlier terminated in accordance with this Agreement.

Either party may terminate this Agreement for convenience upon Notice Period: days' prior written notice to the other party. Issuer may immediately suspend or revoke access for breach, security risk, suspected unauthorized duplication of the fob, or failure to pay amounts due.

Confidentiality and Security

Holder shall treat all security codes, schedules, access procedures and the physical fob(s) as confidential. Holder shall not disclose, reproduce, copy, duplicate, or allow others to use the fob(s) or any associated access credentials. Holder shall immediately report lost or stolen fob(s) to Issuer.

Holder Acknowledgment (check to acknowledge) I acknowledge and agree to the confidentiality and security obligations above.

Liability; Indemnity; Remedies

Holder is responsible for all acts and omissions that result from use of the fob(s). Holder shall indemnify, defend and hold harmless Issuer and its agents, employees and affiliates from and against any claims, losses, damages or liabilities arising out of Holder's misuse of the fob(s), negligence, willful misconduct, or failure to report loss or theft.

Issuer's liability for any claim arising under or relating to this Agreement shall not exceed the total fees paid by Holder to Issuer under this Agreement during the six (6) months immediately preceding the event giving rise to the claim. In no event shall Issuer be liable for incidental, consequential or punitive damages.

Return of Fobs; Forfeiture

Upon termination or expiration of this Agreement, Holder shall return all fob(s) to Issuer within seven (7) days. Failure to return fob(s) shall entitle Issuer to retain any deposit and charge additional replacement fees. Holder remains responsible for access and any use until the fob(s) are returned or access is otherwise terminated by Issuer.

Notices

Issuer Mailing Address for Notices Holder Mailing Address for Notices

Governing Law; Miscellaneous

This Agreement shall be governed by and construed in accordance with the laws of the State of , without regard to conflict of laws principles.

If any provision of this Agreement is held invalid or unenforceable, the remainder of the Agreement shall continue in full force and effect. No waiver by either party of any breach shall constitute a waiver of any subsequent breach.

Entire Agreement

This Agreement constitutes the entire agreement between Issuer and Holder with respect to the subject matter hereof and supersedes all prior and contemporaneous agreements, understandings and representations, whether oral or written. Any amendments must be in writing and signed by both parties.

Issuer:

Print Name:

By:

Date:

Holder:

Print Name:

By:

Date:

What the Miscellaneous Fob Holder Agreement Is

A Miscellaneous Fob Holder Agreement documents the assignment, custody, transfer, or permitted use of access fobs, electronic keys, or similar security tokens between parties. It defines who holds the fob, the permitted uses, responsibilities for loss or damage, replacement procedures, and any fees or deposit requirements. The agreement can be standalone or annexed to an employment, lease, vendor, or facilities access contract and is commonly used by property managers, employers, and service providers to reduce liability and clarify access controls.

Why a Clear Fob Holder Agreement Matters

A concise agreement reduces access-related disputes, assigns financial responsibility for lost or damaged fobs, and documents consent to access controls. It also supports auditability and access revocation procedures required by facility security policies.

Typical parties who complete this agreement

Organizations and individuals use this agreement whenever physical or electronic access tokens are issued, transferred, or centrally managed.

Property managers and landlords issuing building access fobs for tenants or contractors.
Employers and facilities teams controlling employee or vendor access to secured areas.
IT or security vendors who temporarily hold tokens for maintenance or service access.

Use the agreement to record issuance, establish return procedures, and set replacement fees to limit operational and security risk.

Who signs and why

Facilities Manager

A facilities manager signs to document issuance and to record serial numbers or access levels; the agreement protects the organization by clarifying return obligations, replacement costs, and immediate revocation procedures in case of loss or employment termination.

Employee / Holder

The holder signs to acknowledge receipt, permitted uses, and financial responsibility for loss or damage; the signature provides attribution and demonstrates intent to be bound by the agreement's terms.

Step-by-step: completing a Miscellaneous Fob Holder Agreement

Follow these steps to complete, sign, and retain the agreement in a compliant and auditable way.

01

Prepare document: Use the standard template and enter party names and fob identifiers.
02

Confirm terms: Agree on replacement fees, permitted uses, and return timeline.
03

Signatures: Have holder and issuer sign and date the signature block.
04

Record and retain: Store the signed copy per retention policy with audit trail.

How to set up an online signing workflow

Configure roles, authentication, and notifications before sending for signature to ensure a smooth eSigning process.

Field	Configuration
Signature Authentication	Email link or SMS code for attribution; choose stronger auth for high-security sites
Notifications	Enable signer reminders and completion emails for auditability
Conditional Fields	Use conditional fields for deposits or tiered access levels
Retention Settings	Attach retention tags and export signed PDF to secure storage

Digital signing and platform considerations

Choose a platform that supports clear audit trails, file export, and appropriate signer authentication for access-control documents.

File formats: PDF and DOCX widely supported
Authentication options: Email, SMS code, or higher-assurance methods
Integrations: Connect to HR or property systems for record sync

Ensure the platform can produce a tamper-evident signed PDF with an audit trail (timestamp, IP, signer identity) and export to cloud storage or records management systems.

Typical online signing flow for a fob agreement

An efficient online workflow reduces turnaround and ensures each action is recorded in an audit trail.

Upload: Uploader places required fields and fob identifiers.
Assign signers: Add holder and issuer emails and signing order.
Authenticate: Signer confirms identity via email or SMS code.
Complete: Signed copies and certificate of completion are generated.

Essential clauses to include in the agreement

A well-drafted agreement balances operational needs with enforceable terms; include clauses that enable clear enforcement and auditability.

Issuance Details

Describe the fob serial number, issue date, issuing party, and access level. Precise identifiers prevent disputes over which token is covered by the agreement and enable immediate revocation when necessary.

Permitted Use

Limit access to authorized locations and specify prohibited uses. Clear boundaries reduce unauthorized entry and support disciplinary or recovery actions if the holder breaches use limits.

Loss and Replacement

State holder responsibility for lost or damaged fobs, replacement fee, and timeframe for reporting loss. Explicit financial terms avoid conflicts about who pays for reprogramming or replacement.

Return and Revocation

Set return procedures, deadlines, and immediate revocation triggers (termination, theft). This clause supports security by clarifying when access is revoked and how returns are processed.

Liability Limits

Allocate risk for misuse, indemnification for damages, and any caps on liability. These terms protect both issuer and holder by setting expectation for accountability and remedies.

Data and Audit

Require maintenance of an access log and permission for the issuer to audit token usage. This enables incident investigation and supports compliance with internal security policies.

Practical tips for accurate and efficient agreements

Follow these practices to reduce disputes and speed administrative processes.

Standardize templates

Use a single approved template with controlled fields and drop-downs to avoid inconsistent terms and missing information.

Record serial numbers

Always include unique fob identifiers and link them to access logs for traceability.

Keep signed records

Store signed PDFs with timestamps and audit trails in secure, access-controlled storage.

Automate revocation

Integrate badge systems with HR or property management to revoke access automatically on termination.

Common preparation mistakes to avoid

Omitting the fob serial number or identifier, which prevents reliable tracking and complicates replacement or revocation.
Using vague fee language like 'reasonable replacement cost' instead of naming a fixed fee or formula.
Failing to record the effective date and return deadlines, leading to ambiguity about when obligations begin and end.
Not storing a signed, tamper-evident copy with an audit trail, which weakens enforceability and complicates disputes.

Consequences of an incomplete or incorrect agreement

Unofficial access: Ambiguity in access rights

Financial loss: Unclear replacement cost recovery

Compliance exposure: Weak auditability for security incidents

Enforcement hurdles: Difficulty proving holder responsibility

Operational delays: Delayed revocation increases risk

Liability claims: Potential third-party claims

Real-world examples of how organizations use this agreement

Short examples show how the agreement fits into common operational workflows.

Office Building Manager

A mid-size manager issues fobs to contractors with a 14-day return window and $75 replacement fee.

The contractor signs at check-in and returns the fob at job completion.
The signed agreement and recorded serial number enabled quick recovery when a lost fob triggered an access audit, minimizing disruption and reprogramming costs.

Corporate IT Security

IT issues temporary fobs for after-hours maintenance with limited access.

Access is time-limited and logged.
Automated revocation at the scheduled end date and retained signed agreement supported a post-incident review and demonstrated internal control over privileged access.

How this agreement differs from related access documents

Compare the Miscellaneous Fob Holder Agreement with similar documents to choose the correct form for your situation.

Criteria	Miscellaneous Fob Holder Agreement	Lease Agreement
Notarization Needed		sometimes
Witness Count	none	varies by state
Primary Purpose	fob custody and use	property occupancy terms
Retention Importance	operational audit	legal record for tenancy

Typical eSignature vendor pricing and features for signing access agreements

Compare general starting prices and common capabilities across vendors; signNow is listed first per platform comparisons.

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

Common questions about Miscellaneous Fob Holder Agreements

Answers to frequent questions address enforceability, notarization, revocation, and preferred eSigning methods.

Need help? Contact support

Can this agreement be e-signed?
Yes. Electronic signatures are generally enforceable under the federal ESIGN Act (15 U.S.C. §7001) and UETA in most states, provided the signature shows intent, consent, attribution, and the record can be retained and reproduced.
Is notarization required?
Typically no for a fob custody agreement, but some states or specific landlord/tenant contexts may require notarization; check state law or lease terms before omitting notarization.
Who must sign the agreement?
Both the issuing organization (authorized representative) and the holder should sign; an authorized signer demonstrates organizational consent and the holder demonstrates acceptance and attribution.
How do I cancel or revoke access?
Revocation is usually performed by the issuer (deactivating the fob) per the agreement's return and revocation clause; notify the holder in writing and document the deactivation in access logs.
What if the holder disputes a replacement fee?
Maintain the signed agreement, incident report, and any cost receipts. Clear, pre-agreed fees and documented loss reports strengthen enforceability and reduce dispute risk.
How should signed copies be stored?
Keep a tamper-evident signed PDF with an audit trail (timestamps, signer emails, IP) in secure records storage; for HIPAA-related contexts, enforce access controls and follow 45 CFR §164.530(j).

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now