• 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. /How to Sign Off on Vendor Work

How to Sign Off on Vendor Work

When a vendor finishes a job, they select Request Completion on their work order page. The job then waits for you. You either approve the work, which completes the work order, or send it back with a...

Last updated November 10, 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 sort and arrange folders and files
  • 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
    • Create a Service Ticket
    • Documents on a Service Ticket
    • How the Emergency Number Is Chosen
    • How to choose who receives resident service requests
    • How to Convert a Service Ticket into a Board Decision
    • How to download, rename and remove files on a task
    • How to filter service tickets and tasks
    • How to Reassign Work When Removing a Team Member
    • How to Set the Emergency Line
    • How to Sign Off on Vendor Work
    • Notes on a Ticket, and What the Resident Can See
    • Service Ticket Statuses Explained
    • Service Tickets, Troubleshooting
    • Service Tickets: Glossary
    • Service Tickets: Overview
    • 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 the Ticket Activity Tab Records for Vendors
    • 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
    • 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
    • Bank detail change alerts
    • Enter or replace a vendor's bank details
    • How to view and add a vendor's expenses
    • Requesting Completion, and Technician Notes
    • Vendor Billing Tab overview
    • Vendor Billing Tab, FAQ
    • View a vendor's full bank number
    • What a Contractor Sees on a Work Order
    All collections

    On this page

    • Who can do it
    • How you find out
    • Review the request
    • Approve the work
    • Send the work back
    • Who receives the vendor's email
    • What gets recorded
    • Good to know

    When a vendor finishes a job, they select Request Completion on their work order page. The job then waits for you. You either approve the work, which completes the work order, or send it back with a note saying what still needs doing. This article covers both.

    Who can do it

    Anyone who is a member of the property and holds the permission to create and edit service tickets. If you do not have that permission, you still see the vendor's request on the card, but the Approve completion and Send back buttons are hidden. Your role (staff, property manager, or board member) does not matter; only membership and that permission do.

    How you find out

    When a vendor requests completion, URBI emails the property's managers and the person the ticket is assigned to (anyone who has switched off email notifications is skipped). The email is titled "Work completion requested" and has a Review Work button that opens the ticket. The vendor is sent a confirmation too.

    Review the request

    1. Open the service ticket and go to the Request for Proposal tab (the vendor tab).
    2. Find the vendor's card. A Completion Requested pill shows, with a line such as "Requested Oct 14, 2026 at 3:10 PM. Review the work, then approve it or send it back." The time is shown in the property's time zone.
    3. Check the vendor's notes on the ticket's Comments and Activity tabs if you want to see what they reported.
    The vendor card with the Completion requested tag and the Approve completion and Send back buttons

    Approve the work

    1. Select Approve completion.
    2. In the confirmation, "Approve completion?", read the message: this marks the work order complete and emails the vendor that the work is approved. Select Approve completion to confirm.

    The card changes at once: the pill reads Completed and the card says who approved it and when ("Approved by on "). The ticket's work order is complete. The vendor is emailed "Work approved" with a button to open their work order, and their job moves to Awaiting invoice on their side until they send an invoice.

    There is no success message after you approve. You only see a message if something goes wrong: "Could not approve the completion. Try again." If you see it, the card goes back to how it was and nothing was sent. The message stays on screen until you close it.

    Send the work back

    1. Select Send back. A window titled "Send back to " opens.
    2. Under What needs to change?, write what still needs doing. A note is required, and it can be up to 2,000 characters. The counter under the box shows how much you have used.
    3. Select Send back.

    The card changes at once: the pill reads Sent back and the card shows "Sent back on " with your note. The ticket returns to In progress. The vendor is emailed "Changes requested" with your note, and their work order page shows a Changes requested block with the same note. When they have made the changes, they select Request Completion again and the card returns to Completion Requested.

    If something goes wrong you see "Could not send this back. Try again." and the card goes back to how it was.

    The Send back window filled in, and the Sent back state of the vendor card

    Who receives the vendor's email

    The email goes to the vendor's primary contact. If there is no primary contact, it goes to an account contact, then a schedule contact, then any other contact that has an email address. If the vendor has no contact with an email, the sign-off still saves, but no email is sent, so let them know yourself.

    What gets recorded

    Both outcomes add a row to the ticket's Activity tab, for example "Completion approved: signed off the work by . Status changed to Complete." or "Completion sent back: returned the job to . Note: ." See "What the Ticket Activity Tab Records for Vendors."

    Good to know

    • A vendor can send their invoice while the job is waiting for your sign-off, and after you approve it. Approving does not depend on an invoice.
    • You can only approve or send back a job that is waiting for sign-off. If another person already answered it, your action is refused, you see the error message above, and the card goes back to how it was. Reload the ticket to see their decision.
    • Nothing here is automatic. A vendor's completion request is never approved without a person doing it.

    Was this article helpful?

    Related articles

    Operations

    Attach a Vendor to a Service Ticket

    Overview URBI Kore lets you attach vendors to service tickets for RFP (Request for Proposal) workflows or direct assignments. This ensures the right contractors are involved and their proposals are...

    Read
    Operations

    How to Reassign Work When Removing a Team Member

    When you remove a staff member, board member, or PM who has open service tickets or tasks assigned to them, URBI will block the removal until their work is transferred to someone else. This prevents...

    Read
    Operations

    Add Assignees to a Service Ticket

    Learn how to assign team members and collaborators to service tickets in URBI Kore.

    Read
    Operations

    Convert a Service Ticket to a Task

    Overview Sometimes a service ticket is really day to day work that belongs in your task list, not in the maintenance queue. URBI Kore lets you convert a service ticket into a task in one click. This...

    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