How to use the scorecard
Choose one anonymized automotive or flat-glass job. Ask each vendor to demonstrate the same transitions. For every row, record:
- 0 — Missing or unclear: not demonstrated and not documented.
- 1 — Partial: possible with a workaround, duplicate entry, or separate tool.
- 2 — Demonstrated: completed in the current product with a clear record.
- N/A: intentionally outside your shop’s requirements.
Do not calculate the total until you identify your non-negotiable rows.
Workflow scorecard
| Area | Requirement to demonstrate | Weight | Score | Evidence or concern |
|---|---|---|---|---|
| Intake | Capture source, contact, vehicle/property, requested work, photos, and unknowns | |||
| Ownership | Assign an owner, status, next action, and due time | |||
| Automotive | Represent vehicle, package, film, shade, add-ons, and removal | |||
| Flat glass | Represent site, room, panel, measurements, film, and scope revisions | |||
| Estimating | Build and revise an itemized estimate without losing prior decisions | |||
| Approval | Record exactly what the customer accepted and when | |||
| Deposits | Request and record deposits against the correct job | |||
| Scheduling | Reserve duration, staff, bay or work area, and dependencies | |||
| Install handoff | Show installers the current scope, notes, photos, and commitments | |||
| Changes | Record a changed scope and customer approval before work continues | |||
| Completion | Connect completed work, photos, invoice, payment, and warranty | |||
| Follow-up | Keep the next customer action visible after completion | |||
| Permissions | Limit access by role and remove former staff access | |||
| History | Show who changed important customer, scope, or money records | |||
| Export | Export customers, projects, money records, and supporting files | |||
| Support | Define who configures, imports, trains, and resolves failed workflows |
Commercial and implementation check
| Question | Vendor answer | Verified source |
|---|---|---|
| What is the complete recurring subscription cost for our staff and locations? | ||
| Which features or usage levels cost extra? | ||
| Which payment, messaging, storage, or integration fees are separate? | ||
| Who owns import cleanup and validation? | ||
| What data can an owner export without contacting support? | ||
| What happens to data and files after cancellation? | ||
| Which capabilities are in beta, gated, or dependent on provider approval? | ||
| What support channel and response expectations are included? |
Failure and exception cases
Include failure and exception cases in each demonstration:
- A customer changes the scope after approval
- A deposit fails
- An appointment moves to another installer or bay
- A text or email cannot be delivered
- Staff create a duplicate customer
- A technician lacks permission to view a record
- A refund or credit is needed
- An export contains more records than fit on one screen
A useful system makes failure visible and recoverable. It should not silently convert an operational problem into missing context.
Decision record
Complete this before selecting a platform:
The three workflows we cannot compromise:
The largest unresolved implementation risk:
The person responsible for configuration and migration:
The evidence we still need before deciding:
PRINTING TIP
Use your browser’s print command to save this scorecard as a PDF. Keep one completed copy per product so the decision can be revisited without relying on memory.