NEO makes the
office add up.

Consider an ordinary office move. One employee changes desks. Facilities needs the new location. IT needs to know where the equipment belongs. Someone must update the drawing, and someone else may need to arrange the work. The chair travels a few feet. The information has farther to go. This is an illustrative scenario, but it captures the problem NEO has organized its software around: keeping workplace records connected when the workplace changes.

NEO, the Atlanta company behind NEOWorks, comes at that problem from commercial project management. Its background includes construction, consolidations, furniture, equipment, technology, and security projects for corporations across the United States. It also expanded into facilities staffing. The software carries that practical inheritance: people have locations, locations have drawings, and changes have work attached.

• The job: connect workplace people, properties, assets, and activities.
• The mechanism: shared records, linked floor plans, and work orders.
• The buyers: facilities and real estate teams working with IT, HR, and security.
• The useful lesson: make routine transactions keep the records current.

01The drawing knows who sits there

Start with the floor plan. NEOWorks links a space to a person or room type: a conference room, storage area, or huddle space. Click the space and you can see its occupant and associated work orders. Start with the employee list and you can find the person on the drawing. The relationship works in both directions.

Then comes the move. Through its MAC workflow, meaning moves, adds, and changes, NEOWorks supports changing an employee’s or contractor’s location. Once the work order is completed, the person’s profile and drawing update together. Teams can also change a location manually; NEO says the system still logs the event for tracking.

That last option is revealing. NEO accommodates customers who want a location record without a formal work order. Its floor-plan documentation likewise allows building-level or floor-level tracking when individual seats are unnecessary. The operational lesson is straightforward: collect enough detail to support the decision. Requiring a desk coordinate for every situation would add work without necessarily adding useful information.

02One write. Several departments.

NEO calls its underlying idea “one write”: enter data once and use it many times. Its data-sharing description singles out IT and facilities, two disciplines that need information from one another. Shared access lets them use work orders, floor plans, dashboards, upcoming activities, and historical records.

The same logic extends beyond seating. An equipment record can include maintenance details, sit on a drawing, and move through a work-order system. Property records can hold lease expirations, escalation dates, improvement history, and documents. The visitor kiosk connects visitors and vendors with employees or contractors already in the application.

Those features put NEOWorks in the workplace-management market, spanning space, assets, maintenance, and visitor processes. Its own marketing names separate spreadsheets, applications, and databases as the alternative. The distinction it emphasizes is connection across those jobs. A team buying only a visitor register would have a narrower need; a team reconciling several departments’ records has a reason to examine the combined workflow.

“one write”

03The thermostat is part of the story

The demand-maintenance examples are wonderfully ordinary: “too hot” and “too cold.” NEO also lists requests for help with a layout or ergonomic needs. Users submit work orders, typically to facilities for review and dispatch. Vendors can be organized by work type, building, floor, or administrator-defined criteria.

This gives the company’s customer description some texture. Facilities managers sit alongside real estate, technology, HR, environmental health and safety, security, contractors, and vendors in its published user list. NEO describes work stretching from daily operations to renovations, consolidations, and other projects. The buyers are coordinating physical workplaces and the people who support them.

The company’s account of its culture fits that work: collaboration, keeping commitments, and anticipating problems that cause downtime or extra cost. That is NEO’s own description. The product offers a concrete expression of the same priorities: requests have a destination, locations have a record, and changes leave a history that another department can use.

04A spreadsheet is a starting point

NEO’s published setup process begins with materials an organization may already have. For people-on-floor-plan views, it asks for a spreadsheet containing names and unique identifiers, drawings preferably in DWG format or alternatives such as Visio and PDF, and a list of authorized users. Floor plans are optional. Its stated target is access to the supplied data in ten days or less, a company promise rather than an independently measured deployment time.

The business model is a subscription. The setup page describes unlimited users and all features included for use as needed. An August 2017 post also advertised no additional setup, training, or support expenses. Treat that as a historical offer to discuss with the vendor when scoping a purchase.

The commercial idea is useful regardless of the eventual quote: spread access across the disciplines that maintain and consume the data. NEO’s August 2017 explanation makes that argument explicitly, describing one application cost shared across a workplace footprint. Restricting participation could undermine the very connections the product is meant to create.

05Keep the record moving

The copyable practice here is to attach record maintenance to the work itself. Complete a move and update the profile and drawing. Record the equipment where it belongs. Give the people dispatching maintenance access to the same workplace context. NEO’s October 2017 writing describes ongoing verification and correction as part of the design.

That approach depends on participation. As an operational inference, shared software will lose its usefulness if departments continue making changes elsewhere and leave its records untouched. A sensible evaluation would therefore follow one real move or maintenance request from entry to completion, checking who updates what and who can see the result.

NEOWorks makes its case in the small transactions that accumulate around a building. A desk changes occupants. A room needs attention. An asset needs maintenance. Connecting those events is the product’s central proposition. For the teams responsible for making an office function, those little updates are the work.