Appliance Registers

Appliance Functions

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 the property, type (boiler, gas fire, cooker, hob, water heater, gas meter, flue, other), location and make. Model, serial, GC number and flue type sit under More details.
• 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.
• An appliance page shows its fault-code history and offers a printable QR sticker, and the Appliances list can export selected rows to CSV.

Why The Register Matters

• 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.

Reading Types by Appliance

• Every appliance carries the same three results (safety devices, ventilation, flue or chimney) and the same optional readings and tests: flue flow test, spillage test, visual condition, operating pressure in mbar, heat input in kW, CO ppm and CO₂ ratio.
• Record the spillage test and flue flow test where the appliance and flue type call for them; Manifold does not hide them by appliance type.
• An appliance passes or fails on its three results and whether a defect was identified; readings are evidence and do not change the result.
• FlueScan can auto-fill CO and CO₂ from the analyser to reduce transcription error.

Data Quality Standard

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.

Customer-Facing Consequences

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.