SOP & Company Wiki

SOP & Company Wiki defines a Growth-stage Foundation setup for process documentation. Start with the process that causes the most rework. Write one concise page per process containing its owner, trigger and steps, and place it where the team already works. The recommended workflow runs from trigger through steps, owner and checklist to review after each run. The register captures category, department, description, ownership, version, priority and review dates. A version field records the label; it does not itself provide version-control behavior or distribute changes to readers.

The default deliverable is a short recommendation. An explicit setup, build or conversion request produces artifacts after essential missing facts are resolved. Advice receives a direct answer, while a review works from the material provided. This keeps the size of the proposed setup tied to the requested outcome.

Use it when process knowledge lives in one person’s head, new joiners receive inconsistent instructions or a shared SOP index is missing. It does not version-control edits or notify readers when a process changes. Publication into a live workspace requires an authorized operation rather than delivery of a static mapping.

This is an empty-template workflow, not processing of real employee or customer records. Automation, reminders and synchronization require the separate integration layer. Sensitive decisions and adjustments require qualified human review before anything is acted on.

Ask which processes need documentation, whether they are already written and how many are in scope; owners, operators and new-hire use; step-by-step detail versus checklists, tools and decision points; present practices and failures; and onboarding, handover or audit purpose. Questions are asked one at a time, excluding anything already answered in earlier messages. Unknown facts stay unknown. Intent, confirmed facts, open questions and requested formats remain internal unless the user asks to inspect them; no missing answer is invented.

The field model includes SOP Title (text); Category (select); Department (text); Description (long_text); Last Reviewed (date); Next Review (date); Owner (text); Priority (select); SOP ID (id); Status (select); Tags (text); Version (text).

Category starts with Process, How To, Checklist, Reference, Template. Priority starts with Low, Medium, High, Urgent. Status starts with Draft, In Review, Published, Under Revision, Retired.

Requested CSV, SQL DDL, JSON Schema and Notion mappings derive from one field list. Display names remain identical across CSV and JSON, and normalized SQL identifiers are documented. Relation fields keep their relational meaning, dates remain dates and money remains currency. Machine-readable data is separated from explanation, with validation failures and limitations reported separately.

One supplied SQL example is:

CREATE INDEX idx_sop_company_wiki_status ON sop_company_wiki (status);

Excel-compatible CSV uses UTF-8 with a byte order mark. Because CSV has no column types, numeric, date and currency formatting is identified after the data. A CSV is not an .xlsx workbook; the latter is generated only when requested. Example rows require an explicit request and must be clearly synthetic. Sensitive identifiers are not unnecessarily repeated in a review, and generated templates remain empty.

Notion output goes to notion-manual-import for the CSV, property mapping, import steps and verification checklist. Manual mappings require no connection. Requested workspace changes require verified tool access, the actual target and authorization; a claimed connection is insufficient evidence. Notion relation columns resolve only after both databases have been imported. Select options are an initial vocabulary that can be renamed to match the business. people-directory supplies the related employee master record; notification-reminder-hub is the separate due-date reminder module. Personal identifiers and sensitive financial details stay out of generated templates.