Workplace operations services, described as they are delivered.
Each service below has a purpose, a scope, a way of working, and a set of deliverables. You can commission one of them or combine them in the engagement offer. Nothing here includes construction, furniture supply, or on-site staffing.
Direction
Workplace Operating Model
Give the workplace a clear owner, a weekly rhythm, and a way decisions get made without hunting for the right person.
Many offices run on goodwill. Someone books the rooms, someone else talks to the landlord, and a third person notices when the kitchen fails. The operating model names that work. It shows who decides, who delivers, who is consulted, and which conversations happen every week rather than only in a crisis.
Scope
A review of how the workplace is run today, a map of responsibilities, the meeting and note rhythm, and the paths used when something needs a decision.
Process
We speak with the people who already carry the office, draft the model in their language, walk through it with them, and issue a final operating note once the owners are agreed.
Deliverables
An operating model note, a responsibility map, and a simple rhythm for the week. The proposal lists the exact documents before work starts.
Who it suits
Organizations whose office functions, but only because a few people remember how. Useful when a founder, an operations lead, or a people team has inherited the workplace.
Put requests, routines, and handoffs on a path the team can see, so the day is coordinated instead of reconstructed from messages.
Daily coordination is the live layer of workplace operations. It covers how a request enters, who acknowledges it, what “done” means, and how a recurring issue is noticed before it becomes folklore. We do not sit in place of your office manager. We set the route with them and, where agreed, stay close while the route is first used.
Scope
Intake routes, a daily or weekly check, an issue log, and the handoff between the internal team and the people who act on site.
Process
We set the route, watch it in use long enough to see what breaks, adjust the log and the check, and hand the rhythm back with a short written guide.
Deliverables
An intake map, an issue log the team can keep, and a weekly operations note format. Ongoing coordination, if wanted, is a separate line in the proposal.
Who it suits
Offices with repeating friction and no single place where work is acknowledged. Also useful when a coordinator is new and needs a rhythm rather than a pile of advice.
Bring the vendors and in-house partners who serve the workplace into one picture, with expectations and a review that happens on purpose.
Partner oversight does not mean changing suppliers. It means the client can say what each partner is there to do, how issues move, and when the relationship is reviewed. Cleaning, maintenance, catering, plants, waste, security, and similar services are included only as coordination. Contracts stay with the client and their advisers.
Scope
A partner inventory, a plain-language expectation for each relevant service, an escalation path, and a review cadence the client can host.
Process
We list the partners with you, draft the expectations from how the service actually shows up on site, agree the review agenda, and facilitate the first cycle if you want a worked example.
Deliverables
A partner register, service expectation notes, and a review agenda. We do not renegotiate commercial contracts unless a separate, explicit scope says so, and even then we do not provide legal advice.
Who it suits
Teams juggling several suppliers without a shared view, and teams about to renew a service who want the operational expectation clear before the commercial conversation.
Help the workplace match how people use it, especially where hybrid habits have made rooms feel either empty or contested.
This service looks at neighborhoods, shared rooms, and the informal rules that have grown around them. We use what you can already see and what your team can describe: booking behavior you choose to share, observations agreed in the scope, and the complaints that keep returning. We do not install sensors and we do not run a surveillance program.
Scope
How neighborhoods and shared rooms are used, where rules are missing, and which adjustments are realistic without a refit.
Process
A brief, a structured look at the current pattern, a written recommendation, draft rules for shared space, and a follow-up once people have tried them.
Deliverables
A space-use note, shared-space rules, and a short list of adjustments. Furniture layouts and building works, if needed, are identified for others to design.
Who it suits
Hybrid teams, underused rooms, crowded corners, and offices where the booking system and the real day have drifted apart.
Write the practical standards people can follow for the moments that otherwise generate the same questions every week.
A useful playbook is closer to a floor note than a policy manual. It covers arrival, visitors, rooms, shared amenities, incidents worth escalating, and how the day closes. Tone matters. If it sounds like a punishment, it will be ignored. If it sounds like a colleague who has done the job, it will be used.
Scope
The recurring moments you want handled the same way, agreed with the people who host them. We do not draft employment contracts or legal policy.
Process
We collect current practice, draft the pages, review them with the operators, and publish a short playbook your team can host wherever you already keep working notes.
Deliverables
A workplace playbook and one-page standards for the moments in scope. The length is kept short on purpose.
Who it suits
Teams tired of answering the same questions, new hosts, and organizations that want a visitor or room experience to feel consistent without a script.
Coordinate the operational side of a move, a restack, or a workplace change so people know what happens, when, and who decides.
Moves fail in the gaps: the access list, the first Monday, the unlabeled room, the partner who was not told. This service runs that operational thread. It does not manage construction, appoint contractors, or design the fit-out. Those remain with the specialists you choose. We keep the timeline, the communication, and the first week of stabilization coherent.
Scope
An operational timeline, stakeholder communication, a day-of run of show, and a stabilization period after people arrive. Technical works stay outside the scope.
Process
We confirm the change with you, build the run of show with the people affected, coordinate the operational decisions as the date approaches, and stay for an agreed stabilization window.
Deliverables
A change timeline, communication notes, a day-of checklist, and a stabilization note. The proposal states the dates we will cover.
Who it suits
Offices relocating, teams restacking a floor, and workplaces reopening or consolidating sites. Best started before the week of the move, not during it.
Describe the workplace and what keeps sticking. We will suggest a starting point, or say if the work belongs with someone else. The engagement path explains what happens after you write.
We use one essential cookie to remember this choice. A session cookie is used only on the contact page to protect the form. We do not use analytics or advertising cookies. Read the Cookie Policy.
Cookie settings
Your choice is stored in an essential cookie named ap_consent for 180 days. You can change it at any time from Cookie Settings in the footer.
