Can I sign the stub electronically?

Yes. Electronic signatures are generally enforceable under the ESIGN Act (15 U.S.C. ch. 96) and UETA where adopted, provided intent, consent, attribution, and retention requirements are met.

When is notarization required?

Notarization depends on state law and the document’s intended legal effect; check state notary rules. Certain states or internal policies may require a notary for deeds or affidavits.

How do I correct a signed stub?

Do not alter a signed copy. Create an amendment or a new stub that references the original; retain both documents to preserve an auditable history.

What if names or quantities don’t match?

Mismatched names or quantities can invalidate acceptance and cause accounting discrepancies; document the discrepancy immediately and obtain corrective signatures.

How long must I keep the stub?

Follow your retention policy and legal baselines: IRS records minimum 3 years (IRC §6501(a)) and HIPAA-related records 6 years (45 CFR §164.530(j)).

How do I revoke or cancel a stub?

Execute a written amendment or cancellation signed by authorized parties that references the original stub; keep the cancellation alongside the original record.

Electronic Signature
Templates
Miscellaneous
Miscellaneous Copper Stub

Miscellaneous Copper Stub

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

MISCELLANEOUS COPPER STUB AGREEMENT

Client Name: Contractor Name:

Client Address:

Contractor Address:

Effective Date:

RECITALS

WHEREAS, Client requires supply, installation and testing of a copper stub used for telecommunications or similar service at the location identified below; and

WHEREAS, Contractor represents that it has the necessary expertise, licensed personnel and materials to perform the work described in this Agreement; and

WHEREAS, the parties desire to set forth the terms and conditions under which Contractor will furnish the copper stub, install same, perform acceptance testing and deliver documentation to Client.

COPPER STUB DETAILS

Stub Identifier Installation Address

Cable Type

Pair Count

Length (ft)

Material Supplier Completion Date (anticipated)

Field Test Results and Notes

SCOPE OF WORK

Contractor shall furnish all labor, materials, equipment and supervision necessary to supply, install, terminate and test the copper stub described above in accordance with the Acceptance Criteria and the timelines set forth in this Agreement. Work includes trenching (if required), conduit placement, cable pulling, termination, labeling, as-built documentation and one set of acceptance tests.

Detailed Scope (attach specifics)

PAYMENT TERMS

Total Contract Amount: $

Payment Schedule

Late Payment Fee: Invoices are payable within days of invoice date.

TERM AND TERMINATION

Term Commencement Date:

Termination Date (if applicable):

Either party may terminate this Agreement for material breach by the other party if the breaching party fails to cure such breach within days after written notice. Termination for convenience by Client requires days prior written notice and payment for work performed to date.

CONFIDENTIALITY

Each party shall keep confidential and not disclose to any third party, except as required by law or with the disclosing party's prior written consent, any non-public technical, commercial or financial information disclosed in connection with this Agreement. Confidential information does not include information that is or becomes public through no fault of the receiving party, was rightfully in the receiving party's possession prior to disclosure, or is independently developed without use of the confidential information.

The obligations of confidentiality shall survive termination or expiration of this Agreement for a period of years.

ACCEPTANCE

Acceptance Criteria: The stub shall pass the agreed test procedures as documented in Test Results and meet labeling and as-built documentation requirements. Client shall perform final acceptance within business days after receipt of Contractor deliverables.

Acceptance Notes

WARRANTIES AND LIABILITY

Contractor warrants that materials supplied shall be new and conform to the specifications set forth in this Agreement for a period of months from final acceptance. Except as expressly provided herein, Contractor disclaims all other warranties, express or implied.

Neither party shall be liable to the other for consequential, incidental or punitive damages except for breaches of confidentiality or willful misconduct. Contractor's aggregate liability for any claim arising out of this Agreement shall not exceed the total amount paid by Client to Contractor under this Agreement.

GOVERNING LAW

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

ENTIRE AGREEMENT

This Agreement, including any exhibits 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 and understandings, whether written or oral. Any amendment or modification must be in writing and signed by authorized representatives of both parties.

NOTICES

All notices required or permitted under this Agreement shall be in writing and delivered to the addresses set forth above or to such other address as either party may specify by written notice to the other. Notices may be delivered by certified mail, courier, or overnight delivery service and are effective upon receipt.

Client:

By:

Date:

Contractor:

By:

Date:

What the Miscellaneous Copper Stub Is and when it’s used

The Miscellaneous Copper Stub is a short, supplementary document used to record incidental details related to copper assets, small material transfers, or inventory adjustments when a full bill of sale or schedule is not required. It typically captures item descriptions, quantities, source or destination, date, party names, and a concise purpose statement. Organizations use this stub where a lightweight, auditable record is necessary for operational tracking, short-term custody transfers, or to support a larger transaction file without creating a full contract or ledger entry.

When a concise stub adds practical value

A Miscellaneous Copper Stub provides a quick, auditable record to avoid disputes, support inventory reconciliation, and document chain-of-custody for low-value copper transfers. It reduces administrative overhead while preserving essential facts that may be needed for accounting, compliance, or later reconciliation.

Typical users and teams that prepare this stub

Use the stub where speed and clarity matter but a full contract or formal bill of sale would be disproportionate.

Warehouse staff and inventory clerks who log small material movements and reconcile physical counts.
Site supervisors and foremen who record on-site transfers, deliveries, or returns during projects.
Accounts payable or procurement staff who need a lightweight supporting record for low-value disbursements.

Representative signers and approvers

Operations Manager

Typically signs to confirm transfer or receipt of copper materials on behalf of the company; responsible for verifying quantities and ensuring the stub aligns with inventory records and internal controls.

Field Supervisor

Often the on-site signer who witnessed the transfer, records condition and location, and provides a contact for follow-up; ensures the stub matches physical movement and project logs.

Core elements to include in a professional stub

Include consistent, concise sections so the stub stands alone as a usable record across teams and audits.

Item Description

Precise description of copper items including type, purity, weight, serial number, or SKU so readers can identify materials without external references.

Quantity and Units

State exact quantities and measurement units (pounds, kilograms, pieces) and any rounding conventions to avoid later discrepancies.

Date and Time

Record the transfer or receipt date using MM/DD/YYYY and local time zone if relevant; this anchors inventory and accounting entries.

Parties Involved

List full legal names of transferring and receiving parties, including company name and authorized representative for clear attribution.

Purpose or Reference

Briefly state the reason for the transfer (e.g., return, scrap removal, job-site use) and reference related PO, job number, or invoice when available.

Signatures

Signature blocks for sender and receiver plus printed names and titles; include witness or notary lines where state or internal policy requires authentication.

Essential compliance and security annotations

ESIGN / UETA: 15 U.S.C. ch. 96 compliance

Audit Trail: Timestamp and IP address

Encryption: TLS 1.2/1.3 and AES-256

HIPAA Note: BAA required if PHI present

Access Control: Role-based permissions

Retention Tag: Retention class and owner

Step-by-step completion checklist

Follow these four core steps to produce a clear, auditable stub.

01

Prepare details: Gather item, quantity, and reference documents.
02

Complete fields: Enter names, dates, and descriptions precisely.
03

Sign and date: Have both parties sign with printed names.
04

Distribute copies: Provide signed copies to all stakeholders.

Configuring an online stub workflow

Set up these core workflow settings to streamline creation, signing, and archival.

Template	Use a locked template to standardize fields.
Conditional Fields	Show or hide fields based on transfer type.
Authentication	Choose email, SMS, or KBA per risk level.
Notifications	Enable signer and admin alerts on completion.
Integrations	Connect to ERP or inventory systems for sync.

Digital signing and distribution considerations

Choose a platform that provides an audit trail, secure storage, and export options to maintain chain-of-custody and compliance.

File formats: PDF, DOCX supported
Integrations: Salesforce, NetSuite, Google Workspace
Auth methods: Email, SMS code, KBA

Where to file or send the completed stub

Use this routing pattern to ensure the stub reaches all required record holders and systems.

Originator copy: Sender retains a signed copy for operational files.
Recipient copy: Receiver stores copy in local site records.
Accounting: Send reference to AP or inventory system.
Archive: Upload into central document repository.

Typical timelines and processing expectations

Timelines vary by organization; use these expectations to plan reconciliation and accounting entries.

Immediate recording:

Record stub at time of transfer when possible.

Accounting update:

Post to inventory within 1–3 business days.

Internal review:

Supervisor review typically within 3–7 business days.

Dispute window:

Retain evidence for at least 30 days for quick resolution.

Archival:

Move to long-term storage per retention policy.

Key stages from creation to archival

Track these numbered stages to ensure the stub completes the lifecycle without gaps.

01

Stage 1 — Creation

Complete fields and capture signatures at transfer.

02

Stage 2 — Verification

Supervisor or QA confirms quantities and references.

03

Stage 3 — Posting

Update inventory and accounting records accordingly.

04

Stage 4 — Archival

Store signed stub in secure repository with retention tags.

Common mistakes to avoid when preparing the stub

Leaving out a reference number disconnects the stub from invoices and purchase orders, making reconciliation slow and error-prone.
Using ambiguous item descriptions like 'metal' or 'copper scrap' leads to inconsistent inventory records and disputes over quantity or value.
Failing to capture printed name and title with the signature makes it difficult to attribute responsibility during audits or investigations.
Not archiving the signed stub in a central system risks losing the record and undermines chain-of-custody controls.

Short risks and compliance consequences

Record Rejection: Missing data can void internal acceptance

Accounting Error: Leads to misstated inventory balances

Audit Exposure: Inadequate trail increases audit findings

Legal Dispute: Unclear transfer terms risk contention

Regulatory Risk: Industry rules may require retention

Operational Delay: Rework slows downstream processes

Comparing eSignature vendors for signing and storing the stub

Basic pricing and capability differences influence cost, authentication options, and whether a BAA or advanced compliance is available for sensitive records.

	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
HIPAA Compliant	Yes	Yes	Yes	No	No

Practical examples of similar lightweight records in use

Two real examples illustrate how lightweight signed records support operational needs without full contracts.

Optica Ventures

Small-transaction record used for site transfers to speed processing and reduce paper overhead.

The team logged details and signatures onsite.
The stub served as a quick reference for inventory reconciliation and customer-facing delivery confirmation, improving turnaround while preserving necessary audit details.

Tech Data

Field transfer record standardized across locations to avoid mismatches between sites.

Supervisors captured signatures and reference numbers.
Standard templates ensured consistent data capture, enabling faster posting to ERP systems and clearer evidence in vendor reconciliation processes.

FAQs and troubleshooting for common completion issues

Answers to common questions about e-signing, notarization, corrections, and storage to help resolve routine issues.

Need help? Contact support

Can I sign the stub electronically?
Yes. Electronic signatures are generally enforceable under the ESIGN Act (15 U.S.C. ch. 96) and UETA where adopted, provided intent, consent, attribution, and retention requirements are met.
When is notarization required?
Notarization depends on state law and the document’s intended legal effect; check state notary rules. Certain states or internal policies may require a notary for deeds or affidavits.
How do I correct a signed stub?
Do not alter a signed copy. Create an amendment or a new stub that references the original; retain both documents to preserve an auditable history.
What if names or quantities don’t match?
Mismatched names or quantities can invalidate acceptance and cause accounting discrepancies; document the discrepancy immediately and obtain corrective signatures.
How long must I keep the stub?
Follow your retention policy and legal baselines: IRS records minimum 3 years (IRC §6501(a)) and HIPAA-related records 6 years (45 CFR §164.530(j)).
How do I revoke or cancel a stub?
Execute a written amendment or cancellation signed by authorized parties that references the original stub; keep the cancellation alongside the original record.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now