PromptBase
Upgrade
Close icon
General
Home
Marketplace
Create
Hire
Login
Chat
Sell
Explore

Prompt Details

Model
Chat - (gpt-5.6)
Token size
451
Example input
[Departing Role and Operational Scope]: Principal Cloud Architect and Founding DevOps Engineer at a Series B fintech SaaS. Sole architect of the AWS multi-region infrastructure, Kubernetes deployment pipelines, and database replication topography for 4 years. [Critical Systems and Proprietary Knowledge]: Undocumented Terraform state drift handling, custom bash deployment scripts in legacy Jenkins, root AWS account credentials, Cloudflare edge firewall rules, and personal relationships with dedicated AWS enterprise support reps. [Successor Profile and Handover Timeline]: Two internal Senior Site Reliability Engineers dividing duties (one covering Kubernetes/CI-CD, one covering database/cloud security). Transition window: 10 business days before departure. [High-Risk Dependencies and Transition Challenges]: No written runbooks for quarterly database failover; manual TLS certificate renewals for three legacy subdomains; risk of single-point-of-failure if an outage occurs during subsequent quarterly compliance audits.
Example output
### 1. Critical Knowledge & Tacit Process Inventory Matrix | Knowledge Domain | Undocumented Workflow / Asset | Transition Recipient | Severity Rating | | :--- | :--- | :--- | :--- | | **Cloud Infrastructure** | Legacy Terraform state drift and manual AWS overrides | SRE Lead (Infra) | Critical | | **CI/CD Pipelines** | Custom Jenkins deployment automation bash scripts | SRE Lead (Apps) | High | | **Network & Security** | Manual Cloudflare edge rate-limiting rule sets | SRE Lead (Infra) | High | | **Vendor Escalations** | Direct contact channels for enterprise AWS support | VP of Engineering | Medium | --- ### 2. Phased Handover Execution Schedule * **Days 1 to 3 (Documentation & Architecture Audits):** Conduct recorded 90-minute screen-share walkthroughs covering VPC peering, IAM role structures, and the Jenkins deployment scripts. Publish raw architecture diagrams to internal wiki. * **Days 4 to 6 (Active Shadowing & Access Transfer):** Successors shadow the departing architect through live production deployments. Transition root administrator credentials to company-managed hardware security tokens. * **Days 7 to 9 (Reverse Shadowing):** Successors execute routine maintenance, staging deployments, and mock incident recoveries while the departing architect observes without intervening. * **Day 10 (Final Sign-Off):** VP of Engineering, departing engineer, and successors complete formal handover sign-off review. --- ### 3. System Access, Security & Credential Deprovisioning Audit * **Root Access Reassignment:** Transfer primary ownership of AWS Root, Cloudflare Enterprise, GitHub Organization, and Datadog accounts to the VP of Engineering. * **Secret Rotation:** Regenerate all personal access tokens (PATs), SSH bastion jump-box keys, and database administrative passwords immediately on the final day at 17:00. * **Hardware Asset Logistics:** Complete inventory check of company-issued laptop and YubiKey; execute remote MDM cryptographic wipe post-exit. --- ### 4. Emergency Reach-Back Protocol & Operational Contingency Runbook * **Reach-Back Scope:** Limited strictly to catastrophic production outages caused by pre-existing legacy architecture within 30 days post-exit. * **Engagement Channel:** Contact routed exclusively through VP of Engineering via designated personal email, paid at pre-agreed advisory consulting rates. * **Emergency Outage Fallback:** If undocumented systems fail, escalate directly to AWS Enterprise Support concierge using Account PIN 8841.
GPT

Keyperson Offboarding Handover Sop

Add to Cart
PromptBase Select
Get this prompt + 9 more with SelectFrom $14/mo · Cancel anytimeFrom $14/mo · Cancel anytime
View Select
Instant accessInstant access
Usage rightsCommercial use
Money-back guaranteeMoney‑back
By purchasing this prompt, you agree to our terms of service
GPT-5.6
Tested icon
Guide icon
4 examples icon
Free credits icon
Capture undocumented institutional knowledge, system dependencies, and administrative access before key personnel depart. Built for HR executives, department heads, and operations leaders looking to eliminate operational disruptions and prevent single-point-of-failure vulnerabilities. Generates tacit knowledge extraction matrices, handover schedules, and access revocation checklists.
...more
Added 2 weeks ago
Report
Browse Marketplace