Establishing secure connection…Loading editor…Preparing document…

Power of Attorney PBGC Form 715

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

NOTICE OF REVOCATION OF
DURABLE POWER OF ATTORNEY

WHEREAS, I as Maker, created a Durable Power of Attorney by a written instrument:

WHEREAS, I, as Maker, appointed Appointee to serve as my Agent and to exercise the powers set forth in the said instrument:

WHEREAS, pursuant to the terms of the said instrument, I reserved unto myself the exclusive right to amend or revoke at any time the powers created thereunder, including the power to remove my Agent, without the consent of my Agent;

NOW THEREFORE, pursuant to the aforesaid right of revocation, I do hereby revoke in its entirety the said Durable Power of Attorney created by me.

IN WITNESS WHEREOF,

I have hereunto set my hand and seal this day of ,

Enter text

What Power of Attorney PBGC Form 715 Is and when it applies

The Power of Attorney PBGC Form 715 is a written authorization used to designate an individual or firm to act on behalf of a plan sponsor, plan administrator, participant, or beneficiary in dealings with the Pension Benefit Guaranty Corporation (PBGC). It specifically authorizes representation for administrative matters such as claims, notices, information requests, and correspondence regarding defined benefit pension plans. This form is limited to PBGC-related matters and differs from a general durable power of attorney; accuracy of names, scope, and dates is critical to avoid processing delays.

Why completing Form 715 matters for PBGC interactions

A correctly completed Power of Attorney PBGC Form 715 makes it clear who may receive privileged plan information and transact with PBGC on behalf of a plan or individual, reducing administrative delays and preventing unauthorized inquiries.

Why completing Form 715 matters for PBGC interactions

Who typically uses the Power of Attorney PBGC Form 715

Common users include plan sponsors, plan administrators, participants, beneficiaries, and their professional representatives.

  • Plan sponsors and administrators: Authorize administrators or third-party administrators to manage PBGC filings and respond to PBGC inquiries on the plan's behalf.
  • Participants and beneficiaries: Appoint attorneys or family representatives to obtain information, file claims, or receive plan notices when the individual cannot act directly.
  • Attorneys and consultants: Use Form 715 to obtain client authorization to communicate with PBGC and to submit documents for pension matters.

Who can sign and represent parties

Authorized Representative

An attorney, consultant, third-party administrator, or named individual who accepts authority to act before PBGC. The representative should provide identification and, where requested, proof of the agency relationship or firm affiliation to avoid verification delays.

Plan Sponsor

An employer or plan sponsor signs to delegate PBGC interactions. The sponsor's signer must have corporate authority (officer or delegated signatory), and the signature must match the legal entity name used on PBGC filings and plan documents.

Step-by-step: completing Power of Attorney PBGC Form 715

Follow these core steps to complete Form 715 accurately and avoid common processing problems with PBGC.

  • 01
    Gather documents: Collect plan name, PBGC case number, and valid IDs.
  • 02
    Complete fields: Enter full legal names, addresses, and scope of authority.
  • 03
    Sign and notarize: Signatures and notarization where required ensure acceptance.
  • 04
    Submit to PBGC: Send the original or e-submission per PBGC instructions.

Digital workflow settings when e-submitting Form 715

Configure e-signature and routing to match PBGC acceptance requirements and internal approvals before sending for signature.

Field Configuration
Authentication Method Email link | SMS code | ID verification
Signer Order Sequential or parallel
Field Locking Lock after signing
Retention Setting Store final PDF and audit trail

How e-submission of Form 715 typically proceeds

A concise flow shows upload, placement of signature fields, signer authentication, and final delivery to PBGC or the plan file.

  • Upload: Sender uploads completed PDF to platform.
  • Place fields: Assign signature, date, and text fields.
  • Authenticate: Signers verify identity per chosen method.
  • Deliver: Send signed copy and audit trail to PBGC and parties.

Core parts of the Power of Attorney PBGC Form 715 explained

Understanding each section helps ensure that the form grants exactly the authority intended and will be accepted by PBGC without additional verification.

Principal identity

Full legal name, address, and identifying details to tie authority to the correct person or plan sponsor; essential for PBGC file matching and compliance.

Representative details

Name, firm, contact information and professional identifiers so PBGC can communicate directly and verify representation when needed.

Scope of authority

Clear, enumerated powers (e.g., receive documents, submit claims) to avoid misinterpretation and limit unintended grant of rights.

Effective and expiration dates

Defines when the POA begins and ends; an expiration prevents perpetual authority and clarifies parties' obligations.

Notarization and witness

When required by state law or PBGC practice, notarization or witness blocks provide proof of execution and reduce acceptance issues.

Submission instructions

Provide how copies should be delivered to PBGC, whether an original is required, and any internal routing expectations for retention or audit.

Security and compliance considerations for electronic Form 715

Encryption: TLS 1.2/1.3 in transit, AES-256 at rest
Certifications: SOC 2 Type II, ISO 27001
HIPAA support: BAA available where needed
Audit trail: Detailed timestamp and IP log
Authentication: Email, SMS, or stronger methods
Record laws: ESIGN and UETA compliant

Consequences of an incorrect or incomplete Form 715

Invalid authorization: PBGC may refuse representation
Delayed processing: Case actions may be postponed
Misdirected notices: Important communications lost
Civil penalties: Potential regulatory exposure
Privacy breaches: Unauthorized PHI disclosure risk
Rejection by PBGC: Form returned for correction

Common mistakes when preparing Form 715

  • Using informal or abbreviated names that do not match plan or government records, causing PBGC to require additional verification before acceptance.
  • Failing to state the scope of authority precisely—broad language can lead to disputes or PBGC refusing to act on ambiguous powers.
  • Omitting notarization or witness signatures when state law or PBGC practice requires them, leading to rejections or processing delays.
  • Providing expired effective dates or leaving expiration blank, which can result in PBGC declining to recognize the representative.

eSignature platform comparison for submitting and storing Form 715

Comparing core platform attributes can help organizations choose an eSignature vendor that meets PBGC documentation, security, and retention needs.

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 (tiered) Yes Yes Yes No
Audit Trail Yes Yes Yes Yes Yes
HIPAA Compliant Yes Yes Yes No No
Envelope Cap No cap 100 envelopes/user/yr Varies Varies Varies

Technical and integration considerations for electronic Form 715

Ensure the eSignature platform supports required integrations, secure storage, and audit logs before e-submitting Form 715.

  • Integrations: Salesforce, NetSuite, Google Workspace
  • Formats: PDF, DOCX, TIFF supported
  • Record exports: Audit trail and signed PDF

FAQs and troubleshooting for Power of Attorney PBGC Form 715

Answers to common questions about validity, notarization, e-signature acceptance, and PBGC submission practices for Form 715.


Need help? Contact support

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