Engineers and Team

Team Functions

• Owners invite office users, engineers and client portal users from Settings, then Team, choosing the role (Owner, Office, Engineer, or Client / agent) as they send the invite. Invites stop at the plan’s seat limit; add seats under Settings, then Billing & plan.
• Track engineer active status, which controls whether they can be assigned checks.
• Switch on sole-trader mode to hide the Team tab and team prompts and auto-assign checks to the owner.
• Change member roles, transfer ownership, and deactivate a member when someone leaves.

Engineer Readiness

• Engineers need their own account to keep signatures and record generation attributable.
• An engineer must be active to appear as assignable in scheduling.
• Engineers should confirm mobile sign-in and camera permission before their first field day.

The Team Page

Engineers, in the sidebar, is the working list of your field team. Settings, then Team, holds every member with the invitation and role controls; the Engineers page is where you browse, search and maintain the engineers themselves. The two work together rather than competing.

• See every engineer with their email, phone and active status, with search, an active/inactive filter, and sorting.
• Open an engineer to view or edit their details, or use Invite engineer to send a new engineer their invite directly from this page.
• Import engineers in bulk with the CSV importer when onboarding a bigger team.
• Use bulk actions to deactivate several members at once, for example after a seasonal crew finishes.

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.