IETEL OS · Pass 5 vertical slice 4
Sales-to-Operations Handoff — IET-ASMT-2026-001
What Operations needs to plan and execute this project without re-contacting the customer or re-asking Sales — consuming the Approved Estimate Revision and Authorization without re-entering either.
Prototype UI — the handoff note and contact note are editable for demonstration only; nothing here is saved. Reloading the page resets it to the sample data.
Handoff Readiness
Composed from upstream facts — not a field anyone fills in directly.
DerivedREADY- Estimate Revision approved
- ✓
- Customer approved the Proposal
- ✓
- Contract authorization satisfied
- ✓
- Solution Design ready
- ✓
- Acceptance Criteria exist
- ✓
- Responsibilities identified
- ✓
Customer Need
InheritedWarehouse and main entrance currently use shared brass keys — no record of who entered or when, and a lost key means rekeying the whole building.
Proposed Solution
InheritedCloud-managed access control platform replacing shared brass keys at both openings. Credentials issued and revoked centrally; every event logged with identity and timestamp.
Scope / System Categories
Access Control, Network Infrastructure
Included Work
- Cloud-based access control panel (1, supports up to 8 doors)
- Electrified exit device conversion kit (2 openings)
- PoE network switch upgrade (1, 8-port)
Acceptance Criteria
The full approved set — not filtered to customer-visible only, unlike the Proposal document. This is what Operations must prove, in full technical detail.
InheritedEvery credential use at the warehouse door and main entrance is logged with timestamp and user identity.
Criticality: transition-critical · Verification method: system-record
A revoked credential is denied access within 5 minutes of deactivation.
Criticality: safety-critical · Verification method: test-result
After-hours access attempts by non-approved credentials are denied and logged.
Criticality: transition-critical · Verification method: test-result
Customer Responsibilities
Inherited- Confirm employee roster source for credential issuance.
- Provide a static IP or DHCP reservation for the access control panel.
Third-Party Responsibilities
Inherited- Local fire marshal review for the warehouse door hardware change.
- Fire marshal sign-off required before finalizing warehouse door hardware.
Site access (from Assessment)
InheritedWarehouse dock accessible only during business hours; main entrance accessible anytime via the lobby.
Assumptions & Exclusions (operationally relevant)
Design assumptions/exclusions only — Estimate’s own commercial/pricing-validity language is not shown here; it affects the customer price, not what Operations delivers.
- Assumes the existing conduit pathway between the IT closet and main entrance is reusable.
- Excludes replacement of the legacy CCTV system — out of scope for this phase.
Risks
- Rekeying constraint at the warehouse door if fire code requires free egress hardware.
Unknowns
- Warehouse-side power panel location not yet confirmed.
- Available network port at the warehouse door not yet confirmed.
Documented Exceptions
The exception fact only — the Sales Director’s and General Manager’s internal approval reasoning stays in Estimate/Authorization and is not shown here.
- Customer accepted proceeding with warehouse power/network TBD, confirmed via email 2026-08-17.
Technical Baseline
The exact Solution Design state this Estimate Revision priced — frozen at approval time. Not the current mutable working Design.
Inherited- Design Snapshot 1
- IET-ASMT-2026-001-DESIGN-SNAP-1
- Design status at snapshot
- READY WITH DOCUMENTED EXCEPTIONS
- Proposed Solution
- Cloud-managed access control platform replacing shared brass keys at both openings. Credentials issued and revoked centrally; every event logged with identity and timestamp.
- System components
- 3
- Acceptance Criteria
- 3
Baseline Integrity
Is the approved technical, commercial, and authorization chain internally consistent?
DerivedCONSISTENT- Estimate Revision references an Approved Design Snapshot
- ✓
- Proposal response references this Estimate Revision
- ✓
- Authorization references this Estimate Revision
- ✓
- Acceptance Criteria belong to the Design Snapshot
- ✓
Commercial & Authorization
What Sales committed to and what authorizes IETEL to proceed — the approved commercial baseline, never the mutable working Estimate.
- Approved Estimate Revision
- Revision 1 — IET-ASMT-2026-001-EST-REV-1
- Proposal response
- Approved by customer
- Authorization status
- Authorized to proceed
- Mechanism
- Signed contract
- Signature authority confirmed
- ✓
- Deposit invoice issued
- ✓
Deposit AMOUNT/percentage policy: NOT CONFIGURED / FUTURE POLICY — no such rule exists in the repository yet. Only the fact of invoice issuance is tracked.
Project Manager Budget View
Approved internal delivery cost — not the customer’s selling price, and not margin. Selling price and gross margin stay Sales Director / Estimator / General Manager visibility.
Purchasing/financial approval thresholds are a separate authority concept, not yet defined (roles.ts, Project Manager responsibilities) — no numeric PM spending limit is shown because none exists in the repository.
Handoff Context
Genuinely new information Operations needs — everything else on this page is inherited, not re-typed here.
Operational Acknowledgement
Internal confirmation that Operations has reviewed this package — not Customer Acceptance, which happens much later, after delivery.
Project Creation Preview
What the resulting Project record inherits at creation — fetched live from the authenticated API once the Handoff is complete, not re-entered.
- Project reference
- IET-ASMT-2026-001
- Customer
- Example Manufacturing LLC (sample)
- Site
- Boise, Idaho
- Project type
- Large / Multi-Site Access Control Project
- Design status
- READY WITH DOCUMENTED EXCEPTIONS
- Approved Estimate Revision
- 1
- Authorization
- Signed contract
- Acceptance Criteria
- 3
- Approved internal budget
- $4,642.00
- Customer responsibilities
- 2
- Third-party responsibilities
- 2
- Documented exceptions
- 1
- Lifecycle template
- Large / Multi-Site Access Control Project
- Initial operational owner
- Project Manager
The fields above are computed from upstream data for preview purposes; the real, authoritative Project — including its actual id — comes from the Operational Acknowledgement above, fetched live from the authenticated API.