Checking session…

IETEL OSInternal · Phase 1

Sign in required

This area is restricted to authenticated IETEL OS users.

IETEL OSInternal · Phase 1

Home
Organization
Project Lifecycle
Processes
SOPs
Standards
Forms & Documents
Assessments
Sample Project
Search
Administration
Sign In

Not deployedLocal build only — no auth, no real business data. See internal/README.md.

SOPs / Sales-to-Operations Handoff Procedure

ESPhase 1 · Read-only

SOPs

Sales-to-Operations Handoff Procedure

Make sure nothing the customer already told Sales has to be asked again by Operations.

Performed by

Project Manager

Used in processes

Sales-to-Operations Handoff

Preconditions

Contract signed.
Deposit invoice issued.

Procedure

1Sales Director schedules a handoff briefing with the Project Manager.
2Transfer the signed contract, proposal, customer requirements, and site survey notes.
3Project Manager reads and confirms understanding of the scope.
4Project Manager asks clarifying questions before the briefing ends, not after.

Decision / troubleshooting points

Is anything referenced in the contract missing from the handoff package? → Return to the Sales Director before starting Project Creation.

Required evidence

Handoff briefing completed flag
Scope confirmation from the Project Manager

Completion criteria

The Project Manager can state the full scope and any commitments made during sales without needing to re-contact the customer.

Escalation

When: Missing information blocks understanding the scope.

Involve: Sales Director

Future system assistance

Auto-attach every opportunity document to the new project record.
Checklist confirming each required document transferred.