Issue or revoke a power of attorney

When to use

The company must authorise a named person to act in its name, or must end such an authority. Not for routine acts inside an employment relationship — that is people.hire-employee and the contract itself. Not for signing an ordinary commercial contract — that is documents.sign-with-eparaksts; a POA is for when someone *other than the board member with representative authority* must sign or represent.

Before you start

• The attorney-in-fact and the exact acts they may perform are decided, not "handle our affairs".
• A known end date exists, or the owner has explicitly accepted an indefinite mandate.
• It is known whether the receiving side (bank, court, registry, notary, land book) demands a notarised or

What a run requires6

The trail12 steps

1. S1

   Fix the scopeagent

   Write down: who, what acts, before whom, monetary limits if any, start and end dates, whether sub-delegation is allowed.

   Done when the owner has confirmed this scope in one written sentence or the draft's header.

2. S2

   Determine the required formagent

   Check the receiving side's requirement and the general rule that a mandate may be given in any form unless the underlying act demands more (e.g. real-estate and many registry acts — notarised). ⚠ verify the form for the specific act, with the notary or the receiving registry.

   Done when the form is written in the record: simple written + e-Paraksts, or notarised.

3. S3

   Draftagent

   Draft in Latvian (and the counterparty's language if needed — see documents.translate-contract), with the company's registration data, the exact acts, limits, term, and an explicit revocation clause.

   Done when a draft exists in the documents module, versioned.

4. S4

   Approve the textownerneeds approval · owner

   Approval · S4 · owner — the run stops until a named person records the decision

   Done when the owner has approved the exact text and named the signatory for the company.

5. S5

   Signprincipal

   Simple form: both sides sign with qualified e-Paraksts or wet ink. Notarised form: book the notary; the board member (or someone with an existing POA) attends.

   Done when a signed file or notarial original exists.

6. S6

   Deliveragentneeds approval · ownerirreversible

   Approval · S6 · owner — the run stops until a named person records the decision

   Irreversible · S6 — an agent never closes it alone

   Send or hand the original to the attorney-in-fact or the receiving third party, as the owner approved.

   Done when delivery is proven — receipt confirmation, courier note, or the third party's confirmation.

7. S7

   Recordagent

   File the signed document and scope summary in the documents module; add the expiry to the watch.

   Done when the record shows scope, term, form, delivery proof and expiry date.

8. S8

   Diariseagent

   Set the expiry reminder far enough ahead to renew or revoke deliberately.

   Done when the reminder exists and is linked to the record.

9. S9

   On revoke: prepare the revocationagent

   Draft a revocation naming the original POA and its date, effective immediately or on a stated date.

   Done when a revocation draft exists and the original POA record is referenced.

10. S10

    Approve the revocationownerneeds approval · owner

    Approval · S10 · owner — the run stops until a named person records the decision

    Done when the owner has approved the revocation text and date.

11. S11

    Notifyagentneeds approval · ownerirreversible

    Approval · S11 · owner — the run stops until a named person records the decision

    Irreversible · S11 — an agent never closes it alone

    Send the revocation to the former attorney-in-fact and to every third party known to have relied on the POA (bank, registry, counterparties).

    Done when each notice has delivery proof.

12. S12

    Close the recordagent

    Mark the original POA revoked in the documents module, attach the notices, remove the expiry reminder.

    Done when the record reads revoked, with date and notice proof.

Checks — how we know it worked

• Scope read back: the signed text says exactly what S1 recorded — no "and related matters" without limits.
• Form matches what the receiving side demands (their written requirement is in the record).
• Term is stated; if indefinite, the owner's acceptance is in the record.
• A revoked POA: every known third party has a dated notice; the record is closed.

If it goes wrong

What each step leaves behind

1. S1the owner has confirmed this scope in one written sentence or the draft's header.
2. S2the form is written in the record: simple written + e-Paraksts, or notarised.
3. S3a draft exists in the documents module, versioned.
4. S4the owner has approved the exact text and named the signatory for the company.
5. S5a signed file or notarial original exists.
6. S6delivery is proven — receipt confirmation, courier note, or the third party's confirmation.
7. S7the record shows scope, term, form, delivery proof and expiry date.
8. S8the reminder exists and is linked to the record.
9. S9a revocation draft exists and the original POA record is referenced.
10. S10the owner has approved the revocation text and date.
11. S11each notice has delivery proof.
12. S12the record reads revoked, with date and notice proof.

Evidence to keep

Approved scope (S1) · signed POA or notarial original (scanned) · delivery proof · expiry reminder id · on revocation: revocation text, notice proofs, closed record. The next person must be able to see, from the record alone, who could act for the company, when, and when that ended.

How this playbook improves

After every 10 runs ask: how often did the form turn out wrong at the receiving side (S2 miss)? Did any attorney-in-fact act beyond scope? Were any revocations late or unprovable? A new version tightens S2's verification or the scope template, and says so in its change note.