Can the form be electronically signed?

Yes. Electronic signatures are legally valid under the federal ESIGN Act (15 U.S.C. ch. 96) and UETA where adopted. Ensure the signature meets intent, consent, attribution, and retention requirements to satisfy 15 U.S.C. §7001 standards.

Do I need a notary for device records?

Generally no for internal inventory or support purposes. Notarization is only required when a device record must serve as an acknowledged legal instrument; check state law and the receiving party's requirements before obtaining notarization.

What if the device holds patient data?

If the device stores or transmits protected health information (PHI), apply HIPAA safeguards and execute a BAA with vendors. Retention and access controls must follow 45 CFR §164.530(j) and relevant organizational policies.

How do I correct an error after submission?

Create an amendment or corrected form that references the original record and includes a signed attestation describing the correction. Preserve both records in the audit trail to maintain forensic integrity.

Is remote notarization (RON) acceptable?

RON is permitted in most states but requirements vary. Confirm identity-proofing, audio-video recording retention, and any state-specific rules before relying on a remote notarization method.

How long must I keep these records?

Retention depends on purpose: follow federal minimums (e.g., IRS 3 years under IRC §6501(a)), HIPAA 6-year rule (45 CFR §164.530(j)) where applicable, and any longer state or industry-specific obligations.

Electronic Signature
Templates
Miscellaneous
Device Information Form

Device Information Form

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

DEVICE INFORMATION FORM AND SERVICE AGREEMENT

This Device Information Form and Service Agreement (the "Agreement") is made by and between:

Client Name: Provider Name:

Agreement Date:

WHEREAS

WHEREAS, Client desires to obtain devices and related services from Provider and requires a written record of device details, custody, and service obligations; and

WHEREAS, Provider is duly qualified and equipped to supply, configure, maintain and, where applicable, service devices described in this form under the terms and conditions set forth in this Agreement; and

WHEREAS, the parties intend for this Device Information Form to record device-specific data and to constitute the operative agreement governing custody, service obligations, payment terms and confidentiality for the listed device(s).

DEVICE DETAILS

Device Identifier / Asset Tag: Device Type: Manufacturer:

Model Number:

Serial Number:

IMEI / MAC Address (if applicable): Condition on Delivery: Accessories Included: Software / Configuration Summary:

Assigned To (Name / Role):

Department / Location:

Delivery Date:

Expected Return Date (if loaned):

Ownership and Security Flags: Device is company property Device may contain sensitive or confidential data Device is required to be encrypted per policy

SCOPE OF WORK

The parties agree that Provider will perform the services related to the device described above. Detailed scope, tasks and deliverables are documented below. Provider's obligations include configuration, deployment, maintenance, and reasonable troubleshooting related to the device, subject to the terms herein.

Scope of Work (describe services to be provided):

PAYMENT TERMS

Client shall pay Provider for services and/or devices in accordance with the following terms.

Total Payment Amount: Payment Schedule / Milestones: Late Payment Fee:

TERM AND TERMINATION

This Agreement commences on the Start Date below and continues until the End Date or until earlier terminated in accordance with this section.

Start Date:

End Date:

Notice Period for Termination:

CONFIDENTIALITY

Each party acknowledges that in connection with the performance of this Agreement it may receive Confidential Information of the other party. "Confidential Information" includes device configurations, passwords, system architecture, personally identifiable information and any business information reasonably understood to be confidential. Each party shall: (a) use Confidential Information only for performance under this Agreement; (b) restrict access to employees and agents on a need-to-know basis; and (c) not disclose Confidential Information to third parties except as required by law. The obligations in this section survive termination for a period of three (3) years.

Acknowledgement of Confidentiality (check to acknowledge): I acknowledge and will comply with the confidentiality obligations set forth above.

GOVERNING LAW

This Agreement shall be governed by and construed in accordance with the laws of the jurisdiction identified below without regard to conflicts of law principles.

Governing Law (State / Jurisdiction):

ENTIRE AGREEMENT

This Agreement, together with any attached device schedules and forms completed pursuant hereto, constitutes the entire agreement between the parties with respect to the subject matter and supersedes all prior and contemporaneous agreements, proposals and communications, whether written or oral. Any amendment or waiver must be in writing and signed by both parties.

ADDITIONAL NOTES / MAINTENANCE LOG

Maintenance / Service Notes:

Client:

By:

Date:

Provider:

By:

Date:

What the Device Information Form Is

A Device Information Form is a standardized record used to capture technical and ownership details about an electronic device for inventory, support, warranty, compliance, or asset-management purposes. Typical entries include device identifiers (serial number, IMEI, MAC), make and model, configuration or software versions, assigned user or department, physical location, and date of issue. Organizations use this form to track custody, perform security assessments, support maintenance, and meet regulatory or contractual recordkeeping obligations where device provenance or configuration matters.

Why a Clear Device Information Form Matters

A concise, accurate Device Information Form reduces support time, helps maintain security posture, and provides a consistent audit trail for compliance checks. For regulated contexts it helps demonstrate control over device lifecycles.

Who Typically Completes or Uses This Form

The completed form supports downstream processes such as provisioning, decommissioning, support ticketing, and regulatory audits.

IT asset managers and system administrators responsible for inventory and updates.
Help desk and operations staff documenting incidents, warranties, and repairs.
Security and compliance officers tracking configuration and control status.

Core Sections to Include in a Professional Device Information Form

A complete form groups device identifiers, owner and location, configuration and software state, status and lifecycle dates, supporting documentation, and a signer block that shows who certified the data. Well-structured sections reduce ambiguity and speed processing.

Device Identifiers

Serial number, IMEI, MAC address, and model designation used to uniquely identify the physical device and link to vendor records or warranty claims.

Ownership

Legal entity or individual assigned to the device, department, and contact details used for accountability and return logistics.

Location

Physical location or network zone where the device is deployed; include building, room, or rack identifiers as applicable for asset recovery.

Configuration

Installed OS, firmware and software versions, applied security controls, and any nonstandard modifications that affect support or compliance.

Lifecycle Dates

Issue date, expected decommission date, warranty start/end, and last audit date to track obligations and retention triggers.

Attachments

Place for invoices, warranty certificates, purchase orders, and photos—these support repair, RMA, and audit processes.

Step-by-Step: Filling and Submitting the Device Information Form

Follow these sequential steps to ensure data accuracy, validate identity if needed, and route the completed form to the correct owner or system.

01

Collect Identifiers: Record serial, IMEI, and MAC directly from the device or system console to avoid transcription errors.
02

Confirm Ownership: Enter the assigned user or department and verify contact details for accountability.
03

Attach Evidence: Add photos, receipts, or warranty documents as PDF attachments to support future claims.
04

Sign and Route: Sign the form and route to asset management, procurement, or security for final processing.

How to Configure an Online Device Information Workflow

Key workflow settings reduce manual handoffs and ensure the form enters asset systems with minimum friction.

Field Mapping	Map form fields to your asset inventory fields for automatic ingestion.
Conditional Logic	Show follow-up fields for devices with specific models or warranty claims.
Authentication	Require email, SMS code, or higher-strength authentication for custodial signers.
Template Versioning	Lock approved templates to prevent unauthorized edits to required fields.
Notifications	Set automated emails to asset owners and IT after submission.

Digital Signing, Formats, and Integration Needs

Choose a platform that supports audit trails, API ingestion, and the authentication strength your compliance policy requires.

File Formats: PDF, DOCX, and exported CSV supported.
Integrations: Connectors for MDM, Service Desk, and CRM.
Security: TLS in transit and AES-256 at rest.

Typical Digital Submission Flow

This flow shows the common path from data capture to signed record and ingestion into asset management systems.

Capture: Collector enters device details into the form or scans a barcode.
Validate: System or admin verifies identifiers and ownership.
Sign: Authorized party signs electronically with audit trail.
Ingest: Data is pushed into the asset inventory or ticketing system.

Security and Compliance Data Points to Include

Encryption: TLS 1.2/1.3, AES-256

Audit Trail: Timestamp, IP, action log

Access Control: Role-based permissions

Authentication: Email, SMS, or MFA

BAA Availability: HIPAA requires BAA

Record Integrity: Tamper-evident storage

Common Errors and Practical Issues to Avoid

Entering partial or truncated serial numbers that prevent warranty matching and inventory reconciliation.
Using informal owner identifiers (nicknames or department slang) that break automated owner lookup routines.
Failing to attach purchase or warranty proof, which delays RMAs and vendor support eligibility.
Allowing unsigned submissions to enter the inventory system, removing accountability and auditability.

Operational and Compliance Risks from Incorrect Forms

Warranty Denial: Incorrect serials may void vendor warranty.

Delayed Support: Missing data slows troubleshooting and incident resolution.

Security Gaps: Untracked devices create exposure in asset inventories.

Regulatory Exposure: PHI on devices can trigger HIPAA violations.

Audit Findings: Inaccurate records cause compliance exceptions.

Data Loss: No attachments impede forensic analysis.

Typical Timing Expectations and Update Deadlines

Define clear submission and update deadlines so the inventory and support teams have current data for audits and incident response.

Initial Submission:

Submit at time of procurement or device issuance.

Status Updates:

Update within 5 business days of ownership or location changes.

Security Patch Notes:

Record major firmware upgrades at deployment time.

Decommission Entry:

Log decommission date when device is retired or disposed.

Audit Cycle:

Schedule reconciliation at least annually.

eSignature Pricing Comparison (signNow First)

Common vendor criteria for eSignature solutions relevant to Device Information Forms: starting price, trial availability, bulk send, audit trail, HIPAA capability, and any envelope limits.

	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	Yes, 7-day free trial	Varies	Varies	Varies	Varies
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

Practical Tips for Accurate and Efficient Completion

Adopt standardized templates and validation rules to reduce errors and simplify downstream processing.

Use Validation Rules

Implement format checks for serials and IMEIs at data entry to prevent transcription mistakes and failed vendor lookups.

Centralize Intake

Route submissions to a single asset-management inbox to ensure consistent processing and reduce duplicate records.

Require Evidence

Mandate attachments like purchase receipts or photos for high-value devices to speed RMA and audit workflows.

Log Changes

Track ownership and location changes with signed amendment records to preserve chain-of-custody for audits.

Real-World Examples of Device Information Forms in Use

These examples show how organizations use the form to speed service, preserve compliance, and support integrations with asset systems.

Optica Ventures: Streamlined Support

The team required consistent device IDs for remote troubleshooting

Device serials and photos attached to every record
As a result, support teams resolved incidents faster and warranty claims processed with fewer vendor escalations due to accurate tracking and attached evidence.

Fertility Centers: Secure Records

Clinical staff needed device provenance tied to patient care equipment

HIPAA addendum and BAA included in workflow
The center maintained audit-ready records with signed attestations and retained device logs in compliance with healthcare retention schedules.

Frequently Asked Questions About the Device Information Form

Answers to common questions about validity, electronic signatures, notarization, retention, and error correction for device records.

Need help? Contact support

Can the form be electronically signed?
Yes. Electronic signatures are legally valid under the federal ESIGN Act (15 U.S.C. ch. 96) and UETA where adopted. Ensure the signature meets intent, consent, attribution, and retention requirements to satisfy 15 U.S.C. §7001 standards.
Do I need a notary for device records?
Generally no for internal inventory or support purposes. Notarization is only required when a device record must serve as an acknowledged legal instrument; check state law and the receiving party's requirements before obtaining notarization.
What if the device holds patient data?
If the device stores or transmits protected health information (PHI), apply HIPAA safeguards and execute a BAA with vendors. Retention and access controls must follow 45 CFR §164.530(j) and relevant organizational policies.
How do I correct an error after submission?
Create an amendment or corrected form that references the original record and includes a signed attestation describing the correction. Preserve both records in the audit trail to maintain forensic integrity.
Is remote notarization (RON) acceptable?
RON is permitted in most states but requirements vary. Confirm identity-proofing, audio-video recording retention, and any state-specific rules before relying on a remote notarization method.
How long must I keep these records?
Retention depends on purpose: follow federal minimums (e.g., IRS 3 years under IRC §6501(a)), HIPAA 6-year rule (45 CFR §164.530(j)) where applicable, and any longer state or industry-specific obligations.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now