Recipe Platform Stakeholder Analysis

Stakeholders

Stakeholder Map

Stakeholder / Actor	Evidence-Based Role	Needs	Evidence Quality	Evidence
Recipe author / standard user	Creates recipes, views My Recipes, receives returned-to-submitter notes.	Simple authoring, duplicate handling, clear revision feedback, personal recipe scope.	Observed	src/services/mock_auth_service.py; src/services/workflow_service.py; tests/test_my_recipes.py
Reviewer	Reviews submitted/reviewed/analyzed items and controls go-live.	Workflow portal, status summaries, required reasons, advanced workflow visibility.	Observed	src/services/workflow_service.py; src/services/policy_service.py; route tests
Dietitian	Analyzes approved items before live release.	Nutrition authority fields and workflow handoff.	Observed	src/services/workflow_service.py; src/services/policy_service.py; tests/test_policy_service.py
Admin / super user	Broad workflow access and administrative override capability.	Complete workflow visibility and management controls.	Observed	src/config/roles.py; src/services/workflow_service.py
Menu planner	Builds dated menu cycles and assigns live items.	Efficient planning grid, copy/paste/clear workflows, print views.	Observed	src/services/menu_service.py; webpage/templates/menu_detail.html; tests
Production manager	Forecasts production and reviews production records/history.	Forecasting controls, production summaries, variance reporting, posted facts.	Observed	src/services/menu_forecast_service.py; src/services/production_record_service.py
Floor operator	Records actual production and end-service outcomes.	Simple quantity entry, reason/notes, printable production record.	Inferred	Production Record UI/services imply floor use; no direct stakeholder statement.
Inventory user	Counts locations, reviews usage and planning, links invoice lines, places items.	Fast dashboard, count pages, planning, catalog review, invoice review, substitute choices.	Observed	docs/agent_context/inventory.md; inventory services/templates/tests
Purchasing or vendor manager	Maintains vendor/category preferences and reviews vendor source data.	Vendor-specific item/source mapping, cutoff windows, catalog history.	Inferred	Ordering preferences and invoice/vendor tables imply role; no explicit role exists.
Finance/accounting	Future consumer of invoice, cost, receiving, and inventory period data.	Reliable accounting boundaries and cost facts.	Inferred	Docs explicitly defer accounting/finalization and note future costing bridge.
Analyst / analytics consumer	Future consumer of posted production facts, inventory, usage, purchasing, and cost contracts.	Stable versioned contracts and trustworthy historical data.	Observed/Inferred	README.md; posted facts service; Analytics route is deferred.
Vendor systems	Possible future source of API invoices/catalog data.	Import contracts and vendor item identity mapping.	Inferred	Schema supports vendor_api; docs list API/CSV/PDF/email sources.

Stakeholder Concerns

• Observed: Kitchen-facing users need responsive pages; heavy planning calculations are moved off /inventory to /inventory/planning.
• Observed: Inventory users should not be forced to review every Recipe Collection base food; catalog review is demand-driven.
• Observed: Production managers need operational memory from drafts and posted facts, but downstream consumers should rely on posted records.
• Inferred: Purchasing stakeholders need stronger item-level vendor resolution because category-level vendor preferences are too broad for split vendors.
• Inferred: Finance stakeholders will need clean separation between operational counts, invoice placement, receiving, and accounting periods.

BA Alignment

• Activity areas: Elicit and collaborate; plan and monitor analysis work.
• Techniques used: Stakeholder analysis, document analysis, role/permission analysis.