Affective TechnologiesIHNYC Service Docs

Closing reports

Active2 min read

Table of Contents

Closing staff already record refrigerator temperatures and stock observations at the end of a shift. The closing-report workflow turns that familiar message into structured, reviewable information without making the tender learn a second reporting tool.

What happens

flowchart LR
  TENDER["Tender sends the closing report"] --> CHECK["Service validates and interprets it"]
  CHECK --> RECORD["Reviewable closing record"]
  RECORD --> ALERT["Authorized follow-up when needed"]
  1. A tender sends the expected closing information through the staff channel.
  2. The service checks whether the report can be understood and separates temperature readings from stock notes.
  3. Authorized operators can review the resulting record and correct information that was interpreted incorrectly.
  4. A reading that needs attention is surfaced for human follow-up.

Automation supports the process; it does not replace food-safety judgment, equipment checks, or the venue’s required response procedure.

For closing staff

  • Use the usual reporting format and include all required readings.
  • If a refrigerator appears unsafe, follow the venue’s immediate escalation procedure; do not wait for the software.
  • Correct a mistaken message in the staff channel or notify the responsible operator.

For operators

  • Review reports that could not be interpreted confidently.
  • Confirm unusual readings against the physical equipment and operating procedure.
  • Record corrections through the protected workflow so the audit trail remains coherent.
  • Treat stock notes as operational observations, not an automatically reconciled inventory count.

Privacy and access

Closing records may contain staff attribution and operational details. They are limited to authorized Pub roles and are not part of the patron website. Public pages do not expose report messages, tender contact information, or follow-up history.

Technical boundary

The ingestion path is isolated from public publishing and accepts only the narrow closing-report format. The service preserves ambiguous submissions for authorized review instead of inventing missing values. Alerts and corrections are recorded as product activity, but the exact parsing rules, operational thresholds, and delivery configuration remain in private runbooks.

Related: Architecture · Admin access