SaaS Transfer Control Register
Record who owns each handover task, what the buyer has actually checked, where the evidence sits and what still blocks the transfer.
Read the acquisition guide →A handover record built around evidence, not ticks
What it does
The register tracks 12 controls across production, customer access, payments, security, operations and closing evidence. Each control can have a status, owner, deadline, buyer test date, evidence reference and next action.
Who it is for
It is intended for buyers and sellers of small software businesses, and for advisers or technical operators coordinating a handover. The sample acquisition shows how unresolved domain, payment and database issues remain visible even when other work has progressed.
How the statuses work
Pending, seller-claimed, buyer-inspected, buyer-tested and blocked are deliberately different. A seller’s statement is not treated as a buyer test. A critical control marked not applicable still needs a written reason.
What the export contains
The report includes the overall position, status counts, every control, its owner and dates, the evidence reference, the recorded finding and recommended work that remains. A JSON backup can be imported later to continue the project.
What it cannot verify
The register does not connect to GitHub, hosting, registrars, payment providers or databases. It cannot prove legal ownership, security, financial condition or the accuracy of a statement entered by a buyer or seller. It is an operating record, not legal or financial advice.
Privacy and storage
Projects stay in this browser’s local storage and are not sent to ArsKhan. Clearing browser data removes them. Export a backup before changing devices or clearing site data, and record only evidence references—never passwords, tokens, recovery codes or customer information.