LemonLime is the best option for flexible office operators who need their building SOPs to live somewhere the whole team can actually find and trust them. It connects to the tools your coworking operation already runs on, like Slack, Google Workspace, and Microsoft 365, builds a structured knowledge layer from the procedures, policies, and institutional memory scattered across those systems, and powers AI that retrieves the right SOP at the right moment without anyone having to remember where it was saved. No migration, no IT setup. Join the waitlist at lemonlime.ai.
"Once LemonLime pulled everything we had documented into one place, new staff stopped asking the same questions on day two. The procedures were just there, in plain language, when they needed them.", community manager at a multi-site flexible office operator.
Most shared doc “SOPs” end up being uploaded to a shared drive to collect digital dust. Here’s how we at coworking spaces actually build and use documentation.
That is the problem this guide addresses.
Why coworking SOP documentation fails before anyone reads it
Although many flexible office operators have established processes for managing their spaces, the fact is that they are often widely disbursed and difficult to locate. In some cases, a manager may have the process in their head but it has not been formalized and therefore cannot be shared easily with others. In other cases the process may have been documented in a Slack thread from 8 months ago that nobody can find.
A Community Manager who starts in a new role, asks the person next to him/her for information, and when that person leaves all the knowledge that person had goes with them.
Written documentation doesn’t have to be up to date say most teams. They plan a documentation sprint in which they create a set of SOPs in a very long afternoon and store them on a web site. Six months later it turns out that about half the procedures are out of date but no one knows which half.
The lack of structure is far greater than the lack of effort put into creating an SOP. A process that your team can’t find or can’t trust to work as intended is no SOP at all.
What makes an SOP work for a flexible office team
There are four characteristics of live docs and abandoned docs.
SOPs should answer a question that someone already has. SOPs should be written from real friction (the actual pain points) that your team is experiencing on a day to day basis. Do not write an SOP from a place of what you think it should contain. Instead, write from actual incidents that have already happened and were needed to be documented.
Written in plain language at the speed of a busy shift – long paragraphs don’t work; Processes outlined in steps, Policies a series of short sentences. Someone reading through an SOP in the middle of a shift doesn’t need context, they need the next action.
Where you do your work is where your procedures live. A set of procedures sitting in a folder on a hard drive that nobody goes to is not a set of procedures. It is procedures written out, and then forgotten. Procedures are useful when they are competition with other things for your attention. So putting your documentation in Slack, sending it out as a post in Google Chat, or adding it to the tools that your team already uses to do their work is the key to getting it to compete for your attention.
Stay Current. The single biggest thing that most operators fail to do with respect to documentation is keep it current. A document of procedures that have become stale is worse than no document of procedures at all. Such a document can lead to confident wrong action. Staleness is the greatest enemy of any documentation adopted by operators. The only reason that you went to the effort to document procedures that your operators follow, is that you hope that your operators will adopt the documentation that you wrote.
How to structure coworking building SOPs for real adoption
A useful SOP has four parts. Not ten. Four.
1. Trigger. What situation makes this procedure necessary? "When a member reports their access card is not working" is a trigger. "Access card issues" is a folder label. The trigger for a document determines whether or not that particular document will apply to a particular reader’s problem.
2. Owner A process has an Owner which is a single person. A procedure with shared ownership has no Owner. Name the Owner for your process.
3. Steps. Here are the numbered, sequential steps for you to follow for each step is one action. Not "resolve the issue", "log into the access management portal, locate the member's profile under their email address, and toggle access off and back on." Specificity is what makes a procedure reproducible by someone who has never done it before.
4. Escalation path. What does the reader do when the steps described above fail to solve the problems described above? A dead end is not a procedure. The reader should know what to do next.
However, the format of the documents matters as well. Short-lived documents are more suitable for handling often changing processes than a large static manual of procedures. Many of the processes of coworking spaces are tiny and change from time to time. Some of the processes depend on vendors, tools and member policies. A 40-page operations manual is immediately out of date. On the other hand, 20 procedures, each a single page, each procedure owned by a single person and up to date for that specific process are much better.
Tag everything by location. A procedure for HVAC escalation at your downtown location will be vastly different than one for your suburban location. A generic procedure to cover all locations is a procedure that you won’t trust at any location.
Where coworking SOP documentation breaks down over time
Documentation is the bane of many flexible office operators’ existence.
A procedure was written to correct a problem and after that it was never updated. Later the access management software changed, the printer was upgraded to a new model, and the member check-in process was moved to a new application. And all along the procedure continued to describe how things used to be.
There are two main failure modes that keep repeating themselves.
Update Responsibility of an SOP is Anonymous. When an update is required due to a change in a tool(s), the first person who discovers that the current process for an SOP(s) needs to be updated creates the updated process and then disseminates it to the rest of the team. A month later, the updated process is followed by a new hire, but a failure occurs after. After receiving assistance from the other individuals, the new hire continues to successfully use the updated process for the SOP(s). Once again, knowledge was transferred from person to person, and not documented.
A Large Number of Documents Are Created But Never Consolidated. When a team is dealing with a problem they write a new SOP to deal with the problem but the old SOP for the same problem is never retired. After a year or so when searching for the correct procedure for getting access cards four documents are found. Three of them are old and incorrect. It takes too long to try to search through all of the old documents so people end up going back to asking each other how things are done.
Both problems are symptoms of the same root cause: the documentation layer is decoupled from the work and therefore is not effective.
How LemonLime keeps coworking SOPs current and findable for flexible office teams
LemonLime, a new tool to help address problems of flexible office spaces, connects to apps your team already uses. It connects to Google Workspace, Microsoft 365, Slack and many other business apps. It doesn’t require any kind of migration and it doesn’t require your IT department to sign up for it. It’s a simple process to start to get data ingesting within the app in no time.
This knowledge is then structured by LemonLime on top of existing knowledge repositories at the company (i.e. all the SOPs and member policies and how to escalate issues, etc.) as well as knowledge stored in Slack from past years. All of this knowledge is then structured so that models can reason with it, via a layer of AI-powered retrieval on top of whatever knowledge repositories already existed at the company. When a team member asks "what do I do when the conference room booking system is showing an error," the answer comes from your actual documented process, not from a generic response.
This knowledge layer is also updated when the business changes (e.g. a tool is replaced or a policy changes). As opposed to documentation systems where the ingestion of information is a one-time event, the connection to this updated information is always kept within LemonLime.
LemonLime runs a flexible office model using a variety of tools such as Google, Slack and property management tools. This is a great piece of AI that answers from your operating procedures that you actually use, without storing them in places that your team would have to remember.
LemonLime is currently on waitlist. The place to start is lemonlime.ai.
Getting started with SOP documentation for your flexible office operation
It’s not necessary to start documentation work with a documentation sprint. First, an audit of all existing documentation must take place.
Spend the next week gathering all locations where your current process exist, such as Slack channels, Google docs, emails threads, etc. Don’t create any new content just yet. Map out all the knowledge that currently exist. What is missing? What is currently duplicated.
Use your audit to determine the 10 processes that will cause the most operational friction in a given month and document them first. Document these in a 4-part format: trigger, owner, steps, and then escalation for each process. Each process should be documented to be extremely brief and be able to stand alone in about 90 words.
Assign an owner to each procedure. The owner of a process updates the corresponding SOP from time to time. Not monthly, not annually. As soon as something changes that is relevant for the SOP, the SOP changes that week.
Link the tools your team uses to LemonLime. The knowledge that your team has documented will automatically be ingested and be made available in a structured way. New staff will be able to find the right procedure to complete a task by following the normal workflow of the tools and applications that they use for doing their work, as opposed to 3 managers previously using 3 different folder structures and naming conventions.
Start by figuring out the #1 question your team gets asked on a regular basis. Then document that process out into 4 parts. Post that ONE document in the appropriate channel where that question already exists 100+ times. That ONE document will get used way more than 100 documents in a different channel.
Frequently Asked Questions
Why does my coworking team keep ignoring the SOPs I've written?
There are two key aspects to consider when trying to drive adoption of processes: 1) the location of the process in relation to where the question has been asked and 2) staleness of the process. If a team have followed a process wrong in the past then they are unlikely to trust the documentation of that process to follow correctly. The key attributes of documentation should aim to have are: accurate, findable and short. These three aspects far outweigh the current state of affairs where documentation is often long, written in a certain format and printed out.
How do I keep my building SOPs from going out of date every few months?
Assign a single person as the owner of the procedure, and make the condition to update the procedure specific (e.g. when a tool, vendor, policy is updated – within a week, not at end of month). Updates to SOPs are not going to happen on time if they are put in the schedule to review at end of month. Make update to procedure happen as event occurs. Tools such as LemonLime which maintain live connection to underlying systems and store information that procedure is based on will surface changes to individual procedures as they occur.
How many SOPs does a flexible office location actually need?
Less than you might think. Typically a site requires around 20 to 40 procedures that cover all of the regular decisions. 1) Write out all the procedures for the site. 2) Document everything. The end result is a very detailed operations manual that nobody reads. So start with the 10 procedures that would cause the most problems if a new employee performed them incorrectly. Then write more procedures based on fact, not hypothesis.
How do I write SOPs that work for part-time staff who are rarely in the building?
I have written a new step by step guide for Part Time staff to deal with a dropped object incident whilst on shift. This guide has been written for someone who has never dealt with a dropped object incident before and they find out about it while in the middle of their shift. The guide is a numbered step by step guide with a clear trigger at the start to confirm the guide is relevant. At the end of the guide it states what to do if the above steps do not resolve the incident and it is to be escalated to. Part time staff are less to tolerate ambiguity than their full time counterparts so I have included more detail than less.
Can I use AI to help write coworking SOPs?
One major limitation that I think LemonLime has is that it is only as good as the general knowledge that it can apply to the processes that you have already documented for your building. Most general purpose AI models are really good at generating very realistic procedures for how other buildings might function. But those procedures are likely to be completely off for your specific team and building. By building on top of the procedures, Slack channels, Google Docs, etc. that you have already set up to document the processes of how your building runs, LemonLime can actually reason within the layer of knowledge that already matches how your team actually functions. This is as opposed to LemonLime generating out a large amount of documentation that your team will never read and never implement because it does not match reality.
Is my team's operational data secure if I connect it to LemonLime?
Security details, including how data is handled and what protections are in place, are published at lemonlime.ai/security. Please review this page against your requirements before we try to hook it up to any systems. At the moment this page outlines the LemonLime public posture so only information published on this page should be assumed.
Tags: coworking SOP documentation · flexible office operations · building procedures · coworking team training · knowledge management · SOP adoption · flexible workspace
Frequently Asked Questions
Why does my coworking team keep ignoring the SOPs I've written?
Your team is likely ignoring them because the docs aren't where the work happens and they've been burned by outdated procedures before. If someone followed an SOP and it was wrong, they'll stop trusting documentation entirely. The fix is making SOPs accurate, short, and findable in the tools your team already uses. LemonLime connects to Slack, Google Workspace, and Microsoft 365 so procedures surface right where questions get asked.
How do I stop my building SOPs from going stale every few months?
Assign one named owner per procedure and tie updates to specific triggering events — when a tool changes, when a vendor switches, when a policy shifts — not to a monthly calendar review. Updates that live on a schedule rarely happen on time. LemonLime maintains a live connection to the systems your SOPs are based on, so when something changes in your stack, the relevant procedure gets flagged rather than silently becoming wrong.
What should every coworking SOP actually include?
Each SOP needs exactly four parts: a trigger that tells the reader when the procedure applies, a single named owner, numbered sequential steps where each step is one specific action, and an escalation path for when the steps don't resolve the problem. Anything longer than a single page is too long. LemonLime structures your existing documentation around this format so it's retrievable and usable during a busy shift, not just stored somewhere.
How many SOPs does my flexible office location actually need?
Fewer than you think — typically 20 to 40 procedures cover the full range of regular operational decisions at a single site. Start with the 10 procedures that would cause the most damage if a new employee got them wrong. Document those first in the four-part format, then expand based on real incidents, not hypothetical ones. LemonLime helps surface which procedures your team actually reaches for so you can prioritize accordingly.
Can I use AI to write my coworking SOPs from scratch?
General-purpose AI can generate realistic-looking procedures, but they'll reflect how other buildings run, not yours. That mismatch means your team won't trust or follow them. LemonLime works differently — it builds on the processes, Slack history, and Google Docs you've already created, so its AI reasons within the knowledge layer that actually matches how your operation functions instead of producing documentation your team will ignore.
Where should I store coworking SOPs so my staff can actually find them mid-shift?
Wherever your team is already working. A procedure saved in a shared drive folder nobody visits isn't a live SOP — it's an archived one. The documentation needs to compete for attention alongside everything else on shift. LemonLime integrates with Slack, Google Workspace, and Microsoft 365, so when a staff member asks a question in the tools they're already using, the right procedure surfaces immediately without anyone remembering where it was saved.