Issuing a Power of Attorney on FreeholdIP

You issue a secure, revocable digital record of a Power of Attorney your client owns, one that anyone can confirm is genuine and currently in force, without calling your office.

⬇ Download this guide as a PDF

What this is, honestly

The record accompanies the executed instrument. It doesn’t replace it, or any execution formality under your state’s law. Its job is to let anyone confirm, without calling you, that a mandate is genuine and currently in force. Set client expectations accordingly:

• It’s strongest where no settled acceptance process exists: digital and self-custodied assets, where there is no clerk and RUFADAA visibly fails.
• With a traditional institution it supports the paper, most usefully as the “has this been revoked?” check, rather than supplanting the institution’s own process.
• It is also, simply, an authoritative live registry of every mandate your firm has issued and its current status.

One-time setup

Your firm is a verified issuer with a signing/login file. Safeguard it like a signature stamp. It signs every mandate as your firm, and we never hold a copy. (Optional: bind your firm’s domain so your own domain vouches for your key.)

For each mandate

1. Sign in at authority.freeholdip.com with your firm’s login file, you land directly in the mandate console.
2. Using Clio? Connect it first and import the matter: the client’s name and address pre-fill from your own records, no re-keying. (Connect before unlocking your signing key: connecting hops to Clio and back, and the unlocked key lives only while the page stays open. The connection is per-session; we never store your Clio tokens or client data.)
3. Unlock your firm keystore: the key decrypts and signs in this browser only; we never see it.
4. Identities: send the client an intake link (they fill in their own details and create their identity; it arrives back as a draft you review), or use the “✉ Invite” button beside each name. Creating an identity takes about two minutes.
   Take a copy of the client’s Recovery Sheet for the client file, your standard fiduciary safekeeping, and the client’s backstop if their own copy is lost.
5. Fill the mandate: scope, effective (immediate or springing on incapacity), jurisdiction, limitations. Upload the executed Power of Attorney; its fingerprint is sealed into the record.
   Expiration is optional: leave it unset and the mandate is in force until revoked, and the record says so plainly.
   Optionally name co-agents and successor agents, with an exercise rule: acting singly, jointly, or by an M-of-N threshold. (See “Beyond the basic mandate,” below.)
6. Issue: the mandate is signed in your browser with your firm key; we never see it.
7. Deliver the verify link, QR code, and downloadable copy to the client and the agent. Connected to Clio? One click files the self-verifying copy into the matter’s Documents. The firm’s system of record holds the artifact that keeps verifying even offline.
8. Maintain: revoke, reinstate, renew, or re-scope anytime under Manage; activate a named successor when the moment comes. Changes take effect immediately for anyone who checks.

Beyond the basic mandate

The same record carries authority through its whole life: the handoff on incapacity or death, and the self-custodied digital assets a custodian can never be served for. Each of these rides the same signed, revocable rail; none of it ever holds a key or an asset.

Multi-party roles & clean transitions

• Co-agents & successors. Name co-agents who serve alongside the primary and ordered standby successors, with an exercise rule (single, joint, or M-of-N). The certification shows exactly who holds authority.
• Activate a successor. When the triggering event occurs, you activate the named successor from Manage with your firm key. The certification then leads with who is acting now, on a clean, Bitcoin-anchored history: your defensible answer to “who held this authority, and when did it change?”
• Springing safeguard. Gate an incapacity transition behind typed two-physician attestations, a waiting period, and a protector’s veto, so it springs only when it should.
• The survivor path. Pre-authorize, at issuance, named attestors whose independent statements can activate a successor even if your firm can no longer act, checked by math at verify-time, with no call to the firm. A true continuity backstop for your clients.

Digital & self-custodied assets: the operate layer

• Asset & succession inventory. Issue a companion record that triages a client’s assets: what a custodian can be compelled to disclose, versus the control-based assets the statute can’t reach. It records public, watch-only references only (an xpub, a descriptor, a domain, a handle). A fail-closed guard blocks anything that looks like a secret.
• Reconstruction recipe. For a control-based asset, attach a successor-only “how to take control” map: a Shamir-share plan, or a native-multisig policy where the successor is a co-signer from the start. It is encrypted to the successor’s own key before it reaches us; we hold only ciphertext. The shares and co-signing keys stay with the client’s chosen people, and the successor reconstitutes control on the asset’s own chain, on their own device. No key, share, or signature ever passes through you or us.

Your responsibilities

• You vouch for what the record states. The accuracy of the mandate is yours, the same as any attestation you make.
• It accompanies, never replaces, the executed instrument or its execution formalities.
• No custody. Neither you nor FreeholdIP ever holds the client’s assets or keys. The record proves who is authorized; it never moves anything itself.
• You attest the binding, not the secret. For an inventory or a reconstruction recipe, you record where things are and who holds them, never a key or a share. The accuracy of that map is yours; the secrets stay in client/fiduciary custody.