Pre-scope control / context
Replace “Israel-ready” with decisions someone can verify.
No single checklist describes every Israeli audience or organisation. This canvas records what is true for this service, this operating environment, and this release.
Direction
Language and mixed flow
- Which screens require Hebrew, Arabic, English, or a combination?
- Who approves terminology and meaning?
- What numbers, dates, IDs, and tables mix directions?
- Which devices and assistive technologies must be tested?
People
Audience and access
- Public visitors, customers, staff, partners, or administrators?
- Anonymous, invited, authenticated, or age-sensitive access?
- What accessibility bar and review owner apply?
- Which channels matter when the primary path fails?
Continuity
Operating pressure
- What functions must remain available during disruption?
- Which degraded modes are acceptable?
- Who can authorize an urgent change?
- How will the team communicate when a vendor is unavailable?
Dependencies
Systems and suppliers
- Where does data enter, travel, and rest?
- Which identity, messaging, analytics, hosting, or payment vendors participate?
- What contracts or local access assumptions need confirmation?
- Which dependency has a manual fallback?
Support
Ownership after launch
- Who receives incidents and user reports?
- What response window is actually funded?
- Which changes require a language or professional reviewer?
- Who maintains documentation, credentials, and vendor accounts?
Evidence
Acceptance and release
- What exact journey must pass?
- Who sees the evidence and makes the decision?
- What blocks release even if the code runs?
- What rollback proof and post-release monitoring are required?
Country context informs discovery; it does not create a universal market profile. Current official sources, responsible business owners, qualified reviewers, and real-user evidence should replace broad assumptions.