Run an SOP Workshop in Ortigas: Turn One Repeated Task Into a Checklist
A repeated task can look straightforward until two people explain it differently. An SOP workshop gives your team time to agree on one practical way of working, then test whether another person can follow it. Start with one routine process—not an entire operations manual.
This guide is for small-business teams preparing a working session in Ortigas. The output is a draft standard operating procedure (SOP), a short test record and a named person responsible for revisions. It still needs your team's approval before becoming the official process.
Choose a process small enough to finish
Pick a task with a clear starting point and a visible finish: receiving an inquiry, checking a delivery or preparing a handover file, for example. Define what is outside the session. A checklist for responding to an inquiry is not the same as redesigning your whole sales process.
Bring the people who actually do the work, someone who receives its output and the person who can approve changes. Ask each to bring a blank template or a redacted example. Leave customer details, passwords and unnecessary confidential records out of the workshop materials.
Map what happens before writing what should happen
Walk through one ordinary example from start to finish. Record each action, the input it needs and who performs it. When people describe different methods, mark the difference instead of quietly picking one.
Separate a required control from a personal preference. Ask what can go wrong if a step is skipped, and who can confirm the rule. If the answer depends on an unresolved policy or specialist advice, note that dependency; do not turn an assumption into an approved instruction.
Build a checklist that someone else can use
Use these fields in your working document:
Process name and scope: what starts the task and what counts as finished.
Required inputs: the files, information and permissions needed before starting.
Steps: one action per line, using clear verbs and naming the responsible role.
Checkpoints: how to recognise a correct output before moving on.
Exceptions: when to stop and whom to ask rather than improvise.
Document owner, version and review date: who keeps the instructions current.
Replace vague directions such as “check everything” with an observable check. For example, “compare the requested date with the confirmed schedule” tells the reader what to compare. Use your own approved process details; this example is not a statement of The Hangout's booking procedure.
Test the draft with a fresh pair of eyes
Ask a participant who did not write the steps to work through a sample while the writer watches without coaching. Note where the person pauses, needs an unstated input or interprets a step differently. Revise those parts, then test the changed section again.
Close the workshop with three separate lists: ready for approval, questions still open and changes to test. Assign an owner and next action to every open item. Keep the draft clearly labelled until the authorised person approves it; a productive workshop is not itself policy approval.
Plan the room around the working session
For an in-person SOP workshop, allow for discussion, shared document editing and the walkthrough—not only a presentation. Tell The Hangout Coworking Space Ortigas your preferred date, start and finish times, headcount and layout. Ask which display or writing equipment is suitable and included for your particular session.
Our currently listed conference-room base rate is ₱1,000 for the first hour and ₱500 for each succeeding hour, subject to the room, headcount, setup and quote. Confirm availability, inclusions, total cost and booking terms with the team before payment. The room photo shows an arrangement, not guaranteed availability or equipment.
Find us at Unit 2408, 24th Floor, Tycoon Center, Pearl Drive, Ortigas Center, Pasig City. Call 0917 193 1276, or send your workshop brief through WhatsApp to ask about a suitable conference room.
Comments