What's new

Changelog

What shipped in scopedrift, newest first. Every entry is something you can use today.

Run Inception your way: playbooks, intent, and change orders

scopedrift now runs the first phase of a project as a configurable playbook: capture what the business wants before anyone decides how, bring the technical team in when your firm says so, or start from a recorded kickoff. For software teams this is the Inception phase of AI-DLC, the AI-driven development lifecycle published by AWS. It works just as well for a process change, a system rollout, or a policy project.

  • Playbooks. Three built-in orders of operations (Business first, Technical from the start, Meeting-led kickoff) with stages, participants, exit gates, and a stage rail on every project. Clone and edit them under Settings, pin one per organization, and pick one when you create a project.
  • Intent. What the business is trying to achieve and why now, approved by the sponsor as the first gate, fed to the interviewer and the requirements generator, and printed at the top of every export.
  • Business and technical interviewer modes. Business stakeholders are never asked how to build it; ideas they volunteer are parked for the technical stage. Technical stakeholders see those parked ideas and can send a question back to a named business stakeholder.
  • Meeting-led kickoff. A recorded kickoff (Recall.ai) or a transcribed upload drafts the intent for the sponsor to confirm and mines the transcript against every stage of the playbook.
  • Acceptance criteria and units of work. Every requirement now carries Given / When / Then criteria cited to the answers behind it, grouped into units of work the team can push to Jira or Linear as epics with their stories.
  • Inception timeline. Each project overview shows measured days from intent to approved requirements to hand-off, with the events in between.
  • Change orders routed by business unit. When scope drift finds work that was never agreed, the drafted change request names the stakeholder whose answers shaped the affected requirements, goes to them for a decision through the questionnaire they already know, and exports as a signable PDF.
See how it works

Specialists: a review panel built for each client

scopedrift reads what a client runs, what regulates it, and the documents you upload, then proposes the specialist reviewers that project needs. Each one asks its own discovery questions and reviews every requirements document from its angle.

  • Admins approve, edit, fork, or write specialists before any of them is active.
  • Reference checklists for HIPAA, SOC 2, WCAG 2.2, PCI DSS, AWS and Azure Well-Architected, OWASP ASVS, and GDPR.
  • Findings carry evidence and consequence, and ship in the PDF and Word exports.
Read about Specialists

Intake portal and modern app shell

A branded portal where business users submit and vote on requests in plain language, feeding the roadmap and the per-organization changelog, alongside a refreshed application shell.

  • Public portal per organization with voting, status, and a shipped-items changelog.
  • Plain-language copy throughout the surfaces business users touch.

Scope drift detection

Connected Jira, Linear, GitHub, Notion, and Confluence work is compared with the agreed requirements on a schedule. Work that was never agreed and requirements whose implementation has moved are raised as findings for triage on the Requirements tab.

  • Nightly scans with creep and drift findings, acknowledge, dismiss, or mark as change-order material.
  • A change request document drafted from the change-order queue, grounded in the agreed requirement codes.