An account folder per site
Contract and scope, service lines, schedule, visit history, complaints and contacts, in a fixed order.
For owners and operations directors running crews across many buildings: commercial cleaning, facilities services, grounds maintenance, field service. We build the account record, the visit record, the complaint file and the crew instruction into one place, so the work stops living in text threads, a shared drive and one person's memory.
What gets built
The folder has the same sections in the same order every time. A supervisor who has worked one account opens the next one already knowing where everything is. A site starts with nightly cleaning, adds floor care in the spring, drops window work after a budget review, and picks up a second wing when the tenant expands, and the account keeps that history rather than overwriting it.
An account folder per site
Contract and scope, service lines, schedule, visit history, complaints and contacts, in a fixed order.
Service lines that change
Each line carries its own frequency, instruction and start and stop date over the life of the account.
Complaints with before and after
Photographs from when it was raised and after the correction, closed with who verified it.
The instruction to a crew
Short, specific, tied to a site and a visit, recorded as sent and kept in the account history.
Scheduling and visit records
Who is at which building, on which night, for which lines, including what was skipped and why.
Hiring and training records
Applicants, their stage, the documents collected, and the training completed against each person.
An approval queue before sending
Nothing leaves the building without a person reading it, releasing it, and leaving that on the record.
The roles it has to serve
Five people look at the same account for different reasons, and most of them are not at a desk. The screen a person sees is decided by what they are responsible for. Permissions are set once per role and inherited by every account.
The owner or operations director
Every site at once: what is open, what is late, and which accounts have complaints against them.
The account manager
One client's buildings, the scope agreed for each, and the history that explains why it reads that way.
The supervisor
Tonight's buildings and crews, on a phone, with the instruction to send and the photographs to take.
The crew member
What is expected at this site, in the order it is done, with no access to anything commercial.
The office
Scheduling, hiring, training records, and the approval queue that is the only path to an outbound message.
Most of the people entering information are standing in a building at night. Every screen works the same on a phone in a stairwell and on the office desktop, and a photograph is captured and attached in one action.
What it connects to
The build reads and writes real records in them before the connection is called finished.
Accounting and payroll
Hours and visit records out, employee records in, as a reconciliation rather than a second set of books.
Email and calendar
Correspondence filed against the account, schedules published as a feed any calendar reads.
Business phone and messaging
Inbound attached to the site it concerns, outbound held in the approval queue.
Document storage
Contracts, insurance certificates and building documents read in place, from where they already sit.
Sales and pipeline records
A won bid becomes an account folder with its scope populated from what was quoted.
Timekeeping and access hardware
Clock events and building entry evidence matched to the visit record for that night.
Scope, data and delivery
A fixed scope, agreed in writing before anything is built, settled in two conversations.
The first call is a reading of how the operation currently runs: how a site is won, what happens the first night, who hears about a complaint, what a supervisor sends, and which three things cost the most time every week. Nothing is proposed on that call.
The second call is the plan: the scope, the roles, the connections to existing systems, and a working mockup of the real screens in the real design, carrying every button and setting the finished product will have. Changes happen there, before the build starts, because a change at that stage costs a conversation.
Five things are settled in the plan because none of them can be added afterwards without a rebuild: separation of one client's records from another, enforced at the data layer rather than in a screen; what each role may read, write and release, decided on the server; what is kept when a record changes and who changed it; what may be sent and who approves it; and how the operation gets all of its own data back out, readable, on any day it asks.
Client names, building addresses, crew records and photographs are the sensitive part of this sector.
Anonymous by sector
Engagements are described by sector and outcome, and no client of ours is named to another prospect.
Your account, your data
The database and file storage sit in your own environment or a private cloud, with the credentials held by you.
Works offline
A record entered in a basement with no signal is held locally and reconciled when the device reconnects.
Personnel records
Hiring and training files are visible to the roles that need them and to nobody else, supervisors included.
Photographic evidence
Before and after images are stored against the complaint, with the date and the person who captured them.
Nothing sends itself
Automatic sending is off by default, a person releases each message, and the release is recorded.
The first call will tell you what the system should hold. Then how to start: call (252) 666-7217 or email [email protected].