No products in the cart.
The storeroom is on the far side of the building, the SDS is in a binder in the office, and the person who knows what that machine costs to fix is on vacation. All three are on the phone in your pocket, attached to the room they belong to.
FacilityGuardYour whole building, on your phone, on every shift of the year.
The service is a census and a tag on every door. The product is what shows up on your phone
Five signals. Every room. On a screen your staff already carry.
CI FacilityGuard captures the building once — approved products, safety data sheets, equipment, storage rooms, shutoffs, vendors, task cards — and then puts that record on a phone, a tablet and a browser. Stock against par, SDS completeness, preventive maintenance due, corrective actions ageing, seasonal readiness. Every record arrives with the state it is supposed to be in. Alerts arrive with what to do next. The log writes itself.
The record already exists in most buildings. It exists in a binder that is one revision behind, a spreadsheet on one laptop, a text chain, and the memory of the person who has been there longest. It is reachable during office hours by people who know where to look, which is roughly forty hours out of every one hundred and sixty-eight, and not at all on the night shift. Almost every expensive facility event — the rush order, the wrong product on a finished floor, the machine down for two weeks waiting on a manual, the audit finding, the resignation that takes twenty years with it — happens inside that gap.
Now · the record lives in a binder and a person
With FacilityGuard · same staff
- Hold the approved product list, SDS library, equipment registry, building facts, inspections and task cards in one record, reachable from any phone in the building.
- Open the right record from a QR tag on a door, a closet, a dispenser or a machine — without a login hunt or a menu tree.
- Watch par levels, PM dates, corrective-action age, SDS currency and seasonal windows, and raise the item before it becomes an event.
- Prepare the reorder — exact product, package size, approved substitute, reasoned quantity — and hold it for a manager’s approval.
- Generate the operating record: who did what, where, when, with which product, and what the closure evidence was.
- Control anything. Nothing in the app starts a machine, opens a valve, changes a setpoint, or places an order without a person approving it.
- Replace a CMMS or an enterprise work-order platform on a plant that already runs one well.
- Certify compliance. It makes safety documentation reachable; it does not perform your hazard assessment or your training.
- Encourage substitution. Where a product is out, only approved alternatives for that surface and that task are shown.
- Replace the operator’s judgement. It shortens the distance between a condition and a decision.
FacilityGuard is a record and reminder service. It has no control authority over building systems. There is no button in the app that changes how the facility runs. Physical operation, contractor direction, hazard assessment and emergency response remain with the facility manager and the owner.
Three moments in the same building, as they arrive on the phone
Pick a moment. The screen and the next move both change.
This is the working surface. Not a document library and not a CMMS shrunk to fit — a single scrollable list of what the building needs right now, ordered so the thing that requires a decision is at the top. Most mornings it says nothing needs you. That is the point of it.
Screens, product names and values shown are representative of a mid-size institutional building. Actual par levels, approved products, alert routing and approval rules are set per site at the census against that building’s own record.
The site is named the way the staff name it, with the age of the last update beside it. If a record has not been touched since a product changed, the header says so rather than presenting a stale par level as current.
Every line shows what it is and where it stands. EverClear Bio means nothing to a relief custodian at 22:00. EverClear Bio · 0.5 case · below reorder point is a decision.
An open condition appears directly beneath the record that caused it, in the colour of its severity, with the sentence an operator needs. Everything else stays quiet. There is no wall of red badges to learn to ignore.
Front-line staff never navigate a menu tree. The tag on the door is the query. A closet, a machine, a dispenser or a drain opens its own record in about four seconds, with no login hunt.
Status is carried by a labelled pill and a border, not by colour alone — readable under bad lighting, in sunlight at a loading door, and by staff with colour vision deficiency.
Approving a reorder or closing a corrective action writes a name, a timestamp and, where required, a photo. That line is what answers the question a year later about who knew what, and when.
- Building status with every item’s state, one screen, no configuration.
- QR scan opens the room, closet, machine or dispenser record instantly.
- Current SDS, PPE, dilution and spill response on the product in your hand.
- Push alerts with the response steps inside the notification.
- Approve, modify or deny a reorder in one tap; the log records who and when.
- Photos and closure evidence captured in the room where the work happened.
- All buildings side by side with status at a glance.
- Usage by product and by room, reorder history, and cost per building.
- Inspection score trend by zone, and corrective-action closure times.
- Repair spend by asset, with the replacement recommendation attached.
- Report generation and export for audits, budgets and contract review.
- Role-based access for staff, supervisor, manager, viewer and auditor.
The browser view is where the quarter gets explained and the review gets made
Same record, more room. Built for the desk, the trend and the budget.
The phone answers what needs me now. The dashboard answers what has been happening, and what do I change. Multi-building portfolios get a rail with a status colour against every site, so the first thing a manager sees on Monday is which building has moved and which have not.
| What the console is showing | Why it belongs · manager note | |
|---|---|---|
| 1 | Every building on one screen | A status colour against each site in the rail, so a six-building portfolio is read before any single number is. The one that needs attention is the one that is not green. |
| 2 | Cards carry the verdict, not just the count | Each measure shows its value and its state. A warning card changes its border and its label; it does not rely on the manager remembering that three open actions with one ageing is different from three fresh ones. |
| 3 | One banner for the open condition | The same rule as the phone. The item that needs a decision sits above the trends with its age and its escalation point in the sentence. |
| 4 | Trends read together, not one at a time | Products below par and open actions on one 30-day frame, because the shape of the pair is the diagnosis. Stock discipline improving while corrective actions climb is a staffing problem, not a purchasing one. |
| 5 | Everything on the screen exports | The same view becomes a CSV, a PDF, or a formatted review pack. Nothing is retyped into a spreadsheet to become a report to the owner. |
Usage velocity against expected use, cost per square metre, reorder frequency by product, closure time by owner, repair spend by asset, and season-over-season comparison are calculated from the same records the phone writes. Raw lists ask the manager to do the correlation by hand, from memory. Derived measures do it in advance.
Administrator, manager, staff, viewer and auditor roles, with multi-factor authentication. Sensitive building facts — shutoff references, access notes, high-risk rooms — are permission-controlled. An auditor can be given a read-only account against a defined period instead of being handed a folder of screenshots.
An alert that does not say what to do is a louder version of the problem
Condition, consequence, first moves, expected closure. Four parts, every time, in that order.
Most facility software fails here. It pushes a badge and a count to somebody who is driving, and the staff learn to dismiss it. FacilityGuard notifications are written to be acted on by a competent operator who is not a chemist, who may be holding a mop, and who may be reading a lock screen in a truck at the loading door.
Reorder point crossed · Meltdown de-icer · 1 pail on hand. Freeze forecast Monday. Suggested 4 pails, exterior shed. Tap to approve, change or deny.
Weekly summary ready · Riverbend Centre.
Lite delivers by email. Core adds app push. Managed adds SMS and the escalation ladder. Integrated adds routing by role across sites. Whichever channels a building carries, the four-part wording is identical, so a person reads the same thing on a lock screen, in an inbox, and in the console.
A safety-record alert — a product in active use with no current SDS attached — is not a housekeeping item. It is delivered on every channel the tier supports, the product is locked from reorder until it is resolved, and it stays open until a named person closes it. This is the only signal where the correct response to uncertainty is to stop using the product.
Meltdown liquid de-icer has fallen to 1 pail against a par of 4 and a reorder point of 2, six days ahead of the usual November crossing.
The forecast shows a freeze on Monday. A de-icer stock-out during the first freeze produces a slip exposure at the entrances, an emergency purchase at retail pricing, and staff improvising with whatever bagged product is in the shed.
- Approve the prepared reorder for 4 pails, or change the quantity if the forecast has moved.
- Check the entrance mat plan and the walk-off coverage before the first event, not after it.
- If delivery cannot land before Monday, use the approved substitute shown on the record — not the nearest bag on the shelf.
Approved before Monday, the order lands on the scheduled delivery and no emergency purchase is made. If usage is running above the par level three seasons running, the par is wrong, not the staff.
“Expected closure” is what separates a useful alert from an anxious one. It tells the person whether this is an emergency, a watch item, or a normal feature of the building nobody had written down. It is also what stops the Saturday call-out that did not need to happen.
| SignalWhat it watches | WarningWatch and diagnose | CriticalAct now | First moveBefore reaching for a product | Escalate only if… |
|---|---|---|---|---|
| S1Stock against par | At or below reorder point | Below reorder point with a seasonal event forecast, or two consecutive rush orders | Approve the prepared order, or ask why usage moved before raising the quantity. | The same product crosses early three periods running — the par level is wrong, not the staff. |
| S2Safety record | SDS older than the supplier’s current revision | Active product with no SDS attached, or an unapproved product found in use | Attach the current sheet, or remove the product from the active list and tell the people using it. | The product is in daily use and the gap is not closed the same week. |
| S3Equipment | PM due inside 7 days, or a second fault inside 90 days | PM overdue, or the asset is out of service | Open the asset record. Manual, warranty status and last repair before anyone calls a vendor. | Repair spend on one asset passes the replacement threshold set at the census. |
| S4Follow-through | Corrective action open past its deadline | Open past deadline on a safety or slip item, or a third repeat in the same zone | Confirm the owner still owns it. Most late actions are unassigned, not refused. | Median closure time climbs across two quarters. That is a workload problem. |
| S5Seasonal readiness | Readiness window open with the checklist unstarted | Forecast event inside 72 hours with items unstocked | Pre-stage the products and the tools. Check storage before ordering more of what is already there. | The same season catches the building twice. That is a calendar fix, not a purchasing one. |
Five signals decide whether a building is being run or being chased — and nobody is standing there when they move
Five signals. Six records. One census.
The screens above are only as good as what is behind them. Six records carry five signals: stock, safety, assets, follow-through and season. Each is banded against this building’s own usage and its own history, not a textbook. Tap a zone on the section drawing to see what it covers.
Entrances, mats, ice and salt residue carry the risk. Pre-stage de-icer and rinse before the first freeze — Meltdown and SaltRinse.
Salt film, grit and dull finish arrive together. Neutral cleaning and finish repair, not stripping — check dilution before adding product.
Heat moves drains and organic load into the complaint window. EverClear Bio on a schedule beats a counteractant after a call.
HVAC start-up, coil cleaning, mat plans and winter stock. The readiness checklist opens before the first event, not after it.
Seasonal problems are the most predictable events in a building and the most reliably handled late. The difference between a readiness window that opens on the record and a note in someone’s calendar is that the record knows what is already in the shed, what was used last season, and which entrance generated the slip report.
A product recommendation that arrives without usage history, a photo, or a repeat count is a guess with a logo on it. FacilityGuard exists so that the conversation with your CI representative starts from what the building actually did last quarter — which rooms failed twice, which product usage moved, which asset is costing money — and the chemistry follows from that.
The quarter ends and the review is already written
The second product is the file, and it is the one that is worth the most a year later.
Every scan, reorder, approval, inspection, photo and closure is retained for the term of the tier. The review pack is generated from that record rather than assembled by hand from a clipboard, a spreadsheet and a memory of what the quarter was like. What used to be a week before the audit is a download.
What the record has to survive is a question asked a year later.
Under WHMIS, an employer must ensure that a current safety data sheet is readily available to workers who may be exposed to a hazardous product, and to anyone responding on their behalf. CCOHS is explicit that computer access satisfies this where workers have access to the device, know how to use it, and the equipment is kept in working order. In the United States, OSHA’s Hazard Communication Standard uses the same behavioural test — readily accessible during each work shift, with electronic access permitted where nothing stands between the worker and the sheet.
FacilityGuard is built to that standard rather than around it. The sheet is attached to the product record, the product record is attached to the room, and the room carries a tag. The worker holding the container reaches the sheet from where they are standing. What the file then adds is the part that is normally missing: what was used, where, by whom, on what date, at what dilution, and what the closure evidence was.
A digital SDS library supports your obligations. It does not perform your hazard assessment, your worker training, or your inspections. Confirm your obligations against your jurisdiction’s OHS legislation and your own program.
What a quarterly review pack contains.
Building name, account, reporting period, and the census baseline the targets were set against at launch.
Products at or below par, reorder history with approver and reason, rush orders, usage by product, and any par level the data says is wrong.
SDS completeness, products locked from reorder, PM completed on time, repair spend by asset, and replacement recommendations.
Inspection scores by zone, repeat zones flagged as bad actors, corrective actions with owners, deadlines, closure times and evidence.
Hosted in Canadian cloud regions, with handling aligned to Canadian privacy legislation.
TLS 1.3 in transit, AES-256 at rest, with device-level authentication for the app.
Administrator, manager, staff, viewer and auditor roles, with multi-factor authentication on management accounts.
Transaction records held one to five years; usage and issue trends retained longer for season-over-season comparison.
The app records, reminds and prepares. It does not operate building systems and it does not place an order without a person approving it.
Integrated sites can push records into an existing CMMS, ERP or reporting system through a secure API.
Research on workplace knowledge consistently finds that a large share of what a person knows about their job is unshared with any coworker, and that staff lose hours every week finding information or recreating what already exists. In a building, that is the shutoff nobody can locate, the machine nobody can identify, and the product nobody can name. A record that survives a resignation is not a filing improvement. It is the difference between onboarding a new custodian in a week and in a season.
No sensors, no trenching, no control panel — a tag on every door and a census that takes a day
The part of the service that is not on a screen.
FacilityGuard has no field instrument to install. What it needs from the building is a walkthrough and a tag. A CI technician walks the site with the facility manager, captures the rooms, products, storage locations, equipment and the recurring headaches, and leaves behind a tag on every door, closet, dispenser and machine that matters. The constraint that matters here is not accuracy. It is that a label has to survive a janitorial closet, a mechanical room, an exterior shed at −35°C, and being wiped down with a quat every day for five years.
| Component | Specification | Why it is specified that way |
|---|---|---|
| 1 | Location tagLaminated polyester QR label, permanent acrylic adhesive | Roughly 50 × 50 mm, or 25 mm for dispensers.Survives daily disinfectant, floor stripper overspray, and a wet mop handle. Paper labels in a janitorial closet last one season. |
| 2 | Asset tagAnodised aluminium or polyester, serialised | Rated −40°C to +80°C.Machines live in mechanical rooms, on loading docks, and in exterior sheds. The tag has to read in February with a glove on. |
| 3 | Placement standardEye height, inside the door frame, same position in every room | Consistency is the feature.Staff should never hunt for the tag. Same height, same side, every room, so scanning becomes reflex rather than a task. |
| 4 | DeviceAny current iOS or Android phone or tablet with a camera | No dedicated hardware to buy, charge or lose.The service runs on the phone staff already carry. A shared building tablet is available where personal devices are not used. |
| 5 | ConnectivityWi-Fi or cellular; records cached on the device | Capture continues where signal does not.Mechanical rooms, basements and freezer rooms are exactly where the record is needed and the signal is worst. Entries sync when the device comes back into coverage. |
| 6 | SecurityRole-based accounts, MFA on management roles, permission-controlled building facts | Shutoffs and sensitive zones are scoped, not published.A building record is useful because it is complete, which is exactly why access to parts of it is controlled. |
| Capture | What it covers | Typical count · mid-size building | Time on site |
|---|---|---|---|
| Rooms and zones | Storage rooms, janitorial closets, mechanical spaces, restrooms, kitchens, laundry, exterior zones | 25–60 tagged locations | 2–3 hours |
| Products | Approved product list with storage location, use case, dilution, par level, package size and substitute | 40–90 active products | 2–3 hours |
| Safety records | Current SDS, PPE, storage separation, spill response and handling notes attached to each product | 1 per active product | Assembled off site |
| Equipment | Autoscrubbers, extractors, vacuums, dispensers, pumps, snow tools, HVAC service items | 15–50 assets | 1–2 hours |
| Building facts | Floor areas, shutoff references, drains, sump areas, high-risk rooms, vendors, access notes | 1 record per building | 1 hour |
| Recurring headaches | The rooms, drains, entrances and machines that come up every year, with what has been tried | 5–12 named items | Interview |
For buildings that reconfigure rooms or add equipment often enough that waiting on a tag order becomes the reason a record goes stale.
Where personal devices are not used for work. Mounted in the janitorial office and carried on inspection walks.
Down to individual dispensers and refill points, for sites where consumption is the number that keeps surprising the budget.
Time-boxed, read-only accounts scoped to the areas a contractor works in — task cards and SDS without the building facts.
There is no power to run, no penetration to make, no network to commission and no panel to certify. The census is the install. That is deliberate: the failure mode for facility software is not a bad sensor, it is a rollout that takes six months and is abandoned in month four with half the rooms entered.
Four levels — what changes is coverage and cadence, not whether the service works
Every tier includes the census, the tag set, onboarding, app access and CI technical support.
A single hall with one closet and a good caretaker does not need what a school division with fourteen buildings and an approval policy needs. The record structure and the app are the same in all four tiers; what moves is how much of the building is captured, how much the system watches on your behalf, how long the record is kept, and how much of the review is generated for you.
| Capability | LiteProduct vault and SDS discipline | CoreThe standard building deployment | ManagedActive management discipline | IntegratedMulti-site and contract-ready |
|---|---|---|---|---|
| Records captured | Products, SDS, storage locations | Plus equipment, manuals, building facts | Plus inspections, task cards, issue history | Plus cross-site standards and contract records |
| QR tags | — | Rooms, closets, machines and dispensers | Full tag set with task cards at point of use | Standardised tag scheme across all buildings |
| Stock and reorder | Par levels and reorder quantities | One-touch reorder with manager approval | Approval rules, usage review, seasonal pars | Approval routing by role and by site |
| Watching on your behalf | Low stock and SDS gaps | Plus PM due dates and asset faults | Plus corrective-action age and seasonal windows | Plus cross-site exceptions and standards drift |
| Alert channels | Email and app push | Email, push and SMS with escalation | All channels, routed by role and site | |
| Inspections | — | — | Checklists, scores, photos, corrective actions | Standardised templates with site comparison |
| Reporting | Data export | Monthly summary | Quarterly review pack with trends and closure times | Custom reporting, budget and contract formats |
| Record retention | 1 year | 2 years | 3 years | 5 years |
| Buildings covered | Single building | Single building | Up to three buildings | Unlimited, with portfolio dashboard |
| API access | — | — | — | Secure REST API for CMMS, ERP and portal integration |
| CI review cadence | Annual product review | Semi-annual review with scheduled delivery | Quarterly review with recurring-issue report | Quarterly by site, with programme management |
| Technical support | Business-hours email | Business-hours phone and email | Priority phone and email | Dedicated account manager |
The graveyard of facility software is full of systems that did everything and got used for nothing. Buyer research consistently finds that satisfaction tracks with proving value in a scoped trial rather than a full rollout, and the adoption data shows the gap is never the software — it is whether the team actually lives in it. Lite exists so the record earns its way into the daily routine instead of demanding it. We would rather earn the second tier than sell it.
How much of your building can actually be looked up right now?
Enter your real numbers. The readout is arithmetic, not a sales estimate.
The number that decides whether this service is worth anything to a building is not a price. It is how many hours a week the building’s own record can be opened by the person who needs it, and how much time is currently spent finding what already exists. Put your own numbers in and the tool returns the coverage arithmetic, the tier that matches the site, the record set that goes with it, and the CI360 lanes worth pre-staging for the conditions you selected.
Set the four numbers on the left, tick whatever is true about the building, and the readout will show how much of the week the record can currently be opened against what an app-first record would produce.
This is a screening calculator, not a quotation or a design. The information-time figure uses a conservative fifteen minutes per person per working day, which is well below the published research on time lost finding internal information. Record scope, tag placement, par levels, approval rules and service scope are confirmed against the actual building during the census.
Rooms, closets, mechanical spaces, exterior zones and the recurring headaches, captured before a single par level is argued about.
The approved list is what this building actually uses, stored where staff actually look. A master catalogue dropped in whole is how a vault becomes ignored.
Par, reorder point, package size and approved substitute per product, agreed with the manager. A threshold nobody agreed to is a threshold nobody will act on.
Who requests, who approves, who can override, and what happens to an unacknowledged item. Decided before the first alert fires.
Same height, same side, every room. A supervised go-live week removes the alerts that fire on normal building behaviour — this is where alert fatigue is prevented.
Task cards, thresholds, contacts and building facts recorded where the next person will find them, which is the entire point of the exercise.
Hours a week the record can be opened by whoever needs it. This is the number the service exists to move, and it should reach 168.
Active products carrying a current sheet. The target is 100% within thirty days of the census, and it does not drift if reorder is locked behind it.
Emergency purchases for par-managed products. Should approach zero once reorder points are set; if it does not, the par is wrong.
Corrective action raised to closed with evidence. A rising median usually means workload, not indifference.
Scheduled maintenance done on or before the due date. The leading indicator behind every repair-spend number you will look at later.
How long a new staff member takes to work unsupervised from the task cards. The clearest test of whether the record is real.
CI SupportLab™ FacilityGuard is a facility operations service guide, not a substitute for site-specific engineering, hazard assessment, worker training, or the judgement of the person responsible for the building. Application screens shown are illustrative representations of the operator interface; layout, values, product names and alert wording are configured per site. Record scope, thresholds, approval rules and service scope are confirmed per building during the census and commissioning. A digital SDS library supports WHMIS and OSHA Hazard Communication obligations; it does not replace hazard assessment, training, or your written program. Confirm all product dilution, dosage and handling against current labels and SDS before use. Product names follow the Chem International catalogue; linked names open the product page on chemintonline.com.
Want to know what your building looks like before you drive in?
A site census covers rooms and storage, the approved product list, SDS currency, equipment and manuals, building facts, approval rules and the recurring headaches — and returns a scoped deployment for your exact building.