Establishing secure connection…Loading editor…Preparing document…

Prime Contractors Information Statement

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

PRIME CONTRACTOR'S INFORMATION STATEMENT- CORPORATION

(NRS § 52-143(1))

THE UNDERSIGNED as a representative of a corporate prime contractor hereby states that he or she received a request for information from a claimant who may claim a lien through the undersigned under the Nebraska Construction Lien Act on (date), and responds to the request within ten (10) days of receipt of such request, by stating the following:

1) The real estate being improved is sufficiently identified and described as:

2) The undersigned contracted with the following contracting owner: whose address is:

3) There is or is not a surety bond, and the name of the surety (if applicable) is:

This the day of 20

Signature

Type or Print Name

Title

Name of Corporation

Enter text

What the Prime Contractors Information Statement Is

The Prime Contractors Information Statement is a standardized document used to record core contracting details about a prime contractor on a public- or private-sector project. It typically lists the contractor's legal name, tax identification, contact information, scope of work, key performance dates, and any bonding or insurance references. Agencies and owners use it to confirm compliance with procurement rules, subcontractor reporting requirements, and payment-processing workflows prior to contract award or first draw request.

Why accurate Prime Contractors Information Statements matter

Accurate statements reduce payment delays, ensure correct tax reporting, and help meet procurement and audit requirements. They create a single canonical record for the prime contractor used across invoicing, compliance checks, and subcontractor tracking.

Why accurate Prime Contractors Information Statements matter

Who prepares and relies on this statement

The completed statement serves as a reference for audits, payment set-up, and downstream subcontractor reporting.

  • Project managers and contracting officers who verify compliance and vendor onboarding details.
  • Accounts payable teams that use the statement to validate remit-to addresses and tax identification for payment.
  • Prime contractors and their legal or finance teams who supply required identifiers and attestations.

Core sections to include in a professional statement

A complete Prime Contractors Information Statement organizes contractor credentials, contract identifiers, financial and compliance attestations, and signature blocks so receiving parties can readily verify eligibility and process payments.

Contractor Identity

Legal business name, DBA if any, and Employer Identification Number (EIN) or Social Security Number for sole proprietors.

Contact Details

Primary business address, remit-to address, phone, and email for contracting and billing.

Contract References

Contract number, project name, award date, and scope or line items associated with the prime contract.

Financial Info

Banking or ACH details if required, bonding information, and relevant insurance policy numbers.

Compliance Attestations

Tax status, small-business or veteran-owned certifications, licensing numbers, and any mandatory attestations.

Signatures

Authorized signer name, title, signature block, and execution date with witness or notary details if required.

Step-by-step: filling and submitting the statement

Follow this sequence to prepare a clear, verifiable Prime Contractors Information Statement for submission to the contracting authority.

  • 01
    Collect documents: Gather formation documents, EIN letter, insurance certificates, and bonding evidence.
  • 02
    Complete fields: Populate all required fields using exact names and MM/DD/YYYY dates.
  • 03
    Verify accuracy: Cross-check TIN/EIN and addresses against official records before signing.
  • 04
    Submit and retain: Send to the contracting officer and save an executed copy in the contract file.

How to configure an online completion workflow

Set up a consistent digital workflow to collect the statement, authenticate signers, and store an audit trail.

Field Configuration
Required fields Make legal name, EIN, and signature required
Authentication Use email + SMS code for higher-assurance signers
Routing Auto-route to AP and contracting officer after signature
Storage Save PDF and audit trail in a secure repository

Key digital signing and integration considerations

Select a platform that supports secure e-signing, audit trails, and integrations with your procurement systems.

  • Authentication Options: Email, SMS, knowledge-based, or advanced signer authentication as needed
  • File Formats: Support for PDF and DOCX with flattened signed output
  • Integrations: Connectors for ERP/CRM systems reduce manual data entry

Ensure the chosen platform provides a verifiable audit trail, secure storage, and the integrations your back-office needs.

Where the completed statement goes and what follows

Understanding destination and next steps helps you avoid processing delays once the statement is signed.

  • Submit to Contracting Office: Send the executed statement to the designated contracting officer for onboarding.
  • Accounts Payable Setup: AP uses the remit-to and EIN details to configure payment terms and tax reporting.
  • Attach to Contract File: Store the statement with the contract, insurance, and bond documents for audits.
  • Distribute to Subcontractors: Use the prime's details to populate subcontractor notices or reporting templates.

Common timing and deadline expectations

Some submissions must occur before payment or competitive milestones; others are requested at award or first invoice.

Before award:

Complete and return upon award notification to avoid payment holdups

Before first draw:

Provide completed statement prior to first payment application

Tax reporting:

Maintain correct TIN for year-end 1099 reporting (see IRS requirements)

Insurance renewals:

Update certificates on renewal to keep coverage current

Contract closeout:

Retain executed statement through contract closeout and audit period

Key milestones from submission to retention

A sequential view of stages clarifies what happens after the statement is submitted.

01

Submission

Contractor submits completed statement to the contracting authority for review.

02

Verification

Agency verifies EIN, licenses, insurance, and bonding where applicable.

03

Account Setup

Accounts Payable enters remit information and configures vendor record.

04

Audit Retention

Executed statement is stored with contract records for the required retention period.

Common mistakes to avoid

  • Entering an incorrect EIN or TIN that triggers backup withholding or vendor record rejection.
  • Using a different legal name than appears on formation or IRS documents, causing verification failures.
  • Omitting signature authority details or failing to include a corporate resolution when required.
  • Failing to update insurance or bond numbers leading to payment holds or noncompliance.

Penalties and risks of incorrect or late statements

Backup withholding: Incorrect TIN can trigger 24% backup withholding under IRS rules.
Payment delays: Missing or mismatched data often results in invoice holds and delayed payments.
Contract noncompliance: Incomplete attestations can breach contract requirements and affect performance payments.
Audit exposure: Incorrect records increase the risk of findings during vendor or procurement audits.
Tax penalties: Incorrect information returns may trigger IRC §6721 penalties for filing incorrect returns.
Legal disputes: Misstated identity or authority can lead to contract disputes or debarment proceedings.

Representative eSignature vendor pricing and features

Comparison of entry-level pricing and key capabilities for common eSignature vendors; signNow is presented first per comparative convention.

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 No No No No
Bulk Send Yes Yes Yes Yes No
Audit Trail Yes Yes Yes Yes Yes
HIPAA Compliant Yes Yes Yes No No

Security, compliance, and encryption essentials

In Transit: TLS 1.2/1.3
At Rest: AES-256 encryption
Certifications: SOC 2 Type II, ISO 27001
Privacy Laws: GDPR, CCPA compliance
Regulated Use: HIPAA with BAA; 21 CFR Part 11 support
Accessibility: WCAG 2.0 Level AA

Practical examples of completed statements

Two real-world scenarios show how the statement supports onboarding and payment.

Public Works Prime

A prime contractor provided full bond and insurance details at award

  • Owner verified licenses and saved time on pre-qualification
  • The completed statement was filed with contract records and avoided payment holds during first invoice processing.

Healthcare Vendor

A supplier included HIPAA attestations and a BAA reference

  • Hospital procurement linked the statement to vendor onboarding
  • That linkage enabled secure exchange of patient-related purchase orders and satisfied internal audit requirements.

Who can sign or certify the statement

Corporate Officer

An authorized officer such as CEO, CFO, or an individual named in a board resolution may sign to bind the entity. If an agent signs, attach written evidence of their authority.

Authorized Representative

Procurement or finance managers with delegated signing authority can sign routine onboarding statements; ensure delegation limits are documented and retained.

Frequently asked questions and troubleshooting

Answers to common questions about completing, signing, and storing the Prime Contractors Information Statement.


Need help? Contact support

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