Scope

What it is

Loop is an internal web app that lets managers send two kinds of messages to employees: process corrections (when someone deviates from an SOP) and process recognition (when someone follows a process well). Both are tied to a specific process, include a manager note, are delivered as a Slack DM, and are tracked through to acknowledgement so the team can see patterns like repeat issues, recognition frequency, and which processes are working versus failing.

The product is built around two core flows:

• Corrections: Process → Correction → Acknowledgement → Compliance
• Recognition: Process → Recognition → Reinforcement → Culture

Scope is deliberately tight: 7 screens, 3 database tables, 1 Slack integration, 1 AI API call, and voice input.

What it is not

Loop is intentionally narrow. It is:

• Not a training platform or LMS
• Not an HR or performance management system
• Not a Trainual plugin — process links are just URLs that can point at any SOP tool
• Not a reporting suite — v1 is operational, not analytical

Future

Two things to keep in mind when making v1 decisions, even though they are not in scope to build now:

• Multi-tenancy — don't hardcode a single team. Use org-level scoping where it's practical.
• API-first design — keep in mind if the frontend and backend are separated.

Not required for v1

The following are explicitly out of scope for the first release:

• User registration or self-service onboarding
• Email notifications
• Escalation rules or auto follow-ups
• Issue type categorisation
• Weekly digests
• Trainual API integration
• Native mobile app
• SSO or OAuth