How to Manage Logged Requests

The Logged Requests Board allows Property Managers to review service requests submitted by occupants within an estate.

A logged request can describe a maintenance issue, repair, or another service need that requires the attention of estate management.

Open the Logged Requests Board

1. Sign in to your Rytche account.
2. Open the estate you want to manage.
3. Open the estate management menu.
4. Select Logged Requests Board.

The Logged Requests Board displays requests that have been submitted by occupants of the estate.

Review a request

Open the request you want to review and examine the information provided by the occupant.

Review the available request information to understand:

• Who submitted the request.
• The estate and unit associated with the request.
• The issue or service being requested.
• Any additional information provided with the request.
• The current state of the request.

Use the information provided to determine the appropriate action.

Determine how to handle the request

After reviewing a request, the Property Manager determines how the issue should be handled.

A request may be handled through the estate management process or may require an external service provider.

note

A logged request does not automatically become a gig. The Property Manager determines whether the requested work should be handled through estate management or published as a gig for service providers.

Publish a request as a gig

When an external service provider is required, the Property Manager can use the request as the basis for publishing a gig.

The general workflow is:

1. Review the logged request.
2. Determine that an external service provider is required.
3. Open the Estate Gigs Board.
4. Select Publish Gig.
5. Provide the required gig information.
6. Publish the gig.

Once published, the gig becomes part of the vendor workflow.

See How to Publish a Gig.

What happens after the gig is published?

After a request has been published as a gig, vendors can discover the gig through Gigs Hub.

The workflow can continue through:

1. Vendor applications.
2. Application review.
3. Vendor quotations, where applicable.
4. Quotation review.
5. Vendor assignment.
6. Gig completion.
7. The applicable payment and release process.

See:

• Gigs Hub
• Gig Applications
• Gig Quotations
• Gigs History

Request versus gig

It is important to distinguish between a logged request and a gig.

Logged Request	Gig
Records a service need reported by an occupant.	Makes a service opportunity available to vendors.
Starts within the estate request workflow.	Starts the vendor service workflow.
Is reviewed by estate management.	Can receive vendor applications and quotations.

A request therefore represents the need, while a gig represents the service opportunity made available to vendors.

Example workflow

A typical service request may follow this process:

Occupant
   ↓
Logs Request
   ↓
Logged Requests Board
   ↓
Property Manager Reviews Request
   ↓
Determine Required Action
   ↓
Publish as Gig (if external service is required)
   ↓
Vendor Finds Gig
   ↓
Vendor Applies
   ↓
Quotation Review
   ↓
Vendor Assignment
   ↓
Work Completion