Start a conversation
Trevanna Tracks · Product engineering

Make the software fit the exceptions in the work.

Xivic worked with Trevanna Tracks to represent licensing and fee requirements correctly, improve track classification and make frequently used media information easier to reach.

Context
Licensing and media workflows
Xivic’s role
Engineering · UX · QA
Release
Confirmed on live, August 2022
The business rule

“No license required” can still mean payment is required.

Teams needed to record a track’s licensing requirements without losing the documents needed for payment. Client review clarified two separate decisions: the licensing exception controls licensing documents; the fee exception controls payment documents.

The behavior had to fit the existing interface, track data, imports and document workflow.

The distinction in the released product

No license required; a fee still applies
Keep the payment workflow available.
No license and no fee required
Disable payment documents.

Quotes and confirmations remain available under the exception rules.

Additional product changes

Make the surrounding product easier to use.

  • Explain the exception.

    Teams can record the reason and see it in the track summary when no fee is required.

  • Classify tracks consistently.

    Track types are available in list management and CSV imports, connecting classification to the ways people manage the data.

  • Bring frequently used information forward.

    People can favorite media-list blocks so the blocks they return to appear at the top.

How the work reached production

Review the rules together. Verify the released behavior.

  1. Client review

    Resolve the combinations.

    Trevanna’s product lead worked directly with Xivic’s engineering and QA leads to define which documents should remain available and what the track summary should show.

  2. Staging

    Keep changes and scope visible.

    The team reviewed the behavior in staging. An additional change was separated into its own approved scope, and client feedback also shaped the media-list usability.

  3. Release

    Check the production behavior.

    QA confirmed the license-exception changes and media favorites on the live platform.

Related service

Business rules belong in the product, data and release checks.

The useful change was in how the existing application handled real decisions and exceptions. The interface and document behavior changed together, while track classification and favorites improved the surrounding work.

Explore custom software and applications

What does your next release need to handle?

Talk with us about the rules, exceptions and connected systems behind the work.