Module 6: Run and improve
Review one complete operating cycle
Map current systems, improve one painful workflow, compare the result with your records, and decide the next change.
Outcome
Complete or map one real operating cycle, compare the records, and choose one improvement supported by what you observed.
Map the current system before changing it
List every place that currently holds customer, equipment, rental, payment, schedule, service, and document information. Mark the main record your team trusts for each category and who updates it. Two spreadsheets with similar names are not one reliable record.
Choose one painful workflow. Good candidates are specific, frequent, and observable: confirming delivery readiness, finding the current balance, matching equipment to a rental, or closing a pickup. Avoid “automate everything” as a first project.
- 1Inventory systems, files, paper records, and responsible owners.
- 2Name the authoritative source for each record category.
- 3Choose one workflow and record its current steps, time, errors, and rescue work.
- 4Define the result that would count as an improvement in the next cycle.
Prepare a reviewed transition or migration
Map source fields and record relationships before importing or re-entering data. Decide how duplicates, inactive records, balances, attachments, and exceptions will be treated. Historical transactions must not become new payment instructions.
Use a small representative sample first. Reconcile counts, totals, relationships, and known edge cases. If the repository or product does not support the required importer, use a reviewed manual plan or obtain a separate fixed engineering scope.
- 1Choose a representative sample with normal records and known exceptions.
- 2Write the field map, duplicate rule, balance treatment, and excluded categories.
- 3Rehearse the sample and compare source and destination totals.
- 4Record unresolved exceptions and approve or reject the cutover explicitly.
Review the real operating cycle
Follow a rental through inquiry, agreement or requirements, delivery, billing, payment, service, pickup, and closeout. Review customer communication and the records at each step. A completed delivery does not mean the invoice and payment records match, and a returned unit does not mean the rental is closed.
Separate demo activity from real activation measures. For a real cycle, record time to the first meaningful workflow, rescue steps, customer-impacting errors, direct cost, and owner time without sending sensitive renter data to marketing analytics.
- 1Select one completed or active real rental that can be reviewed under your privacy policy.
- 2Trace its records and evidence through each operating transition.
- 3Compare payment, equipment, schedule, and document states for consistency.
- 4Record friction, correction work, owner time, and the customer impact in general terms.
Improve one control and repeat
Choose the smallest change that removes the observed obstacle: a required field, clearer ownership, a checklist, a notification, or a supported automation with a defined exception path. Do not automate an unclear decision.
Review the next operating cycle using the same baseline. If the change moves work elsewhere or creates repeated rescue, revise it. Expansion should pause when navigation, reconciliation, or support load repeatedly prevents customers from completing the intended path.
- 1Select one friction point supported by the cycle review.
- 2Assign the change, evidence, exception path, and rollback owner.
- 3Apply the change in the supported workflow without changing older records just to make them match.
- 4Review the next cycle and decide whether to keep, revise, or remove the change.
Completion check
Reconcile one cycle and choose the next improvement
- Current systems and authoritative sources are named.
- One painful workflow is selected with a baseline and expected improvement.
- Any transition uses a sample, reconciliation, exception record, and explicit cutover decision.
- Customer, equipment, rental, and balance totals are reviewed separately.
- The next improvement is based on observed friction rather than a broad automation goal.
Use this in Rivet
Organize one difficult part of the operation in Rivet.
Use connected inquiry, customer, rental, invoice, payment, equipment, delivery, service, return, and closeout records to improve one operating cycle without changing older records just to make them match.
- Choose one workflow and identify the main record you trust today.
- Compare a small group of records before switching.
- Review the next cycle and keep, revise, or remove the change.
The lesson and tool remain free without an account. New workspaces are free for up to three active rentals with no payment method required. Optional services have separate published scopes and limits.