Equipment across Projects →
Find an asset across all accessible active Projects.
FLAGSHIP · ISSUE FINDER & FIXER
Start with the problem. Finish with verified evidence.
HVACR troubleshooting often begins with a symptom, not a module name. Start free from what you are observing, then move into project-bound evidence, corrective action, retest and verification when the job requires traceability.
Engineering judgement stays visible. HVACR Studio structures troubleshooting and suggests checks; it does not silently replace a competent professional or evidence-based verification.
THE ENGINEERING TRAIL
Find it. Fix it. Prove it.
A useful troubleshooting record is more than a guessed cause and a “done” status. The workflow keeps observation, checking, corrective action and verification distinct.
Observe
Record the symptom, complaint or abnormal condition before jumping to a cause.
Check
Capture relevant readings, conditions and engineering references.
Diagnose
Work through likely causes using measured evidence and structured checks.
Correct
Record the corrective action and engineering reason.
Retest
Measure again after the intervention instead of assuming the fix worked.
Verify
Compare the new condition with the intended acceptance or performance target.
Close
Preserve the issue, action, evidence and verification trail for future reference.
REAL FREE WORKFLOW · R60.1 CAPTURE
See a genuine logged-out Issue Finder workspace.
This authentic release-candidate capture was recorded before the R61 problem-first entry redesign, so its first screen shows the earlier equipment-first sequence. It remains genuine product UI, not a reconstructed mockup, and it uses no Project or customer record.
FREE BASIC ISSUE FINDER
Start with what is wrong. Continue through retest and verification.
Choose the field problem first, refine the equipment only when needed, record observations/readings, follow deterministic checks, record the action actually performed, then retest and decide whether the correction is verified, failed, needs monitoring or should be escalated.
Problem-first field loopObserve · Check/readings · Likely causes · Action · Retest · Verify
Recent Issues without loginUp to six lightweight sessions are stored locally on this browser/device for up to 30 days. Nothing is silently uploaded or synced.
Need formal traceability?Professional Fixer adds Project/equipment context, formal evidence, RCA/CAPA, verification history and issued reports.
Work from an observed problem through checks, corrective action and retest.
Explain this screen
Use this when: A room, system or asset is behaving differently from the expected condition.
This helps you: Keep possible causes separate from measured evidence and verified outcomes.
How to use it
- Choose the observed problem and equipment when known.
- Record checks; use Not sure when a check has not been confirmed.
- Review possible causes and perform only checks appropriate to your competence.
- Record the action, retest and choose the observed outcome.
Before relying on it: Stop or escalate work outside your competence or site authorization. A local session is not saved Project evidence.
STEP 1 · START WITH THE PROBLEM
What is happening?
Choose what you are observing in the field. You do not need to know the exact equipment category first.
10 supported problem families
Already know the equipment?
Guided troubleshooting
Use symptom-first guidance, references and engineering checks without turning every problem into a paid workflow.
- Start from what you observe.
- Follow practical checks one at a time.
- Use free engineering tools alongside the diagnosis.
Traceable issue resolution
Connect diagnosis to registered equipment, Before/Retest evidence, corrective action, verification, RCA, Five Whys, CAPA and reporting where supported.
- Preserve project and asset context.
- Retain evidence and corrective-action history.
- Differentiate completed work from verified closure.
HVACR STUDIO · BY LEAL