Document 01 · Scope expansion
Summerfield sent an updated requirements brief. It asks for more than our first proposal covered — extra modules, integrations, and operational detail. That is the main reason the project scope and budget went up. This note walks through what was already in the first proposal versus what the brief added. For the full build plan and pricing, see Document 02 · Project Scope.
| Area | Brief asks for | First proposal |
|---|---|---|
| Toast POS integration | Required — pull sales, push menu | In scope F1.4 |
| 5 → 50 stores | Architecture must scale | In scope F2.19, A1, A3 |
| 5-month timeline | ~5 months kickoff to deployable | In scope 20-week Gantt |
| Phased sprints | Working software each sprint | In scope 2-week sprints |
| Recipe & BOM | Central recipe DB + BOM | In scope F2.2, F2.3 |
| Dashboard | Consolidated HQ dashboard | In scope F2.1 |
| RBAC | Designed before build starts | In scope F1.3 |
| Audit log | All privileged actions logged | In scope F2.12 |
| Approval workflow | Franchisee submissions | In scope F1.6 |
| Recipe versioning | History + effective dates | In scope F2.2 |
The brief names six systems. The first proposal only scoped Toast:
| System | Brief | First proposal |
|---|---|---|
| Toast POS | Required — sales, menu, inventory deduction from BOM | In scope |
| Square Payroll | Required — labor hours; no manual re-entry | Not included |
| QuickBooks | Read-only — financial metrics on the dashboard | Not included |
| Sysco / LA Food | PO by email/PDF at minimum | Missing — receipt upload only |
| DoorDash | No direct integration — via Curate | Not stated |
| Curate | No direct integration | Not stated |
Most of the operational inventory work was not in the original scope:
The brief describes 12 LMS capabilities. The first proposal only had a course list and read-only video playback in F3.4, with everything else deferred:
"Without a real LMS in place before franchisees open, we have no defensible record... and legal exposure if an employee or franchisee later claims they were not trained."
The first proposal mentioned basic daily open/close checklists in F3.4. The brief asks for eight distinct capabilities:
| Topic | Brief | First proposal |
|---|---|---|
| Roles | Five — HQ Admin, HQ Ops, Store Manager, Franchisee, Staff | Three roles in F1.3 |
| MFA | Required for HQ Admin and HQ Ops | Missing |
| SSO | Google or Microsoft when ready | Mentioned in assumptions only |
| Deactivate, don’t delete | Keep training and audit history | Missing |
| RBAC matrix | Documented before development | Missing |
| Audit before/after values | Required | Partial — format not defined |