Skip to content

Repair Statuses

Repair Statuses allow managers to define and maintain a standardized list of repair progress indicators that track equipment through the entire repair workflow. This feature supports both custom status definitions and predefined standard statuses to ensure consistent progress tracking across your repair operations.

Overview

With Repair Statuses, you can:

  • Create standardized status codes with clear descriptions
  • Map custom statuses to standard workflow stages for reporting consistency
  • Set a default status that's automatically assigned to new repair orders
  • Track repair progress systematically from receipt to delivery
  • Support both standard repair flows and specialized workflows
  • Generate comprehensive reports on repair progress and bottlenecks
  • Improve customer communication with clear status updates
  • Enable automatic lifecycle date tracking for key repair milestones

Understanding Repair Statuses

Repair Statuses serve as progress indicators that track equipment through your repair workflow. Each status consists of:

  • Code: A short, unique identifier (up to 20 characters) for quick reference
  • Description: A clear explanation (up to 100 characters) of what the status represents
  • Standard Status: An optional mapping to predefined workflow stages for reporting consistency
  • Default Status: An optional designation that automatically assigns this status to new repair orders

This dual approach allows you to create custom statuses that meet your specific needs while maintaining compatibility with standard reporting and workflow patterns.

Default Status Feature

The Default Status feature streamlines repair order creation by automatically assigning a predetermined status to new repair orders. This ensures consistency in your workflow and reduces manual data entry.

Key Features

  • Automatic Assignment: New repair orders automatically receive the default status when created
  • Uniqueness Enforcement: Only one repair status can be marked as default at any time
  • Workflow Efficiency: Reduces manual status selection and ensures consistent starting points
  • Flexibility: Default status assignment doesn't override manually entered statuses

How Default Status Works

  1. Configure Default: Mark one repair status as the default in the Repair Statuses setup
  2. Automatic Assignment: When technicians create new repair orders without specifying a status, the system automatically assigns the default status
  3. Manual Override: Users can still manually select different statuses during repair order creation
  4. Uniqueness Maintained: If you mark a different status as default, the previous default is automatically unmarked

Default Status Best Practice

Choose a default status that represents the most common starting point for repairs, such as "RECEIVED" or "LOGGED". This status should represent the first step in your typical repair workflow.

Standard Status Workflow

Quick Repair includes predefined standard statuses that represent a typical repair workflow:

Standard Status Description Typical Use
Not Received Equipment has not yet arrived Initial status for scheduled repairs
Received Equipment has been received and logged Upon package receipt and initial inspection
Waiting for Customer Awaiting customer approval or response When estimate approval or information is needed
Waiting for Repair Equipment is queued for repair work Ready for technician assignment
In Progress Repair work is actively being performed Technician is working on the equipment
Repair Finished All repair work has been completed Quality check and testing completed
Shipped Equipment has been returned to customer Final status when repair is complete

Automatic Lifecycle Date Tracking

When repair orders are updated to statuses mapped to Received, In Progress, Repair Finished, or Shipped standard statuses, the system automatically populates corresponding lifecycle dates. Start Date has special set-once behavior (preserves the original repair commencement date), while other lifecycle dates prompt for confirmation when overwriting existing values. Learn more about Automatic Lifecycle Date Tracking.

Setting Up Repair Statuses

Prerequisites

  • You must have Manager permissions to create and modify repair statuses
  • The Quick Repair extension must be installed and configured

Creating a New Repair Status

  1. In Business Central, use the search function to find and open Repair Statuses.

  2. On the Repair Statuses page, select New to create a new record.

  3. Fill in the following fields:

  4. Code: Enter a unique identifier for the repair status (up to 20 characters)

    !!! tip "Naming Convention" Use descriptive codes like "DIAGNOSED", "PARTS-ORDERED", or "TESTING" for easy identification.

  5. Description: Provide a clear description of what this status represents (up to 100 characters)

  6. Standard Status: Optionally select the closest standard status for reporting purposes

    !!! note "Standard Status Mapping" Mapping to standard statuses helps maintain consistency in reports and enables standard workflow tracking, even when using custom status names.

  7. Default Status: Check this box if this status should be automatically assigned to new repair orders

    !!! warning "Default Status Uniqueness" Only one repair status can be marked as default at a time. If you mark a different status as default, the system automatically unmarks the previous default status.

Example Repair Statuses

Here are some common repair statuses you might want to set up:

Code Description Standard Status
LOGGED Equipment received and logged into system Received
DIAGNOSED Initial diagnosis completed In Progress
QUOTE-SENT Repair estimate sent to customer Waiting for Customer
APPROVED Customer approved repair estimate Waiting for Repair
PARTS-ORDER Waiting for replacement parts to arrive Waiting for Repair
REPAIRING Technician actively working on repair In Progress
TESTING Repair completed, undergoing quality testing In Progress
READY Repair finished and ready for pickup Repair Finished
COLLECTED Customer has collected repaired equipment Shipped
WARRANTY Under warranty review process Waiting for Customer

Configuring Default Status

To set up a default status for automatic assignment to new repair orders:

  1. Choose Your Default Status: Select the status that represents the most common starting point for new repairs. Typically this should be:
  2. LOGGED or RECEIVED: If most repairs start when equipment is received
  3. WAITING-DIAG: If repairs start in a diagnosis queue

  4. APPROVED: If most repairs have pre-approval before creation

  5. Mark as Default: On the repair status record, check the Default Status field

  6. Automatic Uniqueness: If another status was previously marked as default, it will be automatically unmarked

  7. Test the Configuration: Create a test repair order without specifying a status to verify the default is automatically assigned

Default Status Scenario

If you mark "LOGGED" as the default status, every new repair order created without a specific status will automatically be assigned "LOGGED" status. This ensures consistent workflow initiation and reduces manual data entry for technicians.

Managing Repair Statuses

Editing Existing Statuses

  1. Open the Repair Statuses page
  2. Find the repair status you want to modify
  3. Make your changes directly in the list
  4. The changes are saved automatically

Managing Default Status

Changing the Default Status: 1. Open the Repair Statuses page 2. Find the status you want to make the new default 3. Check the Default Status field for that status 4. The previous default status will be automatically unmarked

Removing Default Status: 1. Open the Repair Statuses page
2. Find the current default status (marked with a checkmark in the Default Status column) 3. Uncheck the Default Status field 4. New repair orders will no longer receive automatic status assignment

Impact of Default Status Changes

Changes to default status settings only affect new repair orders created after the change. Existing repair orders retain their current status regardless of default status modifications.

Deleting Repair Statuses

Before Deleting

Ensure the repair status is not being used in any existing repair records before deleting. Consider deactivating instead of deleting if the status has historical usage.

  1. On the Repair Statuses page, select the line you want to delete
  2. Press Delete or use the Delete action
  3. Confirm the deletion when prompted

Best Practices

Designing Your Status Workflow

  • Follow Logical Progression: Ensure statuses represent a logical flow from start to finish
  • Avoid Redundancy: Don't create multiple statuses that represent the same workflow stage
  • Use Clear Language: Choose status names that are immediately understood by all team members
  • Plan for Exceptions: Include statuses for common exceptions like "On Hold" or "Escalated"

Default Status Strategy

  • Choose Common Starting Point: Select the status that represents where most repairs begin
  • Consider Workflow Impact: Ensure the default status aligns with your actual business process
  • Train Your Team: Make sure technicians understand when the default status applies and when to override it
  • Monitor Usage: Review whether the default status choice is improving efficiency or causing confusion

Standard Status Mapping Strategy

  • Map Similar Stages: Connect your custom statuses to the closest standard equivalent
  • Maintain Consistency: Use the same standard status mapping for similar custom statuses
  • Consider Reporting: Think about how standard status grouping will appear in reports
  • Leave Unmapped When Appropriate: Not every custom status needs a standard mapping

Workflow Considerations

When designing your repair status workflow, consider:

  • Customer Communication Points: Which statuses require customer notification
  • Internal Handoffs: Statuses that trigger transitions between departments
  • Approval Gates: Points where customer or management approval is required
  • Quality Checkpoints: Statuses that indicate testing or verification stages
  • External Dependencies: Statuses for waiting on suppliers or third parties

Training Your Team

For Technicians

Ensure your repair technicians understand: - When to update repair status and how it affects workflow - The importance of timely status updates for customer communication - Which statuses require additional documentation or actions - How status updates integrate with time tracking and billing

For Customer Service

Help customer service staff understand: - What each status means in terms customers can understand - Which statuses indicate good times to contact customers - How to use status information to provide accurate delivery estimates - When status changes require proactive customer communication

For Managers

Help managers understand: - How to use status data for workflow analysis and optimization - Which status transitions indicate potential bottlenecks - How standard status mapping supports cross-location reporting - The impact of status accuracy on customer satisfaction metrics

Permissions

Different user roles have varying levels of access to repair statuses:

Role Permissions Description
Manager Read, Modify, Delete, Insert Full access to create and manage repair statuses
Technician Read Can view repair statuses for workflow reference
Read Only Read Can only view existing repair status definitions

API Integration

Repair Statuses are also available through the API for integration with external systems. The Repair Status API page exposes this data for:

  • External repair management systems
  • Customer communication platforms
  • Workflow automation tools
  • Mobile applications for technicians
  • Business intelligence and reporting systems

API Usage Examples

The API can be used to: - Synchronize status definitions with external systems - Trigger automated customer notifications based on status changes - Generate custom reports combining status data with other business metrics - Build mobile apps that allow technicians to update repair status in the field - Integrate with shipping systems for automatic status updates

Workflow Analysis and Reporting

Repair Status data provides valuable insights for:

Performance Metrics

  • Average time spent in each status
  • Bottlenecks in the repair workflow
  • Technician productivity by status transitions
  • Customer satisfaction correlation with status accuracy

Process Improvement

  • Identifying statuses where repairs frequently get stuck
  • Optimizing workflow by analyzing status transition patterns
  • Training needs based on status update consistency
  • Capacity planning based on status distribution

Customer Experience

  • Proactive communication triggers based on status changes
  • Accurate delivery estimates using historical status timing
  • Transparency through real-time status sharing
  • Service level agreement compliance tracking

Troubleshooting

Common Issues

Q: I can't create new repair statuses
A: Ensure you have Manager permissions. Contact your system administrator if needed.

Q: My team isn't updating statuses consistently
A: Provide training on the importance of status updates and consider implementing workflow reminders or automation.

Q: Should I map all custom statuses to standard statuses?
A: Not necessarily. Only map statuses that align well with the standard workflow stages. Specialized or exception statuses can remain unmapped.

Q: Can I change the standard status mapping after creating repair records?
A: Yes, but consider the impact on historical reporting. Changes will affect how past data is categorized in standard status reports.

Q: How many statuses should I create?
A: Start with essential statuses that represent major workflow stages, then add specialized statuses as needed. Too many statuses can complicate workflow management.

Q: Can I reorder the standard status workflow?
A: The standard statuses represent a typical workflow sequence, but repairs don't have to follow this exact order. Your custom statuses can reflect your actual workflow patterns.

Q: New repair orders aren't getting the default status automatically
A: Verify that you have marked a status as default and that users are creating repair orders without manually specifying a status. The default only applies when no status is explicitly entered.

Q: I can't mark a status as default
A: Ensure you have Manager permissions. Also verify that the status record is saved before attempting to mark it as default.

Q: What happens if I delete the current default status?
A: If you delete a status that is marked as default, no automatic status assignment will occur for new repair orders until you designate a new default status.

Q: Should I always have a default status configured?
A: While not required, having a default status improves workflow efficiency and ensures consistent starting points for repairs. Most repair shops benefit from this feature.

For additional support or questions about Quick Repair, contact BC4All support or consult the community forums.