The optional pre-gate intake: one page, enough on paper to decide whether an idea earns a Gate 1 review. Don't design anything yet — requirements, options and priorities come at the gates. Once it's worth pursuing, this carries forward into Gate 1.
Mirrors the canonical FSD-FRM-00 — FitSD v0.3.0; the canonical form is the authority, so review before use. Nothing is sent to any server — this runs entirely in your browser; download a Markdown record to save your progress.
Resuming a saved form? Load a .md you (or a teammate) downloaded earlier to pick up where it left off — read in your browser only, nothing is uploaded.
.md
Who raised it: someone on the team, another team, or a third party / customer asking the team to take the work on.
Where it came from and why: strategy, customer, compliance, risk, operational, finance/people; value / compliance / risk reduction.
One page. What's the problem, what would “done” look like, and what's roughly in and out of scope.
What's the problem or gap this addresses?
What would “done” look like — the outcome, not the design.
Name the standing Service Acceptance baseline as the quality bar this must eventually meet, and flag any project-specific emphasis, so quality shapes selection and design from the start, not just at acceptance. By reference only; don't re-specify it here.
Yes, see FitSD — Service Acceptance Criteria.
e.g. this one leans hard on availability / continuity / a regulatory measure.
One line on why.