Establishing secure connection…Loading editor…Preparing document…

Census Data Request Form

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

CENSUS DATA REQUEST AND DATA USE AGREEMENT

Parties

Requester Name:   Organization:

Data Provider Name:   Provider Unit:

WHEREAS

Whereas Requester seeks access to certain aggregated and/or customized census-related data for legitimate research, planning, or administrative purposes to be described in the Scope of Work; and

Whereas Data Provider maintains custody of the requested datasets and requires reasonable assurances regarding use, confidentiality, compensation for services, and compliance with applicable data protection obligations; and

Now, therefore, in consideration of the mutual promises set forth herein, the parties agree to the terms and conditions of this Census Data Request and Data Use Agreement.

Scope of Work

Years requested: From to

Desired file format:   Delivery method:

Payment Terms

Total fee for services: $ (USD)

Late payment: If any undisputed amount is not paid within days of invoice, interest will accrue at % per month or the maximum permitted by law, whichever is less.

Term and Termination

Agreement term begins on and ends on unless earlier terminated in accordance with this section.

Either party may terminate for cause upon written notice if the other party materially breaches any obligation and fails to cure within days after receipt of written notice. Upon termination, Requester shall promptly return or securely destroy all non-public datasets and certify destruction if requested by Data Provider.

Confidentiality and Data Use Restrictions

Requester shall treat all non-public or restricted data as confidential, implement reasonable administrative, technical, and physical safeguards to prevent unauthorized access, and limit access to authorized personnel who have a documented need to know. Requester shall not attempt to identify, re-identify, or otherwise infer the identity of any individual or small group from aggregated or microdata, nor permit any third party access without prior written consent of Data Provider.

If Requester discovers a breach or unauthorized disclosure, Requester shall notify Data Provider promptly and cooperate in mitigation, notification, and remediation efforts. Requester agrees to indemnify Data Provider for losses resulting from Requester's negligent or willful failure to comply with confidentiality obligations.

By checking this box, Requester certifies agreement to the confidentiality and data use restrictions above and represents that it will implement the safeguards described.

Certifications and Assurances

Requester certifies that the data requested will be used solely for the stated purpose, that results will be reported in aggregated form that prevents disclosure of personally identifiable information, and that Requester will comply with all applicable statutes, regulations, and policies governing the use of the requested data.

Requester acknowledges that attempting to re-identify individuals or to publish disclosive cell sizes is prohibited and subject to penalties, including revocation of access and financial liability.

Liability, Indemnity, and Limitation of Remedies

Except to the extent arising from willful misconduct or gross negligence, neither party shall be liable for incidental, consequential, or punitive damages. Requester shall indemnify, defend, and hold harmless Data Provider from third-party claims arising out of Requester's misuse of the data or breach of this Agreement.

Governing Law

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

Entire Agreement

This Agreement, including any attachments or written amendments signed by both parties, constitutes the entire understanding between the parties with respect to the subject matter hereof and supersedes all prior proposals, negotiations, and agreements, whether written or oral.

Contact for Notices

Acknowledgement of Fees and Timeline

Signatures

Requester Printed Name:

By:

Date:

Data Provider Printed Name:

By:

Date:

Enter text✕

What the Census Data Request Form Is and when it’s used

The Census Data Request Form is a structured request used to obtain census-derived datasets, extracts, or customized tabulations from a government statistics office, research data center, or agency. It records requester identity, institutional affiliation, a clear statement of purpose, dataset identifiers, geographic and temporal scope, intended uses and dissemination limits, and any required assurances about confidentiality or data handling. The form also indicates whether the requester will sign a data‑use agreement, provide IRB approval for restricted data, or accept access conditions that limit redistribution.

Why this form matters for lawful, auditable access

A well-prepared Census Data Request Form documents legal authority, purpose of use, and security controls required by the data holder, helping agencies evaluate compliance and privacy risk.

Why this form matters for lawful, auditable access

Who typically files a Census Data Request Form

Institutional sign-off, an authorized official, or a designated data custodian usually completes or certifies the form depending on agency rules.

  • Academic researchers conducting controlled studies or requiring microdata for authorized projects.
  • Government program analysts and planners requesting tabulations for policy or funding decisions.
  • Private-sector analysts and nonprofits requesting aggregated data for market or community research.

Stepwise process to complete and submit the form

Follow these steps in order to prepare a complete request and reduce review cycles.

  • 01
    Prepare: Gather IDs, project summary, and institutional approvals.
  • 02
    Fill: Enter requester details, dataset identifier, scope, and intended use.
  • 03
    Attach: Include IRB letters, support memos, or data-use agreements as required.
  • 04
    Submit: Send form through the agency’s accepted channel and retain proof of submission.

Typical online workflow settings for electronic submission

When submitting electronically, configure routing, authentication, and retention to match agency rules.

Field Configuration
Upload Method PDF/A or DOCX accepted; prefer PDF/A for long-term preservation.
Authentication Use email plus SMS OTP or institutional SSO where available.
Routing Set sequential review: intake → legal → data steward → final approval.
Retention Store signed form and attachments per agency retention policy.

Technical considerations for eSubmission and eSigning

Match your submission platform settings to agency rules for signature authenticity, redaction, and record retention to avoid rejection.

  • File Types: PDF, DOCX, and sometimes CSV for metadata uploads.
  • Authentication: Email plus SMS OTP, KBA, or SSO depending on sensitivity.
  • Integrations: Systems commonly integrate with Google Workspace, Microsoft 365, and enterprise CRMs.

How electronic submission and review typically flow

Most agencies follow a predictable sequence from intake to delivery; configure each step to capture audit data.

  • Upload: Submit completed form and attachments to the agency portal or secure email.
  • Initial Review: Intake validates completeness and forwards for legal or technical review.
  • Approval: Data steward approves scope, confidentiality, and any access controls.
  • Delivery: Approved data provided under specified controls or via secure transfer.

Common timelines and what to expect after submission

Processing times vary by agency and request complexity; plan ahead for longer reviews when restricted data, IRB, or interagency approvals are required.

Acknowledgement:

Agency typically acknowledges receipt within 5–10 business days.

Standard Review Time:

Simple tabulations: often 2–4 weeks; complex or restricted requests: 6–12+ weeks.

Expedited Requests:

May be considered for urgent public-interest needs; timelines vary by policy.

Revision Cycles:

Incomplete forms commonly trigger a 1–3 week additional processing delay.

Delivery Window:

Data delivery depends on format and approvals; allow extra time for secure transfers.

Key milestones in the request lifecycle

Track these numbered stages to monitor progress and identify bottlenecks during processing.

01

1. Submission

Complete form submitted with attachments and signatures for intake.

02

2. Intake Review

Staff check completeness and route to appropriate reviewers.

03

3. Technical/Legal Review

Data steward assesses confidentiality, scope, and any DUA requirements.

04

4. Delivery & Close

Approved dataset delivered under agreed controls; record closed.

Essential data elements the agency will verify

Requester Name: Full legal name
Institution: Legal employer name
Project Title: Concise study name
Dataset ID: Official dataset identifier
Purpose: One-sentence intent
IRB / DUA: IRB number or DUA status

Consequences of incomplete or noncompliant requests

Access Denial: Request may be refused
Civil Penalties: Fines or administrative sanctions
Criminal Liability: For willful disclosure of protected data
Data Breach Liability: Obligations to notify and remediate
Project Delays: Extended review cycles
Contract Termination: Loss of access or future privileges

Common mistakes that delay processing

  • Using informal or abbreviated organization names that do not match institutional records, which prevents verification and routing.
  • Failing to specify dataset identifiers or variable lists, requiring follow-up and extending review time significantly.
  • Omitting required attachments such as IRB approval letters or signed data-use agreements, triggering automatic holds.
  • Submitting unsecured files or unredacted sensitive data, creating compliance concerns and possible rejection of the request.

Core components a professional request always includes

A complete form balances specificity with legal and operational details so reviewers can assess risk and scope quickly.

Request Purpose

Clear project description explaining why the data are needed, intended analyses, and whether findings will be published or shared.

Scope & Variables

Precise geographic and temporal scope, dataset identifiers, and a variable list or schema to avoid ambiguous requests.

Access Controls

Requested delivery method (aggregate files, secure enclave, deidentified extracts) and any required technical protections.

Legal Basis

Citation of statutory authority or institutional need, and identification of any required permits, DUAs, or IRB approvals.

Confidentiality Terms

Statement of non-disclosure obligations, publication restrictions, and data destruction or return timelines after project end.

Signatures

Authorized signatory block for requester and institutional official; indicate whether notarization or witness signatures are required.

Comparing eSignature providers for submitting the form

Many agencies accept electronically signed forms; below is a pricing and capability snapshot to help choose a compliant eSignature provider.

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

Frequently asked questions about completing and submitting the form

Answers address common processing questions, signature validity, and documentation you may need to attach for successful review.


Need help? Contact support

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