When must the entity give a requested appraisal statement?

Section 262(e) requires the statement within ten days after the entity receives the qualifying request or within ten days after the section 262(d) demand period expires, whichever is later. The current provision says the statement shall be given. It does not require that every statement be mailed.

Responsible actor. The surviving, resulting or converted entity receiving the qualifying statement request.

Verify the requester’s subsection (a) and (d) compliance and actual request receipt.

Determine the transaction route and actual statutory demand expiry.

Compare both ten-day limbs before selecting the controlling delivery boundary.

Establish both events and the applicable transaction-approval route. The demand expiry may be the pre-vote meeting requirement or the subsection (d)(2) notice and offer comparison. A single request-receipt input cannot establish the later event.

1. Both established request receipt and expiry of the applicable appraisal-demand period
2. Establish both limbs before counting ten corporate calendar days from the controlling later event. Chancery’s short-period exclusions do not govern this company delivery. No automatic corporate last-day extension is assumed.
3. Give the statutory aggregate statement to the qualifying requester. Preserve the request receipt, separately established demand expiry, statement contents and evidence of completed delivery. Do not equate sending a draft or promising an answer with giving the statement.

Current Delaware Code and retained Chancery compilation reviewed. An editorial check does not establish an amendment commencement date. Establish the statutory version applicable to the actual transaction. The Court compilation is current through June 1, 2026.

The single-input preset does not establish both request receipt and the transaction-specific demand expiry. This guide supplies no computed or paid date.

Fictitious comparison. If a request is received September 1 but the established demand period expires September 10, the expiry limb controls. If the request instead arrives September 15, the receipt limb controls. These facts illustrate the comparison; they do not determine another transaction’s demand period or completed statement delivery.

The single-input preset does not establish both request receipt and the transaction-specific demand expiry. This guide supplies no computed or paid date.

Approval mechanism controls demand expiry

The meeting route requires demand before the vote. The nonmeeting routes use subsection (d)(2), including the section 251(h) offer comparison.

Given rather than mailed

The current statement obligation uses delivery wording. Preserve evidence of the method actually satisfying that obligation instead of inserting a mail-only completion event.

Qualifying requester

The underlying statement right depends on compliance with subsections (a) and (d), including the specified aggregate counting treatment for beneficial-owner demands.

• Establish both events and the applicable transaction-approval route. The demand expiry may be the pre-vote meeting requirement or the subsection (d)(2) notice and offer comparison. A single request-receipt input cannot establish the later event.
• The single-input preset does not establish both request receipt and the transaction-specific demand expiry. This guide supplies no computed or paid date.

• Verify the requester’s subsection (a) and (d) compliance and actual request receipt.
• Determine the transaction route and actual statutory demand expiry.
• Compare both ten-day limbs before selecting the controlling delivery boundary.
• The meeting route requires demand before the vote. The nonmeeting routes use subsection (d)(2), including the section 251(h) offer comparison.
• The current statement obligation uses delivery wording. Preserve evidence of the method actually satisfying that obligation instead of inserting a mail-only completion event.
• The underlying statement right depends on compliance with subsections (a) and (d), including the specified aggregate counting treatment for beneficial-owner demands.