• Solutions for Every Building, Every Stakeholder

    URBI is the first Building OS powered by HERO AI. Whether you manage properties, own them, or operate them day to day, URBI transforms complex, disconnected workflows into a single, intelligent platform that drives efficiency and builds stronger communities.

    Role Benefits

    • For Property ManagersStreamline operations and enhance tenant satisfaction with centralized management tools.
    • For Building OperatorsSimplify daily tasks and maintenance with intelligent automation and workflow management.
    • For OwnersMaximize ROI and property value with comprehensive oversight and analytics.
    • For Finance TeamsClose faster with double entry books, trust accounting, and reconciliation that runs nightly.
    • For BusinessesConnect with building communities and expand your service offerings.

    Building Benefits

    • Residential BuildingsSimplify living with one app for bookings, packages, payments, and community updates.
    • Commercial BuildingsStreamline operations, vendors, and compliance while giving tenants a frictionless experience.
    • Education BuildingsManage facilities, visitors, and compliance for safer, smarter, more connected campuses.
    • Senior LivingAnswer families around the clock, publish life enrichment once, and see every community on one screen.
  • One Platform. Smarter Buildings.

    URBI centralizes daily operations and adds AI intelligence to transform complexity into clarity.

    Products

    • URBI KoreThe central hub where managers, owners, and staff run building operations in one place.
    • URBI KonnectA marketplace that connects buildings with trusted vendors, services, and community events.
    • URBI AccountingAI consolidation, invoices and receipts processed by AI, books pre reconciled before month end. In Beta.
    • URBI AIOne intelligence across URBI. HERO answers your team's questions, Arthur answers your community's calls, texts, and emails 24/7.

    Features

    • Operations & Workflow
    • Amenities & Booking
    • Events & Ticketing
    • Communication & Community
    • Payments & Transactions
    • Data & Compliance
    • HERO AI Intelligence
    • IoT & Hardware Integration
    • Community Experience
    • Accounting (In Beta)
    View All
  • Customers
    • All ResourcesGuides, support, and customer stories in one place
    • Help CenterGuides and answers for every part of URBI
    • BlogWhy URBI works the way it does
    • ReleasesEvery update we ship, in plain language
    • System StatusHow every part of URBI is running right now
    • About UsLearn about our story and mission
    • MilestonesHow URBI got here and where it is going
    • CareersWe're HiringJoin our growing team
    • FAQStraight answers about URBI, HERO and Arthur
    • ContactGet in touch with us

Schedule a Demo

  1. Help Center
  2. /Operations
  3. /Service Tickets
  4. /Set Up Recurring Service Tickets

Set Up Recurring Service Tickets

Learn how to set up recurring service tickets in URBI Kore to automate repetitive maintenance and operational work.

Last updated September 6, 2026

Operations
  • Approvals: decide expenses, board votes and RFPs in one place
  • Board Decisions: overview
  • Confirming packages, and what a refused package means
  • Document sharing
  • Finding the packages for one home
  • How to approve expenses and RFPs in Approvals
  • How to create a decision
  • How to create a time limited public link
  • How to generate the PDF report
  • How to run a vendor RFP through Board Decisions
  • How to share a file or folder
  • How to upload with drag and drop
  • How to vote and finalize a decision
  • How to vote on board decisions in Approvals
  • Operations
  • Troubleshooting
  • Troubleshooting document sharing
  • When a scanned package needs a look
    • Add Assignees to a Service Ticket
    • Attach a Vendor to a Service Ticket
    • Convert a Service Ticket to a Task (and make sure it stays visible)
    • Create a Service Ticket
    • Documents on a Service Ticket
    • Finding a Ticket: Search and Filters
    • How the Emergency Number Is Chosen
    • How to Convert a Service Ticket into a Board Decision
    • How to Reassign Work When Removing a Team Member
    • How to Set the Emergency Line
    • Notes on a Ticket, and What the Resident Can See
    • Service Ticket Statuses Explained
    • Service Tickets: Glossary
    • Service Tickets: Overview
    • Service Tickets: Troubleshooting
    • Set Up Recurring Service Tickets
    • The History on a Ticket: What It Records
    • The Tabs on a Service Ticket, Explained
    • Troubleshooting
    • What Residents See When They Create a Ticket
    • What's New in Service Tickets
    • Who Can Do What on a Service Ticket
    • Add Assignees to a Task
    • Create a Task
    • Organize Tasks with Categories, Projects, and Labels
    • Set Up Recurring Tasks
    • Access Request Statuses Explained
    • Choosing Who Receives a Request for Access
    • How to Send a Request for Access
    • Mandatory vs Request: Which One to Send
    • Recording an Answer on Someone's Behalf
    • Requests for Access: Glossary
    • Requests for Access: Overview
    • Requests for Access: Troubleshooting
    • Reschedule Requests: How They Work
    • Sending a Reminder for a Request That Has Not Been Answered
    • What the Recipient Sees and How They Answer
    • Awarding the Work
    • Comparing Proposals
    • How to Invite Vendors to an RFP
    • Putting an RFP to a Board Vote
    • Requests for Proposal: Glossary
    • Requests for Proposal: Overview
    • Requests for Proposal: Troubleshooting
    • RFP Statuses Explained
    • What a Vendor Sees and How They Submit a Proposal
    • Asset Impact: Overview
    • Asset Impact: Troubleshooting
    • Cancel Bookings or Block New Ones
    • Closure Statuses Explained
    • Confirming a Closure, and Why Scheduling Is Not Enough
    • How to Close an Amenity for Scheduled Work
    • What Happens to Bookings and Money When You Close an Amenity
    • How to view and add a vendor's expenses
    • Requesting Completion, and Technician Notes
    • Vendor Billing Tab: FAQ
    • Vendor Billing Tab: Overview
    • What a Contractor Sees on a Work Order
    • Set Maintenance Schedules for Assets
    • Track Equipment and Warranties
All collections

On this page

  • Overview
  • Two Recurrence Modes
  • Setting Up Recurring on Schedule
  • Step 1: Open the Ticket
  • Step 2: Select "On Schedule"
  • Step 3: Choose a Frequency
  • Step 4: Set the Interval
  • Step 5: Choose an End Condition
  • Step 6: Save
  • Setting Up After Completion
  • Step 1: Select "After Completion"
  • Step 2: Set the Duration
  • Step 3: Choose an End Condition
  • Step 4: Save
  • How Recurring Tickets Appear
  • Stopping a Recurrence
  • Common Use Cases
  • What gets recorded when you finish one

Overview

Recurring service tickets automate repetitive maintenance and operational work. Instead of manually creating the same ticket every week or month, URBI Kore generates them automatically on your schedule.

Two Recurrence Modes

URBI offers two ways to set up recurrence:

  • On Schedule: Tickets are created on a fixed calendar schedule (e.g., every Monday, the 1st of each month, or every 90 days)

  • After Completion: The next ticket is created only after the previous one is marked complete (e.g., 14 days after the last ticket is finished)

Setting Up Recurring on Schedule

Step 1: Open the Ticket

Create a new ticket or open an existing one. In the detail drawer, scroll down to the Recurring section in the sidebar.

Step 2: Select "On Schedule"

Choose On Schedule from the recurrence type dropdown.

Step 3: Choose a Frequency

  • Daily: Repeats every N days

  • Weekly: Repeats every N weeks on selected days. Toggle the day buttons (S, M, T, W, T, F, S) to choose which days of the week.

  • Monthly: Repeats every N months on a specific day of the month (1 through 31)

  • Yearly: Repeats every N years on a specific month and day

  • Custom: Full control over interval value and unit (days, weeks, months, or years)

Step 4: Set the Interval

Enter how often the ticket should repeat. For example, "every 2 weeks" or "every 3 months."

Step 5: Choose an End Condition

  • Never: Continues repeating indefinitely

  • After N occurrences: Stops after a set number of tickets (1 to 365)

  • On date: Stops on a specific calendar date

Step 6: Save

Click Save Recurrence. A recurring icon will appear on the ticket to indicate it is part of a recurring schedule.

Setting Up After Completion

Step 1: Select "After Completion"

In the recurrence section, choose After Completion.

Step 2: Set the Duration

Enter how long after completion the next ticket should be created. For example, "create next ticket 14 days after completion."

Step 3: Choose an End Condition

Select either Never (continue indefinitely) or On date (stop on a specific date).

Step 4: Save

Click Save Recurrence.

How Recurring Tickets Appear

Upcoming recurring tickets appear as "ghost" entries in your calendar and list views before they are formally created in the system. Once the scheduled date arrives, the ticket is automatically generated with the same title, description, assignee, and other details from the original.

Stopping a Recurrence

Open the ticket detail drawer, go to the Recurring section, and click Stop Recurrence. No further tickets will be generated.

Common Use Cases

  • Weekly cleaning inspections: On Schedule, weekly on Monday

  • Monthly HVAC filter changes: On Schedule, monthly on the 1st

  • Quarterly fire extinguisher checks: On Schedule, every 3 months

  • Pest control after each visit: After Completion, 30 days after the last ticket is closed

  • Annual elevator certification: On Schedule, yearly

What gets recorded when you finish one

When you mark a repeating ticket finished, the history line and the alerts that go out are recorded under you, the person who actually finished it. They cannot be recorded under somebody else.

If your administrator has switched off your ability to create tickets, finishing a repeating one will not create the next occurrence either. You will see a short explanation rather than a silent failure, and nothing is half-created: no ticket, no history line and no alerts. Ask an administrator if you need that permission changed.

Was this article helpful?

Related articles

Operations

Service Tickets: Glossary

The words used across tickets, access requests, proposals and closures, in one place.

Read
Operations

Service Tickets: Overview

A service ticket is how a resident reports an issue in their unit or the building, such as a maintenance problem, a repair request, or anything else they need staff to look at. Residents create...

Read
Operations

Service Tickets: Troubleshooting

Common issues with Service Tickets: Reassign Work blocks, Operations plan gating, sidebar filters, and document previews.

Read
Operations

What's New in Service Tickets

Service Tickets update: convert to task auto assign, vendor work order default, convert to board decision, removal reassignment, filters, and document previews.

Read
All Operations articlesAsk the URBI team
URBI

URBI is the Building OS, founded in Calgary in 2023. One platform with HERO AI built in, running thousands of units for property managers, condo boards and owners.

Solutions

  • All Solutions
  • For Property Managers
  • For Building Operators
  • For Owners
  • For Finance Teams
  • For Businesses

Building Benefits

  • Residential Buildings
  • Commercial Buildings
  • Education Buildings
  • Senior Living

Products

  • All Products
  • URBI Kore
  • URBI Konnect
  • URBI AI
  • URBI Accounting (Beta)

Company

  • About URBI
  • About Us
  • Milestones
  • Reviews
  • FAQ
  • CareersWe're Hiring
  • Contact

Resources

  • All Resources
  • Help Center
  • Blog
  • Releases
  • System Status
  • FAQ
  • For AI assistants

Compare

  • Compare Us to Residential
  • Compare Us to Commercial
  • Compare Us to K-12

Legal

  • Security & Privacy
  • Terms & Conditions
  • Terms of Service for Konnect

© 2026 URBI. All rights reserved.

Privacy PolicyTerms of Service

Schedule a Demo