The rule, the boundary, and the records—up front
This is the shortest source-mapped path to the Honeywell answer. Use the public rule first, then match it to the employee’s actual plan, award, dates, and records.
| Answer layer | What the current record says | Where to verify it |
|---|---|---|
| Public rule | What current sources establish The guide provides examples showing that an effective date can affect payroll access and benefit coverage. A last working day should not be assumed to be the legal separation or pension date. | |
| Where it changes | Exceptions and population boundaries Involuntary separation, accrued leave, severance, disability, pension eligibility, and local employment rules can create a different sequence. |
|
| Decision sequence | What to confirm before acting Create a four-line calendar and obtain written confirmation from HR, the pension administrator, and the 401(k) administrator where different programs use different dates. | Reviewed July 13, 2026Source register and review dates ↓ |
Public sources establish the baseline. The governing plan, award, account, and employment records establish the employee-specific result.
Ordinary words, administrative distinctions
The same final workday can be coded two different ways
An employee can tell a manager, “I am retiring on June 30,” and mean it plainly — while payroll is recording a last working day, a resignation effective date, and a pension commencement date that are not all June 30. The everyday word hides a set of administrative distinctions, and benefits systems read the effective dates, not the intention behind them.
Honeywell’s 2026 guide draws those lines deliberately. It distinguishes the last working date, the resignation effective date, the pension benefit commencement date, and the benefits coverage end. For the process it describes, the last working date is generally one day before the resignation effective date, while pension commencement may require a first-of-month date. A last working day should not be assumed to be the legal separation date or the pension date — so every one of them is worth confirming before you submit anything.
Write the sequence before you file
Benefits systems read effective dates, not intentions
The stakes show up when the systems disagree. If one program treats the departure as a resignation while another expects a retirement workflow, then pension paperwork, annual-match eligibility, final pay, or benefit communications can follow an unexpected path — and you may not notice until a payment or a form arrives looking wrong. The examples in the guide make clear that an effective date can affect payroll access and benefit coverage, so the safe move is to define the dates before notice, not after.
Before giving notice, write a one-sentence definition beside every date — last day performing work, last day on payroll, resignation effective date, benefit coverage end, and pension commencement — and ask each administrator which field actually controls its rule. Capturing them on one calendar is the whole exercise:
- Last working date
- Last day paid
- Resignation effective date
- Pension benefit commencement date
- Benefits coverage end date
Make every office tell one story
HR, payroll, and the plan should read the same dates
It is worth remembering how much the public guide cannot settle. It explains a general retirement process, but it cannot resolve a participant’s employment coding, legacy plan, union agreement, leave status, or a negotiated separation. An involuntary separation, accrued leave, severance, or a disability can each create a different sequence, which is why written confirmation — from HR, the pension administrator, and the 401(k) administrator — matters wherever different programs read different fields.
A clean departure record is one in which the manager, HR, payroll, the pension administrator, and the employee all use the same confirmed dates. That alignment is what keeps a label from changing the financial outcome, and it turns the retirement date from a word into a set of facts everyone agrees on.
This guide provides general education for Honeywell employees. It is not individualized financial, investment, tax, legal, benefits, or securities-law advice and is not a recommendation to buy, hold, sell, exercise, transfer, roll over, or donate an asset.
Frequently asked questions
Questions to take back to the documents
Is retiring from Honeywell administratively different from resigning?
It can be. The retirement process may involve pension and benefit steps that a standard resignation does not. Confirm how HR will code the departure.
Which date controls Honeywell annual-match eligibility?
The public match page uses active employment through December 15 for the contribution it describes. Confirm which employment-status date applies to your case.
Should my pension date appear in my resignation notice?
Follow Honeywell's current instructions and your plan's application process. Do not assume a manager-facing notice alone establishes the pension commencement election.
Primary sources
What this guide is based on
Sources were reviewed on the dates shown. Later plan amendments, filings, agreements, or employee communications may change the answer.
Apply the education carefully
Connect with an advisor experienced with Honeywell employees.
Share the Honeywell planning topic and timing in general terms so Aerospace Wealth can consider an appropriate employer-specialist introduction. Do not include exact balances or sensitive documents.