Keep the record together
Bring the issue, location, relevant notes, supporting documents, dated updates, and prior history into one working record.
For facilities and workplace teams
Stop chasing requests.
Start running a system.
The Operations Desk gives facilities teams a working view of unresolved requests: what is at risk, what has been promised, who owns the next move, and when follow-up is due.
Not a CMMS replacement. A control layer for unresolved work between your existing systems.
Bring one real example of work that went quiet, got stuck, or required too much chasing.
Operations Desk · unresolved work
What needs attention today
JFS-2408
Emergency light flickering, stairwell B
⚠ Safety review
JFS-2411
Meeting Room 3 temperature too high
⚠ Breaches in 6 h
JFS-2404
Recycling collection missed twice
⚠ No owner
Illustrative data — not customer activity.
The operational problem
The work is moving. The record is scattered.
Facilities and workplace requests arrive by email, chat, phone, walk-up conversation, vendor update, landlord notice, and inspection finding. The request may be logged. The work may even be underway. But once responsibility moves between a coordinator, a vendor, and an approver, the trail splits across systems and inboxes.
When a director, tenant, finance partner, or executive asks what is still outstanding, the answer is rebuilt from memory. A vendor disputes a date and there is no record of who said what. The cost is not only a missed request — it is time spent chasing updates, service issues that resurface, vendor commitments that drift, and repeat problems treated as one-offs because the history is fragmented. See the honest comparison →
What it does
Give unresolved work a clear next move.
The Operations Desk is a control layer for the work that falls between existing systems. It does not ask you to replace your CMMS, workplace platform, building-management process, or existing tools.
Make ownership visible
Record the current owner, the next action, and the date that action is due — including when the work is waiting on a vendor, an approval, or access.
Surface work that needs attention
Review open items, overdue follow-ups, waiting commitments, and work that needs a decision before an issue escalates.
The working test: if a request still needs three emails and a status meeting to identify the owner and next step, it is not under control.
Example workflow
A request can be logged and still be unresolved.
A recurring HVAC comfort complaint — the kind every facilities team knows. The point is not another reporting task. It is making the work your team already chases easier to manage.
| What happens | Without a working record | With the Operations Desk |
|---|---|---|
| Comfort complaint reported | Logged — location and history attached | Recorded with location and prior history |
| Forwarded to the contractor | Sits in an inbox thread | Contractor named as owner, attendance date set |
| Temporary fix applied | Fix noted nowhere central | Findings and next action retained on the record |
| Update promised for Friday | Promise lives in someone's memory | Commitment has a named owner and a due date |
| A week of silence | Nobody notices | Shows as overdue — impossible to miss |
| The issue returns | Treated as a brand-new complaint | Full history informs the root-cause decision |
Illustrative workflow — not customer activity.
On cost
Keep the evidence with the issue.
Where your team needs it, an operational record can include a cost estimate, approval note, vendor quote, invoice reference, or supporting document. The Operations Desk is not a replacement for finance, procurement, or your existing approval process — the goal is decision evidence attached to unresolved work.
Why this exists
Built for the work between the request and the resolution.
JFS OPS was founded by John Shelly, a facilities and workplace operations professional. The company began with a recurring observation: a request can be logged, assigned, and still become invisible once the next action sits with a vendor, an approver, or another team.
JFS OPS is being built to make those handoffs easier to manage — starting with one focused workflow at a time.
Document what happened. Make the next owner clear. Follow through on the commitment. Use the record to improve.
A practical starting point
Start with the work your team is already chasing.
Most facilities teams do not need a large technology programme to fix a broken handoff. JFS OPS is speaking with facilities and workplace leaders who want to identify one workflow that is difficult to manage today.
Start a conversation ↗Bring one real example of work that went quiet, got stuck, or required too much chasing.