Business Operations

Canon status: NOT CANON Partner-use status: NOT CONFIGURED Release status: NOT RELEASED MASTER Supports: 07-01 · Both models · Up to four designated attendees

Configuration

Partner: {{PUBLIC_BRAND_NAME}} Model: {{MODEL}} Partner project owner: {{PARTNER_PROJECT_OWNER}} Atlas training owner: {{ATLAS_PROJECT_OWNER}} Signed scope: {{SIGNED_SCOPE_VERSION}} Target launch window: {{TARGET_LAUNCH_WINDOW}}

Training boundary

Training covers use of the delivered Atlas-configured business systems. It is not clinical, professional, legal, regulatory, employment, licensure, compliance, or continuing-education training and does not certify employee performance.

Designated roles

One person may hold multiple roles, but every critical task needs a named primary. If no backup exists, record a named escalation/continuity route, risk, mitigation owner, and activation consequence; do not invent staff. More than four attendees or additional training is change-controlled.

Up to four training attendees does not imply four CRM user licenses. The standard CRM configuration includes up to three users; a fourth attendee may train without CRM access unless an additional user is separately authorized and change-controlled.

Nonproduction test-chain preflight

All integrated exercises use one traceable nonproduction test chain. Before an integrated task starts, record the following without storing secrets or using live customer data:

• Current rendered build/version and test entry route: TBD (gated)
• Isolated CRM test workspace/account and exact entry/routing mapping: TBD (gated)
• Partner-controlled test inbox/destination and, if in scope, test phone: TBD (gated)
• Booking test route, {{TIME_ZONE}}, and test calendar owner when booking is in scope: TBD (gated) / N/A
• Test-send authorization, canonical fictional TEST-record ID, evidence location, and test-record cleanup owner/date: TBD (gated)
• Rollback/hold route, fallback state, and authorized owner for each activated test target: TBD (gated)

Missing preflight information blocks only the affected exercise or route. A safe-hold exercise may prove that an excluded or gated route remains unavailable; it never proves that the underlying workflow is active.

Standard training sequence

Scheduling and prerequisite controls

• One included reschedule per live session when the required advance notice is satisfied; exact notice terms come from the signed schedule.
• Missing access pauses the affected task, not unrelated training.
• Use fictional TEST records only; do not expose live customer data or secrets in recordings/evidence.
• Training material follows the accepted configuration. Material system changes trigger guide/task review.
• Attendance or module completion alone is not readiness evidence; assigned critical tasks must pass objectively before the related role is marked ready.
• A route excluded by signed scope may be N/A only with the cited scope reason. A route that remains in scope but lacks a prerequisite is BLOCKED. A safe-hold test may pass only for the hold boundary itself and does not clear the underlying workflow or activation target.

Acceptance test

• [ ] Up to four attendees map to every required role and task.
• [ ] Each attendee has the minimum access needed and no unnecessary access.
• [ ] Required modules and live sessions are scheduled.
• [ ] Every critical role has a primary plus either a backup or a documented escalation/continuity route, risk, mitigation owner, and activation consequence.
• [ ] Task evidence location and evaluator are named.
• [ ] One nonproduction test-chain preflight records source build, routes, test destinations, {{TIME_ZONE}} where booking is in scope, evidence, cleanup, and rollback/hold status.
• [ ] Unresolved prerequisites have an owner, consequence, and next action.

Result: PASS / CONDITIONAL / FAIL Owner/date: TBD (gated)

Canon status: NOT CANON Partner-use status: NOT CONFIGURED Release status: NOT RELEASED MASTER Supports: 07-02 · Recorded module 3 of 5

Outcome

The designated partner user can manage the delivered inquiry, pipeline, booking, confirmation/follow-up, consent/suppression, and basic admin workflow using fictional test records.

Required configuration

CRM: {{CRM_PLATFORM}} Partner administrator: {{PARTNER_PROJECT_OWNER}} Customer-response owner: {{CUSTOMER_SUPPORT_OWNER}} Approved sender/contact: {{APPROVED_CONTACT_EMAIL}} Booking destination: {{BOOKING_URL}} Booking time zone: {{TIME_ZONE}} (required whenever booking is in scope)

Training environment/build: TBD (gated) Controlled fictional TEST recipient email: TBD (partner-controlled) Controlled fictional TEST recipient phone, only if an approved phone workflow is in scope: TBD / N/A Test-send authorization owner/date: TBD Test-record cleanup owner/date: TBD

Only fictional TEST records and partner-controlled test destinations may receive training messages. Never use a customer/prospect record or route a customer message to Atlas.

Lesson sequence

1. Account ownership, users, least privilege, MFA, recovery, and no-secret documentation.
2. Business-only field dictionary and handling unexpected sensitive information.
3. Core pipeline stages, record owner, source, tasks, and dispositions.
4. Booking, reschedule, cancellation, and no-show paths.
5. Confirmation and two follow-ups: trigger, exact approved copy, reply ownership, unsubscribe/suppression.
6. Troubleshooting, export/admin handoff, and vendor/platform boundaries.

Objective task check

Completion rule

The assigned user passes the tasks relevant to their role. Training does not include indefinite CRM administration, list acquisition, cold outreach, SMS, deliverability guarantees, or additional workflows.

Canon status: NOT CANON Partner-use status: NOT CONFIGURED Release status: NOT RELEASED MASTER Supports: 07-02 · Recorded module 4 of 5

Outcome

The designated user can find the accountable owner and correct SOP for a routine request, system failure, privacy/data issue, vendor exception, or gated product/professional matter without assigning customer communication or judgment to Atlas.

Required source materials

Configured OPS-01 responsibility map; OPS-02 journey/escalation map; OPS-03/04 vendor and account records; selected OPS-05 SOPs; applicable OPS-06/07 addendum; OPS-08 continuity/offboarding record.

Lesson sequence

1. One accountable owner, partner customer-communication ownership, and Atlas configuration/support boundary.
2. Normal inquiry, booking, onboarding, support, and closure routes.
3. Vendor/platform, payment, access, privacy/data, and incident exceptions.
4. Product, supplier, professional, safety, fulfillment, and geography gates.
5. Case records, escalation evidence, next-update ownership, and closure.
6. Continuity, fallback, export, access removal, and offboarding.

Scenario task check

Completion rule

All applicable scenarios reach an existing owner, record, SOP, and boundary without improvisation. A gated scenario passes when it blocks safely and visibly.

Canon status: NOT CANON Partner-use status: NOT CONFIGURED Release status: NOT RELEASED MASTER Supports: 07-02 · Recorded module 5 of 5

Outcome

The partner decision-maker and administrator can read Ready/Conditional/Blocked status, authorize or hold Atlas-controlled activation, use rollback and issue routes, verify handoff, and distinguish stabilization support from new work.

Lesson sequence

1. Readiness status and why an external blocker prevents operational readiness even when the related Atlas-controlled deliverable is complete.
2. Activation sequence, preconditions, owners, rollback/disable path, and Go/No-Go authority.
3. Preactivation check evidence and the configured HO-02 activation-test plan: website → CRM → booking → email plus negative tests.
4. Draft handoff manifest: planned ownership, access, files, sources, licenses, renewals, exports, and recovery.
5. Acceptance: valid deficiency versus new preference, changed fact, added feature, or third-party issue.
6. Thirty-day stabilization: named email, included corrections/how-to, two reviews, exclusions, and closeout.
7. Access removal, data/export limitations, continuity, and change control.

Objective task check

Completion rule

The final readiness report records incomplete tasks and external gates. Module completion does not itself authorize activation; the named partner decision-maker records the Go/No-Go decision.

Canon status: NOT CANON Partner-use status: NOT CONFIGURED Release status: NOT RELEASED MASTER Supports: 07-05 · One decision session up to 60 minutes

Meeting boundary

This is a readiness decision meeting, not another general training session. TR-11 should be substantially prefilled. Reaching minute 60 does not clear a blocker or authorize activation.

Facilitator: Atlas Delivery Trainer — TBD Partner decision-maker: {{DECISION_MAKER}} Atlas owner: {{ATLAS_PROJECT_OWNER}} Meeting date/link: TBD (gated)

Timed agenda

Status rules

• READY: Atlas-controlled critical tasks/tests pass and no activation-blocking dependency remains.
• CONDITIONAL: named limits allow only the recorded partial/held activation; owner, consequence, and next action are explicit.
• BLOCKED: a critical task, test, approval, account, route, or dependency prevents responsible activation.

A READY result recommends progression into controlled activation. It does not authorize activation or prove that activation succeeded. HO-01 is the sole activation authority; HO-02 must pass during the coordinated cycle or the affected target is held/rolled back.

Meeting record

Atlas delivery status: ACCEPTED / CONDITIONAL / BLOCKED Operational activation status: READY / CONDITIONAL / BLOCKED Readiness recommendation: PROCEED TO ACTIVATION CONTROL / PROCEED WITH LIMITS / HOLD Decision-maker/date: TBD Open items/owners: TBD

Canon status: NOT CANON Partner-use status: NOT CONFIGURED Release status: NOT RELEASED MASTER Supports: 07-06

Project record

Partner/model: {{PUBLIC_BRAND_NAME}} / {{MODEL}} Scope/build version: {{SIGNED_SCOPE_VERSION}} / TBD Atlas owner: {{ATLAS_PROJECT_OWNER}} Partner decision-maker: {{DECISION_MAKER}} Training dates/attendees: TBD

Two-status decision

Atlas Delivery Status: ACCEPTED / CONDITIONAL / BLOCKED Operational Activation Status: READY / CONDITIONAL / BLOCKED

Atlas delivery completion and external operating readiness are not the same decision.

Deterministic status rules

• READY requires all applicable critical TR-10 tasks and preactivation functional checks to pass with no activation-blocking dependency.
• CONDITIONAL requires an explicit limit, owner, consequence, next action, and held/allowed item list.
• BLOCKED applies when a critical task/test, route, approval, account, or external dependency prevents responsible activation.
• Atlas Delivery Status records only included Atlas-controlled deliverables against the signed scope.

Atlas Delivery Status rules:

• ACCEPTED: every applicable signed-scope line required at this checkpoint passes its acceptance criterion.
• CONDITIONAL: only an explicitly limited noncritical deficiency/external condition remains, with cure owner/date and held items recorded.
• BLOCKED: a critical signed-scope deficiency prevents readiness progression. DEFICIENCY is a linked issue type, not a fourth delivery status.

READY means ready to enter the controlled activation cycle: HO-01 draft plan → HO-02 pre-activation test → HO-01 controlled authorization → activation → HO-02 smoke/rollback verification → HO-01 final target disposition. It is not evidence that activation has already succeeded; a failed HO-02 test holds or rolls back the affected target and requires the readiness record to be updated.

Readiness summary

Nonproduction test-chain status

Source build/version, test entry/routing, CRM test workspace, partner-controlled test destination, booking route and {{TIME_ZONE}} when booking is in scope, evidence location, cleanup, and rollback/hold route: TBD (gated). A missing item holds only its affected route; it does not turn an excluded/gated workflow into an operating one.

External-dependency register

Task and functional-test result

TR-10 critical tasks passed/failed/blocked: TBD Preactivation integrated-check result: PASS / FAIL / NOT RUN Preactivation gate status: CLEAR / HELD / N/A HO-02 activation-test plan configured: YES / NO / BLOCKED Rollback/disable result: TBD Partner admin/recovery result: TBD Open defects/cure status: TBD

Authorized decision and acknowledgment

Readiness recommendation: PROCEED TO ACTIVATION CONTROL / PROCEED WITH LIMITS / HOLD Allowed activation items: TBD Held items and limits: TBD Planned handoff/support controls: TBD Remaining partner actions: TBD

The partner acknowledges that this report concerns the recorded Atlas-controlled scope and does not certify legal, clinical, regulatory, licensure, supplier, facility, product, market, employee-performance, or business-outcome readiness.

Partner decision-maker/date: TBD Atlas delivery owner/date: TBD