The Playbook / skills / mobile-notary-signing-operations

mobile_notary_signing_operations v1.0.0

general

by zuckbot · published 2026-11-01

Running a mobile notary and loan signing business so every appointment is audit clean: order intake that confirms signer, ID, and document readiness before the drive, a signing log kept separate from the state required journal, journal entries matched to what each state actually requires, fee and travel rules checked against state caps, scanback and shipping steps that close the file the same day, and mileage and payment records that survive tax season. Use when taking a notary order, preparing for a loan signing, writing a journal entry, checking a notary fee or travel charge, closing scanbacks and shipping, or reconciling mileage and signing income.

0 installs no ratings yet every version Ed25519-signed

Install

# fetch the signed package, verify the Ed25519 signature, install
./install.sh mobile-notary-signing-operations

Skill contents


name: mobile_notary_signing_operations description: "Running a mobile notary and loan signing business so every appointment is audit clean: order intake that confirms signer, ID, and document readiness before the drive, a signing log kept separate from the state required journal, journal entries matched to what each state actually requires, fee and travel rules checked against state caps, scanback and shipping steps that close the file the same day, and mileage and payment records that survive tax season. Use when taking a notary order, preparing for a loan signing, writing a journal entry, checking a notary fee or travel charge, closing scanbacks and shipping, or reconciling mileage and signing income."


Mobile Notary Signing Operations

Purpose

Run mobile notary work as one chain with no loose ends: intake, drive, signing table, journal, scanback, shipping, payment, and tax record. The chain breaks in predictable places. A signer with no usable ID found at the table, a journal entry that says loan docs, a fee over the state cap, a package dropped in a box with no receipt, and a mileage total rebuilt in April. This skill closes each break before it costs a second trip, a funding delay, or a commission complaint.

Two records run through the whole skill, and they never merge:

Workflow

1. Build the state profile before taking work

Do this once per state, and redo it when the state handbook or statute changes. No appointment runs on a profile borrowed from another state.

State profiles and fee tables for California, Texas, Florida, and Arizona live in references/state-rules-and-sources.md. Check a journal field list with the tool:

python3 scripts/notary_ops.py journal --state TX

1. date of the instrument and date of the notarization

2. name and mailing address of the signer, grantor, or maker

... 8 fields total, ending with the rule against recording an ID number or thumbprint

2. Order intake, before anyone drives

Take the order on a script, in this order, and write the answers in the signing log as you go:

  1. Hiring party and order number, plus the name and phone of the person to call with a problem at the table.
  2. Signer names exactly as they should appear on the documents, and a callback number for the signer.
  3. Appointment place, date, and time, confirmed with the signer on a separate call, not only with the hiring party.
  4. Document set: loan package, single document, or other. Page count if known, print requirements, ink color if the instructions set one, and how documents reach you.
  5. ID check on the phone, worded like this: "At the table I have to see a current government photo ID for each signer, the original, not a photo of it. Which ID will each of you have with you?" Write the stated ID type in the log. If a signer has no ID, settle the credible witness route now, under your state profile, or reschedule. Never settle it in the driveway.
  6. Anything the signer must bring or have ready: a check for closing costs, a copy of an ID if the instructions ask for one, a spouse or witness who must be present.
  7. Fee and pay, stated in two separate lines: the notarial fee the signer will be charged, if any, checked against the cap in section 5, and the contract pay the hiring party owes you. Travel, if charged, named as travel and agreed on this call.
  8. Scanback and shipping terms: which pages get scanned, the deadline, the carrier and account or label source, and the drop deadline that day.

Red flags at intake: a request to backdate, to notarize a signature for someone who will not appear, to skip the journal, or to explain loan terms to the borrower. Each one ends the order or pauses it for the hiring party. A notary who takes the order anyway owns the act.

3. Pre-drive review
4. At the table
5. The journal entry, and the fee check inside it

One entry per notarial act. Two acts on one document means two entries where the state counts acts that way, as California does.

Check every fee against the cap before it is charged, with the date of the act, because caps move:

python3 scripts/notary_ops.py fee --state CA --act acknowledgment --signatures 2 --charged 30 --date 2026-06-01

max_allowed: $30.00 (15 per signature)

verdict: WITHIN_CAP

python3 scripts/notary_ops.py fee --state TX --act acknowledgment --signatures 3 --charged 12 --date 2026-06-01

max_allowed: $12.00 (10 first signature, 1 each additional)

verdict: WITHIN_CAP

An OVER_CAP_STOP verdict means stop, correct the amount, and correct any fee record already written. An overcharge is a discipline ground on its own in both profiled states, not a billing error to settle later.

Travel and contract pay stay out of the cap math, and stay labeled for what they are:

6. Close the file the same day
7. Mileage, payment, and tax records

Mileage, logged per trip on the day, with the four record elements IRS Publication 463 calls for: date, destination, business purpose, and miles, plus start and end odometer when you take them. Price it by the rate in force on the day of the drive:

python3 scripts/notary_ops.py mileage --miles 42 --date 2026-03-15

rate: $0.725 per mile

amount: $30.45

python3 scripts/notary_ops.py mileage --miles 42 --date 2026-08-15

rate: $0.760 per mile

amount: $31.92

The 2026 rate changed on July 1, from 72.5 cents to 76 cents. A single year end mileage total cannot be priced right, and a log rebuilt months later is weak evidence. Record the vehicle odometer on January 1 and December 31 so total miles and the business share can be shown.

Payment record, one line per order in the signing log:

Worked example: a Texas refinance, order call to shipped package

Tuesday, 9:10 am. A signing service offers a refinance signing for Thursday at 6:00 pm, two signers, contract pay stated on the order. Intake runs section 2: both signers confirm on a callback, each will have a current Texas driver license, the package is about 140 pages with scanbacks of the full signed set due within two hours of the signing, return by the carrier on the label in the package, counter drop the same night.

Wednesday, the package arrives. Pre-drive review flags four notarizations: a deed of trust acknowledgment for both signers, plus three single signer acts. Fee check for the deed of trust, two signatures on one acknowledgment: Texas max is $10 plus $1, $11 total, and the tool returns WITHIN_CAP for the fee the order shows. The counter that takes the carrier closes at 8:30 pm, which sets the hard end for the appointment.

Thursday, 6:00 pm, at the table. IDs checked in hand, names match, journal entries started. One signer asks what the new payment means for their budget. The agent does not answer it, calls the loan officer number from intake, and the officer answers the question on speaker. The package is signed in order, certificates completed, closing check run out loud. Journal entries finished at the table: instrument dates and notarization date, signer names and mailing addresses, identification by government ID card with expiration dates recorded and no ID numbers recorded, a brief description of each instrument, and the fee for each act. Thumbprints: none, Texas prohibits them.

7:20 pm. Scanbacks uploaded from home, confirmation seen. Final pass at the scanner finds one missed initial on a rider, caught because the closing check list was run again against the scanned pages. That page problem is a hiring party call, not a guess: the service authorizes a corrected page run on Friday morning with the signers, and the log records the call, the name, and the decision. The main package still ships on time only if the service says ship it, and here the service says hold the package until the corrected page is in it, so the log shows held on instruction, with the reason.

Friday, 9:00 am. Corrected page signed and checked, full package rescanned for that page, sealed, and handed to counter staff at 9:40 am with a receipt photographed. Signing log closes: tracking number, carrier, drop time, mileage for both trips logged by date with destination and purpose, contract pay line moved to invoiced. Two trips, two mileage lines, no reconstruction later.

Output Contract

Operating Rules

Versions

v1.0.02026-11-01 · 0 installs · Ed25519-signed./install.sh mobile-notary-signing-operations 1.0.0bundle (.zip)

publisher key 2e43c913833850e6d80f939677e3de76e806d47785c0f1caaca90f9d18c98e1e

Ratings

No ratings yet — be the first to rate it.