Welcome to IssuesId
IssuesId is a defect, inspection, and handover platform built for construction teams that work on real sites — where signal is unreliable, hands are full, and the audit trail matters.
This guide walks you from sign-in to your first tracked defect in about five minutes.
Who IssuesId is for
- →Site supervisors and foremen capturing issues during walk-throughs.
- →Project managers assigning work, tracking close-out, and exporting reports.
- →QA inspectors running checklists and producing signed handover packs.
- →Trades and sub-contractors receiving assignments, uploading evidence, and requesting sign-off.
- →Clients and consultants viewing read-only project status without touching the build.
Each role sees a dashboard tailored to their job — no menu wading, no permissions surprises.
Before you start
There are three ways into IssuesId, depending on who you are.
Starting a workspace. Sign up and you'll go through three short steps — you, your company, then a password — with your workspace URL previewed as you type it. Verify your email, and the setup wizard walks you through a logo, an accent colour, and your first team invites.
Joining one. An admin invites you by email. The link drops you straight into their workspace with your role already set.
Trades. If you've been sent a defect, the notification itself is your way in. Your email is matched against the builder's contractor list and you land in their workspace, scoped to your own work — no new company to set up, and no duplicate to untangle later.
Beyond that you need a modern browser (or the installed app on your phone) and a project to work in. If you don't have one, ask a project admin to create it, or read Projects to set one up yourself.
Defects, or inspections?
Not every industry calls them the same thing. A builder snags defects; a facility, a fleet, or a plant runs inspections and records what failed. IssuesId ships both words and lets your organisation pick one.
The setting lives in Organisation settings, as a two-option choice. Switching it changes the wording everywhere the term is read aloud to a person: the menu, the dashboards, breadcrumbs, the report catalogue, notification emails, and the pages you send to people outside your team.
What it doesn't change is anything a machine reads. Saved filters, exported column headers, report identifiers, and API fields keep the same values whichever term you choose, so switching the word can't break a spreadsheet or an integration built against the old one.
New organisations start on inspections. The rest of these docs use defect, since it's the shorter word and the register behaves identically either way.
Your first defect
- 01Open the Capture screen from the dashboard or scan a QR code on site.
- 02Take a photo, drop a pin on the drawing, and dictate a voice note describing the issue.
- 03Pick who raised it, then a trade, priority, and cost category (defect, variation, or backcharge).
- 04Hit Save. The record syncs immediately if you're online, or queues for background sync if you're not.
That's it. The defect is now in the register, assignable, and reportable.
What to read next
- →Defects — the full lifecycle, from draft to closed.
- →Roles & dashboards — who sees what, and which role you'll want for whom.
- →Inspections — QA checklists and signed handovers.
- →Work orders — issuing work and tracking cost.
- →Trades, tenants & clients — read this before handing a login to anyone outside your company.
Tip: Everything in IssuesId is built around evidence. If a status changed, a photo was added, or a sign-off happened, it's timestamped and attributable — by design.