Start a conversationContact

Property operations

Work-order orchestration from intake to verification.

Bedrock AI engineered a shared work-order system for residents, coordinators, technicians and vendors. Defined workflow states govern assignment, repair, resident verification and final closure.

Completed engagement

A resident has reported a kitchen sink backing up. The coordinator needs a plumber on it today, with a current insurance certificate.

  1. The requestas it reached the desk

    WO-1047Triaged

    Kitchen sink backing up — standing water under disposal

    Resident reports the kitchen sink will not drain and water is pooling in the cabinet beneath the disposal. Cabinet base is wet; resident has stopped using the sink. Triaged as high — active water intrusion into casework.

    Next moves

    • Assigned
    • Cancelled

    Vendor

    Not assigned

    Costs

    No costs entered yet

    Activity

    1. 22 Sep · 08:14Resident called at 8:05. Sink will not drain, water pooling in the base cabinet. Advised her to stop running the disposal and to clear the cabinet.
    2. 23 Sep · 17:30Same riser as the 1A laundry drain we’re working. If the tech finds the branch line blocked rather than the trap, flag it before he starts cutting.

  2. The assigned workon the vendor’s own list

    Marcus ElleryOutside vendor · signs in by link

    Assigned to you

    1. WO-1047AssignedKitchen sink backing up — standing water under disposalDue 25 Sep 2026
    2. WO-1037In progressLaundry room floor drain slowDue 24 Sep 2026
    3. WO-1039ScheduledWater heater thermostat replacementDue 25 Sep 2026
    4. WO-1043ResolvedToilet running continuouslyDue 22 Sep 2026
    5. WO-1034VerifiedKitchen faucet cartridge replacementDue 19 Sep 2026
    6. WO-1031ClosedHot water pressure low in showerDue 16 Sep 2026

  3. The completed recordback at the desk

    WO-1047Resolved

    Kitchen sink backing up — standing water under disposal

    Resident reports the kitchen sink will not drain and water is pooling in the cabinet beneath the disposal. Cabinet base is wet; resident has stopped using the sink. Triaged as high — active water intrusion into casework.

    Next moves

    • Verified
    • In progress

    Vendor

    Marcus Ellery

    Costs

    $227.50

    Labour
    Cleared branch line to riser, reset trap
    $185.00
    Materials
    P-trap kit and cabinet base gasket
    $42.50

    Activity

    1. 22 Sep · 08:14Resident called at 8:05. Sink will not drain, water pooling in the base cabinet. Advised her to stop running the disposal and to clear the cabinet.
    2. 23 Sep · 17:30Same riser as the 1A laundry drain we’re working. If the tech finds the branch line blocked rather than the trap, flag it before he starts cutting.
    3. 24 Sep · 11:15Marcus cleared the branch line back to the riser and replaced the trap assembly. Resident confirmed the sink drains and the cabinet base is dry.
One work order at three moments: as it reached the desk, on the assigned vendor’s list, and resolved—its next move, verified or back in progress, left to the resident.Client systemRe-drawn from the application · same fields, states and sequence

Operational state scattered across boards and messages.

Requests moved between a shared board, messages and the people coordinating the work. Assignment, progress and confirmation depended on manual follow-up across those channels.

Role-specific actions across the work-order lifecycle.

A technician or vendor records the repair as resolved. The resident confirms the repair or returns the request to active work. The operations desk closes the order after confirmation.

One work order, five moves, four holdersFour lanes: the resident, the operations desk, the technician and the outside vendor. A single work order moves between them: reported by the resident, assigned by rule at the desk, completed in the field by the technician — or by a vendor, when the desk assigns one — returned to the resident to confirm or reopen, and closed by the desk. The resident’s confirmation is marked as the move no one else can make.ResidentOperations deskTechnicianOutside vendorOr a vendor, when assignedReports itAssigns by ruleDoes the workConfirms, or reopensCloses itReports itResidentAssigns by ruleOperations deskDoes the workTechnician · or a vendor, when assignedConfirms, or reopensResidentCloses itOperations desk
One work order · five moves · four holders. The marked move is the one the office cannot make for anyone: the resident confirms the repair or sends it back.

Deployment status

Completed engagement. The state of each component when the engagement ended.

One work order recordEvery part below reads and writes it

Resident request lifecycle

Ran in production

Ran in production during the engagement, with real resident sign-ins.

Notifications

Verified in production

Email and text delivery verified in production.

Below this line: built, with no recorded production use

Operations console

Built

No production operator use recorded.

Technician tools

Built, not released

Verified at device sizes; not released to staff.

Vendor dispatch and insurance checks

Built, not deployed

Finished after the last deployment.

Recurring work, inspections and invoices

Implemented

Routine use unverified.

The application as it stood when the engagement ended, with the state of each part marked on it.

Response times, completion times and adoption were not measured. Bedrock AI no longer operates or supports the system.

Start a conversationadam@bedrockos.co