How to use a Righthand with Rentman
Use Righthand to prepare a Rentman equipment-and-crew readiness review for an event project.
Quick answer
Use Righthand to prepare a Rentman equipment-and-crew readiness review for an event project. Keep reservations, quantities, and actual availability separate.
Start with a reviewable deliverable, keeping Rentman as the accepted home for its records. This guide uses an explicitly approved snapshot or browser read; it does not assume that every provider API action is exposed by your Righthand connection.
Evidence and access
Rentman's support center covers rental inventory, crew scheduling, and account configuration. See the official Rentman reference. Provider capabilities and Righthand's available tools are separate checks.
Scope the packet to the approved rental project, equipment assignments, schedule, and confirmed reservation state. Retain the owner's unit and availability definitions. Verify the required tools and owner-approved scope through Righthand integrations; use the supplied packet when a native read is unavailable.
Define the objects and authority
Include these fields in the working input: project reference, equipment line, requested quantity, reservation status, crew role, dates, owner. These are the requested review columns, not a promise that every provider endpoint returns them under those exact names.
Do not interpret a draft requirement as a confirmed allocation. Substitutions, bookings, and commercial changes need the production owner's approval.
| Responsibility | Owner |
|---|---|
| Prepare source scope and access | Account owner |
| Organize evidence and proposed next steps | Righthand |
| Approve consequential changes | the production manager |
Illustrative first-run brief
Use the owner-provided Rentman snapshot or approved read-only view. Review the supplied project equipment and crew lists. Flag unconfirmed quantities, missing roles, and conflicting date windows. Prepare questions without allocating stock or staff. Run once for the agreed sample, using America/Los_Angeles for the review deadline and preserving source timestamps separately. Return the draft in this conversation by Friday at 3 PM Pacific for the production manager to review. Include source references and missing fields. Do not write records, spend money, change permissions, or send external messages. Stop and report an unavailable source rather than substituting another account.
Expected result and verification
A requested camera package can be listed while its reservation remains unconfirmed. The report preserves that gap.
Check a line item and its project date window against the original reservation view. Record the source cutoff, applied filters, and items excluded from the sample. The reviewer should be able to follow each consequential finding back to an original object. A well-written summary is not evidence that a proposed action happened. If a later write is authorized, verify its specific result separately before changing the task's status.
Illustrative input and draft output
These synthetic entries show the requested review, not live account results or a provider field schema.
| Source item | Supplied observation | Draft conclusion |
|---|---|---|
| Equipment A | Return verified before need | Candidate allocation |
| Equipment B | Return only planned | Availability provisional |
| Project C | Overlapping allocation | Ask coordinator to resolve |
Common failure and recovery
Similar equipment names can hide different kits or accessories. Resolve the specific item reference before suggesting substitutions.
If a project allocation conflicts with an equipment return time, flag the specific resource and ask the rental coordinator to resolve availability.
FAQ
What should the reviewer verify first?
Verify project and equipment IDs, quantities, allocation dates, preparation windows, and confirmed return evidence. Planned availability is distinct from equipment physically returned.
How should a repeat run be scoped?
Retain project IDs and resource schedule cutoffs. Refresh overlapping bookings and return evidence at each review; do not carry yesterday's available quantity into a new event automatically.
For connection and permission details, use Righthand Docs. Review Pricing alongside any separate provider charges before expanding the workflow.