Free Work Order & Maintenance Tracker Template for Baserow

Most facilities teams manage maintenance the same way: a text message to a technician, a sticky note on a monitor, a spreadsheet nobody opens until something breaks twice. It works until it doesn't — and by the time it doesn't, you've lost the paper trail on when the HVAC unit was actually serviced.

This post walks through a free, open-source work order template built in Baserow: a requester submits an issue, it becomes a trackable work order, a technician gets assigned, and a formula field — not a paid automation, not a promise on a marketing page — flags the job the moment it slips past due. Download it, see how it's built, and decide for yourself whether you need the dedicated CMMS bill.

The real cost of "text your maintenance guy"

Ad-hoc maintenance tracking has three failure modes, and most teams hit all three eventually.

Nothing is written down. A verbal request or a text message doesn't leave a record of when the issue was reported, who owns it, or whether it actually got fixed. When an auditor, an insurer, or a new facilities manager asks "when was this last serviced," the answer is a shrug.

Nothing surfaces on its own. A spreadsheet is a record, but it isn't a system. Someone has to remember to open it, scroll through it, and manually notice that a work order from three weeks ago never closed. Most people don't do that reliably, which is exactly why things fall through.

Nothing distinguishes urgent from routine. A cracked light fixture and a failed rooftop HVAC unit look identical in a plain list. Without a due date and a status that a system actually checks, everything competes for the same attention, and the loudest complaint wins instead of the most critical asset.

The dedicated maintenance-management software category — UpKeep, Fiix, MaintainX — solves this well, and honestly. But all three price per technician seat, which means the cost of tracking maintenance scales with your headcount, not your asset count. A five-technician team and a fifteen-technician team are solving the identical structural problem, but one pays three times as much for the same workflow.

What a real work order system needs

Strip away the vendor dashboards and the mobile apps, and a maintenance tracker needs exactly three things to function:

1. A record of the asset — what it is, where it is, and how critical it is if it fails.
2. A record of the work — who reported it, who's fixing it, what state it's in, and when it's due.
3. A way to know, without looking, when something is late.

That third one is where most "free template" options quietly give up.

What the free templates get right — and where they stop

We looked at three of the most-used free work order and maintenance templates before building this one: an Airtable community base, a Notion maintenance request tracker, and Smartsheet's work order template set. Each one gets a real piece of the problem right.

Airtable's maintenance log base ships a genuinely clever idea: when you complete a maintenance task, you stamp the next required service point directly onto the schedule record — mileage-based, in the original, but the same logic works for calendar due dates. It turns a static log into a forward-looking schedule without a complicated recurrence formula. We borrowed that instinct.

Notion's maintenance request tracker frames the problem correctly: stop managing repairs by text message, start managing them as a ticket with a requester, a vendor, and a cost. It's a clean starting shape for intake.

Smartsheet's work order set gets the intake right too — a mobile-friendly capture form so a technician can log an issue from the job site instead of walking back to an office computer.

Here's where all three stop: none of them ship a due-date check that actually works without a paid tier. Smartsheet's automatic notifications and dashboard rollups are Smartsheet-platform features sitting behind a subscription. Notion's "next service due" reminders need a paid automation or a third-party tool wired in. Airtable's base has no due-date concept at all — it's mileage-only. Every one of them describes a system that watches for overdue work. None of them prove it on the free download.

Inside the Baserow Starter template

The template ships three linked tables:

• Assets — the equipment or facility item, with a location and a criticality tier (Low through Critical).
• Technicians — who does the work, with a trade specialty.
• Work Orders — the actual job: linked asset, linked technician, requester name and contact, priority, status, due date, completion date, cost, and notes.

The part that matters most is a single field on Work Orders: Overdue_Work_Order. It's a formula, not an automation, and it fires under exactly one condition — the due date has passed and the status isn't Completed or Cancelled. That second clause matters more than it looks. A naive "is the due date in the past" check would incorrectly flag a job that was finished a day early, or one that was correctly cancelled as a duplicate. Ours doesn't, because we tested it against fixture data built specifically to catch that mistake: a work order completed ahead of its due date, and one cancelled after its due date passed, both correctly stay silent. Two more fixtures — a genuinely overdue "on hold" ticket and a job still comfortably inside its window — round out the proof.

A second formula, Days_Past_Due, turns that flag into a number, so an overdue view sorts worst-first automatically.

Four views come with the Starter: All Work Orders sorted by due date for daily use, Overdue Work Orders filtered to exactly the jobs that need attention, and By Technician and By Asset views for workload and repair-history visibility.

None of it depends on a webhook, a scheduled automation, or a paid tier. Import the file, and the overdue flag is already computing correctly on the sample data — you can watch it work before you've entered a single real work order.

Who actually needs this

This pattern shows up anywhere a team is responsible for physical assets rather than pure IT tickets — a genuinely wide list. A school district tracking HVAC and plumbing across a dozen buildings. A hospital facilities team where a broken refrigeration unit isn't a minor inconvenience. A retail chain managing store-level equipment across dozens of locations. A manufacturing floor where a down machine stops a production line, not just an inconvenienced employee. An office manager juggling everything from a leaking faucet to a flickering conference-room projector.

The common thread isn't the industry — it's the object being tracked. If what breaks is a thing with a location, not a person's login, this pattern fits better than a generic IT help desk tool. That's also why we built it as its own pattern instead of reusing our Request Intake & Triage template: an IT ticket and a broken HVAC unit both start with "someone reported a problem," but everything downstream — the asset record, the technician trade-matching, the criticality tiering — is different enough to deserve its own tables.

How the formula actually reads

If you're new to Baserow formulas, here's the overdue check in plain language, not syntax: "the due date is earlier than today, and the status is not Completed, and the status is not Cancelled." All three have to be true for the flag to fire.

That's the whole rule. No hidden dependency on a scheduled job checking in every hour, no webhook that has to stay configured correctly, no automation platform that needs its own login. Baserow recalculates formula fields whenever the underlying data changes or the page loads, so the flag is always current the moment you look at it. If a work order's due date passes at 2 a.m., you don't have to wait for a nightly automation to catch up — it's already flagged the next time anyone opens the table.

We built the fixture data specifically to stress-test the two easiest mistakes to make in a rule like this. The first mistake: flagging a job that's actually done. Our sample data includes a routine filter change completed a day before its due date passed — if the formula only checked "is the due date in the past," this would incorrectly show as overdue. It doesn't, because the status check catches it. The second mistake: flagging cancelled work. A duplicate ticket, cancelled after its due date already passed, also correctly stays silent. Both of those are the kind of bug that looks fine in a demo and quietly erodes trust in the tool once real data hits it.

Starter, Operational, and Enterprise

The Starter template is free and covers what most small facilities or IT-adjacent teams need on day one: intake, assignment, status, and an honest overdue flag.

Operational adds what a growing team asks for next: technicians become a full table with capacity and skill matching, a preventive-maintenance schedule table, cost tracking tied to each asset so you can start asking "repair or replace," and real notification automations.

Enterprise adds what a compliance-conscious organization needs: role-based dashboards, a cost-threshold approval step before a work order can close, a full audit trail of every status change, and escalation logic for critical-asset failures.

You don't have to buy the top tier to get value — the Starter alone replaces the text-message-and-spreadsheet approach outright.

The per-technician-seat problem, named plainly

UpKeep, Fiix, and MaintainX are legitimate, well-built products. They also all charge per technician, which means your maintenance software bill grows every time you hire a technician, independent of how many assets you actually manage or how much maintenance work exists. A facilities team that doubles its headcount for an unrelated reason — say, expanding into a second building — doubles its CMMS bill for a workflow need that hasn't changed at all.

Self-hosted Baserow doesn't have that constraint. You're not paying per technician, per login, or per seat. The cost is hosting, which scales with your infrastructure choices, not your org chart. For a lot of small and mid-size facilities teams, that's the entire decision.

Get the template

The Starter template is free, gated behind an email so we can tell you when we ship the Operational tier. It comes with the three tables, the overdue formula, sample data you can clear in under a minute, and a README covering both cloud and self-hosted Baserow import.

[Download the free Work Order & Maintenance Tracker template →]

Frequently asked questions

Does this replace a full CMMS? Not the Starter tier, and we're not going to pretend otherwise. It replaces the text-message-and-spreadsheet workflow. Preventive maintenance scheduling, parts inventory, and mobile field apps are Operational and Enterprise territory.

Can I use this without any Baserow experience? Yes. Import the file, and the tables, views, and formula are already configured. No formula-writing required to use it.

What if I outgrow the Starter tier? That's what Operational and Enterprise are for — same underlying pattern, more depth on technician workload, preventive scheduling, and governance.