Philippines staffing guide
Keep a Living SOP Index for a Growing Assistant Team
An index that names the owner, the last review, and the trigger for change is more valuable than a folder of perfect documents.
Published · 8 minute read
On this page
Every assistant team eventually has a folder called SOPs. It contains three versions of the same checklist, one document named final-final, and a procedure that references a tool the company retired in March. The problem is not missing documentation. It is that nobody owns the index that tells a reader which document is current and when it should be trusted.
List the procedures that actually run
Build the index from the work, not from an org chart. Pull the last month of completed tasks and group them by the procedure a new person would need. You will usually find ten to fifteen recurring procedures and a long tail of one-offs that do not deserve a document. Start with the procedures that touch money, customer commitments, access, or a recurring deadline.
Give every entry four fields
Each row needs a current owner, the last review date, the next review date, and a change trigger. The trigger is the event that makes the document suspect: a tool migration, a pricing change, a new approval threshold, a customer contract. A document without a trigger will be reviewed on a calendar nobody remembers. A trigger gives the owner a reason to look.
Separate the stable rule from the local workaround
Most procedures contain one durable rule and several local habits. Mark the rule clearly, then label the workaround with the condition that justifies it. When the condition disappears, the workaround should disappear too. This distinction prevents a temporary fix from becoming policy simply because it was written down in the same font as everything else.
Keep the index where work begins
Link the index from the intake form, the shared drive landing page, and the assistant's first-week checklist. A perfect index buried three folders deep will not be used under pressure. Add the procedure name to the task template so every recurring task points back to its instructions. If people still ask in chat, the link is not where the work happens.
Review a sample, not the whole library
Each month, pick five entries and test them against a real recent task. Did the steps produce the expected result? Did a missing prerequisite cause a detour? Did the owner answer a question the document should have answered? Record the finding on the index row. This is faster and more honest than asking everyone to certify that all documents are current.
Retire deliberately
Move superseded procedures to an archive with the date and the reason. Do not delete them, because an auditor or a client may need to know what the team was following at the time. Remove archived items from the active index so the working list stays short. A small, current index beats a comprehensive one that nobody trusts.