FireCert Clock

How FireCert Clock works: one site's week

A contractor and a facilities manager share one clinic. Here is the week, and who opens the list.

Property managers and HSE teams each get a starting page. Facilities teams can track the building they occupy.

A contractor and a facilities manager share one clinic. The contractor already writes the inspection reports. The manager already keeps the binder. The miss is the next date: an extinguisher that was serviced in March and nobody booked October, an emergency light discharge that needs after hours labor, a hood ticket that sat in a cab. FireCert Clock is the dated list for that clinic. It is not a dispatch board, a quote, or a filing service.

FireCert Clock does not lodge a statement with a council and does not sign a certificate. You confirm every date. The authority having jurisdiction still sets the interval.

One site, Monday to Friday

Monday the contractor creates the site and names it the way the manager already says it: the street, not a job number. Eighteen extinguishers come in from a CSV, or they are typed if the list is short. Each row gets a type, a location, and an interval. US presets follow common NFPA patterns. UK presets follow common BS patterns. If the local rule differs, the interval on the asset is the one that is used. The product does not decide the code.

Tuesday last year's report PDF is uploaded on the visit. On Free, the service date is typed. On Starter and above, the product reads dates off the PDF and the person at the keyboard confirms them before they become the schedule. Confirming is the point. A wrong read should not move a due date quietly. A report that prints both the work date and a suggested return needs a human to pick which one is last service.

Wednesday the lead tech subscribes to the iCal feed in Google Calendar, Outlook, or Apple Calendar. The feed is the work list. There is no separate dispatch board and no truck routing. Thursday's buildings show up as calendar rows because the assets are due, not because someone built a route.

Thursday the 30 day notice for an annual emergency light discharge arrives. That is enough time to book after hours labor. A monthly 30 second light test cares more about the 7 day, 3 day, and 1 day notices, because the window is short. Both dates can exist as separate assets so the annual does not hide behind twelve monthlies. Notices run at 30 days, then 14, 7, 3, and 1. Those marks are the same on every plan.

Friday anything still past due sits on the overdue list until someone logs a passing visit. Logging a failure on your own sheet does not clear the row. The site PDF lists each asset, last service, next due, and status, with the uploads attached. That PDF is what you hand to a manager or a fire marshal instead of flipping a binder for February.

What each day uses

DayAction on the clinicPlan that includes it
MondayCreate one site, add up to 25 assets, pick NFPA or UK presets, type a local intervalFree, $0 a month, 1 site, 1 seat
TuesdayUpload the report and type the service dateFree
TuesdayRead dates from the PDF and confirm them before they saveStarter, $39 a month, and above
WednesdaySubscribe to the iCal feedFree, and every paid plan
ThursdayEmail notices at 30, 14, 7, 3, and 1 day to the account ownerFree
ThursdayThe same notices to one building contact, plus Slack or TeamsStarter and above
FridayOverdue list and the site PDFFree
FridayBranded client report with your logoPro, $79 a month, 50 sites, 5 seats
Any dayAPI and CSV export of sites, assets, visits, and due datesBusiness, $149 a month, 15 seats, no site or asset cap

Free stops at one site and 25 assets. Starter is 10 sites and 500 assets, still one seat. Pro is 50 sites with no asset cap. Business has no site cap and no asset cap. Yearly billing is the monthly price times 10: $390, $790, and $1,490. The dollar amounts are the published plan prices. Adding a seat does not change them. Adding a site does not change them until you cross a cap.

Who does what

The office coordinator uploads the PDF. On Starter, that person confirms the dates read from it before they become the schedule. The lead technician subscribes to the calendar feed and does not need a dispatch board to see Thursday's buildings. The facilities engineer who walks monthly lights cares about the 7 day, 3 day, and 1 day notes, because a 30 day interval leaves a short window. The owner opens the overdue list and the site PDF before a fire marshal visit. The client contact, from Starter, receives the notice and does not get a login unless you add a seat.

Free and Starter include one seat. Pro includes five. Business includes 15. A seat is a login. A client email address is not a seat. The wording of that email is fixed: asset, site, task, location, and due date. You do not write a custom campaign. Slack and Teams start on Starter, on the same plan as client email and AI date reading. AI date reading proposes fields from the PDF. It does not file anything and it does not replace the confirm step.

Contractors use the list when the field work already produces a PDF and the miss is the next date. Facilities teams who occupy the building use the same sites and assets. The account does not have to belong to a service company. It is a weak fit when every technician needs a tablet form, a quote, and an invoice in the same login. Those jobs stay in the field service tool you already run. The due date can still live here beside it.

What FireCert Clock does not do

It does not lodge an Annual Fire Safety Statement, a Form 3, a building warrant of fitness, or a Fire Certificate. It does not sign as the accredited practitioner, the installer, the owner, or the responsible person. It does not pick the later of two statutory dates unless you type both and confirm the one that applies. It does not send a technician, raise an invoice, or hold stock.

The jurisdiction pages are the place to read the local shape of the date, and then come back and type the confirmed day on the asset:

Each of those guides says the same limit in local words. You keep the date. You upload the paper you already have. You do not ask the product to lodge or to sign.

How a second asset keeps a short interval honest

The clinic's emergency lights are the clearest split. The annual full duration discharge needs a booking, a key holder, and a dark hour. The monthly functional test is a walk with a key. If both live on one asset, the monthly pass can look like the annual is done. Two assets, two intervals, two sets of notices. The annual still gets the 30 day mail. The monthly still gets the late marks. The overdue list shows them as separate rows, so a green monthly does not paint the annual green.

The same split applies to a kitchen hood. Suppression service and grease duct cleaning are different visits, often different companies, often different months. Put suppression on one asset and cleaning on another. The hood page on the site can link them in a note. The schedule should not collapse them into one next date. A certificate that covers only the canopy should not close the duct row.

Extinguishers follow the same habit. Hydrostatic test years are not the annual service year. A six year maintenance is not a monthly visual. When the preset interval is wrong for the building, change the number on the asset and write why in the note. The next person should see the reason without calling you.

What the owner sees on Friday

The overdue list is the only queue that matters at the end of the week. A row stays until a passing visit is logged. A failed visit stays too, because a failure is not a pass. The site PDF is the handoff: every asset, last service, next due, status, and the files you attached. On Pro that PDF can carry your logo. On Free and Starter it is still the same list, without the brand block.

If the manager asks for the hood and the lights in one email, you send the PDF. You do not rebuild a spreadsheet. If a date on the PDF disagrees with memory, the confirmed date on the asset wins, and the note can say the memory differed. The product will not silently prefer the read it proposed on Tuesday.

Business adds the API and a CSV export when a portfolio is too large to click through. The API lists sites and assets, logs visits, and exports due dates. It is the same data as the Friday PDF, available to a system you already run. It still does not lodge and it still does not sign. Pricing for that column is on the pricing page, in the Business row.

Set the clinic up on Free if one site and 25 assets cover the list. Move to Starter when the building contact should get the mail, or when you want dates read from the PDF. Move to Pro when five people need a login or the report should carry your logo. Move to Business when the site count passes 50 or another system should read the due dates. The week itself does not change. Monday is still the list. Friday is still the overdue rows.

Set up a site free

Set up a site free