Establishing secure connection…Loading editor…Preparing document…

Pizza Core & Shell Document

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

Pizza Core & Shell Agreement

This Pizza Core & Shell Agreement (the "Agreement") is made effective as of by and between Landlord Name: and Operator Name: .

Recitals

WHEREAS, Landlord is the fee owner of the real property and building shell located at (the "Premises"); and

WHEREAS, Operator intends to operate a pizza restaurant and requires core and shell work, including but not limited to mechanical, electrical, plumbing, grease management, hood/ventilation, and structural modifications necessary to accommodate pizza-specific equipment; and

WHEREAS, Landlord and Operator desire to set forth the respective obligations, payment terms, schedule and other terms governing the performance of core and shell improvements at the Premises.

Parties and Contacts

Scope of Work

Landlord shall cause and/or Contractor shall perform the core and shell work necessary to ready the Premises for Operator's pizza operations. Core and shell work includes, without limitation, the following categories and specific tasks set forth in the Scope of Work below. All work shall comply with applicable building and health codes, and shall be performed by licensed tradespeople where required.

Payment Terms

Operator shall pay Landlord and/or Contractor the fixed total contract amount for the Scope of Work in accordance with the schedule below. All payments shall be in lawful currency and accompanied by invoices specifying work completed and retainage, if any.

Term and Termination

The term of this Agreement commences on Start Date: and is anticipated to be substantially complete by Completion Date: , subject to adjustments for Force Majeure and approved change orders.

Either party may terminate this Agreement for material breach by the other party if such breach is not cured within the notice period specified above. Termination shall not relieve the breaching party of liability for damages incurred prior to termination.

Permits, Compliance, and Inspections

Responsibility for securing permits and approvals: Landlord Operator/Contractor

All work shall be subject to inspection and acceptance by Landlord or Landlord's representative. Operator shall not occupy or open the Premises for business until final acceptance and any required health and safety approvals are issued.

Confidentiality

Each party acknowledges that it may receive Confidential Information of the other party. "Confidential Information" means non-public financial, technical, operational or business information disclosed in connection with this Agreement. Each party shall (a) use Confidential Information solely for performance under this Agreement; (b) restrict disclosure to those employees or agents with a need to know; and (c) exercise at least the same degree of care to protect Confidential Information as it uses to protect its own confidential materials, but in no event less than reasonable care.

Confidential Information does not include information that is publicly known through no fault of the receiving party, already known to the receiving party without restriction, or required to be disclosed by law or court order (provided the disclosing party is given prompt notice where permitted to seek protective relief).

Warranties; Indemnification

Contractor warrants that all new work performed shall be free from defects in workmanship for Warranty Period: months from substantial completion. Manufacturer warranties for equipment shall be passed through to Operator to the extent assignable.

Each party shall indemnify, defend and hold harmless the other party from liabilities, claims and expenses arising from its negligent acts or willful misconduct in the performance of this Agreement, subject to any statutory caps or insurance coverage limits set forth herein.

Governing Law; Dispute Resolution

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

Entire Agreement; Amendments

This Agreement, including all exhibits and written change orders signed by the parties, constitutes the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior negotiations, representations and agreements. Any amendment to this Agreement must be in writing and signed by authorized representatives of both parties.

Notices

All notices required or permitted hereunder shall be in writing and delivered to the addresses set forth above or to such other address as either party may designate by written notice in accordance with this section.

Representations

Each party represents and warrants that it has full authority to enter into this Agreement and that performance hereunder will not violate any applicable law or other agreement binding on such party.

Landlord / Property Owner

Party Label:

By:

Date:

Operator / Pizza Business

Party Label:

By:

Date:

Enter text✕

What the Pizza Core & Shell Document Is

The Pizza Core & Shell Document is a written project specification that sets the high-level scope, responsibilities, and baseline conditions for a restaurant build‑out, focusing on the core structure and exterior shell while leaving tenant‑fitout details to later phases. It defines ownership of building systems, permitted uses, access points, rough‑ins for utilities, and the division of work between landlord and tenant. The document is commonly used in commercial lease negotiations, construction planning, and permitting to reduce scope disputes and align expectations before detailed design begins.

Why this Document Matters for Projects and Contracts

A clear Pizza Core & Shell Document reduces later disputes by stating who delivers which building elements, what utilities are provided, and which finishes are excluded. It protects parties by allocating costs, clarifying timelines, and identifying responsibility for permits and inspections. Having this document early supports budgeting, coordination with MEP trades, and compliance checks during permitting and closeout.

Why this Document Matters for Projects and Contracts

Who typically prepares or signs a Core & Shell Specification

Several project stakeholders are commonly involved in creating or approving the Pizza Core & Shell Document; each has distinct priorities and signatory authority.

  • Landlords and property managers who define base building obligations and allowable tenant improvements.
  • Tenants or tenant representatives (restaurant operators) who need utility connections, hood / exhaust allowances, and service access defined.
  • General contractors and architects who translate the core/shell scope into bid packages and construction contracts.

Identifying the right participants up front — landlord, tenant representative, general contractor, and architect — reduces negotiation cycles and helps ensure an enforceable agreement.

Core sections to include in a professional Pizza Core & Shell Document

A comprehensive document groups obligations into standard sections so contractors, tenants, and owners can reference precise deliverables. Use consistent headings and measurable criteria to avoid ambiguity during bidding and construction.

Building Shell

Defines exterior walls, roof structure, windows, doors, and structural penetrations the landlord provides and the accepted tolerances for finishing work.

Base Utilities

Specifies electrical service capacity, gas stub locations, water and sewer rough‑in points, and HVAC allowances or pre‑cooling provisions.

Interior Core

Identifies common area finishes, restrooms, corridors, and vertical shafts the owner retains and the interface points for tenant fitout.

Permits & Inspections

Allocates responsibility for permit applications, fees, and scheduling of inspections between landlord, tenant, and contractor.

Hood and Exhaust

Details required roof curb provisions, structural reinforcement, roof access, and electrical/mechanical allowances for kitchen exhaust equipment.

Acceptance Criteria

Lists tests, certifications, and final conditions required for landlord acceptance of core/shell work prior to tenant turnover.

Essential information to include on the document

Project Name: Exact project identifier used on permits
Site Address: Full street, city, state, ZIP
Parties: Legal names of landlord and tenant
Scope Summary: Concise deliverables list
Effective Date: Date scope begins
Signatory Authority: Name and title of approvers

Step-by-step: preparing and finalizing the Pizza Core & Shell Document

Follow a defined sequence to collect approvals, circulate for review, and secure signatures so the document becomes an operational baseline for construction and permitting.

  • 01
    Draft Scope: Owner or project manager drafts core/shell obligations.
  • 02
    Technical Review: Architect/engineer confirms MEP penetrations and roof loads.
  • 03
    Tenant Review: Tenant verifies hood, gas, and utility requirements.
  • 04
    Sign and Record: Obtain authorized signatures and retain executed copy for permits.

Configuring an online workflow to complete the document

Set up document routing and authentication to match project signatories and reduce manual handoffs during review and permit submission.

Field Configuration
Signer Order Sequential routing: landlord → architect → tenant
Authentication Email or SMS code for each signer
Attachments Include drawings, utility specs, and permit forms
Notifications Automated reminders on pending signatures

Digital signing and distribution considerations

Choose eSignature and storage settings that preserve the audit trail, meet industry compliance, and integrate with project systems.

  • File Formats: PDF, DOCX supported
  • Integrations: Connect to Google Drive, Box, NetSuite, Procore
  • Security: TLS 1.2/1.3 in transit; AES-256 at rest

Where to send the executed Core & Shell Document

Distribute the signed document to stakeholders and filing systems to support permitting, contractor mobilization, and tenant fitout planning.

  • Landlord Records: Final executed copy for owner files and insurance
  • Tenant/Operator: Provide tenant with signed baseline for fitout design
  • General Contractor: Attach to bid package and procurement docs
  • Permitting Authority: Include with permit applications as required

Key timing and filing expectations

Track critical dates for construction start, permitting, and turnover; align document effective dates with permit submittals to avoid schedule gaps.

Document Effective Date:

Use MM/DD/YYYY in the form; ties to insurance and warranty start

Permit Submission:

Submit with drawings per local AHJ schedule

Construction Mobilization:

Begin after core/shell acceptance criteria are met

Turnover and Acceptance:

Scheduled upon passing final inspections

Record Retention:

Store executed copy per retention timelines below

Project milestones from agreement to turnover

A typical project moves through sequential milestones; documenting these milestones in the Core & Shell Document sets expectations for mobilization and tenant fitout.

01

Agreement Finalized

Scope and signatures completed; baseline established

02

Permit Filing

Plans and core/shell attached for review by AHJ

03

Core Construction

Landlord completes shell, utilities rough‑in, roof work

04

Turnover

Landlord verifies acceptance criteria and hands site to tenant

Common mistakes to avoid when preparing the document

  • Vague utility specs that result in undersized power or gas connections and change orders.
  • Failing to document who obtains and pays for permits, causing schedule delays.
  • Omitting hood/exhaust structural requirements and roof curb details, requiring rework later.
  • Not matching party legal names to lease or tax documents, complicating enforcement.

Risks and legal consequences of an incomplete or incorrect document

Construction Delays: Change orders and rework increase cost
Permit Rejection: Missing specs can lead to permit denial
Liability Disputes: Ambiguous obligations raise litigation risk
Cost Overruns: Undefined scope shifts cost allocation
Insurance Gaps: Incorrect effective dates may affect coverage
Tax/Reporting: Incorrect party names affect 1099/contractor reporting

Typical eSignature vendor comparison for executing core/shell documents

Platforms differ by price model, bulk send capability, and compliance features. signNow is listed first per comparison conventions.

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 vendor Varies by vendor Varies by vendor Varies by vendor
Bulk Send Yes (Business Premium) Yes Yes Yes Varies
Audit Trail Yes Yes Yes Yes Yes
HIPAA Compliant Yes (BAA required) Yes (BAA available) Yes No No
Envelope Cap No envelope cap 100 envelopes/user/year Varies by plan Varies by plan Varies by plan

Real-world examples of Core & Shell use

Examples show how parties used a clear core/shell document to reduce scope disputes and accelerate construction handover.

Optica Ventures - Tenant Turnover

Optica Ventures standardized a core/shell template to reduce RFIs during tenant fitouts.

  • This clarified HVAC and electrical stub locations.
  • The result was a smoother turnover with fewer change orders and faster tenant buildout coordination across multiple properties.

Martin Properties - Compliance

Martin Properties used a core/shell document tied to permit submissions.

  • Roof curb and hood specs were pre‑approved.
  • This reduced permit comments and allowed tenants to schedule equipment delivery sooner, improving project predictability.

Frequently asked questions about the Pizza Core & Shell Document

Answers to common execution, signing, and compliance questions for project teams and signatories.


Need help? Contact support

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