Appliance registers in Manifold hold every gas appliance at a property, with its type, make, model, and location, so a check knows exactly what to test. A property with an incomplete register risks a check missing an appliance altogether.
- Create appliances with type (boiler, gas fire, cooker, water heater, and more), make, model, and location.
- Capture GC number, serial, and flue type where known; PlateScan can read these from the data plate.
- Attach appliances to a property so each check tests the full register.
- Carry appliance history forward so engineers see prior readings and defects.
- Per-appliance readings (CO ppm, CO₂ ratio, pressure, heat input, flue flow, spillage, visual condition) attach to specific equipment.
- A complete register prevents an engineer from missing an appliance during a check.
- Accurate make and model data improves deduplication when PlateScan suggests a match.
Troubleshooting
- Duplicate appliance created from PlateScan: confirm the serial, GC number, or make and model before saving; Manifold matches on these.
- Appliance missing from a check: confirm it is on the property register and active.
- Readings look attached to the wrong unit: check the appliance location label before submitting.
- Boilers and water heaters typically capture CO ppm, CO₂ ratio, operating pressure, and flue flow.
- Open-flued appliances add a spillage test and flue performance checks.
- All appliances capture a visual condition and a pass or defect outcome.
- FlueScan can auto-fill CO and CO₂ from the analyser to reduce transcription error.
Setup records are not just admin. They become the labels, filters, and certificate fields customers rely on later. A small naming or address mistake in setup becomes a compliance or delivery problem weeks later.
- Use one canonical spelling for every client, property, and appliance.
- Keep property addresses precise, because they drive the route planner, scheduling, and the printed record.
- Keep appliance make, model, serial, and GC number accurate so PlateScan deduplicates cleanly.
- Deactivate former engineers and historical records instead of deleting history that explains past work.
- Run bulk imports in dependency order: clients, then properties, then appliances.
If a value can appear on a record, in the portal, or in an export, write it as if a landlord or letting agent will read it. Manifold reuses operational labels across customer outputs, so there is no separate translation step at delivery time.
Troubleshooting
- If a client sees a confusing name, fix the source record and regenerate future records.
- If analytics split across duplicate names, choose one canonical record going forward and keep the old ones for history.
- If an export does not join downstream, check names, identifiers, and relationships in setup before changing the export.