Today
Shows the next scope decision, recent records, and the simple status of requests or approval records that need attention.
A simple workflow for project scope decisions.
Use Scope when a client request arrives and you need to answer one practical question: is this already included, or should it become approved extra work?
The basic flow
- Create one project. Start with the project name, client name, and currency. SOW and pricing can stay collapsed until you need them.
- Attach an SOW. Use the SOW library to save common agreement text once, then apply it to a project and edit the project copy.
- Add the client request. Paste the request from chat or email, or type it directly into the app.
- Choose in scope or out of scope. In-scope items become included records. Out-of-scope items can include estimated hours, charge amount, and evidence.
- Save an approval record. When out-of-scope work needs confirmation, save a local approval record and copy share text for the client.
- Back up the workspace. Export a JSON backup to the storage location you choose.
Keep it light: Scope is not trying to replace your contract, invoice system, or messenger. It keeps a clear local trail for the moments where scope can become disputed.
What each tab is for
Projects
Manage project details, SOW text, pricing policy, reusable SOW templates, and the active project list.
Records
Review saved approval records, proposed items, approved items, rejected items, and the trail of scope decisions.
Settings
Change language, export a JSON backup, or import a backup while using the app locally.
SOW and pricing notes
Reusable SOW
Create a saved SOW when you reuse similar terms across projects. The template keeps SOW text and pricing policy together.
Project SOW
A project can copy a template and then keep its own edited text, so one client project can differ from the reusable template.
Pricing policy
Use pricing policy text for rules such as revision limits, paid changes, hourly work, or approval before extra work starts.
Charge amount
Out-of-scope items can carry a charge amount. In-scope items are treated as included work with no extra charge amount.
Quick troubleshooting
I do not have an SOW yet.
Create the project first and leave SOW collapsed. You can add a reusable SOW later or write project-specific text when the agreement is clearer.
Why do I need an approval record?
Use it when an out-of-scope item should be grouped and reviewed before you continue. It creates a local record and share text, not a tax invoice.
Where is my backup saved?
The app creates a JSON backup and opens the system share or file flow. The final destination is the place you choose.