Header
Include the request date, your full legal name, contact information, and preferred delivery method (email, secure portal, postal address).
A well-structured request letter reduces ambiguity, speeds administrator response, and creates a documented chain of communication useful for compliance or dispute resolution.
The Letter Requesting Pension Plan Information is used by a range of stakeholders who need plan-level or participant-level documents for decision-making, legal, or administrative purposes.
Use the letter to record the request, indicate any statutory authority (if applicable), and provide contact instructions for secure document delivery.
A current or former employee requesting their benefit statement, vesting schedule, or plan SPD. The requester provides full legal name, date of birth, last four of SSN, plan name, and a clear list of documents requested. Requests are usually written and retained for the participant’s records and for any subsequent appeals.
An attorney or executor acting on behalf of a beneficiary who submits proof of authority (power of attorney or letters testamentary) and requests plan documentation for claims, appeals, or litigation. Proof of authorization and clear contact instructions expedite verification by the plan administrator.
Include the request date, your full legal name, contact information, and preferred delivery method (email, secure portal, postal address).
Address the plan administrator or recordkeeper by name and include the plan name and plan sponsor to avoid routing delays.
Provide participant name, date of birth, and last four digits of SSN or other plan ID to permit accurate matching by administrator.
List specific items such as SPD, summary of material modifications, benefit statement, distribution forms, QDRO procedures, and any historical account statements.
If a representative requests information, attach proof such as a signed power of attorney, court appointment, or other written authorization.
Sign and date the letter. Include a printed name, relationship to participant, and if available, a notarized signature or electronic signature per plan policy.
| Step | Online Setting |
|---|---|
| Upload Template | Use PDF or DOCX; preserve form layout and signature block. |
| Add Fillable Fields | Place name, DOB, SSN-last4, and attachment placeholders with validation rules. |
| Configure Signers | Assign signer roles and require typed or drawn signature plus date field. |
| Authentication | Require email plus SMS code or stronger method for representatives. |
Secure file formats and proper authentication protect sensitive pension data during eSubmission and storage.
Confirm the plan’s accepted e-delivery methods and retain an audit trail showing signer identity, timestamps, and document access events.
| 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 | Yes, 7-day free trial | Varies by vendor | Varies by vendor | Varies by vendor | Varies by vendor |
| Bulk Send | Yes | Yes | Yes | Yes | No |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |
Plan document requests commonly answered within 30 days; see ERISA disclosure rules (29 U.S.C. §1024(b)(4)) for specifics.
Initial claim determinations often follow 29 CFR 2560.503-1 timing—commonly 45 days with limited extensions.
Appeal periods and decision windows vary by plan; check the plan’s claims procedures for defined timelines.
Processing a qualified domestic relations order may have separate administrative timelines tied to plan procedures.
If no acknowledgment, a written follow-up after 30 days documents continued pursuit and may be needed for enforcement.
Save signed documents as PDF/A for long-term retention; this preserves layout and is suitable for archival storage.
Keep an editable DOCX copy for internal records, tracking changes, and creating redacted versions when sharing.
Download and store audit logs showing timestamps, signer identity, and access events to demonstrate chain of custody.
Store records in encrypted cloud storage with role-based access controls and retention policies to meet compliance obligations.