Methodology

Our methods depend on the question. A provider’s documentation can establish what it says a product does on the day we read it. It cannot establish what your account includes, what an export will contain or what a transaction legally requires.

Documentation comparisons

Comparison records note whether a provider’s official documentation names a specific object, such as documents, tasks, contacts, activity history or signature evidence, each with its source and the date checked. A general statement that data can be exported is not used to fill a specific field. Unknown means the documentation did not establish the field, not that the feature is missing, and conflicting statements are kept side by side. No account was opened and no export was requested to produce them.

Before records are published

Each provider’s terms are read before its documentation is compiled, and sources whose terms prohibit compilation are left out. Each source page is opened and read individually. The checks are recorded in each data set’s source ledger.

Measurements

Measurement pages run original synthetic inputs in named runtime versions and publish the raw results, the exact commands and the environment details. The date-portability records, for example, compare how Node.js and Python read twenty invented date strings under one declared time zone. They are parser results, not deadline calculations or tests of any provider’s software.

Fictional models

Some guides test small original models, such as who can see a signing field or which role can open a file, against invented cases with stated expected outcomes. A model shows how a rule behaves; it does not test a provider’s access controls or signing service.

Official guidance

Guides on closing payments, privacy and brokerage practice read the current guidance of the bodies that publish it, such as the CFPB, the FTC, the FBI and the National Association of Realtors, and cite it with the date read. They summarize that guidance; they do not replace it or apply it to a particular transaction.

Historical notes

The RealTech page relies on dated contemporary reporting and says what that reporting does not establish, such as attendance or later editions.

The checklist

The private checklist stores the task fields you enter under a single key in this browser’s storage. It has no account, nothing leaves this browser, and it makes no network requests when saving or exporting. It validates an imported file and asks for confirmation before replacing a non-empty checklist, and if the checklist is open in two tabs, a stale tab reloads the newer copy instead of overwriting it. Exports are JSON or CSV, with CSV text cells protected against spreadsheet formulas. It was checked in a real browser at desktop and phone widths, including with scripts blocked, and its validation code is tested with published fixtures.

What we publish

Compilations and measurements are CC BY 4.0, and original code is MIT licensed. Each data set’s METHOD file, hash list and source ledger are published with it. Those licences do not relicense providers’ documentation, forms, software or marks.