Establishing secure connection…Loading editor…Preparing document…

California Central Valley Project Historic Engineering Features to 1956 Multiple Property Documentation Form

This template is fully customizable. Edit the text, fill out the fields, and send it for signature. Give it a try!
California Central Valley Project Historic Engineering Features to 1956 Multiple Property Documentation Form

What this Multiple Property Documentation Form covers

The California Central Valley Project Historic Engineering Features to 1956 Multiple Property Documentation Form organizes information about historic engineering resources related to the Central Valley Project through 1956 for use with State Historic Preservation Offices and the National Register of Historic Places. It groups related properties, defines historic contexts, describes property types and significance, and provides standardized registration requirements and inventory forms to support surveys, nominations, and preservation planning across multiple sites.

Why a standardized MPDF matters for Central Valley documentation

A focused Multiple Property Documentation Form creates consistency across nominations, reduces redundancy in research, and clarifies registration criteria for similar engineering features built before 1956.

Why a standardized MPDF matters for Central Valley documentation

Who typically prepares and reviews this MPDF

Typical users include preservation professionals, federal and state agency staff, and independent historians working on Central Valley Project resources.

  • State Historic Preservation Office staff and reviewers who evaluate nominations and manage survey inventories.
  • Federal agency cultural resources specialists responsible for Section 106 reviews and programmatic agreements.
  • Consultants, historians, and architectural historians preparing nomination forms, contexts, and property inventory sheets.

Using this form helps align documentation with National Register guidance and expedites review by providing consistent context, property-type definitions, and registration requirements.

Core components included in a professional MPDF package

A complete MPDF for the Central Valley Project includes a clear historic context, defined property types, registration requirements, representative inventory forms, boundary guidance, and a bibliography of sources used to support significance claims.

Historic Context

Narrative explaining the development, engineering themes, and historical significance of Central Valley Project features through 1956, with dates and key events.

Property Types

Defined categories (dams, canals, pumping plants, power facilities) with descriptions of distinguishing features and variations for use in inventorying resources.

Registration Requirements

Criteria for integrity and significance that individual properties must meet to be eligible under the MPDF, including period of significance and character-defining features.

Inventory Forms

Standardized documentation templates for each property including identification, description, construction history, and current condition to ensure consistent records.

Boundary Guidance

Instructions for defining property boundaries and contributing elements, including maps, acreage guidance, and relationship to surrounding infrastructure.

Bibliography

Compiled primary and secondary sources, archival repositories, and mapping resources that substantiate the historic contexts and statements of significance.

Step-by-step: preparing an MPDF nomination package

Follow these sequential tasks to build a complete MPDF and associated inventory forms for submission and review.

  • 01
    Research: Gather primary sources, maps, and engineering reports relevant to Central Valley Project features.
  • 02
    Define Contexts: Draft historic contexts and property-type descriptions that justify significance through 1956.
  • 03
    Complete Inventories: Populate standardized inventory forms for each property with accurate location and descriptive data.
  • 04
    Review and Submit: Have SHPO or peer reviewers check the MPDF before formal submission to the National Park Service where applicable.

Typical document workflow for submission and review

This workflow outlines how documents move from research through formal review and final determination.

  • Drafting: Prepare MPDF narratives and inventories using archival and field data.
  • Internal Review: Circulate drafts among team members and agency specialists for accuracy and completeness.
  • SHPO Consultation: Submit to the State Historic Preservation Office for review and comment per state procedures.
  • NPS Submission: If required, forward the completed nomination to the National Park Service for determination of eligibility.

Recommended digital workflow settings for MPDF files

Configure document files and review settings to maintain version control and ease of reviewer access.

Field Configuration
Master PDF Single searchable PDF with bookmarks for context, inventories, and attachments
File Naming Use standardized names: Project_MPFD_Title_Year.pdf
Version Control Include version number and date in metadata and maintain an edit log
Access Share with reviewers via controlled cloud link with download and comment permissions

Digital platform considerations for eSubmission and collaboration

Choose tools that preserve metadata, enable secure sharing, and generate an audit trail for revisions and approvals.

  • File formats: PDF/A for long-term preservation; searchable text preferred
  • Integrations: Connectors for cloud storage and email simplify reviewer distribution
  • Security: Access controls and encrypted transfer protect research materials

Proper platform configuration reduces review friction, maintains authoritative versions, and documents who accessed or changed materials during nomination and review.

Typical timelines and review expectations

Allow adequate time for research, SHPO review, and any required public comment periods when planning MPDF preparation and submission.

Research phase:

Allow 4–8 weeks for archives, field visits, and document compilation for a focused MPDF.

SHPO review:

Expect 30–90 days depending on state workload and completeness of submission.

Public comment:

If required, public notice periods commonly run 30 days; adjust timeline accordingly.

NPS review:

When NPS review is needed, anticipate 60–120 days for technical review and determination.

Revision cycle:

Factor in 2–4 weeks per revision round after reviewer comments for edits and resubmission.

Key milestones from draft to determination

A sequential view of major milestones helps coordinate team responsibilities and external reviews.

01

Draft Complete

All contexts, inventories, and attachments compiled and internally checked.

02

SHPO Submission

Package submitted to State Historic Preservation Office for preliminary review.

03

Public Review

Public notice and comment period conducted where required.

04

Final Determination

State or NPS issues eligibility determination or requests final revisions.

Common pitfalls when preparing MPDFs

  • Incomplete source citations that prevent reviewers from verifying dates, builders, or construction sequences.
  • Overly broad property-type definitions that fail to distinguish character-defining features across different facility classes.
  • Insufficient maps or boundary descriptions that lead to ambiguity about the extent of the nominated property.
  • Failure to link individual inventory forms clearly back to the MPDF contexts and registration requirements, complicating eligibility assessment.

Consequences of incomplete or inaccurate documentation

Delayed Determination: Review hold times and repeated resubmissions increase project scheduling risk.
Funding Impacts: Incomplete documentation can delay grant approvals or mitigation funding rounds.
Legal Vulnerability: Poorly defined boundaries or histories may weaken protections under Section 106 consultations.
Data Loss: Inadequate file preservation risks loss of archival evidence and future research value.
Stakeholder Friction: Inaccurate attribution or missing stakeholder notice can create local opposition.
Resource Misclassification: Improper property-type assignment can exclude eligible resources from protection.

Data security and compliance when sharing research and drafts

Encryption: TLS 1.2/1.3 in transit
Encryption at rest: AES-256 encrypted storage
HIPAA handling: BAA required for PHI handling
Audit trail: Detailed access and action logs
Certifications: SOC 2 Type II available
Standards: 21 CFR Part 11 supported

Practical tips to improve accuracy and reviewability

Small diligence steps make submissions easier to review and more likely to proceed without major revision requests.

Use consistent naming and metadata
Standardize file names, include creation and revision dates in metadata, and attach a version log to help reviewers track changes and reference the correct package.
Cite primary sources liberally
Support construction dates and builder attributions with archival references, engineering reports, and map citations to reduce reviewer follow-up.
Include clear maps and photographs
Provide high-quality maps with north arrows, scales, and photographs showing context and character-defining features to support integrity assessments.
Coordinate early with SHPO
Engage SHPO reviewers during drafting to confirm expectations, potential issues, and any state-specific supplemental forms or requirements.

Representative use cases where an MPDF helped streamline review

Examples show how a focused MPDF and inventories speeded survey, review, and nomination work for multiple related resources.

Statewide Survey

A transportation agency compiled a Central Valley Project MPDF to document related pumping plants and canals

  • The MPDF established consistent eligibility criteria
  • As a result, dozens of inventories were completed with fewer individual justifications, reducing review cycles and clarifying mitigation approaches for multiple projects.

Grant-supported Documentation

A regional conservancy used an MPDF as the foundation for grant-funded historic surveys

  • The MPDF provided unified contexts and templates
  • The consistent documentation satisfied funder requirements, accelerated SHPO agreement, and allowed efficient aggregation of findings across multiple parcels.

Selected eSignature vendor comparison for document signing and routing

Comparison of basic plans and key features to consider when selecting an eSignature provider for MPDF routing and signature collection.

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 Trial available Trial available Trial available Trial available
Bulk Send Yes (premium tier) Yes Yes Yes No
Audit Trail Yes Yes Yes Yes Yes
HIPAA Compliant Yes Yes Yes No No
Envelope Cap No envelope cap 100 envelopes/user/year Varies by plan Varies by plan Varies by plan

Frequently asked questions and common issues

Answers to frequent questions about preparing, submitting, and preserving MPDFs for Central Valley Project engineering features.


Need help? Contact support

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