Blog ·
Jira for construction: site checks and the inspection calendar
Jira for construction works best in the office behind the site rather than on the site itself. Estimating, submittals, change requests, equipment maintenance, safety inspections and permit renewals are all work that moves between people and has a due date, which is exactly what Jira tracks well. What Jira does not do is replace a dedicated construction management platform for drawings, daily logs and field reporting. This guide sets up Jira for the work it suits, then makes the recurring inspection and maintenance calendar arrive as tickets on its own, so a check never depends on one person's memory.
If you are still deciding whether Jira belongs in your firm at all, there is a section near the end on when another tool is the better call.
Where Jira fits in a construction firm #
Most construction firms already run several systems: accounting, a scheduling tool for the programme, a document platform for drawings, and often a field app for crews. Jira earns its place in the gaps between those, where a request has to pass from one person to another and someone has to see it is stuck.
| Job | Where it lives in Jira | What repeats |
|---|---|---|
| Preconstruction | A project per bid, or one estimating project | Bid deadline checklists, supplier quote chases |
| Submittals and RFIs | One work item per submittal or request | Weekly status review with the design team |
| Change requests | A change project with an approval status | Monthly change log for the client |
| Safety | A safety project | Weekly site inspections, toolbox talks, monthly audits |
| Plant and equipment | An equipment project, one item per machine | Service intervals, inspection certificates |
| Office and compliance | An operations project | Insurance renewals, licence renewals, training refreshers |
Two or three projects cover most small and mid-sized contractors. One for live jobs, one for safety and equipment, one for running the business. More than that tends to produce boards nobody opens.
Set it up in six steps #
- Create one team-managed project for live jobs, using the Kanban template. Give each construction project its own epic, and each submittal, RFI or change request its own work item under it. Team-managed projects let the project managers change statuses without a site admin.
- Create a safety and equipment project. Every machine, vehicle or piece of plant that needs servicing gets a label or a component, so you can filter by it.
- Create an operations project for the office: insurance, licences, HR, IT, finance. Split the areas with labels rather than more projects.
- Keep workflows short. To do, In progress, Waiting on others, Done. Submittals may need a Review status for the design team, but resist adding one per stakeholder.
- Turn on due dates and assignees. Every filter below relies on them, and in construction a date with no owner is a date that slips.
- Decide who needs access. Site supervisors often only need the safety project. Subcontractors usually should not see your change log or your bids.
Leave custom fields, complex permission schemes and automation until a real problem asks for them.
Filters the project manager actually opens #
A board shows everything. A busy project manager needs to know what is due this week and what has slipped. Three saved filters do most of the work:
| Filter | JQL | Who opens it |
|---|---|---|
| Due this week | due <= 7d AND statusCategory != Done ORDER BY due |
Project managers, every Monday |
| Overdue | due < 0d AND statusCategory != Done |
Operations manager, daily |
| Waiting on others | status = "Waiting on others" ORDER BY updated |
Whoever chases the design team |
Subscribe the operations manager to "Overdue" every morning. A filter subscription is a free early warning, and it catches the item that nobody wants to raise in the site meeting. The Jira dashboard examples show how to put the same filters on one page for the weekly review.
The inspection calendar that lives in one person's head #
This is the part construction firms struggle with most. Live project work is visible because people are doing it every day. The checks that come round every week, month or year are not, and they usually belong to whoever did them last time. Typical recurring work:
- Weekly: site safety inspection, scaffold inspection, toolbox talk, programme review with the client.
- Monthly: fire extinguisher and first aid kit checks, vehicle checks, a safety audit, the change log for each client.
- Quarterly: equipment servicing on most plant, a review of risk assessments, subcontractor insurance certificates.
- Yearly: lifting equipment inspection certificates, company insurance renewal, trade licence renewals, training refreshers.
A missed inspection is not an admin slip. It can stop a site. When these checks live in a spreadsheet or a supervisor's diary, they disappear the week that person is on leave or moves to another job. As tickets with due dates and owners, they show up in the filters above like any other work. The question is how they get there each cycle.
| Approach | Effort each cycle | What goes wrong |
|---|---|---|
| Clone last cycle's ticket by hand | Someone clones and redates it | The person who remembers is the system |
| Create a year of tickets up front | One long afternoon each January | Sites open and close, the list goes stale |
| A Jira Automation scheduled rule | None, once the rule exists | Each run spends the automation allowance |
| A recurring-issue app | None, once the schedule exists | One more app on the site |
Cloning by hand #
For two or three checks, cloning works. When the ticket closes, clone it and set the next due date. It fails quietly, because nobody notices a ticket that was never created.
Jira Automation #
As of October 2026, Jira Automation's Scheduled trigger can create a work item on a fixed interval or a cron expression. That suits a handful of simple schedules such as "every Monday". Calendar rules such as "the first working day of each month" need cron, which the Jira cron expression guide walks through. Every run spends from the site's monthly automation allowance, and the Jira Automation pricing guide explains how that is counted.
A recurring-issue app #
This is the approach we build for. Recurring Work Items for Jira lets you write each schedule once, in one project, and from then on the ticket appears by itself. For a construction safety and equipment project that means:
- daily, weekly, monthly and quarterly rules, with working-day and holiday handling, so a Monday inspection never lands on a public holiday when the site is closed;
- dynamic titles, so the inspection arrives as "Scaffold inspection, week 42" rather than a copy of last week's title (the token reference lists them);
- subtask checklists, so "monthly safety audit" arrives with its steps already listed;
- a run history that says what was created, skipped or failed, and why.
It runs its own scheduler, so it does not spend your Jira Automation quota, and it is scoped to the projects you turn it on in, so the safety calendar does not spill into the live jobs board. It is free for up to 10 users. See how a rule is set up.
A starter calendar for a small contractor #
A concrete set of schedules to copy into the safety and operations projects. Adjust the days to your own sites, your own plant and your local regulations, which this table does not replace.
| Ticket | Schedule | Owner | Subtasks |
|---|---|---|---|
| Site safety inspection | Every Monday, per active site | Site supervisor | Walk the site, log hazards, photograph, sign off |
| Toolbox talk | Every Monday | Site supervisor | Pick the topic, deliver, record attendance |
| Vehicle and plant checks | First working day of the month | Plant manager | Check list per machine, raise defects |
| Fire and first aid check | Monthly | Office manager | Extinguishers, kits, signage |
| Subcontractor insurance | Quarterly | Commercial manager | Request certificates, check dates, file |
| Lifting equipment certificate | Once a year, per machine | Plant manager | Book the inspector, file the certificate |
| Insurance and licence renewals | Once a year, a month before expiry | Director | Quote, approve, renew |
Give every recurring ticket a named owner, not a team. A ticket assigned to "Safety" is assigned to nobody. For the IT and admin side of the office calendar, see Jira for IT operations, and for the money side, Jira for finance. If the checks themselves are long, the Jira checklist template guide covers where the steps should live.
When Jira is the wrong tool #
Jira is a good fit for the office and a poor fit for some of the field work. Look elsewhere, or alongside it, when:
- the job is drawings and document control. A construction document platform manages revisions and markups far better than attachments on a ticket;
- the main users are crews on site with a phone. Field apps built for daily logs and photo reports ask far less of people in gloves;
- you need the programme as a Gantt chart with critical path. Jira's timeline is useful for planning work, but a scheduling tool built for construction programmes handles dependencies and float properly;
- nobody will own the board. Without someone closing stale tickets each week, Jira becomes a graveyard within a quarter.
If those describe most of your work, keep Jira for the recurring checks and the office requests, and let the specialist tools run the rest.
Summary #
For a construction firm, Jira works best kept small: one project for live jobs, one for safety and equipment, one for running the business, three filters and one owner per ticket. The recurring inspections and renewals are what keep sites open and insurers happy, so make those tickets arrive on their own, by Automation rule for a few simple schedules, or with a recurring-issue app when the calendar grows. For a fuller comparison of the options, read our guide to Jira recurring tasks.