Software as a service for real estate transaction management.

StatusBuilt inside a working brokerage in MT, ID, WA, WY and ND. Live today: the file, the record, permissions, document storage. In build, in this order: forms, signing, document reading.

Caught at upload, not by a reviewer days later.

FlaggedOwner’s Property Disclosure: seller initials missing on pages 3 and 5 of 7. Not ready to submit.

SignBlock is designed to take each upload apart like a reviewer: every document onto its requirement, and anything that would get the file rejected named by page.

Exploded view of an example closing package of 14 scanned pages, separated into its five documents: the Buy-Sell Agreement, pages 1 to 2, held as a duplicate; the Lead-Based Paint Disclosure, pages 3 to 5, filed; the Wire Fraud Advisory, page 6, filed; the Owner's Property Disclosure, pages 7 to 13, flagged because the seller initial boxes on its pages 3 and 5 are empty; and page 14, not identified, kept in Unfiled.SellerBuyerADetail ASeller initials missingon pages 3 and 5 of 7.pkg pp. 9 and 113HELDpkg pp. 1–2Agreement, copyBuy-Sell4FILEDpkg pp. 3–5DisclosureLead-Based Paint5FILEDpkg p. 6AdvisoryWire Fraud6FLAGGEDpkg pp. 7–13DisclosureOwner’s PropertyUUNFILEDpkg p. 14Not identifiedKept in Unfiled until aperson says what it is.
Exploded view of an example closing package of 14 scanned pages, separated into its five documents: the Buy-Sell Agreement, pages 1 to 2, held as a duplicate; the Lead-Based Paint Disclosure, pages 3 to 5, filed; the Wire Fraud Advisory, page 6, filed; the Owner's Property Disclosure, pages 7 to 13, flagged because the seller initial boxes on its pages 3 and 5 are empty; and page 14, not identified, kept in Unfiled.SellerBuyerADetail ASeller initialsmissing on pages3 and 5 of 7.pkg pp. 9, 11UNot identifiedpkg p. 14UNFILEDKept in Unfileduntil a personsays what it is.6Owner’s PropertyDisclosurepkg pp. 7–13FLAGGED5Wire FraudAdvisorypkg p. 6FILED4Lead-Based PaintDisclosurepkg pp. 3–5FILED3Buy-SellAgreement, copypkg pp. 1–2HELD
Fig. 1. Example closing package, 412 Pine Street, Seeley Lake, MT. Listing side, closing Fri 20 Nov 2026. Document reading is in build; illustrative.
  1. closing-package.pdf, 14 pages, from Nora Bexley’s phone · Tue 27 Oct 2026, MDT
  2. 9:02:14 AM Received
  3. 9:02:19 AM Read
  4. 9:02:21 AM Flagged

Solid: a person did it. Dashed: document reading did it, or it waits on a person.

Checklist, example file. 412 Pine Street, Seeley Lake, MT 59868.
RefRequirementSourceState
1Listing AgreementSigningFiled
2Agency DisclosureSigningFiled
Buy-Sell AgreementSigning
pp. 1–2
FiledHeld
Lead-Based Paint Disclosurepp. 3–5Filed
Wire Fraud Advisoryp. 6Filed
Owner’s Property Disclosurepp. 7–13Flagged
7Earnest money receiptTitle co.Open
Unfiledp. 14Unfiled
5 of 7 filed, 1 flagged, 1 open. Not ready to submit. Everything else checks out. The copy of the Buy-Sell is held, not filed twice. Page 14 is kept in Unfiled until a person says what it is.

Signed and filed in the same second.

When the last signature lands, the executed copy files itself back to its requirement. No one downloads it, renames it or drags it onto the checklist. When a signing email fails, the file says who, when, and what to do next.

The Buy-Sell Agreement, sent to three signers on two sides, passes three signature lines: Desmond Hollister, buyer; Evan Lockhart, seller; Maren Lockhart, seller, last to sign. The executed copy drops into requirement 3 on the checklist, beside the Listing Agreement and the Agency Disclosure, at 9:14:08 AM MDT, the same second as the last signature.ABuy-Sell Agreement3 signers, 2 sidesDesmond HollisterBuyerEvan LockhartSellerMaren LockhartSeller, last to signBSigned, 3 of 3Both sidesCExecuted copyTo requirement 31ListingAgreementFILED2AgencyDisclosureFILED3Buy-SellAgreementFILED9:14:08 AM MDTsame second as thelast signature
The Buy-Sell Agreement, sent to three signers on two sides, passes three signature lines: Desmond Hollister, buyer; Evan Lockhart, seller; Maren Lockhart, seller, last to sign. The executed copy drops into requirement 3 at 9:14:08 AM MDT, the same second as the last signature.ABuy-Sell Agreement3 signers, 2 sidesDesmond HollisterBuyerEvan LockhartSellerMaren LockhartSeller, last to signBSigned,3 of 3Both sidesCExecuted copyTo requirement 39:14:08 AM MDTsame second as thelast signature3Buy-Sell AgreementRequirement 3FILED
Fault note, example fileFailed

Delivery failed: the signing email to Desmond Hollister bounced at 2:14 PM MDT. His documents are safe and unsigned. Fix the address and resend, or send a signing link by text.

Document
Addendum No. 1 (closing date)
Sent to
dhollister@example.net
Bounced
2:14 PM MDT, Tue 27 Oct 2026
State
Safe and unsigned. Nothing was lost.
Remedy
  1. Fix the address and resend.
  2. Or send a signing link by text.

Fig. 2. Example file. The Buy-Sell Agreement’s last signature, Maren Lockhart’s at 9:14:08 AM MDT on Mon 26 October, filed the executed copy to requirement 3 in that second. Signing is in build; illustrative.

Who did it, under whose authority, to the second.

Every action on a file writes one entry to an append-only record: the real person, the authority they acted under, what they did, and the time with its zone. Refused attempts are written too. If anyone alters an entry, it stops verifying. This part runs today.

As written, example file: a confirmation

  1. Tue 27 Oct 2026,
    9:31:07 AM MDT.
    aThe time, with its zone
  2. Ada Kessling,bThe person who acted, signed in as herself
  3. acting for Nora Bexley as transaction coordinator.cThe authority she acted under, kept apart from who she is
  4. Confirmed the Wire Fraud Advisory on its requirement.dWhat she did, in a broker’s words
  5. ConfirmedeThe outcome

As written, example file: a refused attempt

  1. Tue 27 Oct 2026,
    11:48:52 AM MDT.
    aThe time, with its zone
  2. Attempted to open the file.dWhat was attempted
  3. Not permitted.eThe outcome, written down like any other
  4. An agent from another office,bThe person who tried
  5. no relationship to this file.cThe authority checked, and found missing

Record, example file

7 of 38 entries. Tue 27 Oct 2026, MDT.

  1. 9:02:14 AMNora Bexley, listing agentUploaded closing-package.pdf, 14 pages, from a phoneReceived
  2. 9:02:19 AMDocument readingRead 14 pages as 5 documents: proposed 3 to their requirements, held the Buy-Sell copy as a duplicate, kept page 14 in Unfiled.Read
  3. 9:02:21 AMDocument readingOwner’s Property Disclosure: seller initials missing on pages 3 and 5 of 7Flagged
  4. 9:31:07 AMAda Kessling, acting for Nora Bexley as transaction coordinatorConfirmed the Wire Fraud Advisory on its requirementConfirmed
  5. 10:12:40 AMGus Thornbury, as office managerApproved the Listing Agreement. The file itself cannot be approved for submission while a requirement is flagged.Approved
  6. 11:48:52 AMAn agent from another office, no relationship to this fileAttempted to open the file. Not permitted.Refused
  7. 2:14 PMSigningThe signing email to Desmond Hollister for Addendum No. 1 bounced. His documents are safe and unsigned.Failed

Fig. 3. Example file. The record itself runs today, with sign-in, permissions and document storage. Entries made by document reading and signing are illustrative until those parts ship.

Machines propose. People confirm.

Each value read from a document arrives as a proposal, led back to its source. Five values never accept themselves, at any confidence: the purchase price, the closing date, the earnest money, the legal description and the party names. They wait above the file for a person.

Source: Buy-Sell Agreement

Party names

PEvan Lockhart and Maren Lockhart, sellers. Desmond Hollister, buyer.

ProposedWaiting on a person

Legal description

PTract 2 of COS 4471, SE¼ of Section 22, T16N, R15W, P.M.M., Missoula County

ProposedWaiting on a person

Purchase price

P$487,000.00

ProposedWaiting on a person

Earnest money

P$10,000.00

ProposedWaiting on a person

Closing date

PFriday 20 November 2026

ProposedWaiting on a person

Fig. 4. Example file. Each proposal is led back to the line it was read from and held above its place on the file until a person confirms it. P marks a proposal. Document reading is in build; illustrative.

Across this page, solid marks what a person did. Dashed marks what document reading did or proposed, or what still waits on a person.

To the cent. Exactly 100%.

Money is kept to the cent and every split adds up to exactly 100%, so the commission sheet reconciles before it goes anywhere.

a

Nora BexleyListing agent

75.00%

b

BrokerageCompany share

25.00%

=

Listing-side splitDollar amounts follow in whole cents once a person confirms the purchase price.

100.00%

Check: 75.00% + 25.00% = 100.00%.

Fig. 5. Example file. The listing-side split. The commission sheet is in build; illustrative.

Four rules it is built to.

They are engineering requirements, not settings. This page keeps the first two.

No ads.

The workspace carries no ads, upsells or partner offers. Not beside a contract, not anywhere.

No trackers.

No third-party trackers run against your clients’ files.

This page loads no third-party scripts and sets no cookies.

Plain PDF, any day, including your last.

Removal requires no special tools: every file exports as a plain PDF.

One brokerage, one database.

Every brokerage is its own database schema, and that part runs today. Each has its own export and its own deletion boundary.

Request early access.

For owners, brokers of record and operations leads at independent brokerages.

Already have an account? Sign in.

Early access requestReplies come from a person

We reply to every one of these ourselves. Nothing here is sent to a third party, and you will not be added to a list.