Tools & Template Index (Cross-Deck)

Tools & Template Index — quick landing

This is a curated index of field-ready templates, calculators, and checklists your team can use immediately. Each item includes a short note on when to use it and a recommended primary owner (deck) so managers can get the right tool quickly without hunting across decks.

Core templates & when to use them

• Recipe Costing Calculator — Use to calculate ingredient cost, food cost % and plate cost for any menu item. Primary deck: Finance & Costing.
• Menu Engineering Matrix — Compare item profitability and popularity to decide which dishes to promote, reprice, or remove. Primary deck: Finance & Menu.
• Daily Sales & Labor Summary — Quick daily snapshot to compare sales, labor hours and labor% against target. Primary deck: Ops Dashboard.
• Inventory Count Sheet (Par & Cycle) — Standard sheet for daily/weekly counts and variance tracking. Primary deck: Inventory & Receiving.
• Receiving & FIFO Checklist — Step-by-step receiving checks to reduce spoilage and ensure proper rotation. Primary deck: Receiving & Storage.
• Waste Log — Simple form to record food waste reasons, quantities and immediate corrective actions. Primary deck: Waste Reduction.
• Portion Control & Prep Sheet — Standard portions and prep yields to protect consistency. Primary deck: Kitchen Standards.
• Opening & Closing Checklist — Shift-level checklist to ensure consistent shift starts and finishes. Primary deck: Operations.
• Ticket Time & Throughput Tracker — Track order times, bottlenecks and average ticket throughput. Primary deck: Kitchen Performance.
• Staff Schedule Template — Template for building weekly schedules with expected covers and skill requirements. Primary deck: Labor & Scheduling.
• Demand Forecast Template — Simple forecast by day/meal period to support ordering and scheduling. Primary deck: Forecasting & Planning.
• HACCP Plan Template — Core HACCP flow, CCPs and monitoring procedures to adapt to your menu. Primary deck: Food Safety & HACCP.
• Temperature Log — Cold/hot holding and daily equipment temperature checks. Primary deck: Food Safety.
• Preventive Maintenance (PM) Schedule — Recurring equipment maintenance checklist and schedule. Primary deck: Maintenance.
• Onboarding Checklist — New-hire onboarding tasks, required training and early milestones. Primary deck: HR & Training.
• Training Matrix — Skill/role matrix to track who can do what and training status. Primary deck: HR & Training.
• SOP / Recipe Card Template — Standardized recipe card showing ingredients, yields, steps and quality checks. Primary deck: Kitchen Standards.
• Supplier Scorecard — Simple performance scoring for vendors (on-time, quality, fill rate). Primary deck: Purchasing & Suppliers.
• Purchase Order Template — Standard PO fields to ensure clear ordering and traceability. Primary deck: Purchasing.
• Guest Complaint & Incident Report — Capture complaint details, root causes and corrective actions. Primary deck: Guest Experience.
• Catering / Event Worksheet — Estimate costs, staffing, equipment and timelines for events. Primary deck: Catering & Sales.

How to choose the right template

• If the goal is a one-time decision or calculation (e.g., costing a new dish), start with the Recipe Costing Calculator.
• For recurring operational control (receiving, temps, PM), pick the checklist that fits the daily rhythm and make it part of shift standard work.
• When you need consistent employee behavior across shifts or locations, use SOP/Recipe Cards plus a Training Matrix to track competence.
• When multiple teams need the same tool, assign a primary deck owner and nominate a local steward to adapt and keep the template current.

Which templates benefit most from being converted into Interactive Forms

Turning a static template into an interactive form is a practical step when you want reliable, auditable data, easier reporting, or to feed dashboards and analytics. Below are high-value candidates with suggested field schemas you can copy as a starting point.

1. Temperature Log (Food Safety)

• Why convert: Enforce required fields, timestamp entries, and collect historical data for audits and trends.
• Suggested field keys & types: date (date), time (time), location (select), equipment_id (text/select), temp_c_or_f (number), target_range (text), measured_by (text), photo (text/file reference), corrective_action (textarea), verified_by (text), submission_note (textarea).
• Suggested DataType: temperature_log, SchemaVersion: 1

2. Waste Log (Waste Reduction)

• Why convert: Capture consistent reasons and quantities so you can find patterns and test corrective actions.
• Suggested field keys & types: date (date), shift (select), location (select), item_or_category (text/select), waste_reason (select with options e.g., overproduction, spoilage, prep error, plate return), quantity (number + unit select), cost_estimate (number), immediate_corrective_action (textarea), reported_by (text), photo (text/file), follow_up_owner (text), follow_up_due (date).
• Suggested DataType: waste_log, SchemaVersion: 1

3. Inventory Count (Par & Cycle)

• Why convert: Reduce counting errors, keep historical counts, and automate variance calculation against expected par.
• Suggested field keys & types: date (date), location (select), counted_by (text), item_sku (text/select), expected_qty (number), counted_qty (number), variance (calculated), variance_reason (select/textarea), photo (text/file).
• Suggested DataType: inventory_count, SchemaVersion: 1

4. Daily Sales & Labor Summary

• Why convert: Standardize daily reporting, validate labor% calculations, and feed performance dashboards.
• Suggested field keys & types: date (date), location (select), total_sales (number), covers (number), labor_hours (number), payroll_cost (number), labor_percent (calculated), manager_notes (textarea).
• Suggested DataType: daily_sales_labor, SchemaVersion: 1

5. Receiving & FIFO Checklist

• Why convert: Ensure consistent receiving checks, capture supplier exceptions, and enable audit trails.
• Suggested field keys & types: date, po_number (text), supplier (select), items_checked (textarea or repeated group), temp_at_delivery (number), condition_ok (yesno), discrepancy_details (textarea), received_by (text), photo (file).
• Suggested DataType: receiving_checklist, SchemaVersion: 1

6. Preventive Maintenance (PM) Schedule

• Why convert: Track completed maintenance, capture notes and next due dates, and prevent missed service tasks.
• Suggested field keys & types: date, equipment_id (select), maintenance_task (text/select), performed_by (text), time_spent_minutes (number), parts_used (textarea), next_due_date (date), status (select: completed/blocked/deferred), notes (textarea).
• Suggested DataType: pm_entry, SchemaVersion: 1

7. Guest Complaint & Incident Report

• Why convert: Make complaint handling reliable, ensure follow-up, and analyze root causes across locations.
• Suggested field keys & types: date_time, location, guest_name (optional), contact_info (optional), complaint_category (select), description (textarea), immediate_action (textarea), corrective_owner (text), corrective_due (date), status (select), resolution_notes (textarea), manager_signoff (text).
• Suggested DataType: guest_incident, SchemaVersion: 1

Interactive form design checklist

• Keep field keys stable and descriptive (e.g., "measured_by", "item_sku") so integrations and analytics can rely on them.
• Use selects or radio buttons for common categories (waste reason, location, shift) to avoid free-text noise.
• Include required-field validation for critical controls (temperatures, corrective actions) to reduce missing data.
• Allow optional photo attachments for evidence where helpful (receiving damage, waste pile, equipment issue).
• Include an explicit owner and due date fields when follow-up action is expected.
• Design for quick mobile entry — keep required fields short and easy to select on a phone.

Customize, own, and deploy

1. Copy the template into your team deck before editing so you keep the original canonical version.
2. Edit only the fields that reflect local choices (par levels, suppliers, menu names), and keep required fields and definitions unchanged where compliance or comparability matter.
3. Assign a single owner for each template (deck steward) who is responsible for version notes and periodic review.
4. Train staff on any changes and embed the template in shift routines — a template is only useful when people use it consistently.

When to make a template interactive (forms & logs)

Turning a checklist or log into an interactive form is valuable when you want to:

• Capture structured data for reporting (temperature logs, waste logs, inventory counts).
• Enforce required fields and reduce missing or ambiguous entries.
• Store historical submissions for trend analysis, audits, or incident follow-up.

Keep static HTML templates for items used as reference or printable checklists (SOP cards, recipe cards) unless you need the benefits above.

Suggested tags and search terms

Use consistent tags when you copy or save templates so others can find them quickly: cost, inventory, receiving, HACCP, HACCP-plan, PM, onboarding, schedule, forecast, waste, SOP, recipe, training, maintenance, purchasing, catering.

Suggested collections & owners (toolkits you can publish or license)

Organize templates into add-on toolkits that teams can subscribe to or copy into their site:

• Food Safety Starter Toolkit — Temperature Log, HACCP Plan Template, Receiving Checklist, Temperature Escalation Procedure. Owner: Food Safety & HACCP.
• Inventory & Waste Reduction Pack — Inventory Count Sheet, Waste Log, Par Level Guide, Supplier Scorecard. Owner: Inventory & Purchasing.
• Operations Shift Kit — Opening & Closing Checklist, Daily Sales & Labor Summary, Ticket Time Tracker, SOP / Recipe Card Template. Owner: Operations.
• Maintenance & Reliability Bundle — PM Schedule, Equipment Register template, Break/Fix Report. Owner: Maintenance.

These collections map well to the platform's Adaptive Ownable Domains approach so sites can acquire, adapt, and operate them independently while retaining the ability to receive updates from the central steward.

Quick actions

• Need a local variant? Copy the template to your deck, rename it with your location code, and update par levels or supplier names.
• Want automated reporting? Convert the template into an interactive form so submissions are stored and can feed dashboards.
• Missing a template you need? Request a new one from the domain steward and describe the use case, fields required, and who will own it.

Implementation checklist (fast path from template to live form)

1. Decide if the template is primarily reference (keep HTML) or data-driven (convert to InteractiveForm).
2. Copy canonical template into your deck and add local identifiers (location code, version).
3. Design an InteractiveForm schema: stable field keys, labels, help text, validation rules, and select options.
4. Assign owner & steward, set review cadence, and name tags for discoverability.
5. Publish the form and train staff with a one-page quick guide and a short demo shift.
6. Start collecting submissions. Use the platform's data submission capability (POST /content/{contentItemId}/submit) to store structured entries for analytics and audits.
7. After 30–90 days, review submissions for quality, update selects and validations, and create simple dashboard widgets or weekly reports from collected data.

Next steps & governance

Use this index as a living landing page. If your organization acquires or tailors this collection, nominate a deck steward for each major category (Operations, Food Safety, Finance, HR, Maintenance, Purchasing). Periodically review common templates for accuracy and to reflect process improvements.