The Request Tracker Template That Enforces SLAs Before Anyone Asks

Lead: Most request tracker templates give you a queue. Ours gives you a clock. We analyzed the official intake and ticketing templates from Airtable, Notion, and Smartsheet, kept the best idea from each, fixed what they got wrong, and rebuilt the result as a free, open source Baserow template you can download and own outright.

Why most request tracker templates fail the same way

Every team that handles internal requests — IT, HR, facilities, marketing ops — eventually builds or buys a tracker. The tracker promises visibility: see what came in, who owns it, what's done.

The promise holds for about a month. Then the real failure mode appears.

It isn't missing fields or bad views. It's that nothing in the tracker knows how long a request has been sitting. A high-priority request lands on a Monday. Nobody picks it up. By Friday the submitter emails their director. By the following Monday you're in a meeting about "process improvements" that amounts to checking the queue more often.

A request tracker earns its place when it surfaces SLA breaches without anyone checking a queue. That is the standard we used when we rebuilt this category — and it's the test we suggest you apply to any template you evaluate, including ours.

What the big three actually give you

We ran the official intake and ticketing templates from Airtable, Notion, and Smartsheet through our extraction pipeline — same rubric, same review panel, all three scored on demand, reusability, and enterprise readiness. Each one contains exactly one idea worth keeping. None contains all three.

Airtable: the right lifecycle

Airtable's official Issue Tracker formalizes a real intake → triage → resolution lifecycle in priority order. That sounds basic; it isn't. Most templates flatten everything into a status board — submitted items and in-progress items in the same swim lane, sorted by whatever the last person dragged. Airtable's template orders the triage queue by priority, which means the first thing an operator sees is the most urgent unresolved item.

What it's missing: time. There's no SLA or escalation timer. Priority order is manual sorting, not an enforced clock. A "High" request and a "Low" request that both sit for two weeks look identical — neither one complains.

Notion: the right submission UX

Notion's Ticketing System has the lowest-friction submission experience of the three: a clean form that feeds directly into a status board, no login required. The submitter doesn't need a Notion account to file a ticket. That single decision — zero-login intake — is why it actually gets used. Every extra authentication step between "I need help" and "help is requested" is a request that never gets logged.

What it's missing: everything after intake. No priority-based SLA logic. No cross-team routing. No reporting layer. One flat ticket list that collapses at multi-team volume. It's a beautiful front door attached to an empty house.

Smartsheet: the right reporting layer

Smartsheet's Simple Request Intake & Tracking set is the most complete out-of-the-box triage layer of any source we studied: a process map, a request tracker sheet, an "Open Requests by Department" report AND an "Open Requests by Priority" report, plus a management dashboard — all shipped together. It genuinely models triage-by-department and triage-by-priority as two separate first-class views, which is the real definition of this pattern.

What it's missing: enforcement. Reports show priority and age, but there's no SLA-breach flag. A request can sit at "High priority" for weeks with no automatic escalation — only a report a human has to remember to check. And the data model is a single sheet, so departments and requesters are text fields, not linked records.

The three, side by side

Each commercial template wins exactly one column. Ours is the only one with a check in every row.

<!-- COMPARISON GRID: embed content/comparison-grid-request-intake.html here -->

| Capability | Airtable | Notion | Smartsheet | OpenSource AI Pro | |---|---|---|---|---| | Priority-ordered triage lifecycle | ✓ Yes | ✗ No | ✗ No | ✓ Yes | | Zero-login public intake form | ✗ No | ✓ Yes | ✗ No | ✓ Yes | | Department + priority dual reporting | ✗ No | ✗ No | ✓ Yes | ✓ Yes | | Formula-driven SLA breach flag | ✗ No | ✗ No | ✗ No | ✓ Yes | | Relational data model (requests · requesters · departments) | ◐ Partial | ✗ No | ✗ No | ✓ Yes | | Self-host & own your data | ✗ No | ✗ No | ✗ No | ✓ Yes |

Competitor details reflect each platform's public template pages as of July 2026.

The rebuild: all three ideas, one open source template

Our Request Intake & Triage template combines Airtable's priority-ordered lifecycle, Notion's zero-login submission form, and Smartsheet's dual department/priority reporting — built on Baserow, the open source Airtable alternative you can self-host. Then we added the feature none of them ship: an enforced SLA-breach flag.

The Starter edition ships with:

Three linked tables. Departments, Requesters, and Requests — each a real entity. A request links to its department and its requester. Departments aren't a text column; they're records with their own views and rollups.

A public intake form that needs no login. Anyone in the organization can submit a request without a Baserow account. The form creates a row in the Requests table with a timestamp, priority, and department assignment. This is the Notion lesson: if filing a request requires credentials, half of them arrive by email instead.

An SLA breach flag nobody has to maintain. A formula field compares the request's submission date and priority-based SLA hours against the current time. If the clock runs out and the request isn't resolved or closed, the flag fires. It cannot be forgotten, because nobody has to remember to check.

An SLA Breaches view that leads the template. Open the template, click once, see every request that has blown its SLA — across every department, every priority level. This is the view that replaces the "let's go through the queue" meeting.

Working sample data with deliberate breaches. Fifteen requests across four departments — three of them deliberately past SLA, so the breach logic demonstrates itself the moment you open the template.

[VIDEO EMBED: Pattern of the Week — The Intake and Triage Workflow]

What "open source" buys you here

The fair question: Zendesk and Jira have free tiers too. Why does open source matter for a request tracker?

No per-agent-seat pricing. This is where the open source wedge cuts deepest in this category. Zendesk charges per agent. Jira Service Management charges per agent. For a five-person IT team at a 200-person organization, that's a real budget line. Self-hosted Baserow has no per-seat fees at any scale.

Your data stays yours. Request trackers routinely contain PII — employee names, student IDs, patient-adjacent details, client matter numbers. For our readers in healthcare, legal, and higher education, self-hosting means the tracker lives inside your compliance boundary, not someone else's cloud.

The SLA formula is inspectable. The formula that determines what's breached is right there in the field definition. No black box decides your team is "at risk" behind a vendor dashboard you can't audit.

[VIDEO EMBED: Teardown — What Airtable's Issue Tracker Gets Right (and Doesn't)]

How the lifecycle works

The workflow underneath the template is the same one we found, in fragments, across all three commercial tools:

Intake → Triage → Assignment → Resolution → Reporting

The Starter edition implements the spine: a public form feeds requests into a priority-ordered triage queue, an SLA formula flags breaches, and the exception view surfaces everything that needs attention. The Operational edition (coming next) adds a Missing Owner flag, assignment notifications, and department/priority report views. The Enterprise edition adds escalation routing (breach → notify department head), admin-configurable SLA thresholds, and audit trails.

That tiering is deliberate. A template you understand in five minutes gets adopted. A template with an escalation matrix on day one gets abandoned.

Get the Starter template

The Starter edition is free, with working sample data, deployable to any Baserow instance — cloud or self-hosted.

[DOWNLOAD CTA: Get the free Request Tracker Starter template →] (Email-gated download. You'll also get our weekly pattern breakdown — one reusable workflow pattern, every week, no filler.)

Evaluation checklist for any request tracker template

Walking away to build your own, or evaluating another tool? Hold any candidate against these five questions:

1. Does the intake form require a login — or can anyone in the organization submit without credentials?
2. Are requests, requesters, and departments separate linked entities — or one flat list?
3. Does anything flag SLA breaches automatically, or does a human have to notice?
4. Can you see every breached request across all departments in one click?
5. Which of the features above sit behind a per-seat paywall?

The big three each pass one, maybe two. The point of an open source rebuild is to pass all five — and to let you verify that claim by reading the template's own formula.

---

OpenSource AI Pro covers open source tools and AI adoption for higher education, healthcare, and legal teams. The Template Intelligence series analyzes commercial workflow templates and rebuilds the best patterns as open source deliverables.