Choose the document for the job
Use a Project Scope Statement to define boundaries and expected results, or a Statement of Work to describe the work to be delivered. The tool library also includes a proposal, change request, RACI chart and risk documents.
The document generator formats the fields you supply. Review the substance with the people responsible for the engagement before sharing it.
Understand where the content lives
Standalone text fields are kept in this browser's local storage. Use the same browser and site to return to it. Clearing site data, using another browser or blocking storage can prevent that draft from returning.
Download Markdown creates a text file from the current form fields. Keep that file as your portable copy; it is not an automatic account save.
A project instrument is a document saved inside an authorized project. Its export uses the saved project entry. Save changes before using the project's export, then reopen the entry to confirm the version you intend to share.
Check the exact result
- Finish the wording you want to use for the engagement.
- Download and open the Markdown file; compare its fields and wording with the form.
- Reopen the same standalone tool to check the local draft, or reopen the same project's saved instrument to check the project record.
- After editing, create a new download and check it again rather than assuming an older file changed.
Try the scope-document walkthroughMissing draft or unexpected export
Related development status
| Feature | Vision | Current state | Gap | Planned timing |
|---|---|---|---|---|
| Planning documents | Project plans and client paperwork that agree. | Standalone document generators create Markdown from your fields; authorized project instruments have a separate save/export path. | More connected review across the plan and its documents. | Not yet scheduled |
| Drafts and return | Return to the exact work you reviewed, across supported contexts. | Standalone text drafts use this browser's local storage. Markdown downloads are portable copies; project records require an authorized project save. | Account-based cross-device draft saving and browser restore of risk-table rows are not connected. | Not yet scheduled |
| Sharing | Clients see the intended work with appropriate access. | Markdown exports and available item-specific share links support deliberate sharing. | Broader project-level client sharing and collaboration. | Not yet scheduled |