• Sns.Admin
  • /docs/workflows/requests
  • Docs
    • Overview
      • Approach
      • Vision
    • Concepts
      • Communities
      • Places
      • Structures
      • Spaces
      • Assets
    • Platform
      • Architecture
      • Sns.Framework
      • Sns.Spatial
      • Data Model
    • UX Patterns
      • Entity Icons
      • Editors
      • Layouts
      • Navigation
    • Workflows
      • Place Onboarding
      • Asset Uploads
      • Requests
      • Projects
    • Spatial
      • Maps
      • Providers
      • Geo DTOs
      • Digital Twins
    • Data
      • Places
      • Assets
      • NavItems
      • Scoring
    • AI / Automation
      • AI Assistants
      • Completeness
      • Confidence
      • Monitoring
    • Developer Guide
      • Getting Started
      • Repo Map
      • State Patterns
      • Coding Standards

New Page

docs/workflows/requests

Requests

A request captures a place-aware need before it becomes structured project work. It is the preferred term for intake, proposed work, service needs, or customer-facing asks.

What Requests Should Capture

  • The place, structure, or space involved.
  • The client, contact, or stakeholder context.
  • The requested outcome or problem to solve.
  • Enough status and notes to decide whether it should become a project.

Terminology

Use Request consistently for intake. This keeps intake language clear and leaves Project for the coordinated execution workflow.

More info goes here.
  • Home
  • Finder
  • This Place
  • Explore
  • Database
  • Solutions
  • Ready
  • : 1
  • Enterprise: 13
  • Application: 1046
  • NavItem:
  • Theme: 1