CrewViper

FREE WORKSHEET · NO EMAIL REQUIRED

Run one job.
Then decide.

Before moving your business into a new app, prove that one job survives every handoff. Use this scorecard with CrewViper or any field-service software you are evaluating.

Print or save as PDF using your browser’s Print menu. The boxes are for marking on paper; this page does not save answers.

Set the test up safely.

Use one owner or office tester and one crew tester. Start with fictional data in a sandbox. Keep your current software as the source of truth, and leave real customer messages, payments and integrations off.

App / version: __________________Test date: __________________Office tester: __________________Crew tester: __________________

Using the CrewViper demo? It uses fictional data and resets on refresh. Use an existing sample job to explore the screens. The exact practice job below is a worksheet example, not a promise that the demo contains it. Persistent storage, backup recovery, live email and payment processing must be tested separately in an authorized pilot.

Read the office-to-field guide · Plan a small first import · Check team size and costs

One fictional job. No ambiguity.

Peak Garage Co. → Morgan Example: garage reset. Pick a future weekday, schedule 9:30–11:30 a.m. in America/Denver, and assign the fictional Blue Crew. Use a clearly labeled training location, not a homeowner’s real address. Contact: morgan@example.test. Instructions: organize the west wall; do not discard anything without approval.

Practice quote: no tax, discount or deposit in this scenario
LineQuantityUnit priceTotal
Garage reset service1$300.00$300.00
Storage bin2$25.00$50.00
Expected quote and invoice total$350.00

Use a non-personal before/after sample image. Record the same job ID across every screen. If your sandbox cannot perform a step, mark it Not tested, not Pass.

Five outcomes worth proving.

CHECK 1 OF 5

The quote is accurate.

Target: Exactly $350.00, with the right customer and two line items.

  • Check the quantity of two bins and the $50.00 line total.
  • Preview the customer-facing quote. Verify scope, quantity and total match the office view.
  • Complete a test approval, then retry or reload. Confirm one acceptance and no duplicate quote.

Evidence: Record the quote number, total and approved revision. Do not use a real customer or send a live message.

Mark one: □ Pass   □ Not yet   □ Not tested
What needs fixing:

CHECK 2 OF 5

The handoff has a time and an owner.

Target: One job, Blue Crew, a two-hour window, the intended local date.

  • Find the scheduled job in the office calendar and the assigned crew’s view.
  • Move the visit to 10:00 a.m.–noon on the same date. Refresh the crew view and confirm both times changed.
  • Open another move, then cancel. Confirm the last saved time is unchanged.

Evidence: Record the job ID, timezone, assigned crew and final start/end. “Tuesday” alone is not an appointment.

Mark one: □ Pass   □ Not yet   □ Not tested
What needs fixing:

CHECK 3 OF 5

The crew can finish without calling the office.

Target: A complete work record, with zero office pricing visible to crew.

  • On a phone, find the job, location and west-wall instructions.
  • Start the job, add a sample before photo and note, then add an after photo and complete it.
  • Switch back to office: confirm the same job shows completion and the evidence. Check the crew view contains no quote or invoice amounts.

Evidence: Record the completion status and photo/note presence. Time how long it takes a new tester to find the next action; write the result, rather than guessing.

Mark one: □ Pass   □ Not yet   □ Not tested
What needs fixing:

CHECK 4 OF 5

Completion becomes the correct invoice.

Target: One linked invoice for $350.00; completion alone does not mean paid.

  • Create the invoice from the approved work. Confirm the customer, job link and two line items.
  • Cancel an edit and return: the saved total must still be $350.00.
  • In an isolated sandbox only, record a clearly simulated $100.00 payment. Expect $250.00 remaining; retry the action and verify the payment is not duplicated.

Evidence: Record the invoice number, total, simulated payment and balance. No card entry, live charge or real invoice delivery is needed.

Mark one: □ Pass   □ Not yet   □ Not tested
What needs fixing:

CHECK 5 OF 5

The work survives a bad day.

Target: The saved record and photos return after a restart and a separate restore.

  • In an authorized persistent pilot, sign out/in and restart the app. Confirm the same job, assignment and photo contents remain.
  • Have the operator restore a backup into a separate empty test environment, with sending and payment integrations disabled.
  • Compare the restored job, photo and invoice against the backup timestamp. Record recovery time and any missing work after that timestamp.

Evidence: Record backup time, restore date and observed data loss. Refreshing a fake-data demo does not prove durability; a backup that has not been restored remains Not tested.

Mark one: □ Pass   □ Not yet   □ Not tested
What needs fixing:

Decide from the evidence.

  • 5 Pass: consider one approved real job in parallel with the current system. This is a pilot decision, not a full security or compliance certification.
  • Any Not tested: schedule that test before relying on the missing capability.
  • Any Not yet: capture the exact step and expected result, fix it, and rerun the affected handoff.
  • Stop immediately: another company’s data appears, crew sees pricing, photos disappear, money duplicates, or an unapproved message is sent.

Result: ____ / 5 passed   ____ not yet   ____ not tested
Next test / owner / date: ________________________________________
Rollback plan: keep current system authoritative until __________________

Feature counts make good sales copy. A clean handoff makes a good working day. Keep this sheet and compare the same five outcomes across every app on your shortlist.

Want to test it with your own team?

Explore the real CrewViper interface with fictional data first. Early-access requests are optional and reviewed individually; they do not create an account or require payment. No customer files are collected on this worksheet.