This is a vendor-documented trial method, not a hands-on product score. It follows one synthetic operating record: Riverview Property Management needs a post-move-out clean at Suite 204 this Friday, then wants a weekly common-area clean beginning the following Monday. Use fictional contacts, addresses, prices, images, and notes. Run the same record in each trial so the saved evidence answers operational questions rather than reflecting a product score.
1. Capture a synthetic request
Task: Create a fictional request from Riverview for the Suite 204 move-out clean. Include a contact, property address, requested date, a short scope, and two fictional room photos. Jobber’s documentation covers request creation, intake forms, photos, measurements, and choices for moving a request into a job workflow. Jobber Request Basics
Evidence to save: Save a screenshot or PDF of the completed intake record, including the received scope and attached fictional images. Record which required fields could be made explicit during your trial.
Pass/fail question: Can a dispatcher capture enough information in one synthetic request that the estimator does not need to recreate the customer, location, scope, or image context?
2. Record property and job details
Task: Turn the move-out request into a one-off cleaning job and enter the fictional Suite 204 details: 3,200 square feet, four offices, two restrooms, a break room, access after 6 p.m., and a keyholder instruction. Jobber documents one-off and recurring jobs and uses move-out and weekly-cleaning examples; its job documentation also covers job notes, attachments, checklists, scheduling, assignments, and billing. Jobber Job Basics
Evidence to save: Save the job-detail view and a copy of the fictional cleaning scope. Note whether property instructions, job instructions, and repeatable cleaning checks remain distinguishable in the record.
Pass/fail question: Can the trial record preserve the operational detail needed by a crew without relying on a separate spreadsheet or an ambiguous free-text note?
3. Produce a quote
Task: Build a fictional quote for the move-out clean using separate line items for labor, restroom deep cleaning, interior-window cleaning, and disposal. In Jobber, official documentation describes quote line items, statuses, PDF output, activity history, and conversion to a job. Jobber Quote Basics
Evidence to save: Save the customer-facing quote document, the line-item view, and the activity history available in the trial. Record the quote total and the fictional assumptions used to reach it.
Pass/fail question: Does the quote make the priced scope legible to both Riverview and the operations team, with a durable record of what was proposed?
4. Revise scope and options
Task: Change the fictional scope after Riverview asks to add carpet spotting and remove interior-window cleaning. Create, where the trial permits, a second option that keeps windows but uses a different labor allowance. Do not assume a particular revision, versioning, or option feature exists unless the trial demonstrates it; instead test the route your chosen product provides.
Evidence to save: Save the original quote, the revised customer document, and any visible history showing how the change was recorded. Add a short internal note explaining the fictional reason for the revision.
Pass/fail question: Can a dispatcher show exactly what changed, what the customer is being asked to approve, and which scope should reach the cleaning crew?
5. Capture customer approval
Task: Use the product’s trial workflow to represent Riverview approving the revised move-out scope. Jobber documentation identifies quote statuses, PDF output, activity history, and conversion from quote to job as documented parts of its quote workflow. Jobber Quote Basics
Evidence to save: Save the status or history view that represents the synthetic approval, plus the final customer document. If approval is handled outside the product in the trial, save the internal record you would require to link that approval back to the quote.
Pass/fail question: Is there a clear, auditable handoff from an approved fictional scope to the version staff should schedule and perform?
6. Schedule and assign the work
Task: Schedule the Suite 204 move-out clean for Friday evening and assign a fictional two-person crew. Then create the weekly common-area service as a separate recurring-work test. Jobber documents scheduling and assignments on jobs. Jobber Job Basics Housecall Pro states that recurring jobs suit repeat cleaning and distinguishes their schedules, invoices, and job records from multi-day appointments and job segments. Housecall Pro appointments, segments, and recurring jobs
Evidence to save: Save the calendar or schedule view, the assigned crew view, and the first recurring-service record. Record whether the one-time move-out and weekly service stay understandable as separate operational commitments.
Pass/fail question: Can staff see who owns the Friday job while maintaining a distinct record for the ongoing weekly clean?
7. Manage an urgent or unassigned job
Task: Add a fictional urgent request: a spilled-coffee cleanup in Suite 112 needed before an executive meeting tomorrow morning. Leave it unassigned initially, then test how a dispatcher would find it, assign it, and preserve the reason for its priority. This is a reader trial task; the source packet does not establish a particular urgent-job queue or alert behavior.
Evidence to save: Save before-and-after views showing the unassigned synthetic job, its final assignment, and the priority instruction. Note the clicks, filters, or reports required.
Pass/fail question: Can a dispatcher reliably distinguish an urgent unassigned job from routine scheduled cleaning without losing the customer context or scope?
8. Record technician work and notes
Task: For the fictional Friday clean, have the assigned trial user record completion of the four offices, restrooms, break room, and disposal task, then add a fictional note: “Suite 204 key returned to lockbox.” Jobber’s job documentation covers checklists and notes. Jobber Job Basics
Evidence to save: Save the completed job view, any checklist state, the technician note, and the time at which each was recorded if shown. Keep all text fictional.
Pass/fail question: Can an office user later determine what work was completed, what remained open, and what site-specific information the crew left behind?
9. Attach photos or files
Task: Attach fictional before-and-after photos of the break room plus a fictional floor-plan PDF to the Suite 204 record. Jobber’s request documentation covers photos, and its job documentation covers attachments. Jobber Request Basics Jobber Job Basics
Evidence to save: Save the attachment list and one view showing where the files are visible in the workflow. Record whether the attachments remain available after the request becomes a job and after the job is billed.
Pass/fail question: Can the team retrieve the synthetic evidence from the record where a dispatcher, crew member, and billing user would reasonably look for it?
10. Create the invoice and customer document
Task: Create the fictional invoice for the approved Suite 204 move-out scope, then prepare the customer document your trial workflow produces. Jobber documents billing as part of the job workflow, while quote documentation describes PDF output. Jobber Job Basics Jobber Quote Basics
Evidence to save: Save the invoice detail, the final customer-facing document, and the line-item totals. Note whether fictional job notes, attachments, or completion checks appear where you would expect; treat the result as a trial observation rather than a documented capability unless the packet supports it.
Pass/fail question: Does the customer document unambiguously connect the billed work to the approved fictional scope and the completed job?
11. Review job cost and margin
Task: Enter a fictional labor cost and supply cost for the Suite 204 move-out, then attempt to review job cost and margin using the product’s available trial workflow. Jobber documentation describes job-cost export, but the packet does not establish specific cost-entry fields, margin calculations, or reporting screens. Jobber Job Basics
Evidence to save: Save the cost inputs you can record, the resulting job-cost or export view, and a separate calculation of the fictional gross margin if the product does not calculate it in the trial.
Pass/fail question: Can an operator trace a quoted $1,240 fictional job from revenue to labor and supplies well enough to answer whether it met the intended margin?
12. Export the operating record
Task: Export or otherwise preserve the fictional operating record for the move-out job and weekly-service test. Housecall Pro documents job and estimate list reporting with filtering, sorting, visible-column selection, and CSV report export. Housecall Pro Job & Estimate List Reporting Jobber documentation describes job-cost export. Jobber Job Basics
Evidence to save: Save the exported CSV or other available output, the chosen columns and filters, and a screenshot of the source list before export. Check that the file contains only fictional data.
Pass/fail question: Can the operations team produce a usable trial record containing the identifiers, status, schedule, assigned crew, quoted or billed amount, and cost information it needs for its own review?
Sources
- Request Basics — Jobber.
- Quote Basics — Jobber.
- Job & Estimate List Reporting — Housecall Pro.
- Job Basics — Jobber.
- Appointments vs. Segments vs. Recurring Jobs — Housecall Pro.