Get marketing insights first
Subscribe for actionable strategies, growth tips and useful industry insights, delivered straight to your inbox.
Field Systems Brief
Issue 01 · Construction Operations
Jira Service Management × Construction
From site issue to closed loop
A practical operating blueprint for turning defects, RFIs, safety incidents, approvals, breakdowns and handover requests into visible, accountable, SLA-driven work.
Explore the request catalog
12-minute field guide
The blueprint
10 request pathways · 4 domain desks
The brief
One intake layer across the construction lifecycle
Jira Service Management works best here as the front door and governance layer—not as a replacement for scheduling, BIM, cost control or document management.
Give every request a clear owner, a visible clock, an auditable decision trail and an agreed definition of done.
10
core request types
4
recommended domains
1
portfolio view
1
Simple at the portal
Request types use field language—“Report a site defect” or “Request a permit”—instead of system jargon.
2
Structured behind the form
Location, discipline, trade, severity, evidence and due dates give agents enough context to act without chasing basics.
3
Governed by workflow
Queues, approvals and status gates mirror the real construction process while preserving accountability.
4
Measured by outcomes
SLAs and dashboards expose ageing work, bottlenecks, repeat defects and emerging risk before the weekly meeting.
The operating model
One request, five controlled moments
The portal is only the beginning. Value appears when the request moves through a dependable path from evidence to verified closure.
01
Capture
A focused form records the right facts and supporting evidence.
02
Triage
Queues sort by project, trade, risk, critical path and response clock.
03
Coordinate
Ownership, approvals and notifications pull the right parties into the work.
04
Verify
Inspection evidence and sign-off prevent “resolved” from becoming “forgotten”.
05
Learn
Dashboards reveal delay patterns, repeat issues and systemic corrective actions.
The request catalog
Ten pathways that cover the work
Each pathway pairs a plain-language portal request with a fit-for-purpose work type, minimum workflow and response promise.
01
Incident
Site defect / punch-list item
Capture non-conforming work with exact location, responsible trade, severity, drawing reference and mandatory photo evidence.
02
Service request
Request for information
Link the technical question to its drawing revision, discipline, required-by date and potential cost or schedule impact.
03
Change
Design change / variation
Control scope, cost and program changes with impact assessment, conditional approvals, instruction evidence and reconciliation.
04
Incident
Safety hazard / near miss
Prioritise immediate action, risk rating, witnesses, regulatory notification, root cause and verified corrective action.
05
Problem
Quality NCR / inspection failure
Move beyond the failed item to containment, root cause, corrective action, preventive action and proof of closure.
06
Service request
Procurement / material query
Track substitutions, submittal questions and lead-time blockers against the affected package and critical-path decision date.
07
Service request
Permit-to-work / site access
Connect the work window, permit class, SWMS or risk assessment, safety approver and handback confirmation.
08
Incident
Plant / equipment breakdown
Reduce downtime with an asset ID, live location, maintenance owner, repair ETA, test result and returned-to-service gate.
09
Service request
Handover / DLP request
Give clients a focused channel for defects and warranty claims, with contractor responsibility and client verification built in.
10
Service request
Facilities maintenance
Carry the model into operations for HVAC, electrical, plumbing, cleaning, moves and event requests from occupants.
The fastest path through the system should also be the safest path on site.
Safety and quality
Design urgency into the workflow
Critical work should not wait for someone to notice a queue. Use risk-driven fields and automation to make escalation part of the operating design.
✓
Make location and evidence unavoidable. Mobile-friendly forms should capture the exact zone and a photo before submission.
✓
Start the clock from the risk rating. Critical hazards route immediately to the HSE manager; routine items keep a visible 48-hour target.
✓
Separate “actioned” from “verified”. Closure requires inspection evidence and an accountable sign-off, not only a status change.
Operational intelligence
Build dashboards for decisions, not decoration
Different audiences need different views. Site teams act on ageing work; functional leads improve flow; executives watch exposure across projects.
SLA compliance
88%
Defects closed this period
72%
RFIs inside target
61%
Illustrative values shown for layout purposes; use live Jira filters and SLA data in production.
Daily site operations
Open defects by trade and age, overdue RFIs, permits awaiting approval and active plant breakdowns.
RFI turnaround
Average response time, ageing bands, responsible consultant and potential schedule impact.
Defect and quality
Logged versus closed, density by zone, repeat issues by trade and average close time.
Safety leading indicators
Open actions by risk, overdue corrective work, closure rate and recurring hazard categories.
Variation exposure
Pending value, approval-gate age, cumulative cost impact and projected program effect.
Executive portfolio
Critical open items, SLA breach rate by project and cross-project financial exposure.
Architecture decision
Organise by service domain, not every site
At scale, separate domains create cleaner permission boundaries, workflows, queues and SLA policies without multiplying administration for every project.
| Service project | Request types |
|---|---|
| Construction Delivery | RFIs, design changes and variations, procurement and material queries. |
| Site Safety & Quality | Hazards and incidents, quality NCRs, inspection failures and permits-to-work. |
| Client & Defects | Site defects, punch-list items, handover issues and DLP requests. |
| Facilities Maintenance | Post-completion maintenance, occupant requests, moves and event support. |
Start smaller when the organisation is smaller. A single project is a sensible pilot for one site and one team. Split by domain when volumes, permissions and workflow differences make the boundaries valuable.
A practical start
From pilot to portfolio in 90 days
Prove the operating model with the highest-value pathways, then expand once the data and team habits are trustworthy.
Launch the front door
- Choose one active project and accountable service owner.
- Configure defects, RFIs and safety requests first.
- Agree priority definitions and a small set of real SLAs.
- Test every form with field users on mobile.
Close the control loop
- Add approvals, escalations and verified closure gates.
- Clean queues and remove unused fields or statuses.
- Publish daily operations and ageing dashboards.
- Review breaches weekly with named owners.
Expand by domain
- Add change, NCR, procurement and permit workflows.
- Define client and subcontractor permission models.
- Split service projects only where boundaries are clear.
- Roll portfolio reporting up across every domain.
The outcome is not more tickets. It is faster, safer decisions.
Use the service desk to make ownership, urgency and evidence visible from first report to verified close-out.
Key sources and further reading
Editorial note
This field guide is an editorial adaptation of the supplied “Jira Service Management for Construction – Detailed Use-case” study. SLA examples should be calibrated to each organisation’s contracts, risk framework, working calendar and escalation policy.
Photography: Mikael Blomkvist / Pexels and wal_172619 / Pexels . Product interface image: Atlassian .
Jira, Jira Service Management and Atlassian are trademarks of Atlassian. This independent use-case study is not sponsored by or affiliated with Atlassian.
Important updates waiting for you!
Practical ideas for connected customer journeys, digital systems and better work across APAC.