Lock agreements, review change requests, and ship amendments—with mutual OTP and a clear audit trail.
OTP
Both sides verify before activation.
Audit
Events tied to verified identity.
ScopeTracker is built for teams who ship creative and technical work under fixed or milestone contracts. You keep one source of truth for what was agreed, what was asked later, and what both sides signed—including change orders when scope moves.
Incoming asks get reviewed against the locked agreement. You decide in-app whether something is in scope or needs a commercial change—so “small tweaks” don’t silently become unpaid work. Each path stays documented for you and the client.
Activation requires verification from both sides. That reduces one-sided “we’re live” surprises and keeps consent aligned with how you actually work.
Content snapshots and signing events are stored with metadata you can review later—useful when timelines or approvals are questioned months down the line.
When scope changes, generate structured amendments instead of endless email chains. The same signing and audit model applies—so extensions and additions stay as defensible as the original deal.
Your client gets a focused portal to review and sign—without managing another product login for a one-off engagement. You keep the dashboard, automations, and history on your side.
Each step is designed so the legal and operational story matches: what was proposed, what was agreed, and who confirmed it—without relying on screenshots of Slack.
Build contract content in the editor. When you save, ScopeTracker records a structured snapshot so the signed version is explicit—not a moving target.
Invite your client through a dedicated link. Each of you receives a one-time code on your own email (either order); the contract goes active after both verify.
Scope requests land in your workflow. Accept, decline, or convert out-of-scope work into an amendment with a documented decision.
Changes get their own signing flow and audit metadata, so your paper trail stays continuous from original SOW through every extension.
Whether you’re solo or running a small team, the same problems show up: unclear scope, late change requests, and disputes about what was agreed. ScopeTracker is opinionated about fixing that at the contract layer.
Sensitive actions run on the server with a verified session — not on trust in the browser alone. Signing uses one-time codes per person so consent is explicit and easier to audit later.
Straight answers about signing, data, and how ScopeTracker fits next to your other tools.
No — only one inbox at a time. When you sign, you get a code to your email; the other person gets theirs on their login. You can go in either order. The contract (or amendment) only goes fully active after both have entered their codes.
Yes. After a contract is active, use Request to close project to email the other party — they approve or decline so closure is mutual. If you already agreed outside the app, either side can still use Mark completed now. Either side can reopen a completed project if work resumes.
Business records (contracts, amendments, signatures, audit metadata) are stored in the PostgreSQL database you configure for the backend. Supabase handles authentication; your DATABASE_URL points at your own Postgres instance.
You can turn on the auth providers your project uses (e.g. Google) in your Supabase dashboard; the app uses that for sign-in and the API still validates access on the server.
You log scope requests, decide in or out of scope, and when needed spin up an amendment. That amendment goes through the same structured signing flow so the new terms are as clear as the original agreement.
Create an account, draft your first agreement, and invite a client when you’re ready. Compare plans and limits on the pricing page.