Principal-led oversight extends to every trade on site. Our trade-partner portal scopes each crew to the work in front of them — today’s tasks, a two-week lookahead, the approved plans, the camera upload, and a direct thread to the project manager. Nothing more.
Budget, change orders, other trades’ schedules, and client contact information stay invisible — not by policy memo, by architecture. A trade partner’s account is scoped at the data layer, so the pages that don’t apply to their work simply aren’t rendered. An expired Certificate of Insurance (COI) blocks new assignments automatically.
The portal is narrow on purpose. Every surface exists because it shortens the loop between the field and the project manager.
The Today tab is the default landing. Tasks are grouped by due window — today, tomorrow, this week — filtered to whichever build a trade partner is standing on. A project switcher moves between active assignments in a single tap.
Open a task and the full scope is there — the written scope, the reference plans, the materials the builder has staged, and the PM notes. Two primary actions: upload a photo or mark the work done.
The camera is context-aware. A photo taken from a task is auto-tagged with the build, the trade scope, and the task itself — no folder sorting, no cross-trade leakage, no risk of the wrong image reaching the wrong record.
The lookahead is trade-filtered. A trade partner sees every task assigned to their scope across active builds for the next 14 days — never the schedule or scope of the other trades working the same site.
Messages are scoped to the task, not to a general channel. A question about the north-wall junction boxes lives on the north-wall-junction-boxes task — not in a shared room where yesterday’s drywall question is still scrolling.
The profile carries the Certificate of Insurance, the liability and workers’ comp expirations, two-factor authentication (2FA) status, and the Faltz rating from the admin Trades page. An expired COI blocks new assignments — no exceptions.
Scope is an architecture choice, not a policy the PM has to enforce. The portal does not render what is not a trade partner’s to see.
A trade’s scope pricing is their business. The overall build budget is not.
Change-order cost is negotiated between client and principal. Trade partners see the revised scope, not the dollar.
A trade partner sees the wall, the rough-in, and the inspection on their own scope — not the framer’s schedule, not the finisher’s specification.
Direct client contact is handled by the project manager. Trade partners never need the client’s phone number.
The portal is scoped to assignment, not to workspace membership. Past builds a trade partner worked on are read-only for warranty; future builds are invisible until assigned.
Access is granted at assignment, scoped to the work, and revoked on a clear timetable after the build delivers.
There is no open trade-partner signup. Invites come from a Faltz project manager after an initial conversation and a trade-partner agreement.
First sign-in uses the invite email. Trade partners on Google Workspace can link single sign-on (SSO) for faster access on every return visit.
Two-factor authentication (2FA) is offered at first sign-in and required for elevated actions — photo uploads, marking a task complete, and any action that writes to the audit trail.
Tasks, lookahead, reference plans, camera, and PM messaging are all available from invite through delivery.
After the build delivers, the portal switches to read-only for 90 days — enough time for warranty callbacks, photo reference, and any final follow-up. At day 91, access is auto-revoked.
Invites come from a Faltz project manager after a conversation and a trade-partner agreement. If you run a trade crew in metro Atlanta and want to be considered, start with a single message.
Get in touch