Construction Management integration
RedTeam COI compliance integration
Give RedTeam Flex credential statuses that reflect the endorsements, not just the certificate. RedTeam tracks vendor credentials, including insurance certificates, as Not on File, Expired, expiring or Current; Pikorua Security verifies the certificate and its endorsement pages against your subcontract exhibit and returns verified expiration dates and a daily hold list, so project accountants hold the right pay requests.
RedTeam, Cedar Hollow Elementary School
Commitment CHE-031
Hold: COI deficient
GL credential expired 10/12/2026 and primary and non-contributory wording is missing. On today's 6:00 AM hold list.
- Vendor
- Brightwater Plumbing Co.
- Pay request
- #04, $58,310.00
- GL credential
- Expired
- Expiration date
- 10/12/2026
- CG 20 01 (P&NC)
- Not verified
Written by Pikorua Security Oct 16, 2026, 06:00 AM ET
- Setup time
- 2 hours
- Connection
- Scheduled CSV exchange (SFTP or email)
- Fields synced
- 6 fields, 4 trigger events
- Included on
- Professional and Enterprise
Sync fields
What Pikorua Security reads from and writes to RedTeam.
| Field | Direction | What happens |
|---|---|---|
| Vendor roster | RedTeam to Pikorua Security | Exported from RedTeam Flex on a schedule: vendor name, trade, contacts and active projects. |
| Commitments | RedTeam to Pikorua Security | Subcontract numbers, values and projects, so the right requirement template is applied to each vendor. |
| Insurance credential expiration dates | Pikorua Security to RedTeam | Verified dates per coverage line in the credential update file, taken from the policy rather than the certificate's typed term. |
| Credential status | Pikorua Security to RedTeam | Current only when every rule passes. A deficient endorsement keeps the credential from showing Current even when the dates are fine. |
| Verified certificate packet | Pikorua Security to RedTeam | PDF of the certificate and endorsement pages, named by vendor and policy, ready to attach to the credential. |
| Daily hold list | Pikorua Security to RedTeam | Vendors whose pay requests should be held, with the reason and broker contact, emailed to project accounting at 6:00 AM. |
Trigger events
When the certificate changes, RedTeam changes with it.
- Hold
Certificate expires
Then: The credential update file marks the coverage Expired, and the vendor appears on the 6:00 AM hold list with its open pay requests.
- Hold
Endorsement fails, for example CG 20 01 primary and non-contributory missing
Then: The credential is kept from Current and the vendor joins the hold list, even though the certificate dates are valid.
- Warn
Credential expiring within 30 days
Then: The broker receives the day-30 request. RedTeam's own expiration status already warns the project team, so no hold is added.
- Release
Renewal verified
Then: New dates and Current status go out in the next file, and the vendor drops off the hold list.
Setup
Live in 2 hours.
5 steps, done by your RedTeam administrator and a Pikorua Security Admin together. Nothing to install on your servers beyond the file drop you already control.
Scheduled CSV exchange (SFTP or email)- 1
Schedule the exports
Your RedTeam administrator schedules vendor and commitment exports to a Pikorua Security SFTP folder or a dedicated email address.
- 2
Map credential types
Match your RedTeam insurance credential types (general liability, auto, workers compensation, umbrella) to Pikorua Security coverage lines.
- 3
Load requirement templates
Attach each project's subcontract insurance exhibit, or start from Pikorua Security's standard commercial template.
- 4
Choose recipients
Pick who receives the daily hold list and who applies the credential update file in RedTeam.
- 5
Review the first run
The first pass lists every vendor whose RedTeam credential says Current but whose endorsements fail your exhibit.
Credentials in RedTeam Flex, verified upstream
RedTeam Flex is a cloud project management and job cost platform for commercial general contractors, from RedTeam Software in Orlando, Florida, with TeamPlayer as its subcontractor portal. It tracks vendor credentials, including insurance certificates, with plain statuses: Not on File, Expired, an upcoming expiration date, and Current. That catches a lapsed policy. It cannot tell you that a current certificate is backed by the wrong additional insured form.
Pikorua Security does the reading RedTeam leaves to people: the endorsement schedule, the edition dates, the named additional insureds and the limits against your exhibit. The result goes back to the RedTeam team as verified dates and a credential status they can trust.
Why the connector uses file exchange
RedTeam does not publish an open API for third parties, and its own integrations run to accounting systems such as QuickBooks Online, Sage Intacct, Sage 100 Contractor and Acumatica. So the Pikorua Security connector uses scheduled files: exports from RedTeam in, verified credential data and a hold list out. For a regional general contractor where one project accountant runs pay requests, a 6:00 AM list of who not to pay fits the existing routine.
If you also run an accounting system that Pikorua Security writes to directly, the hard stop lives there and RedTeam receives the same verdict for project visibility.
More construction management connectors
Teams that connect this usually connect these too.
FAQ
RedTeam connector questions.
Pikorua Security is compliance software. It verifies certificates and endorsements against your contract requirements; it does not sell insurance or give legal advice.
Does RedTeam need to install anything?
How current is the data?
Does it replace TeamPlayer?
14-day free production trial
Connect RedTeam during your 14-day trial.
Upload your current certificates, authorize RedTeam, and see which vendors would be on hold today before you switch a single rule on.