# Key-Person Risk and Knowledge Lock-Down Kit This kit helps a small business find the people whose departure would hurt most, get what only they know onto paper, tighten access, and respond fast when someone with admin or security duties leaves quietly. It's built to be printed and filled in by hand or in any text editor, with no software and no cost. It's informational only and isn't legal advice: have an employment attorney in your state check any agreement before you rely on it. ## Checklist - [ ] List the 5 to 10 people whose departure would hurt most. - [ ] For each person, write what only they know: pricing rules, customer relationships, passwords, vendor terms, process steps. - [ ] Estimate replacement time and cost for each person (use the worksheet below). - [ ] Pick the first document to write for each person and schedule two hours to write it. - [ ] Move every shared credential into a shared password manager with at least two named admins. - [ ] Set a quarterly date to rotate shared secrets and review who has access. - [ ] Book a review of your confidentiality, invention-assignment and non-solicitation agreements with an employment attorney. - [ ] Check your state's rules on non-competes before relying on one. - [ ] Adopt the 48-hour response plan for any quiet departure of a security, IT or finance lead. - [ ] List every developer tool, AI assistant, browser extension and API key, and remove what's unused. - [ ] Write a one-page disclosure rule for owners and senior staff, with a confidential way to raise concerns. - [ ] Practise the confirmed-versus-claimed note on the next alarming headline before changing any vendor or hiring decision. ## Worksheet 1: Key-person inventory Copy one row per person. | Person | What only they know | What breaks if they leave | Months to replace | Estimated cost of the gap | First document to write | Date done | |---|---|---|---|---|---|---| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | How to estimate the cost of the gap: take the annual revenue that depends on this person, multiply by the accuracy or speed loss you expect, and scale by the months to replace. Example: $2,400,000 of quoted work x 8% accuracy loss = $192,000 a year at risk. Compare that with the cost of capturing the knowledge now. ## Worksheet 2: Knowledge-capture template (one per person, about 2 hours) - Role and who they report to: - Recurring tasks (what, how often, how long): - Decision rules (when X happens, do Y, and why): - Where the files, spreadsheets and records live: - Where credentials are stored (name the location, never write the password here): - Vendor and customer contacts, and what each one needs: - Known pitfalls and past mistakes: - Who else could cover this, and what they would need to learn: - Reviewed by (second person) and date: ## Worksheet 3: Credentials and access register Rule: every critical system has two named admins. Rotate shared secrets every quarter. | System | Owner | Second admin | Where the secret is stored | Last rotated | Next rotation | |---|---|---|---|---|---| | Domain registrar | | | | | | | DNS and hosting | | | | | | | Backups | | | | | | | Code host | | | | | | | Package registry | | | | | | | AI coding assistant | | | | | | | Cloud console | | | | | | | Payroll and banking | | | | | | ## Worksheet 4: Quiet-departure 48-hour response Use this when a person with admin, security, IT or finance duties leaves, especially if it happens without announcement. Hour 0 to 4: - [ ] Disable their accounts and remove them from shared channels and mailing lists. - [ ] Rotate every shared secret they could see. - [ ] Confirm who now owns each account they managed. Hour 4 to 24: - [ ] Review access logs for the past 30 days for unusual logins, downloads or permission changes. - [ ] Recover company devices and revoke tokens, SSH keys and API keys tied to them. - [ ] Notify vendors and clients who deal with them, using a short factual message. Hour 24 to 48: - [ ] Re-run the credentials register and fix any single-owner entries. - [ ] Remind the team of the confidentiality terms they signed. - [ ] Write down what you learned and which document should have existed. Sign-off line for each step: name and time. ## Worksheet 5: Questions for your employment attorney Bring your current agreements and ask: - Does my confidentiality agreement cover customer lists, pricing and process know-how by name? - Does my invention-assignment clause cover work done on personal devices and outside hours? - What does my state allow for non-competes and non-solicitation, and what is realistic to enforce? - Is a retention bonus with a clawback a better tool than a non-compete here? - What must I give employees (pay, notice, new consideration) when they sign a new agreement? - What should the exit interview and return-of-property process look like? - What do I need in place for contractors, who are often not covered by employee agreements? ## Worksheet 6: Disclosure and conflict-of-interest one-pager Owners and senior staff tell [name or role] in writing within 14 days about: - Financial interests in vendors, competitors or customers. - Close personal or family relationships with vendor, competitor or customer staff. - Side work or advisory roles. - Gifts above $[amount]. - Relationships with foreign counterparties that could create a conflict. Concerns can be raised confidentially with [name, phone, email]. Raising a concern in good faith is never held against anyone. Reviewed each year on [date]. ## Templates and prompts Template: confirmed-versus-claimed note for a breaking headline ```text Headline and date: What is CONFIRMED (named document, filing, official statement, two independent outlets): What is CLAIMED (single source, anonymous, or the party's own statement): What is INFERENCE (my own or the writer's reading): What would change my mind (a named asset, a filing, a second source): Does this change a decision I have to make this week? (yes / no, and why): ``` Template: single-owner account alert message to your team ```text Subject: Access cleanup, due [date] We are making sure no system depends on one person. Please reply with: 1. The accounts and tools you alone can log in to. 2. Where the recovery information is stored. 3. Who you suggest as second admin. This is about continuity, not suspicion. Thank you. ``` Prompt 1: key-person risk interview ```text I run a [type of business] with [number] employees. Interview me with 15 questions to identify which people hold knowledge only they have (pricing, customers, systems access, vendor terms). Then produce a key-person risk table with columns: person, what only they know, what breaks if they leave, how long to replace, and the first document I should write. Base it only on my answers. If my answers are too vague to fill a cell, write "unknown, ask me" instead of guessing. ``` Prompt 2: knowledge-capture template ```text Draft a one-page knowledge-capture template for an employee to document their role: recurring tasks, decision rules, credentials location (not the passwords themselves), vendor contacts and known pitfalls. Make it simple enough to finish in 2 hours. Keep it for my business: [describe]. Work from the job description and process notes I paste below, and flag any section where you had to assume something. [paste job description or process notes] ``` Prompt 3: attorney meeting checklist ```text I want to review my employee agreements for confidentiality and invention assignment. Here is the text of my current agreement: [paste]. List the clauses a small business typically needs, which ones my agreement has or lacks, what each does in plain English, and the questions I should bring to an employment attorney in [my state]. Do not give legal advice; give me a checklist for the meeting. Say clearly where state rules on non-competes or assignment may differ and you are unsure. ``` Prompt 4: 48-hour offboarding checklist ```text Create a 48-hour offboarding checklist for when a person with admin or security responsibility leaves: accounts to disable, secrets to rotate, logs to review, vendors to notify, and who signs off on each step. My stack includes: [list tools]. Use only the tools I listed, and mark any step where the right action depends on a setting I haven't told you about. ``` Prompt 5: developer and AI tool access audit ```text Help me audit my developer and AI tool access. Given this list of tools and extensions [paste list], produce a table of owner, permission level, last rotated, and a keep/remove/rotate recommendation, and suggest a quarterly review routine. Where my list doesn't say who owns something or when it was last rotated, mark it "unknown" instead of assuming. ``` ## Sources - https://apprised.news/desk/tech/2026-11-15 - https://apprised.news/desk/tech/2026-11-16 - https://techcrunch.com/2026/11/14/where-was-nvidias-security-team/ - https://decrypt.co/383280/the-week-jensen-huang-fell-how-spy-scandal-toppled-nvidia-ceo - https://arynews.tv/ex-nvidia-ceo-misled-top-lawyer-on-affair-with-chinese-businesswoman - https://www.myjoyonline.com/suspected-china-spy-linked-to-nvidias-ex-boss-left-in-2025-megaspeed-says/ - https://www.bleepingcomputer.com/news/security/cursor-confirms-security-breach-led-to-malicious-claude-code-extension/ - https://www.bleepingcomputer.com/news/security/fbi-warns-artex-ai-hacking-tool-is-powering-global-cyberattacks/