FireCert Clock

One inspection calendar across many sites

Several buildings stay on one account. Each address is a site. Each task is an asset. The feed and the overdue list are the calendar.

A facilities team with a campus, a retail park, or a handful of leased warehouses usually inherits one binder per building and one shared sheet that nobody owns. The binder is what a marshal can hold in the riser room. The sheet is what a regional manager hopes is current. They disagree by March. One inspection calendar means one account where every address is a site, every repeating task is an asset with a next due date, and the people who walk those buildings subscribe to a feed instead of copying dates into a personal diary.

The single-building Monday walk is a different note, on the facilities page. This note is the portfolio: how the dates stay in one list when the team covers more than one address, and how a technician sees only the assets assigned to them.

One site per address

Name the site with the street address the authority already uses. A campus can be several sites when each building has its own marshal visit, or one site when one report covers the whole campus. Pick the shape that matches how you are asked for records. Do not invent a site per trade. Extinguishers, the panel, the lights, and the valves at one address belong on that address, as separate assets, because their intervals differ.

The overdue list for the account is every asset whose next due is before today, oldest first. The asset list for one site is ordered by next due, then by name. You do not maintain a second wall calendar. If a date changes, it changes on the asset. The list on Monday is whatever the assets say that morning.

A technician record produces a calendar feed at /ical/ plus that technician's token. The feed is a calendar file. Each event uses the asset's next due date. The summary is the preset task plus the asset name, or the asset name alone when no preset matches. The description is the location. Subscribe that URL in the calendar app the technician already opens. Assign the asset to the person who will do the work, or the feed stays empty for them and full for nobody.

There is also an account option labeled "Email me a monthly list of upcoming and overdue inspections." When it is on, the monthly message counts sites, overdue assets, and technician calendars, then lists overdue names and dates, up to 40 lines. It is a summary to the account owner. It is not the technician feed, and it does not list every future visit.

A portfolio counted on three presets

These three dates are illustrations from presets already stored in the product. They are not a survey of a real campus.

Quarry Road, wet-system gauges, preset NFPA 25 quarterly tasks, 91 days. Last gauge check 6 January 2026. Adding 91 days lands on 7 April 2026. Notices for that asset leave on 8 March 2026, 24 March 2026, 31 March 2026, 4 April 2026, and 6 April 2026.

Mill Lane, emergency lights, preset BS 5266 monthly functional test, 30 days. Last flick test 2 February 2026. Adding 30 days lands on 4 March 2026. The longest notice offset used by the product is also 30 days, so the first note falls on 2 February 2026, the same day you logged the test. The remaining notes fall on 18 February 2026, 25 February 2026, 1 March 2026, and 3 March 2026. On a 30 day task, treat the shorter notes as the ones that still help. The 30 day note is telling you about work you just recorded. That is a property of matching the interval to the longest offset, not a fault in the building.

Harbour House, fire alarm, preset BS 5839-1 alarm servicing, 182 days. Last service 3 November 2025. Adding 182 days lands on 4 May 2026. Notices leave on 4 April 2026, 20 April 2026, 27 April 2026, 1 May 2026, and 3 May 2026. The alarm servicing note is where that 182 day figure is explained. On the calendar it is simply one asset at Harbour House, beside the lights and the gauges at the other addresses, in the same overdue list.

None of these three spans needs a leap-day correction inside 2026. If you add a 365 day asset whose span includes 29 February, read the stored next due instead of assuming the anniversary. The product adds the day count you saved.

Who can see which building

Free stops at one address. A second building needs a paid plan. Starter, Pro, and Business differ by how many sites and seats they include, and Business is the plan that adds API access and CSV export. The figures are on pricing. Buy seats for people who must sign in. Buy sites for addresses. Do not share one login across the regional team and call that a calendar.

Client contacts are not seats. A landlord who should receive the same notices can be a contact on Starter without a login. A technician who should see a feed needs a technician record, which is not the same thing as a seat that can edit every site. Give edit access only to people who may move a date.

Import is how a portfolio arrives in one afternoon. The CSV needs a site, an asset type, a location, and a last service date. Rows that omit those fields are rejected. After import, open a sample of assets and confirm the preset. A last service date without the right interval produces a next due that looks precise and is wrong. Export of the full asset list, and the API, start on Business. Until then, the screen and the site PDF are the record you can hand someone.

Keeping one calendar after the import

The failure mode is the old sheet staying editable. Someone helpful updates the sheet after a contractor visit and forgets the asset. Next month the feed and the sheet disagree, and the team believes the sheet because it was open. Close edit access on the sheet, or replace it with a PDF snapshot, the day the import finishes. New visits get logged on the asset: upload the report, confirm the service date, let the next due move.

Vendor rotation is the other failure. The outgoing company takes its portal with it. Your account should already hold the PDFs on the visits. The incoming company gets a technician feed and, if you want them mailed, a client contact. They do not get to be the only copy of the history.

The templates hub is where the blanks live: report pack, alarm report, log book, extinguisher checklist, and the due date calculator. Print what the building still wants on paper. The calendar is the due date, not the blank. A filled PDF attached to the asset is how the paper and the feed stay about the same visit.

Blanks do not dispatch anyone. The feed does not dispatch anyone either. It shows the next due date for assets assigned to that person. The supervisor still decides who rolls. If an asset has no technician, it still appears on the account overdue list. Assign it when you know who will go.

A week on the portfolio

On Monday the account owner opens the overdue list, not three binders. Anything dated before today is late, oldest first. Anything inside the coming notices is already in someone's mail: 30 days out, then 14, then 7, then 3, then the day before. The owner does not retype those into a diary.

The technician opens the subscribed feed and sees events titled with the task and the asset, described with the location, dated on the next due. Quarry Road gauges, Mill Lane lights, and Harbour House alarm appear for whoever is assigned, even though the presets differ. Unassigned work stays with the owner.

After the visit, the report goes on the asset that matches the task. Logging the Harbour House alarm does not advance Mill Lane lights. Logging a gauge check does not advance a five-year internal on the same wet system. If those tasks exist, they are additional assets with their own presets. The sprinkler schedule is the place those NFPA 25 tasks are split. The calendar only works if that split already happened.

When a new building is leased, add a site before the first contractor visit, even if you only know three assets. A building that waits for a perfect inventory never joins the list. Add the rest when the survey comes back. Twenty-five assets is the free cap, and it is also easy to pass on a single large floor if you split monthly and yearly tasks. Watch the cap before you promise every trade a row.

What the calendar will not decide

It will not choose the code edition. Presets are starting intervals: NFPA 10, NFPA 25, NFPA 72, NFPA 101, BS 5306-3, BS 5839-1, and BS 5266, plus a custom day count when you type one. The authority having jurisdiction can be stricter. Edit the interval on that asset. The feed updates to the next due you stored.

It will not merge two companies' portals by itself. Recreate sites, import the CSV, attach historical PDFs by hand. The first month looks thin if last year's files stayed in the old portal. Spend the afternoon uploading the files an auditor will ask for, not only the dates.

It will not replace a monitoring centre, a dispatch board, or an invoice. Those stay where they are. The calendar answers a narrower question: which task, at which address, is due next, and who is assigned.

When the portfolio should live in one list, create a free account and add the first address. Import the rest when the plan has room for those sites.

Related guides

FAQ

How many addresses fit on each plan?

Free holds 1 site. Starter holds 10. Pro holds 50. Business has no site cap. Asset caps differ: 25 on Free, 500 on Starter, and no asset cap on Pro.

What shows on the technician feed?

Events for assets assigned to that technician. The date is the next due. The summary is the preset task and the asset name. The description is the location.

Which CSV columns does import require?

Site, asset type, location, and last service date. A file missing those fields is rejected. Confirm the preset after import so the next due uses the interval you intend.

Why does a monthly task mail on the day I logged it?

The longest notice is 30 days before the due date. A 30 day interval makes that first note land on the service day you just saved. The 14, 7, 3, and 1 day notes are the ones that still fall later in the month.

Create a free account

Set up a site free