Industry solution
Every patrol, clean, repair and kilowatt-hour on one record your client can trust
Guard tours, site staffing, housekeeping, maintenance, energy and client reporting, working together for facility and security teams.
The problem
Facility teams deliver security, cleaning and engineering across many buildings with guard tour logs, rosters, cleaning sheets, help desk inboxes and meter exports that never meet, so the monthly client review is rebuilt by hand and argued line by line.
An integrated facility management contract bundles very different work under one set of promises: officers on posts and patrols around the clock, cleaners working to frequencies, engineers answering the help desk and working through planned maintenance, statutory tests in every building, and often an energy target on top. Guarding companies and in-house building teams carry parts of the same load. Each service tends to run on its own tool: a guard tour system, a rostering spreadsheet, paper sign-off sheets on restroom doors, a help desk inbox, a maintenance system, subcontractor portals and utility meter exports.
The trouble is at the seams. A missed checkpoint sits in a report nobody reads until morning. A relief officer arrives with a current license but no site orientation. A restroom sheet says checked while the towels ran out an hour ago. A help desk email waits in a shared inbox while the response clock runs. A building controls schedule left in occupied mode runs the air handlers all weekend.
Margins on these contracts are thin and the work is labor-heavy, turnover among officers and cleaners never stops, and many contracts tie part of the fee to KPIs with service credits for failures. Every month the provider and the client sit down to review performance, and too often the hour goes on whose spreadsheet is right rather than on what to fix.
Contract or Account Director at an IFM provider
Hitting every KPI in the contract, knowing about a failure before the client does, and a monthly review built from records instead of overnight spreadsheets.
Security Operations Manager or Control Room Lead
Every tour completed, every missed checkpoint chased the same night, and incident reports in the client's hands within the agreed window.
Scheduling and Compliance Manager
Every post filled by an officer with a current license and the site orientation (induction), enough rest and hours to spare, even at 05:50 on a Monday.
Soft Services or Housekeeping Manager
Cleaning done to the specified frequency and to real demand, inspections recorded on the spot, and occupant complaints closed before they reach the client.
Hard Services or Engineering Manager
Help desk jobs attended inside their contract clocks, planned maintenance done on schedule, and every deferral carrying its reason and the client's decision.
Client Workplace or Facilities Director
One honest view of service across every building, energy per building against target, and service credits worked out the way the contract says.
A day in the life
Marisol Vega runs Meridane's integrated contract for a life-sciences client's research campus: three buildings and a conference wing, a parking structure, around-the-clock guarding, day and night cleaning, an in-house engineering team and specialist subcontractors. The contract carries sixteen KPIs, an energy target and service credits. This is one ordinary week, and how it would look if the products on this page worked together as designed.
Monday, 05:50
Marisol's phone lights up before dawn: the reception officer is sick, and the scheduler is working down a list of phone numbers. The officer who finally says yes has never worked Linden Park, and by mid-morning the client's lab manager wants to know why a courier was walking the lab corridor alone. In the week this page imagines, the call-out produces a short list of licensed, rested officers who know the site, and the relief officer can ask about the post orders on his phone.
How this is solved: Every post filled by a licensed officer who knows the siteTuesday, 02:19
Marisol hears about the night from the client's security manager, who heard it from a cleaner, two days before Meridane's own report reaches either of them. Nobody on the night shift ignored anything; the system simply told no one until morning. In the imagined week, the control room knows about the missed dock checkpoints within minutes, the officer goes back and finds the door, and the reviewed report is with the client by 09:00.
How this is solved: Missed patrols and incidents the client hears about firstTuesday, 11:05
Three complaints about the Level 2 restrooms reach Marisol through the client's workplace team, forwarded with a pointed note. Soft services manager Hye-jin Park can show a door sheet that says checked, which helps no one. In the imagined week, the restrooms were set to more frequent checks for the event, the first occupant report went straight to the cleaner on that floor, and Hye-jin saw it closed before lunch.
How this is solved: Cleaning to the schedule, and to the needWednesday, 14:20
A lab manager stops Marisol in the corridor to ask why nobody has come about the heat in the west labs; his email reached the help desk log almost an hour after he sent it. By evening her engineering manager, Kofi Addo, is still piecing together why planned tasks slipped in the shutdown week. In the imagined week, the request is logged as it is made, the job reaches an engineer with its clock showing, and every slipped task carries its reason and the client's answer.
How this is solved: Help desk clocks and planned maintenance measured the contract's wayThursday, 09:00
Energy manager Ingrid Larsen spends the morning on meter exports and brings Marisol a number she does not want: Building B is well over last September, and the energy target is slipping. The cause turns out to be a controls schedule nobody switched back after a weekend event. In the imagined week, the jump in night and weekend load was flagged the first Monday, with a work order already on the air handlers.
How this is solved: Energy per building that someone ownsFriday, 10:00
Marisol walks into the monthly service review with a KPI pack her team merged overnight, and within ten minutes Folasade Adeyemi, the client's Head of Workplace, is disputing the priority-one figure. Half the hour goes on whose number is right. In the imagined week, both sides open the same console, every miss lists its records, and the exclusion was requested on the day it happened, with the client's decision waiting for Folasade in the console.
How this is solved: A monthly service review built from records, not spreadsheetsBy Friday afternoon the Linden Park contract looks the same from both sides of the table: posts filled by licensed officers who know the site, patrols and incidents on one record, restrooms cleaned to need, jobs inside their clocks, Building B back on its schedule, and a service review both teams trust. Nothing about the week is dramatic, which is the point: each piece of work lands on a record that the next shift, the client and the next audit can rely on.
Challenges and how they are solved
Each challenge shows the problem as it happens, how the products are designed to hand work to each other, and the concepts that illustrate it. Share any challenge on its own.
Answers are in plain business terms. Choose Technical, or open any technical detail, to see how it works under the hood.
Challenge 1 of 6
At 05:50 on Monday the officer booked for Main Reception in Building A calls in sick; the post opens at 06:00. The scheduler works through a spreadsheet of phone numbers. The first officer who agrees holds a current security license, but he has never completed the Linden Park site orientation (induction), has just finished a twelve-hour night shift on another contract and has not read the post orders. Nobody checks that the post calls for first aid certification. At 08:15 he admits a courier to the Building B lab corridor, which the post orders say needs an escort. Meanwhile two other officers on the contract hold licenses that expire this month, and the only record of it is a spreadsheet column nobody has sorted.
Unqualified cover puts the client's site and the contract at risk, an expired license can mean an officer who must not work, and relief officers who do not know the post orders make avoidable mistakes.
When an officer calls in sick, CrewFoundry is designed to list officers who hold a current license, have done this site's orientation, are rested and have hours to spare, and offer them the shift on their phones. Licenses about to expire are flagged weeks ahead. On the post, Botlit answers the relief officer's questions from the site's own post orders and passes anything else to the supervisor.
Technical detail
CrewFoundry is designed to hold each site's posts by shift with their requirements (license class, site orientation, current post orders read, first aid, key control) beside every officer's licenses and certificates with their expiry dates. When a call-out is logged, it is designed to rank relief officers who meet the post's requirements, have had the minimum rest since their last shift, are within working-hour limits and are not already booked, offer the shift to their phones, and flag expiring licenses weeks ahead. The site orientation runs as a CrewFoundry learning path, so completion is a recorded fact. Once the relief officer accepts, the confirmed roster is designed to pass to the FluidGrids tour checks and to IntelWatchtower, so the control room knows who is on each post and tour. On the post, Botlit is designed to answer the officer's questions from the site's approved post orders, cite the section it used, and send anything the orders do not cover to the supervisor.
Posts are designed to be filled by officers who are licensed, oriented to the site, rested and within their hours, and relief officers get the site's post orders on their phone instead of guessing.
CrewFoundry
Shows every post across the next 24 hours with its requirements, flags the open reception post, expiring licenses and officers short of rest, and ranks relief officers by license class, orientation, post orders read and rest.
Works with IntelWatchtower, Botlit
CrewFoundry
Runs the site orientation and refresher training as a learning path with certificates, so an officer's orientation for this site is a recorded completion the roster can check.
Botlit
Answers only from the knowledge it has been given, cites the source and says so when the answer is not there; here that knowledge would be each site's approved post orders.
Challenge 2 of 6
The Building C night tour, C-N2, has twelve checkpoint tags. At 02:15 a delivery driver flags down officer Tariq Haddad at the gate, and he never reaches the loading dock: checkpoints C-07, C-08 and C-09 are missed. The guard tour system records it, but its exception report is read by the day supervisor at 07:00. At 02:26 the access control system logs a door-held-open alarm on fire exit DK-03, which the control room operator acknowledges without linking it to the tour. At 06:40 a cleaner finds DK-03 wedged open with a pallet. The incident is written into the paper daily activity report, typed up two days later, and reaches the client's security manager as a scanned page after she has already heard about it from the cleaning supervisor.
Gaps in patrols go unnoticed until damage is done, incident reports reach the client late and in inconsistent formats, and the provider loses the client's confidence over events it actually handled.
FluidGrids checks each patrol against its route and tells the control room in IntelWatchtower that night when checkpoints are missed or an officer's check-in is overdue, next to any nearby door alarm. Officers report incidents through a simple form on their phone, a supervisor reviews the report, and the client gets it on time. Damage found on patrol goes to the maintenance team.
Technical detail
FluidGrids is designed to receive checkpoint scans from the existing guard tour system and door alarms from access control, by webhook or by reading their exports on a schedule. A scheduled FluidGrids workflow, using if and compare steps, is designed to check the scans against each tour's checkpoint list and due times, and when checkpoints are missed, a tour runs late or an officer's check-in is overdue, to raise an IntelWatchtower alert carrying the missed checkpoints and any nearby door alarm as observations. IntelWatchtower holds the alert in the control room queue and the incident as a case with a timestamped record; the officer's account and photos come in through a FluidGrids form designed to open that case, and the client report moves from draft through supervisor review to released inside the contract's window. A defect found on patrol is designed to go to AssetHandler as a repair work order, and the officers on each tour come from the CrewFoundry roster.
Missed checkpoints are designed to be chased the same night, and every incident is designed to reach the client as a reviewed report, on time and in the same format.
IntelWatchtower
Holds the alerts FluidGrids raises for missed checkpoints and overdue check-ins on one control room board by site, and follows each incident from the officer's report to a released client report.
Works with FluidGrids, CrewFoundry, AssetHandler
IntelWatchtower
Built for energy sites, this map and timeline of perimeter alarms, patrol reports and guard reports shows the kind of picture a control room needs across many guarded client sites.
FluidGrids
Webhook and schedule triggers like these are designed to take in checkpoint scans and door alarms, and to run the scheduled check of every tour against its checkpoint list.
Challenge 3 of 6
The cleaning specification for Building A says restrooms are checked every two hours, recorded on a sign-off sheet on the back of each door. On Tuesday the training suite hosts 140 people. By 11:00 the Level 2 restrooms are out of paper towels and soap; three occupants email the client's workplace team, who forward the complaints to the provider. The sheet says checked at 10:00, and the cleaner is on the far side of the building following her fixed route. At month end the soft services supervisor walks twenty areas with a clipboard for the cleaning audit, re-keys the scores into a spreadsheet, and finds a pass rate below the contract target with no way to see which areas keep failing.
Fixed routes miss real demand, paper sign-offs cannot be trusted, complaints travel through the client before they reach a cleaner, and audit failures repeat because nobody can see the pattern.
AssetHandler is designed to replace the sheet on the restroom door with a quick scan on the cleaner's phone, so everyone sees which areas are done and which are overdue. Occupants scan a poster to report missing towels or a spill, and FluidGrids sends the job to the cleaner on that floor with a target time. Monthly inspections use the same areas, and failed items go back for cleaning.
Technical detail
AssetHandler is designed to treat each cleanable area (restroom, kitchenette, meeting room, lab write-up space) as a location with a QR tag, to run each cleaning frequency as a recurring checklist on that area, and to record each clean as a scan on the cleaner's phone, replacing the door sheet. A supervisor can raise an area's frequency for an event day, and missed frequencies show on the board as they happen. A report-a-problem QR poster in each restroom opens a FluidGrids form; the workflow is designed to create a reactive cleaning task against that area in AssetHandler, notify the cleaner on shift for that floor as named on the CrewFoundry roster, track the task against a target time and escalate to the supervisor if it slips. Monthly audits are designed to run as inspection checklists on the same QR-tagged areas, where a failed item raises a re-clean work order, and area-by-area results are designed to reach BigConsole for the client review.
Cleaning is designed to follow both the specification and real demand, with every clean and inspection recorded against its area and occupant reports closed without passing through the client.
AssetHandler
Lists every area by floor with its cleaning frequency, last scan and next due time, flags missed frequencies, and shows occupant reports and inspection results beside the schedule.
Works with FluidGrids, CrewFoundry
FluidGrids
Built for hospital room cleaning, this workflow raises a cleaning request, tracks it against a target time and escalates when it slips; the same pattern is designed to handle a restroom report.
Challenge 4 of 6
The contract's priority matrix gives every help desk job three clocks: response, attendance and fix. At 14:20 on Wednesday a lab manager emails that the west labs on Level 3 of Building B are at 27°C, a priority-two job that must be attended within two hours. The email waits fifty minutes in a shared inbox, and the only HVAC engineer on site is across campus on a planned filter change. Planned maintenance has its own gap: eleven lab-area tasks slipped during the client's shutdown week, only four carry a written reason, none has the client's sign-off, and the fire damper subcontractor's visit on September 9, when access was refused, is recorded only in the subcontractor's own portal. At month end planned maintenance completion falls short, and nobody can show which misses the client caused.
Response clocks run out in an inbox, the wrong engineer is sent or none at all, and planned work the client prevented counts against the provider because nobody recorded why it slipped.
Botlit is designed to take a request from any occupant at any hour and log the job at once. AssetHandler shows each job with its contract deadlines, and FluidGrids sends it to an engineer on shift with the right trade or to the right contractor. Planned work is tracked against its schedule all month, and any task that slips carries its reason and goes to the client for a decision.
Technical detail
Botlit is designed to take occupant requests in workplace chat or web chat, ask for the building, floor and problem, and trigger a FluidGrids workflow that logs the job in AssetHandler against the exact asset, here air handler AHU-B3. AssetHandler holds each job with the contract's priority and its response, attendance and fix clocks. FluidGrids decision rules are designed to route it by trade and building to an engineer on shift in CrewFoundry, or to the named subcontractor, whose attendance is recorded on the work order. Planned maintenance, statutory tests included, runs from AssetHandler preventive schedules with checklists, so completion against the schedule is visible all month. When a planned task cannot be done, the deferral is designed to be recorded on its work order with a reason, evidence and a new date, and a FluidGrids approval step is designed to send it to the named client approver for sign-off.
Help desk jobs are designed to reach a qualified engineer with their clocks visible, and every slipped planned task is designed to carry its reason, evidence and the client's decision.
Botlit
Built for residents, this agent triages repair requests day and night and links each one to an AssetHandler work order; here it is designed only to take the request from an office or lab occupant.
AssetHandler
Built for city resident reports, this board matches each report to its asset, links it to one work order and assigns a crew; the same pattern is designed to take a help desk request against air handler AHU-B3.
AssetHandler
Puts planned maintenance on a calendar with scheduled, overdue and completed counts, so completion against the schedule is visible during the month rather than discovered at month end.
Challenge 5 of 6
The contract carries an energy reduction target. On Thursday the energy manager builds September's report from a utility portal, half-hourly meter exports and a building controls trend log, and finds Building B up 18 percent on last September. After a morning of digging she traces it to a time schedule switched to occupied mode for an event on Saturday, September 5, six weeks earlier, and never switched back: two air handlers have run nights and weekends ever since. The sub-meter for the conference wing stopped reporting on the 12th, so the client's chargeback for it will be estimated. None of this was visible until month end, and none of it reached the engineering team as work.
Waste runs for weeks before anyone sees it, meter gaps turn into estimates and disputes, and the energy target is missed for reasons that were fixable on the first day.
EcoImpactHub is designed to show energy use per square meter for every building, how much is used at night and on weekends, and which meters have stopped reporting. FluidGrids brings in the meter readings. When a building starts using power after hours, the engineers get a job in AssetHandler that week, not at month end, and refrigerant top-ups count toward the same carbon totals.
Technical detail
FluidGrids is designed to read half-hourly main and sub-meter readings from metering and building management system (BMS) exports and record them in EcoImpactHub as measurements for each building. EcoImpactHub is designed to show energy per square meter by building, the share used outside occupied hours against each building's baseline, and meters that have gone quiet, and to convert electricity and gas into Scope 2 and Scope 1 lines in the carbon ledger. When night and weekend load rises above baseline, its threshold is designed to raise an alert that a FluidGrids workflow turns into an AssetHandler work order on the air handlers and the controls schedule. AssetHandler's sustainability figures already draw on EcoImpactHub metrics, and the work order is designed to carry a link back to the flagged building in EcoImpactHub. Refrigerant top-ups recorded on HVAC work orders are designed to reach the same ledger as Scope 1 entries.
After-hours waste is designed to reach an engineer within days, meter gaps are caught before they become estimates, and energy and refrigerant figures share one ledger per building.
EcoImpactHub
Ranks buildings by energy per square meter and after-hours share, flags silent meters, and links unusual night and weekend load to the AssetHandler work order raised for it.
Works with AssetHandler, FluidGrids
AssetHandler
Turns each refrigerant top-up recorded on an HVAC work order into a Scope 1 entry for EcoImpactHub and flags units that keep leaking.
Challenge 6 of 6
On Thursday night the contract team merges six exports into the September KPI pack: help desk jobs, planned maintenance completion, the guard tour vendor's PDF summary, the cleaning audit spreadsheet, the incident log and the staffing fill rate. At the Friday review the client's Head of Workplace questions the priority-one figure. One elevator entrapment was attended in 74 minutes against a one-hour target because the client's own security escort was late, which the contract treats as an exclusion, but the note is buried in an engineer's email. Planned tasks in the lab suite show as late because the client closed it for a shutdown week. The service credit is argued line by line, and half the hour goes on whose number is right rather than on what to improve.
Reporting eats the contract team's time, disputed figures wear down trust, and service credits are settled by argument instead of by the contract and the records.
BigConsole is designed to keep every measure in the contract up to date through the month, with FluidGrids gathering the teams' records every day. Each missed target shows the jobs or patrols behind it. When the client caused a miss, the team asks for an exclusion with evidence, FluidGrids sends it to a named person at the client, and the console shows the decision and the credit.
Technical detail
FluidGrids is designed to write the month's records into BigConsole data sinks on a schedule, at least daily: job clocks, planned maintenance completion and cleaning inspection results from AssetHandler, tour completion and incident report times from IntelWatchtower, and post fill and license status from CrewFoundry. An exclusion is designed to be requested on the AssetHandler job or the IntelWatchtower tour record, with its evidence; a FluidGrids approval workflow, started from a form and paused on a wait step, is designed to route it to the named client approver and write the decision to a data sink. BigConsole is designed to hold the contract's KPI set as configured, show which KPIs were met or failed with the records behind each failure, display each exclusion's status, apply the configured service-credit rule, and be shared read-only with the client's workplace team, scoped to their contract.
Provider and client are designed to review the month from one shared set of figures, with failures, exclusions and service credits traceable to the records behind them.
BigConsole
Traces each failed KPI to its failure events and the credit under the contract's rule, and shows every exclusion request with its evidence, requester and the client's decision.
Works with AssetHandler, IntelWatchtower, FluidGrids
FluidGrids
Ends each workflow in a BigConsole data sink, so job clocks, patrol results, staffing, inspections and client decisions land in the review console on a schedule rather than in a monthly export.
How it fits together
One week of work followed across the products: a call-out becomes a qualified relief officer, a missed patrol becomes an alert and an incident, a damaged fire door becomes a timed repair, and every record lands in the console that provider and client review together. The steps show how the products are designed to hand work to each other.
To FluidGrids: Who is on each post and patrol tonight
To IntelWatchtower: A control room alert about the missed dock checks
To AssetHandler: A repair request for the damaged fire exit door
To FluidGrids: The finished job and its response times
To BigConsole: Current figures for every measure in the contract
To Botlit: The live contract results, ready for questions
Step 1 of 7: Fill the post
Technical detail
Products in this solution
Maintenance, housekeeping and compliance records
Designed to keep one record for every piece of building equipment and every area to be cleaned: repair jobs with their contract deadlines, planned maintenance, cleaning checks scanned on a phone, and certificates for statutory tests.
Technical detail
Designed to hold every building asset and cleanable area as a QR-tagged record with preventive schedules and checklists, run help desk jobs with the contract's clocks, keep certificates by building and send refrigerant top-ups to EcoImpactHub, whose metrics its sustainability figures already use.
Licensed, site-ready officers on every post
Designed to show which posts are covered, whose license is about to expire and who has done each site's orientation, and to offer an open shift to the right people when someone calls in sick.
Technical detail
Designed to hold posts by site and shift with their requirements, each officer's and cleaner's licenses and certificates with expiry dates, site orientation as learning paths, and to rank relief staff for a call-out by eligibility, rest and hours.
Security control room picture across sites
Designed to give the control room one live list of missed patrol checkpoints and door alarms across sites, and to turn each incident into a reviewed report the client receives on time.
Technical detail
Designed to hold the missed-checkpoint and door alarm alerts that FluidGrids tour checks raise in one prioritized control room queue by site, run each incident as a case with a timestamped record, and move the client report from draft through review to release.
Checking patrols and moving records between systems
Designed to check every patrol against its route, pass door alarms, meter readings and occupant reports from the systems you already run to the right product, and send each job and client decision to the right person.
Technical detail
Workflows are designed to take guard tour scans, access control alarms and meter readings by webhook or scheduled export, check each tour against its checkpoint list, run incident, restroom and exclusion approval forms, route jobs, and feed BigConsole data sinks.
Contract KPI and service credit console
Designed to show every measure in the contract against its target all month, with the records behind each miss and the credit that follows, and to give the client the same view.
Technical detail
Consoles over FluidGrids data sinks are designed to score each contract KPI against its configured target, list the failure events behind each miss, show each exclusion's client decision, apply the configured service-credit rule and be shared read-only with the client.
Energy per building and the carbon ledger
Designed to show how much energy each building uses per square meter, how much of it runs at night and on weekends, which meters have gone quiet, and what it all means for carbon.
Technical detail
Designed to record meter readings per building, show energy per square meter and after-hours share against baseline, flag silent meters, and convert electricity, gas and refrigerant into Scope 1 and 2 ledger lines.
Answers for officers, occupants and clients
Designed to answer relief officers from the site's post orders, take repair requests from building occupants at any hour, and answer the client's questions about the month using the actual figures.
Technical detail
Agents are designed to answer only from approved knowledge such as post orders and building guides, log help desk requests from chat, and query the KPI console so a client's question is answered with cited figures.
All seven products run on Burdenoff Workspaces: one sign-on for officers, cleaners, engineers and managers, role-based access so clients and subcontractors see only their own sites, one audit trail across patrols, jobs and reports, and one bill.
Concept gallery
15 concepts from 7 products. Each one links to its own page on the product's website, and every view has a link you can share.
CrewFoundry
Shows every post across the next 24 hours with its requirements, flags the open reception post, expiring licenses and officers short of rest, and ranks relief officers by license class, orientation, post orders read and rest.
Works with IntelWatchtower, Botlit
CrewFoundry
Runs the site orientation and refresher training as a learning path with certificates, so an officer's orientation for this site is a recorded completion the roster can check.
Botlit
Answers only from the knowledge it has been given, cites the source and says so when the answer is not there; here that knowledge would be each site's approved post orders.
IntelWatchtower
Holds the alerts FluidGrids raises for missed checkpoints and overdue check-ins on one control room board by site, and follows each incident from the officer's report to a released client report.
Works with FluidGrids, CrewFoundry, AssetHandler
IntelWatchtower
Built for energy sites, this map and timeline of perimeter alarms, patrol reports and guard reports shows the kind of picture a control room needs across many guarded client sites.
FluidGrids
Webhook and schedule triggers like these are designed to take in checkpoint scans and door alarms, and to run the scheduled check of every tour against its checkpoint list.
AssetHandler
Lists every area by floor with its cleaning frequency, last scan and next due time, flags missed frequencies, and shows occupant reports and inspection results beside the schedule.
Works with FluidGrids, CrewFoundry
FluidGrids
Built for hospital room cleaning, this workflow raises a cleaning request, tracks it against a target time and escalates when it slips; the same pattern is designed to handle a restroom report.
Botlit
Built for residents, this agent triages repair requests day and night and links each one to an AssetHandler work order; here it is designed only to take the request from an office or lab occupant.
AssetHandler
Built for city resident reports, this board matches each report to its asset, links it to one work order and assigns a crew; the same pattern is designed to take a help desk request against air handler AHU-B3.
AssetHandler
Puts planned maintenance on a calendar with scheduled, overdue and completed counts, so completion against the schedule is visible during the month rather than discovered at month end.
EcoImpactHub
Ranks buildings by energy per square meter and after-hours share, flags silent meters, and links unusual night and weekend load to the AssetHandler work order raised for it.
Works with AssetHandler, FluidGrids
AssetHandler
Turns each refrigerant top-up recorded on an HVAC work order into a Scope 1 entry for EcoImpactHub and flags units that keep leaking.
BigConsole
Traces each failed KPI to its failure events and the credit under the contract's rule, and shows every exclusion request with its evidence, requester and the client's decision.
Works with AssetHandler, IntelWatchtower, FluidGrids
FluidGrids
Ends each workflow in a BigConsole data sink, so job clocks, patrol results, staffing, inspections and client decisions land in the review console on a schedule rather than in a monthly export.
Pitch kit
Facility and security providers deliver patrols, cleaning, maintenance and energy savings across many buildings, then rebuild the proof by hand every month. Burdenoff brings together rostering of licensed officers who know each site, a security control room picture, housekeeping and maintenance records, energy per building and a shared service credit console on one sign-in and one record of who did what. The products are designed to:
Questions
No. The products are designed to work alongside the systems you already run, taking in the patrol scans, alarms, meter readings and jobs those systems can already export. Which systems to connect, and in what order, is worked out during scoping.
Technical detail
No. The design is to work alongside them. FluidGrids workflows are designed to receive webhooks and read exports from guard tour systems, access control, building management systems and meters through FluidGrids' HTTP, database and code nodes, then pass the data to IntelWatchtower, AssetHandler, EcoImpactHub and BigConsole. Where a help desk or maintenance system stays in place, its jobs can be read for the KPI console. Which systems to connect, and in what order, is worked out during scoping.
Yes, that is the design. You can give each client a read-only view of only its own sites and results, and send reviewed incident reports within the agreed time. You choose what each client sees, and shared views are offered under each product's own name.
Technical detail
That is the intent. BigConsole consoles can be shared view-only with named people or groups, and a view scoped to one contract is designed to show only that client's sites and figures. Incident reports are released to the client from IntelWatchtower after supervisor review. What each client sees is configured per workspace, and shared views are offered under each product's own name.
No. Botlit is designed to answer only from the post orders and building guides you approve. It is designed not to give safety or emergency advice of its own, and to pass those questions, and anything else, to a supervisor or the control room. It does not replace training or your procedures.
Technical detail
No. Botlit is designed to answer only from the post orders and building guides you approve and to cite the section it used. It is designed not to give security, safety or emergency advice of its own, and to hand such questions, and anything else outside the approved material, to the supervisor or control room. It does not replace site orientation, training or your escalation procedures.
BigConsole is designed to follow the targets and credit rules set up for each contract, and to show every miss with the records behind it. Exclusions, such as a delay the client caused, are requested with evidence, FluidGrids sends them to a named person at the client, and the console shows the decision. The contract still decides.
Technical detail
BigConsole is designed to apply the KPI targets, measurement rules and service-credit rules configured for each contract, and to show each failure with the records behind it. An exclusion, such as a delay caused by the client, is requested on the AssetHandler job or the IntelWatchtower tour record with its evidence. A FluidGrids approval workflow is designed to route it to the named client approver and record the decision, which BigConsole then displays and applies to the credit. The console supports the review; the contract and the people who sign it decide.
Yes, by design. The same setup works whether your officers, cleaners and engineers are your own staff or contractors. Work is organized by site and building, the live results can track your internal service targets, and contractors see only the work given to them.
Technical detail
Yes, by design. The same records work whether officers, cleaners and engineers are employed directly or by contractors: AssetHandler, CrewFoundry and IntelWatchtower organize work by site and building, and a BigConsole console can track internal service levels instead of contract KPIs. Workspaces provides one sign-on and role-based access, so contractors see only the work assigned to them.
Not as a finished package. The products are at an early stage and most are pre-launch. This page describes how they are designed to work together, and several screens shown are new concepts. A pilot would start with one site or contract and one or two of the challenges above.
Technical detail
Not as a finished package. The products are at an early stage and most are pre-launch, and this page describes a solution concept for how they are designed to work together for facility and security services. Several screens shown, such as the guard tour exception watch, the post coverage roster and the service credit ledger, are new concepts. A pilot would be scoped around one site or contract and one or two of the challenges above.
Related domains
Finance & BusinessChallenges solved
A solution concept for property businesses that connects listings, leases, maintenance, permits and portfolio yield across eight Burdenoff products on one shared record.
TechnologyChallenges solved
A solution concept for security operations centers, intelligence analysts and multi-agency teams that combines eight Burdenoff products, from fusion to partner release.
Industry & OperationsChallenges solved
How Burdenoff products are designed to work together for trades contractors: calls triaged and booked, the right technician sent, every unit's history on hand, every part billed.
Tell us about your setup. We will walk you through the products involved and scope a pilot around the challenge that hurts most.
This is a solution concept: it shows how Burdenoff products are designed to work together in this industry. The images are illustrations of the concepts, not screenshots of the actual products, and every name and figure in them is sample data.
