Requests list page and key metrics

The requests list is the command center for new inquiries. Use it to see how many requests are coming in, which requests need attention, and which ones have moved into quotes or jobs.

Open Requests.

Requests metrics

The metrics at the top of the list help managers and dispatchers understand request activity without opening every record.

Common metrics include:

• New: Requests created during the selected date range. This includes requests that may later be canceled, archived, or converted.
• Conversion: The percentage of requests in the selected date range that were converted into quotes or jobs.
• Previous period comparison: A trend indicator that compares the selected date range with the same length of time immediately before it.

Use these metrics to spot intake changes, follow-up bottlenecks, and service demand. For example, a high number of new requests with a lower conversion rate can mean the team needs faster assessments, clearer pricing, or better request qualification.

The requests list

Each row represents one request. The list is built for quick review, so your team can scan the important details before deciding what to do next.

Typical columns include:

• Status: Shows where the request sits in the workflow, such as new, assessment scheduled, converted, or archived.
• Name: Shows the request title or primary request name.
• Contact: Shows the client or lead connected to the request.
• Requested date: Shows when the client wants the work or assessment to happen.
• Received date: Shows when the request entered Fieldified.

Open a row to review the full request, including client details, property address, requested services, notes, attachments, and assessment information.

Request status

Status helps your team prioritize work. New requests usually need qualification, assessment scheduling, or a first response. Assessment requests need a scheduled time and assigned team member. Converted requests are already connected to the next stage of work.

Keep request statuses current so managers can rely on the list when reviewing the daily pipeline.

Search requests

Use search when you already know part of the request information. You can search by:

• Client name.
• Company name.
• Request title.
• Property address.
• Phone number or email.
• Request number.

Search is helpful when a client calls in and your team needs to quickly find the open inquiry before creating another one.

Filter requests

Filters narrow the list to the requests that need a specific type of action.

Useful filters include:

• Status: Find new, assessment scheduled, converted, archived, or lost requests.
• Date range: Review requests created, received, or requested within a specific period.
• Team member: See requests assigned to a salesperson, dispatcher, or estimator.
• Client or property: Focus on one customer or location.
• Service type: Review demand for specific products or services.

Date filters also affect the key metrics at the top of the page, so confirm the date range before reviewing performance.

Row actions

Use row actions to update one request without losing your place in the list.

Actions can include:

• Open or edit the request.
• Schedule an assessment.
• Convert the request to a quote.
• Convert the request to a job.
• Archive the request.
• Delete the request.

When a request needs more context before conversion, open it first and review the client, property, service details, notes, and attachments.

Bulk actions

Bulk actions are helpful when several requests need the same update. Select the requests, then choose the action you want to apply.

Use bulk actions carefully for archive, status, and assignment changes. If requests are at different stages, open each one first so the record stays accurate.

Daily review workflow

A simple daily review keeps requests from sitting too long:

1. Open Requests.
2. Confirm the date range and review the New and Conversion metrics.
3. Filter to new requests.
4. Assign ownership or schedule assessments.
5. Convert qualified requests into quotes or jobs.
6. Archive requests that no longer need action.

Use Request basics for request creation and editing, Schedule an assessment for site visits, and Convert a request for moving requests into quotes or jobs.