Reports of recommended ADs Recommended AD list provided to CCH end-users based on account industry information.

Restricted to ADs in shared lists and/or builds.

Percentage of users who view recommended ADs list.

Reports of recommended ADs Recommended AD list provided to CCH end-users based on account affiliation information.

Restricted to ADs in shared lists and/or builds.

Percentage of users who view recommended ADs list.

Reports of recommended ADs Recommended AD list provided to CCH end-users based on account state-agency information.

Restricted to ADs in shared lists and/or builds.

Percentage of users who view recommended ADs list.

Provide report to membership organizations what ADs are being used in shared lists and/or builds.

Percentage of membership organizations who leverage report.

1

Create report of recommended ADs based on account industry information.

Generate report of recommended ADs based on account industry information.

2

Create report of recommended ADs based on account affiliation information.

Generate report of recommended ADs based on account affiliation information.

3

Create report of recommended ADs based on account state-agency information.

Generate report of recommended ADs based on account state-agency information.

4

Deliver industry-based recommended AD list to end-users.

Percentage of users who view recommended AD list.

5

Deliver assoicationassociation-based recommended AD list to end-users.

Percentage of users who view recommended AD list.

6

Deliver state-agency-based recommended AD list to end-users.

Percentage of users who view recommended AD list.

Provide a means for UCF super-administrators to specify which authority documents are recommended to supported state-agencies.

TBD

Not Started

Potential suggested solution, but engineering will consider other solutions: Option 1: create a “dummy” company per supported state-agency and create a list of supported ADs. Ensure state-agency identification is populated in HubSpot which will feed into the reporting engine.

Option 2: create table/form … outside of CCH to allow supper admins to specify supported state-agencies and their related ADs.

Within CCH, provide a means for the user to ask for AD recommendations (only if they have filled out Industry other than “Other” and/or specified some Associations).

P1

Not Started

After the user chooses the option to receive AD recommendations, gather recommended authority documents based upon the self-identified:

1. industry, affiliation, or both

OR

2. state-agency, affiliation, or both

Send the user via email with a PDF attachment for the recommended ADs.

P1

Not Started

The consolidated recommended ADs is based upon ADs in shared lists and ADs in builds.

Once the email is sent, inform the user they should check their email inbox for recommended ADs.

P1

Not Started

Provide key partners (ISC2, ISACA …) with report to list CCH Organizations who are members in their affiliation.

P1

Not Started

Phase 1 will be a manually generated report out of HubSpot, Power BI, or other and sent to the partner.

Phase 2 (called out in phase 2 PRD) will allow for API access.

Provide key partners (ISC2, ISACA …) with report to list CCH users who are members in their affiliation.

P1

Not Started

Phase 1 will be a manually generated report out of HubSpot, Power BI, or other and sent to the partner.

Phase 2 (called out in phase 2 PRD) will allow for API access.

Since we are currently not tracking which affiliations a user belongs to, how will the recommended ADs be derived?

We are tracking which affiliations users belong to. Please see HubSpot or ask Matt.

How do we handle new versions of ADs?

Is this purely data driven or do we need maintenance aspects on the reports we send out?

Frequency of reports?