---
name: tbt-conflicting-units-analysis-brief
description: "Pause a calculation when units or periods cannot be compared honestly for Resolve conflicting units before asking AI for a comparison. Use permitted source material; this kit does not authorise external actions."
---

# Resolve conflicting units before asking AI for a comparison

Pause a calculation when units or periods cannot be compared honestly.

Use the supplied source as authority. Check the account supports the actual file or image operation before attempting it.

## Task instruction

Review these supplied measures before comparing them for [question].
For each, state quantity, unit, period, population and whether it is
observed activity, available input or a modelled result.
Identify the conversion facts and assumptions actually needed.
Use only supplied definitions. Pause incompatible arithmetic and ask
focused questions; do not invent handling time, working days or scope.
Keep the source numbers and unknowns unchanged.

## Source boundaries

- A: 12 requests/week
- B: 10 available hours/day
- Conversion facts unavailable

## Review and correction

A 30-minute/request, five-day scenario implies a capacity ceiling, not observed throughput. Do not compare hours and requests directly.

The answer compares [quantity A] with [quantity B] as though they share
a unit and meaning. Restore the supplied definitions. Identify the
missing conversion facts and stop the unsupported ranking/calculation.
If using the explicitly supplied model, label its result as conditional
capacity, not observed throughput. Keep the original data visible.

Use references/practice-source.json for the labelled example. The practice HTML is a local teaching tool; it does not call an AI service. Apply this method to the user's supplied facts rather than copying fictional example values. Do not infer approval or permission to publish.