Complied — product overview
Complied is a lead-paint compliance platform for New York City. This page explains what it does, who uses it, how a customer organization is set up, and where each part of the work lives in the app. It is the place to start before reading the operator guides or the architecture pages.
What it does
For a firm that inspects and abates lead paint, Complied:
- Watches public agency data (HPD, DOB, ECB/OATH, DOF, 311) for every building the firm tracks, and shows the whole city on a map.
- Surfaces what needs doing: open and overdue violations, and the recurring duties owners owe (annual notices, the one-time Local Law 31 XRF test, exemption monitoring).
- Runs the work. A project records the decision for each HPD order, derives the field work it implies, dispatches the visits, and captures XRF, dust-wipe, paint-chip and abatement data in the field.
- Produces the paperwork: XRF reports, chain-of-custody sheets, the HPD response documents (certifications, contestations, affidavits), proposals and invoices, with a required-document checklist per decided order.
- Proves it with a versioned, auditable document record that clients can be shown through a white-label portal.
Filing with HPD is always done by a person: the app generates the documents, and staff mail or upload them. The agency's acceptance of a filing is not tracked.
Who uses it
| Audience | What they do in the app |
|---|---|
| Staff of a tenant (project managers, dispatch, back office, billing, administrators) | Track buildings, run projects, dispatch visits, generate and file documents, invoice. |
| Inspectors and abatement crews | Open their assigned jobs on a phone or tablet at the site and capture data. |
| Clients (building owners and managing agents) | Sign in to a separate read-only portal to see their buildings, violations, projects, shared documents and invoices. |
| Platform operators (Complied staff) | Sit above all tenants, with cross-tenant access. Impersonating a tenant is time-bounded, needs a reason, and is written to an audit log the tenant can read. |
Tenants
Each customer organization is a tenant: its own staff, clients, tracked buildings, projects, documents, invoices and branding. Tenants share the citywide building and violation data but never see each other's clients or work. Two organizations run on Complied today: Secure Environmental Group (inspections: XRF, dust wipe, paint chip) and Abated NYC (abatement). The vocabulary is fixed: a tenant is always the organization, a client is the tenant's customer, and a resident is an occupant. See the glossary and decisions.
Each tenant signs in on its own subdomain. A sign-in on another tenant's subdomain is refused. Access inside a tenant is controlled by roles, which are sets of permissions the administrator edits (team and roles).
One project can involve more than one tenant. The owning tenant invites another tenant onto that single project as a collaborator (field execution, abatement, clearance sampling or lab coordination). The collaborator sees only that project, and never its invoices, proposals or rate cards.
Services
The platform knows four field services, defined in code:
| Service | What it is |
|---|---|
| XRF inspection | Instrument readings imported from a CSV, room checklists, a floor plan, and a generated inspection report. |
| Dust-wipe sampling | Clearance samples per room, a chain-of-custody sheet for the lab. |
| Paint-chip sampling | Samples per room with a chain of custody, for surfaces XRF cannot resolve. |
| Abatement | Scope of components, notification, materials, crew, and work recorded component by component. |
Staff never declare a service on a project. Services are derived from the decision recorded for each linked HPD order (contest, cure, postpone or dismiss, and the ground or option chosen). The rules that map an order to a path, its documents and its deadlines are in the HPD rulebook.
How a project moves
A project carries a phase (intake, scheduling, field, docs QA, billing, closed) and an optional side state (blocked, on hold, cancelled), shown as text under the header's address. Both are labels that staff set by hand. The header's own status line is Next up: what is still open across Decide, Work and File. Nothing advances them, and Decide, Work, File and Money are always open whatever the phase says. The full walk-through is in running a project.
Where things live in the app
The sidebar groups the destinations a signed-in user can open. Which entries appear depends on the
user's permissions; a section with nothing the user can open is left out. On a phone or tablet the
sidebar is a drawer opened from More on the bottom bar, which also carries the first few main
destinations. Search at the top of the sidebar (or Ctrl+K / ⌘K) opens a palette that finds
buildings and jumps to any destination the user can open, including the pages with no sidebar entry.
| Area | Destination | What it is | Guide |
|---|---|---|---|
| Work | My day (/home) | The office's home page, where office staff land: today's visits on a timeline, Act now (urgent lead orders, apartment deadlines, client requests and your role's queue), this week, who the work waits on, recent activity, and unpaid invoices for whoever sees money. Its Agenda, Week and Month tabs (?view=) are the calendar of everything dated; /calendar redirects there | My day |
| Work | Projects (/projects) | The work hub, with a tab each for All projects (list, create, and the Decide / Work / File / Money workspace), Field work (?tab=field), Work orders (?tab=work-orders) and Floor plans (?tab=floor-plans). A tab shows only to someone who may open it. The count beside Projects is client work orders waiting for a decision | Running a project |
| Projects tab | Field work | The dispatch board for the office; each inspector's own day. The job page is /field/:inspectionId. /field redirects here | Field visits |
| Projects tab | Work orders | Client requests waiting for a decision. /work-orders redirects here | Client portal |
| Projects tab | Floor plans | The floor-plan queue for artists; a plan opens at /floor-plans/:id. /floor-plans redirects here | Field visits |
| Work | Clients | The firm's customers | Violations, buildings and the map |
| Portfolio | Buildings | Tracked buildings and their violations; the count beside it is portal building requests to review | same |
| Portfolio | Violations | The violations explorer over tracked buildings or the whole city | same |
| Portfolio | Map (/map) | Citywide filterable map | same |
| Admin | Team (/team) | People and roles | Team and roles |
| Admin | Settings (/settings) | Licenses, XRF instruments, laboratory partners, branding, report templates. Also in the account menu | Team and roles |
| Portfolio | Deadlines (/deadlines) | The worklist of what each tracked apartment owes next; each building also has a Deadlines tab | Violations, buildings and the map |
| Portfolio | Documents (/documents) | Every document across all levels, with sharing | Documents and filing |
| Admin | Rate cards (/rate-cards) | The prices proposals draw on | Proposals and invoices |
| Search only | New project, Team roles | A new project; the roles editor. Search also lists Field jobs, Work orders and Floor plans, each opening its Projects tab | Running a project |
| Not in the sidebar | Apartment (/units/:id) | One apartment's obligation facts, opened from its building | Violations, buildings and the map |
| Client portal | /portal/* | Dashboard, buildings, violations, documents, invoices, project pages | Client portal |
What Complied does not do
- It does not bill customers for the platform: there are no plans or subscriptions.
- It does not submit filings to HPD, or run notary services. The client e-signs a proposal in the portal; every other signature and notarization is done on paper, and Complied records a name and a time (or the signed scan).
- It does not work offline in the field: capture needs a connection.
- It covers New York City and one compliance program, NYC lead paint. Other agencies' data is ingested for the building's overall risk picture but does not drive projects.
- It has no native mobile app; the field views are responsive web pages.
- It does not create rows in the shared apartment (
units) table. Apartments come from agency data, and the app never invents an apartment label.