Delivery solutions
Choose the delivery model around the work.
Combine the operating program, service, vehicle, equipment, crew, and requirements into one structured Signal delivery plan.
Prepare a delivery requestDELIVERY PLAN
Delivery programs + services
Start with the pattern. Then define the service.
A Program defines how the delivery operates. A Service defines what the work or receiving handoff requires. Together they establish the operating foundation.
Programs
Services
Core delivery / 04
Handling & crew / 04
Receiving / 05
Finishing & recovery / 07
Catalogue capability ≠ local availability Signal can structure requests around the capabilities shown here. Actual fulfillment depends on the request, market, operating requirements, and available network capacity.
Vehicle capacity
Match transport capacity to the load and route.
Vehicle fit considers shipment profile, loading method, route, access, and service requirements. Selection informs the plan; it does not reserve a specific vehicle.
Explore all vehicles →Straight truck
An enclosed truck family with multiple size classes. The appropriate variant depends on the complete request.
Loading method · route · receiving
Vehicle selection informs planning. It does not reserve or guarantee a specific asset.
Handling equipment
Organize handling, access, and protection around the work.
Some equipment may be part of a provider configuration. Other capability, such as forklift access, may need to exist at the site. Signal reviews the distinction for the request.
Explore Services & Equipment →Crew
Set the human requirement deliberately.
Crew configuration follows the handling scope, shipment, equipment, access, and receiving conditions. It does not imply certification or guaranteed availability.
Explore Handling & Crew Support →Receiving service
Define where the handoff ends.
Receiving depth determines how far the planned handoff extends. Access, carry distance, stairs, crew, equipment, and destination conditions can change the scope.
Unpacking, packaging removal, assembly, approved installation tasks, and haul-away are optional tasks reviewed separately. They are not automatic receiving tiers.
Explore receiving service boundaries →Inside
The receiving point is beyond the outside threshold, with the access path reviewed in advance.
Combined requirements
Multiple requirements. One connected plan.
This example assembles a scheduled appliance delivery with transport, equipment, crew, receiving, timing, and proof expectations. The result is prepared request context, not confirmed capacity.
ASSEMBLED
- Operating pattern
- Scheduled
- Field configuration
- Vehicle · equipment · crew
- Handoff
- Room of Choice
Field execution
People carry the plan.
The delivery professional or crew receives relevant context for the work. Signal keeps operating support, progress, handoff results, and available proof connected to the request record.
PROFESSIONAL / CREW
Communication · execution · relevant updates
Build around the work
Start with the shipment, locations, timing, service, handling, and receiving outcome.
Signal can help structure the request around what the delivery requires.