Freeze the cleaning package and site brief
Begin by inventorying the proposed cleaning agreement, site or room schedule, service frequency, access and key instructions, supply list, safety or handling procedure, inspection checklist, incident contacts, invoice schedule, quality or report template, and every addendum or policy included with the package. Record the filename, version, sender, received date, and internal owner for each item. Preserve the originals rather than replacing them with one blended facilities summary.
Add a short site brief written by the coworking operator. Record the locations and rooms in scope, expected member-facing schedule, service windows, access assumptions, supplies the site provides, records expected after a visit, and the person authorized to approve a business change. Keep this brief labeled as context so it cannot be mistaken for cleaning language.
- Name the exact agreement, site, frequency, inspection, and invoice versions under review.
- List every access, safety, supply, or reporting instruction the package incorporates.
- Record the operations, facilities, finance, vendor, member-facing, and approval owners.
- Keep site plans and vendor conversations separate from source-backed terms.
Map one service visit from access through inspection
Draw the service sequence the operator and vendor can actually verify: schedule, access, room or area assignment, supplies, cleaning work, issue or incident, inspection, member-facing communication, closeout, invoice, and the record used for follow-through. For each stage, name the person and record involved and attach the proposed language that appears to describe it.
Leave a stage open when the package does not answer it. An expectation about timing, access, supplies, quality, incidents, or reporting should remain visibly separate from the proposed documents. The site-and-service map is an operating fact record for counsel, not a conclusion about what the agreement requires.
- Use the coworking space's real service and inspection sequence rather than a generic checklist.
- Identify the document and exact source location behind every agreement-derived note.
- Name who can verify each room, access, supply, incident, invoice, and report record.
- Preserve a missing procedure, schedule, record, or owner as an open item.
Pair schedules, supplies, incidents, and invoices with evidence
Create one source-linked table for every site, room, service, frequency, amount, formula, date, supply, inspection, incident, invoice, report, and other cleaning event the package describes. Useful rows may include routine visit, special event, supply delivery, access change, missed area, issue report, inspection, correction, invoice, member notice, and service transition. Keep each entry tied to its source language and label any internal estimate separately.
Then ask the people who will run the space to verify the sequence. Facilities can confirm rooms and supply records, operations can confirm member-facing effects, and finance can confirm invoice administration. Counsel can inspect how those verified facts relate to the proposed language and identify the interpretation or drafting decisions still needed.
- Record each amount, date, inspection, or incident beside the event it appears to address.
- Separate stated terms from an internal staffing or supply estimate.
- Name the owner of each access, supply, inspection, invoice, and report step.
- Keep an undefined correction path or missing schedule visible.
Test access, quality, and transition scenarios
Walk through several concrete site scenarios: access is unavailable, a room schedule changes, a special event adds work, a supply is missing, an inspection identifies an issue, a member-facing notice is delayed, a correction visit is needed, or the operator prepares to move to another cleaning provider. For each scenario, place the expected business response beside the source sections and instructions that appear relevant.
Route each unknown to the right lane. Facilities can verify room and supply records, operations can confirm member-facing facts, finance can confirm invoices, vendor owners can confirm service records, leadership can own business choices, and counsel can address interpretation, drafting, and legal risk. Preserve the question when the source record or site decision is incomplete.
- What site, schedule, access, supply, inspection, invoice, or transition event is being tested?
- Which source passage or instruction appears to address it?
- Who can verify or approve the operator's business response?
- What interpretation or drafting judgment remains for counsel?
Give counsel one site-and-service packet
The handoff should include the frozen document inventory, site brief, source-linked service path, schedule-and-inspection table, access scenarios, missing materials, and the owner of every open decision. Keep superseded checklists, schedules, and informal explanations available but clearly separate from the package counsel is being asked to review.
For each uploaded contract document, CounselOS can preserve source-linked clause extracts, surface playbook deviations, capture questions beside the relevant finding, and export selected material in a review packet. The site map and service records remain human-reviewed operating artifacts; CounselOS provides traceable contract evidence for the operator and attorney making the next decisions.
A note on legal judgment
This article describes a review and handoff workflow. It is general information, not legal advice. Contract meaning and acceptable risk depend on the agreement, the parties, and the applicable law; involve qualified counsel for legal decisions.