How Does Scaftra's Subcontractor Portal Work?

How do you give a sub access to their own jobs without exposing the rest of the company's book?

Scaftra gives each subcontractor a portal scoped to their own commitments, schedule, and punch items, with a sub-side authority distinction between an office admin and a field-standard user.

The problem it solves

A GC buys finish trades from outside vendor companies, and each vendor is both a supplier you pay and a subcontractor who shows up on site, carries insurance, and answers for punch. Inside the vendor company there is its own chain of command: an office person who manages the relationship versus a field lead who just sees their jobs. And the same drywall outfit may work for several GCs, so each must be walled to the company that engaged it.

Why it matters

A sub needs to see their own commitments, schedule, and punch items, and nothing else. If the portal shows the company-wide book, it leaks margin and other vendors' work. If one GC's vendor list bleeds into another's, it is a tenant leak. A portal scoped to the sub's own work, with a real office-versus-field authority distinction, is what lets the GC bring the whole sub relationship into the system safely.

Common mistakes

How it works

1. Onboard the vendor

   The GC creates or reuses a supplier, links it to the company, and creates a subcontractor profile with its trades.
2. Invite the vendor's people

   Each invited person becomes a membership with an office-admin or field-standard role, scoped to that GC.
3. The sub sees their own work

   The sub logs in and sees only their commitments, assigned punch items, and assigned schedule entries.
4. The sub responds in the portal

   Subs work assigned punch, respond to schedule, and handle their own compliance and lien waivers.

How Scaftra does it

Scaftra models one underlying supplier master with a subcontractor profile layered on top for the trade and compliance dimension. Supplier visibility is decided exclusively by a per-company link, never a raw global query, so one GC's roster never leaks to another. The sub portal resolves the vendor's identity from a company membership row and fails closed, then scopes reads to that supplier's own commitments, assigned punch items, and assigned schedule entries, never the company-wide book. A sub-side authority axis distinguishes a sub admin (office) from a sub standard (field) user, stored per user, profile, and company, and only an active membership grants admin authority. Contact and address edits route through controlled paths that prove the ownership chain. This is built and live.

Key capabilities

• Scoped to the sub's own work: A sub sees only their commitments, assigned punch, and assigned schedule, never the company book.
• Office versus field authority: A sub admin manages the relationship; a sub standard user just sees their jobs, per company and profile.
• Per-company vendor walls: Supplier visibility is decided by a per-company link, so one GC's roster never leaks to another.
• Ownership-chain-safe edits: Vendor contact and address edits prove the chain to the supplier and company before writing.

Benefits

• Subs get access to their own jobs without seeing the company-wide book.
• The vendor's office and field people get the right level of authority.
• Vendor rosters stay walled to the company that engaged them.

Who it's for

• Subcontractor office admins.The vendor's office person who manages the GC relationship and the vendor's people.
• Field-standard sub users.The vendor's field lead who just needs to see and respond to their own assigned work.

Related on Scaftra

Go deeper