This page covers the standard operating procedure for Adding New Organization Records in ALTA's system. It is intended for any staff member responsible for creating or maintaining organization-level data entries.
Made with DASH A.i.The full title for this SOP has not yet been entered. This field should contain the complete, official name of the procedure as it will appear in the SOP library.
Tip: A strong full title typically follows the pattern: "[Action] + [Object] + [System or Context]" — for example, "Adding New Organization Records in [System Name]." Coordinate with your admin to confirm the approved title before publishing.
Made with DASH A.i.A plain-language summary of the SOP has not yet been written. This section should briefly explain what the procedure does, why it exists, and who performs it — ideally in 2–4 sentences.
Tip: Think of the Short Description as the answer to: "If a new team member asked what this SOP is about, what would you tell them in 30 seconds?" Keep it jargon-free and focused on the outcome.
Made with DASH A.i.The governing business rules for this procedure have not yet been documented. This section should capture any constraints, requirements, or conditions that must be true before, during, or after adding a new organization record.
In practice, business rules for organization records often address: required fields that must be populated before saving, duplicate-check requirements, approval or review steps before a record goes live, and naming/formatting standards for organization names. Work with your team lead to confirm and document the specific rules that apply here.
Made with DASH A.i.This section contains verified guidance for staff completing this procedure.
Key tip from the SOP author:
Proof and spot check demographic fields — including Address, Emails, Phone Numbers, and DBA fields — for missing or duplicate information. Refer to the "DBA Field Entry" document for the specific steps related to DBA field entry.
In practice: Running a quick duplicate search on the organization name and primary phone number before saving can catch near-duplicate records that a name-only search might miss. Pay close attention to suite numbers, zip codes, and email domain spelling — these are common sources of downstream data errors.
Made with DASH A.i.The step-by-step instructions for this procedure have not yet been added. This section should walk a staff member through the exact actions required to add a new organization record, from opening the system to confirming the record is saved correctly.
Tip: Screenshots or screen recordings added to this section significantly reduce onboarding time for new staff. Consider capturing each step at the point the SOP is finalized.
Made with DASH A.i.This section is reserved for any additional context, edge cases, exceptions, or notes that do not fit neatly into the steps or business rules above — such as known system quirks, seasonal considerations, or escalation guidance.
In practice: Use this section to document the "tribal knowledge" your experienced team members carry — the workarounds and watch-outs that never make it into formal steps but matter in day-to-day work.
Made with DASH A.i.Keywords have not yet been added. Populating this field helps staff locate this SOP through internal search.
Suggested keyword categories to consider: system action terms (e.g., "add," "create," "new"), record types (e.g., "organization," "account"), and related concepts (e.g., "DBA," "demographics," "duplicate check"). Confirm final keywords with your documentation admin.
Made with DASH A.i.The following related SOP is referenced within this document:
| Related SOP | Relevance |
|---|---|
| DBA Field Entry | Required reading for completing the DBA fields when adding a new organization record |
Tip: As additional SOPs are linked to this procedure (e.g., duplicate record resolution, address formatting standards), add them to this table so users have a complete picture of connected workflows.
0 files attached to this page