8. Requests

This chapter covers how to use the My Request module in the BhuMeet Web Application to monitor and manage incoming drone service requests from farmers.

You’ll learn how to:

View requests in various statuses (Pending, Accepted, Rejected, Completed)
Filter requests using tabs or search
Assign drones, pilots, and agro chemicals
Accept, start, or complete requests using contextual UI actions

Each process is guided with step-by-step instructions and visual cues to help you manage field operations seamlessly.

8.1 Dashboard

The My Requests dashboard provides a centralized interface for tracking and managing all farmer service requests. It visually summarizes your request statuses, locations, revenue, and activity trends—helping you stay informed and act efficiently.

This is the default landing view when you click on My Requests from the main menu.

Key Components

The dashboard is composed of the following UI elements:

1. Request Status Summary Cards

Four visually distinct cards display the count of requests in key statuses:

Card Title	Meaning
Placed	Total number of requests submitted by users
InProgress	Requests that are accepted and ongoing
Completed	Requests marked as completed after service
Paid	Completed requests that have been settled

💡 These cards provide real-time counts. Clicking them auto-filters the request table below.

2. Latest Location

Displays the most recently added service location(s) where requests are being received.

Format: City, District, State
Example: Nashik, Nashik, Nashik
Also shows the count of new locations recently added.

3. Total Revenue Summary

This tile shows cumulative earnings till date from completed and paid requests.

Format: [Amount]
Example: 3,25,601
Includes label: (Till July 16, 2025) for time-bound clarity

4. Order Analytics Graph

This visual graph plots the number of requests received across months.

Use the dropdowns to switch between:
- All / Spraying / Survey
- This Year / This Month / This Week

Use this chart to analyze request demand trends by service type and time.

5. Create Request Button

Located at the top-right, the button opens a form to manually add a new farmer request. It supports both spraying and survey service workflows.

6. Calendar View Toggle

Located beside the Create Request button, the calendar icon opens the calendar view mode (documented separately in Section 8.2).

7. Request Filter Bar

Includes multiple controls to filter and search your requests efficiently:

Filter Tool	Function
Search Bar	Search by request number
Status Tabs	Quick filters – All, Placed, Scheduled, etc.
From – To Date	Date range filters for request receipt or service
Select Location	Filter requests based on location

8. Request Table

A paginated table lists all requests matching the current filters.

Column	Description
Request No.	Unique numeric ID assigned to the request
Location	Service location name
Brief Address	Full address of service execution
Service	Type of service requested (e.g., Spraying)
Customer Name	Farmer/customer name
Date Received	Request submission date
Service Date	Expected date of service
Status	Current request status (Accepted, etc.)

“Each row is clickable, allowing DSPs to drill into request details and proceed with request lifecycle actions.”

🔁 Statuses shown here are dynamic and updated in real-time as actions are taken (see Section 8.3).

What You Can Do from the Dashboard

Monitor key request metrics at a glance
Visualize request volume trends over time
Quickly filter to find and act on any request
Create a new request using the top-right button
Navigate to detailed views (assign, accept, reject, complete) using the table

8.2 View and Filter

The My Requests section provides flexible tools to view, search, and filter drone service requests. Users can switch between tabular and calendar views, apply date and status filters, and drill into specific request details for fast, informed action.

Use this section to quickly locate and manage service requests using filters and visual modes.

1. Request View Modes

You can toggle between two primary layouts:

a. Table View (Default)

This mode displays all requests in a structured, scrollable table. It is ideal for detailed list-based inspection and bulk filtering.

Table Columns Include:

Column	Description
Request No.	Unique numeric identifier
Location	Primary location of service
Brief Address	Full delivery or service address
Service	Type of service requested (e.g., Spraying)
Customer Name	Farmer’s name
Date Received	Date request was submitted
Service Date	Scheduled service execution date
Status	Current status (e.g., Placed, Accepted)

🔗 Clicking the Request Details Row opens the detailed request view (see Section 8.4).

Click the Calendar icon (top-right corner) to switch to a monthly calendar layout. This visual mode maps service requests by scheduled dates, offering an intuitive overview.

Features:

Dots on a date indicate requests scheduled on that day.
Clicking a date reveals all requests for that day in a list on the right.
Each request row shows:
- Service Type
- Location
- Pilot Name
- Start Time
- Acreage
- Status

🔗 Clicking a request entry opens the detailed request panel (see Section 8.4).

Shows calendar with selected day and right-hand request list

2. Filters and Tools

Located above the request table, the Filter Bar helps you narrow down your view efficiently.

Filter Tool	Description
Search Bar	Enter a Request No. to directly find a request
Status Tabs	Click to filter: All, Placed, Scheduled, Ongoing, etc.
Date Pickers	Filter requests using From – To date range
Select Location	Filter requests by region or service location

Includes tabs, date range filters, location dropdown, and search field

3. Status Tabs

These filter tabs instantly segment requests by stage:

Tab	Description
All	View every request regardless of status
Placed	Requests submitted but not yet accepted
Scheduled	Accepted and waiting for execution
Ongoing	Services currently in progress
Completed	Service completed successfully
Paid	Fully serviced and payment received
Cancelled	Requests manually cancelled or expired

✅ Tabs are clickable and auto-filter the request list in real time.

4. Pagination

Located at the bottom of the table
Allows smooth navigation across multiple pages
Controls include:
- Next/Previous arrows
- Page numbers
- Current page indicator

What You Can Do in This Section

Action	Outcome
Switch Views	Toggle between calendar and table layouts
Filter by Status	Focus on requests by workflow stage
Search by Request No.	Retrieve specific records instantly
Apply Date or Location Filters	Narrow results by time range or area
Click Request	Open full details and manage request status/actions

8.3 Request Statuses

The My Requests module uses a structured set of statuses to represent the lifecycle of each service request. These statuses are critical for managing operations—from assignment and execution to completion and payment.

Statuses appear in the request table view, calendar view, and dashboard cards, and dynamically determine what actions are available.

Changing Status

DSPs are provided with additional flexibility in managing request statuses. This allows efficient handling of real-world scenarios where a strict sequential flow may not always apply.

Rules for Changing Status:

A DSP can update a request directly to any status within the Approved category, regardless of its current step in the workflow.
- Example: A request can be updated from “Approved” directly to “Completed.”
Restriction on Paid Status:
- A request can only be marked as Paid if it has first been marked as Complete.
- This safeguard ensures financial records remain accurate and consistent.

Note:

This flexibility applies only to DSPs.
Farmers and other stakeholders see the request in the updated state as set by the DSP.

Request Status Types

Status	Description
Placed	Request is created (via onboarding, dashboard, or manually) but not yet assigned
Scheduled	Drone and pilot are assigned and the service date is scheduled
Accepted	The assigned pilot has confirmed the scheduled request
Ongoing	Service has been started and is in progress
Completed	The spraying/survey service was performed successfully
Paid	Payment was confirmed for the completed service
Rescheduled	Scheduled request was modified to a new service date
Cancelled	Request was cancelled before or during service
Rejected	Request was declined (by DSP or system)

Lifecycle Flow

Typical path:
Placed → Accepted → Ongoing → Completed → Paid

If the scheduled request is delayed or changed:
Accepted → Rescheduled → Resume → Ongoing → Completed

Status-Driven Actions

Status	Available Actions
Placed	Assign drone, pilot, agro chemical
Scheduled	Start, Reschedule
Accepted	Start, Reschedule
Rescheduled	Resume (re-activate request using new service date)
Ongoing	Complete, Cancel
Completed	Mark as Paid
Paid	View only
Cancelled	View only
Rejected	View only

Reschedule and Resume

Reschedule:
Available from Scheduled or Accepted Lets DSP update the service date.
Resume:
Becomes available once a request is Rescheduled. Clicking Resume reactivates the workflow, moving it to Accepted or Ongoing.

✅ The system preserves previously assigned resources (drone, pilot) unless manually changed during rescheduling.

Best Practices

Use Placed as your assignment queue.
Move to Scheduled only when all resources are selected.
If a service cannot be executed on time, use Reschedule instead of cancelling.
Resume ensures continuity of rescheduled jobs without data loss.
Monitor Ongoing and Rescheduled closely to avoid delays in execution.

8.4 Request Details

The Request Details View provides a complete overview of any selected farmer service request. From resource assignments to service parameters, status history, comments, and payment breakdowns, this panel helps Drone Service Providers (DSPs) manage every detail with precision.

You can access the Request Details panel by clicking on any row from the My Requests Table or by selecting a request from the Calendar View (see Section 8.2).

Access Request

You can open request details from two primary entry points:

From the Dashboard Table:
1. Navigate to the My Requests
2. Use filters or scroll to locate a request.
3. Click on the row to open the Request Details panel.
From the Calendar View:
1. Click the Calendar icon beside “Create Request”.
2. Select a date and then click a request in the right-side list.

Request Details Panel

Includes all request metadata, status timeline, and available actions.

Request Metadata

The details panel is divided into clearly structured segments:

1. Location and Customer Info

Field	Description
Request No.	System-generated ID for the service request
Service Address	Location of the farm or field
Customer Name	Farmer’s name and contact number

2. Service Details

Field	Description
Crop Name	Selected crop for the service
Agro Chemical	Chemical selected for spraying
Requested Area	Area in acres for servicing
Completed Area	Area actually serviced (updated post-service)
Date Received	Date when the request was logged

3. Resource Assignment

Field	Description
Assigned Pilot	Name of the assigned drone pilot (editable)
Assigned Drone	Selected drone model for operation (editable)
Drone Type	Drone category/type (optional)
Schedule Date	Planned service date (can be changed if rescheduled)

✏️ You can click Change beside Pilot and Drone fields to modify assignments before starting the service.

4. Payment Details
Displays the computed service cost including subsidies and discounts.

Field	Description
Service Charges	Based on area × per acre rate
Subsidy	Auto-calculated based on crop or govt. rules
Discount Toggle	Toggle the discount ON/OFF before specifying %
Discount Value Field	Enter the discount percentage after enabling the toggle
Total Amount	Final amount payable after applying all reductions

5. Request Actions

Contextual buttons appear based on the current status of the request:

Button	When It Appears	Action Description
On Hold	If request needs to be paused	Temporarily suspends action on request
Reschedule	When service date or resources need change	Opens rescheduling panel
Resume	When resuming a paused/on-hold request	Reactivates the service scheduling
Cancel	If request must be voided	Marks the request as Cancelled

Buttons are enabled/disabled based on the request’s current status and user permissions.

6. Request Timeline (History)

A vertical Status Timeline tracks all key updates:

Event	Example
Placed	“Service request has been placed”
Accepted	“Service request has been accepted”
Rescheduled	“Request rescheduled for new date”
On Hold / Resumed	Timeline records status transitions

7. Comments – Adding, Viewing, and Deleting

The Comments tab enables DSPs, pilots, or admins to leave internal notes, instructions, or observations linked to a service request. All comments are time-stamped for tracking purposes.

Action	Description
Add Comment	Type a message in the input field and click Send to post it.
View Comments	Comments appear in descending order under the Comments tab.
Delete Comment	Click the three-dot menu beside your comment and select Delete.

Use comments to share updates, special handling instructions, or pilot notes related to service execution.

Permissions: Only users who posted the comment or those with delete rights can remove entries.

Summary

You Can…	Description
View full request data	Location, pilot, drone, chemicals, cost, etc.
Modify assignments	Change pilot, drone, or chemicals before service
Track progress	Status and date transitions are visible in History
Apply cost adjustments	Add discount or view subsidy logic
Perform actions	Accept, start, complete, cancel, reschedule, or resume
Add Comments	Leave contextual notes viewable by assigned pilot

8.5 Assign Resources

The Resource Assignment Panel enables DSPs to assign or update the Pilot, Drone, and Drone Type for each accepted service request. This assignment must be completed before initiating service execution.

Assignments are mandatory to proceed with further request lifecycle stages such as marking In Progress or initiating the drone operation.

Assign Resources

Resource assignment can be done from the Request Details Panel after a request is placed or accepted.

Steps to Assign or Modify Resources:

Navigate to the Request Details Panel of the selected request (see Section 8.4).
Scroll to the Resource Details
Assign resources using the dropdowns and actions provided.

Resource Assignment

Field	Description
Assigned Pilot	Select a pilot from the dropdown list. Use the Show All checkbox to view all available pilots across locations.
Assigned Drone	Select the drone based on availability. Only drones linked to the selected pilot or region are shown.
Drone Type	The system may auto-populate the drone type once a drone is selected (e.g., Hexacopter). Optional, view-only field.
Schedule Date	Date scheduled for performing the drone service. This is auto-filled from the request but editable if rescheduled.

Click Assign to confirm the selection, or click Cancel to discard changes.

Assignment Controls

Assigning Pilot

Use the Pilot dropdown to select an available pilot.
Enable Show All to view and assign pilots from different locations.
Click Assign to finalize selection.

Assigning Drone

Use the Drone dropdown to choose an available drone.
The dropdown dynamically lists drones linked to selected pilots or site location.
Confirm the assignment using the Assign

Changing an Pilot or Drone

Once a resource is assigned, it appears as a non-editable label with a Change link:

Click Change beside Assigned Pilot or Assigned Drone.
Re-select a new option from the dropdown.
Click Assign to save changes.

Validations and Permissions

Validation Scenario	System Response
No Pilot selected	Assign action remains disabled
No Drone selected	Assign action remains disabled
Pilot and Drone conflict	Error shown if drone not compatible with pilot’s assignment or location
Unauthorized resource change	Assign/Change option not shown if user lacks rights

Summary

You Can…	Description
Assign Pilot	Select a certified pilot from current or all locations
Assign Drone	Choose an operational drone for the request
View Drone Type	Confirm the drone type (auto-filled after selection)
Modify Assignments	Use Change link to update previously saved assignments
Schedule/Reschedule	Adjust service schedule via Request Actions if needed

8.6 Accept or Reject

After a farmer’s request has been created and reviewed, Drone Service Providers (DSPs) must either accept or reject the request based on resource availability, suitability, and operational conditions.

This section describes how to perform these actions from the request details panel and outlines the status changes that follow each decision.

Only users with appropriate access rights (e.g., DSP Admins or Schedulers) can accept or reject incoming requests.

Accepting a Request

Accepting a request confirms that the service can be scheduled based on available pilots, drones, and terrain suitability. Once accepted, further actions like assignment and service execution become enabled.

Steps to Accept a Request:

Go to the My Requests
Click on the request to open the Request Details panel.
Review the details for:
- Location and crop
- Requested area
- Resource availability
Accept the Request

From the Request Details panel, locate the Status Action dropdown at the top-right corner above the History/Comments tab.
Open the dropdown and select Accept.
Once selected, the request status updates to Accepted, and the request moves forward in the workflow.

Displays Accept/Cancel controls and status transition area in the Request Details view.

✔️ On acceptance, the status will change to Accepted, and the request moves forward in the workflow.

Cancelling a Request

If a request cannot be serviced due to constraints (invalid data, duplicate entry, unavailable resources, or unsuitable terrain), it may be cancelled, which functionally acts as rejection.

Steps to Cancel (Reject) a Request:

Navigate to the My Requests dashboard and select a request.
Open Cancel Action

In the Request Details panel, locate the Status Action dropdown at the top-right corner above the History/Comments tab.
From the dropdown list, select Cancel.

Provide Cancellation Reason

The Cancel Request dialog will open.
Select a reason by clicking the corresponding radio button from the predefined list.
If Other is selected, a text box appears where you must enter the custom reason.
Once a reason is selected or entered, the Cancel button becomes enabled.
– Click Cancel to confirm the action.
– Or click Not Now to close the dialog without making changes.

Once cancelled, the request status is updated to Cancelled and is removed from the active workflow.

Reconsidering Rejected Requests

If needed, rejected requests can be reconsidered by reinitiating them manually from the backend or admin console (based on user permissions). This operation is not available by default from the UI for standard users. Please Contact Support for it.

Best Practices

Always review payment breakdowns, pilot availability, and drone type before accepting.
Include clear reasons while rejecting to maintain audit trail and farmer transparency.
If choosing Other, enter a specific reason in the text box to maintain audit accuracy.
Use Not Now if you want to exit without applying cancellation.
Ensure notifications are triggered (email/SMS/in-app) post acceptance or rejection, if configured in the system.

Status Transitions

Action	Before Status	After Status
Accept	Placed	Accepted
Cancel	Placed	Cancelled

8.7 Reschedule

The Reschedule option enables Drone Service Providers (DSPs) to modify the planned service date and justify the rescheduling reason. This feature ensures seamless communication and accountability when changes arise due to weather, technical issues, or user unavailability.

Only requests with a status of Accepted or In Progress can be rescheduled. The updated schedule and reason are recorded in the Request History for traceability.

When to Use Reschedule

You may reschedule a request if:

The farmer or DSP is unavailable on the current scheduled date.
Drone or pilot assignments change.
Field conditions, weather, or platform issues delay operations.

Available From

The Reschedule option is available from the Actions dropdown located at the top-right of the Request Details Panel when a request is in an active state (Accepted or In Progress).

Rescheduling Steps

Follow these steps to reschedule a request:

Open Request Details
Navigate to the My Requests section and select a request with status Accepted or In Progress.
Select Reschedule from Actions Dropdown
From the Actions dropdown located at the top-right corner of the Request Details Panel, choose Reschedule.

Select New Date
In the calendar popup, choose a future service date that aligns with availability and readiness.
Choose Reason for Reschedule
Select one of the provided reasons:
- Farmer Requested Date Change
- Farmer’s Chemicals/Resources Not Ready
- Pilot Unavailable on Selected Date/Time
- Adverse Weather Conditions
- Drone Malfunctioned or Crashed
- Technical Issues in the Platform
- Other (if selected, a text box will appear to manually enter the reason)
Click Reschedule
Confirm the changes by clicking the Reschedule button at the bottom of the dialog.

6. Acknowledge Confirmation
A success message is shown confirming the reschedule, including the request number and updated status.

History and Status Update

After rescheduling:

The new Schedule Date appears in the Request Details.
The Request Status changes to Rescheduled.
The Request History timeline logs the action, including:
- Timestamp
- New schedule date
- Selected reason

🧠 All reschedule actions are traceable for audit and coordination purposes.

Note: Drone Service Providers (DSPs) must use the Reschedule option to assign a new service date when bringing a request out of the On Hold state.

Summary

Step	Description
Identify eligible request	Request must be in Accepted or In Progress state
Launch reschedule popup	Via Reschedule button in request view
Select new date	Choose valid future service date
Add reschedule reason	Pick from predefined list (mandatory)
Confirm reschedule	Submit changes and get confirmation
Track in history	Review event timestamp and comments in Request History panel

8.8 On Hold

The On Hold feature enables Drone Service Providers (DSPs) to temporarily pause a service request when conditions prevent immediate fulfillment. This allows DSPs to manage scheduling challenges, unavailable resources, or unforeseen events without canceling the request.

Requests marked On Hold retain their metadata and assignment details, and can later be Resumed or Rescheduled without data loss.

When to Use On Hold

Typical situations that justify putting a request on hold include:

Field not ready due to irrigation or land prep delays.
Drone or pilot not available temporarily.
External dependencies (e.g., agrochemical delivery, weather conditions).
Internal or platform-level delays.

Available From

The On Hold button is displayed in the top-right action bar of the Request Details Panel when the request status is either:

Accepted
Rescheduled
In Progress

Only one active request can be placed on hold at a time.

Put a Request On Hold

Follow these steps to initiate the On Hold process:

Open Request Details
Go to the My Requests section and select a request with an active status.
Select On Hold from Actions Dropdown
- In the Request Details panel, open the Actions dropdown located at the top-right (above the History/Comments tab).
- Choose On Hold from the list.
Select Reason in Dialog
A dialog titled “Put Request On Hold”
- Choose a reason from the predefined list:
  - Field Not Ready
  - Chemical Not Available
  - Drone or Pilot Not Available
  - Weather Issues
  - Internal Delay
  - Other
- If Other is selected, a text box appears where the user must enter the reason manually.

4. Confirm Action

Once a valid reason is selected, the OK button becomes enabled.
Click OK to confirm.
Alternatively, click Cancel to cancel and exit without making changes.

5. Acknowledge Confirmation
A confirmation dialog appears stating:

“Request has been successfully placed on hold.”

Click Continue to return to the Request Details screen.

Request Status and Timeline

Once On Hold is confirmed:

The Request Status updates to On Hold.
A new entry is added to the Request History panel, indicating:
- Timestamp
- Reason for putting on hold (from list or entered manually)

This status change ensures DSPs and assigned pilots are informed of delays without cancelling service.

Summary

Step	Description
Eligible request	Must be in Accepted, In Progress, or Rescheduled state
Access On Hold feature	Via top-right action bar in Request Details
Provide reason	Select from list or enter a custom reason if “Other” is chosen
Confirm action	Submit by clicking OK
Review confirmation	Acknowledge success popup
Status and timeline log	Request marked On Hold with reason and timestamp logged

8.9 Complete Request

Once a service request has been executed in the field, it must be marked as Completed to transition it through the final stage of the service lifecycle.

How Completion Works

Role	Action
Pilot	Marks request as Completed after field service (via Pilot Mobile App).
DSP (Web)	Can now also mark request as Completed directly from the DSP Web Portal.
System	Updates status across both platforms and syncs related payment information.

Completion Scenarios

Pilot Completion (Mobile App)
- The assigned pilot completes the spraying or survey service.
- Using the Pilot Mobile App, they mark the request as Completed.
- A confirmation prompt ensures verification of completed area and drone details.
- Completion via the Pilot App is the primary flow (see Step 1).
DSP Completion (Web Portal)
- DSPs can now select Completed from the Status dropdown in the Request Details panel.
- When selected, a dialog appears to capture the completed area (by Acre or by Number of Tanks).
  - Enter the value in the provided field.
  - Click Complete to finalize, or Cancel to exit without saving.
- Once confirmed, a Request Completed message is displayed with the request number.
- The Request Details panel and History timeline update to reflect the Completed status.

Process Flow

Step 1 – Service Execution (Pilot App)

The assigned pilot performs the spraying or survey service.
The pilot marks the request as Completed through the Pilot Mobile App.
Confirmation ensures the area covered and drone usage details are accurate.
🧠 Completion via Pilot App remains the default operational flow.

Step 2 – Web Portal Completion (DSP Role)

In addition to pilots, DSPs can now mark a request as Completed:
1. Open the Status dropdown in the Request Details panel (top right above History/Comments).
2. Select Completed from the list.

3. This will show Area Covered dialog.

4. In the Area Covered dialog, choose Acre or Number of Tanks and enter the value.

5. Click Complete to proceed, or Cancel to abort.

6 A confirmation message appears:

- “Request Completed! Your request no. <Request Number> has been completed.”

7. The status and timeline update automatically.

Step 3 – Auto-Sync Across Platforms

Once marked Completed (by Pilot or DSP), the status is synchronized across both the Pilot Mobile App and the DSP Web Portal.
DSPs can review payment details in read-only mode.
Only after Completion can the request proceed to Payment Handling.

Summary

Action	Role	Where It’s Performed
Complete the request	Pilot / DSP	Pilot Mobile App / DSP Web Portal
Update visible in portal	Auto-sync	DSP Web Portal
Payment handling	Post-completion	DSP Web Portal (review)

8.10 Paid

This section explains the steps to mark a completed service request as Paid within the BhuMeet Web Application interface. This action is typically performed by a DSP once the drone service has been completed and payment is confirmed.

Steps to Mark a Request as Paid

1. Open the Completed Request

- Navigate to the Requests section from the left-hand side menu.
- In the All Requests panel, locate a request that has the status Completed.
- Click on the request to open its details.

2. Select the “Paid” Option

- On the top-right of the Request Details pane, locate dropdown list and select the Paid option from the list.

This triggers a confirmation indicating successful payment registration.

3. Acknowledge the Confirmation Dialog

- The confirmation dialog shows the message:
  “Request Paid. Your request no. #xxxxxxxx has been paid!”
- Click the Continue button to dismiss the dialog and return to the Request Details view.

4. Review the Updated Request Status

- In the History tab on the right, a new milestone titled Paid is now visible.
- This entry includes the exact time and date when the payment was confirmed.
- This confirms the request’s transition from Completed to Paid.

Summary

Marking a request as Paid ensures that the financial transaction for the completed drone service is officially registered in the BhuMeet system. This step enhances recordkeeping, supports transparency, and enables audit tracking for DSPs and their associated team members.

Key Notes

Only DSP Admins have permission to mark a request as paid.
Paid status is irreversible. Ensure payment has been received before confirming.
The Paid status is timestamped for audit trail and history logging.

8.11 Create Request

The Create Request feature allows DSPs (Drone Service Providers) to manually log new farmer service requests. This is typically used when a farmer contacts the DSP via phone, in person, or through any offline channel. All manually created requests are visible under the My Requests section and follow the same lifecycle as regular requests submitted by customers.

Accessing the Form

To create a new service request:

Log in to the BhuMeet Web Application using your DSP credentials.
Navigate to the My Requests section from the left-side menu.
Click the + Create Request button located at the top-right of the dashboard.

This opens a modal dialog with a location-integrated map and a request input form.

Steps to Create

Follow the steps below to complete the request creation process:

Enter the Farmer’s Mobile Number.
This must be a valid 10-digit number. It is used for identification and contact purposes.
Enter the Farmer’s Name.
Provide the full name of the farmer.
Search for the Service Location.
- Start typing the area name in the search bar. (e.g., “KKW College Nashik”).
- Select the correct address from the auto-suggest list.
- The location and map below will auto-update.
Select the Preferred Date.
- Use the calendar picker to choose the intended date of service.
- Only today’s or future dates can be selected.
Select the Agrochemical.
- Choose an option from the dropdown (e.g., Grow, Grow Plus).
- This list is pre-configured and may vary by service location.
Choose the Unit of Area.
- Toggle between Acre and Tank using the buttons.
- Acre is the default selection.
Select the Crop.
- Choose the crop that the service will cover (e.g., Cotton, Brinjal).
Enter the Area Value.
- Based on the selected unit, input the numeric value (e.g., 10 for 10 acres).
- This field accepts only positive numeric values.
Click the Create Button.
- The Create button becomes active once all required fields are completed.
- A confirmation popup will appear stating:
  ✅ “Request created successfully”.

10. Click Continue to Finalise.

- The modal closes and the new request appears on the dashboard with a Placed

Field Details

Field Name	Description
Mobile Number	10-digit number of the farmer. Used for identity and updates.
Name	Farmer’s full name. Required field.
Location Search	Location lookup via map-integrated search bar. Mandatory to select from dropdown.
Date	Preferred service date. Past dates are restricted.
Agrochemical	Agrochemical to be used during spraying. Must be selected from available list.
Unit Selection	Acre or Tank. Affects how area is entered.
Crop	Type of crop being serviced. Populated from predefined list.
Area	Size in Acres or number of Tanks. Must be a valid positive number.

Validations and Rules

⚠️ Warning:

Location must be selected from suggestions. Manual typing without selection is invalid.
Mobile Number must be valid.
Area must be a positive numeric value greater than zero.

💡 Tip:
Start typing well-known local landmarks to improve location match accuracy.

Behavior After Creation

The request is created with Placed
It appears immediately in the My Requests
No pilot or drone is assigned at the time of creation unless done later manually.
The request follows the standard lifecycle (Accept → Schedule → Complete).

Summary

Action	Purpose
Manually log service	Add offline or call-based farmer requests into the system
Map-integrated location	Pinpoint geo-location for accurate spraying coordination
Choose crop and chemical	Define what service will be performed and on what crop
Area-based estimation	Decide pricing and coverage via acre/tank unit
Immediate tracking	Request becomes instantly trackable in dashboard and reports

8.12 Lifecycle

This section offers a quick reference to understand how service requests move through various statuses in the BhuMeet Web Application.

Each status unlocks specific actions, determined by the request’s progress and the assigned user role (e.g., DSP or Pilot). These transitions are tracked in the Request Timeline, and most actions are performed via the Request Details Panel.

Typical Lifecycle Flow

Placed: Request created but not yet acted on.
Accepted: Request approved by DSP.
Ongoing: Marked automatically when service starts.
Completed: Pilot confirms completion via mobile app.
Paid: Payment confirmed (Pilot only).
On Hold / Rescheduled: Temporary diversion from the main flow.
Rejected / Cancelled: Final status; no further actions possible.

Status Actions

Status	Permitted Actions
Placed	Assign drone/pilot, Accept, Reschedule, Cancel
Accepted	Assign resources, Reschedule, Put On Hold, Cancel
Ongoing	Mark as Completed (Pilot App only)
Completed	View only
Paid	View only
Rescheduled	Resume, Modify Schedule
On Hold	Resume, Reschedule
Cancelled	View only

Note: While the standard lifecycle follows the sequential flow described above, DSPs have the flexibility to directly update a request to any status within the Approved category. For details, refer to Changing Status.

BhuMeet Web User Manual

8. Requests

8.1 Dashboard

Key Components

8.2 View and Filter

1. Request View Modes

2. Filters and Tools

3. Status Tabs

4. Pagination

8.3 Request Statuses

Changing Status

Request Status Types

Lifecycle Flow

Status-Driven Actions

Reschedule and Resume

Best Practices

8.4 Request Details

Access Request

Request Details Panel

Request Metadata

Summary

8.5 Assign Resources

Assign Resources

Resource Assignment

Assignment Controls

Validations and Permissions

Summary

8.6 Accept or Reject

Accepting a Request

Cancelling a Request

Reconsidering Rejected Requests

Best Practices

Status Transitions

8.7 Reschedule

When to Use Reschedule

Available From

Rescheduling Steps

History and Status Update

Summary

8.8 On Hold

When to Use On Hold

Available From

Put a Request On Hold

Request Status and Timeline

Summary

8.9 Complete Request

How Completion Works

Completion Scenarios

Process Flow

Summary

8.10 Paid

Steps to Mark a Request as Paid

Summary

8.11 Create Request

Accessing the Form

Steps to Create

Field Details

Validations and Rules

Behavior After Creation

Summary

8.12 Lifecycle

Typical Lifecycle Flow

Status Actions

Related