Danvas
Danvas
DashboardSupportWelcome

👤 USER DOCS

User Guides

Getting Started

Getting StartedDashboard & OnboardingApp Settings

Tutorials

Tutorial: Setting Up Shift Tasks & ClosersTutorial: Managing Incidents in the InboxTutorial: Tracking Compliance & Sync StatusTutorial: Operational Workflows with the AI AssistantTutorial: Building & Deploying Custom Checklists

Daily Operations (Staff)

Shift Workspace & TasksService Day SetupDaily Line-UpStaff Service Day ReportsForms

Communication & Chat

Messages & AnnouncementsUnified Operations InboxAI Assistant

Manager & Admin Guides

Daily Line-Up SetupStaff SchedulingManaging LocationsNPS and Guest FeedbackCouponsContacts and Guest HistoryManager CloseoutsDaily Line-Up & ComplianceAnalyticsIncident ReportingWhistleblower Concerns & FeedbackAdmin Tools

⚙️ DEVELOPER DOCS

Getting Started

Getting StartedDevelopmentDeployment Guide

Architecture

Architecture OverviewExplanation: AI Integration & Tenant SecurityExplanation: Dynamic Forms Engine DesignExplanation: Compliance Ledger DesignExplanation: Live Sync & Data FreshnessData FlowArchitecture Decision Records

Core Domain

Core DomainDatabase ReferenceLocations DomainAuth & RBACScheduling DomainReports DomainIncidents DomainUnified Operations InboxLive Sync Data FreshnessToast Sync PipelineNotifications DomainCoupons and Guest NPSAudit Log & Compliance ArchitectureDesign Audit FindingsAI Chat IntegrationAnalytics & Tips Integration

Frontend

Frontend ArchitectureFormsLoading SkeletonsComponentsPWA & Offline ShellScreenshots

API Reference

API Reference

Endpoints

POS Sales APIOptimization Data APISchedule Shifts APIEmployee Export APIReports APIIncidents APIAI Chat APIPush Notifications APIWebhooks APICron API

Contributing

ContributingCode Examples

Security

Security & Compliance

Release Notes

What's New

Reports Domain

Current technical overview of staff and manager report workflows

Overview

The reports domain records service-day staff reports and manager closeout reports. This page is an audience-facing overview; the staff report contract, manager report contract, accepted ADRs, and executable package schemas own the detailed behavior.

Current model

  • A staff member submits one report per service day and location. The report's primary daypart and combined goals are derived from the staff member's published Daily Line-Up assignments.
  • A manager report is also service-day scoped and is finalized through the manager publish workflow.
  • form_drafts is the canonical recovery store for in-progress report forms. Legacy server_reports.status = 'draft' rows are migration fallback data, not the current draft contract.
  • Staff compliance obligations are seeded and reconciled from published Daily Line-Up assignments, not from a report-local scheduler.
  • Final submission/publish commands, audit events, rate limits, and notification delivery are server-owned.

Ownership and references

  • ADR-0070 — Staff Service Day Accountability owns staff report grain and lineup-publish seeding.
  • ADR-0077 — Manager Report Service-Day Accountability owns manager report grain and closeout.
  • packages/reports owns report domain commands and shared schemas.
  • The current app surfaces are /reports/new, /reports/[id], /reports/manager, and /inbox; verify routes against the app tree before adding links.

Related

Shift Reports

Daily Line-Up

Workspace & Tasks

Scheduling Domain

Current technical architecture of read-only 7shifts scheduling and service-day planning

Incidents Domain

Technical lifecycle, ownership, and audit trail of operational incidents

On this page

OverviewCurrent modelOwnership and referencesRelated