For your HR, finance and technology teams
A clearer way
to evaluate SSGI.
Understand the service, explore the workspace and prepare the questions that matter to your organization. Review these materials together before deciding on a change.
Employer evidence room
Clear evidence.
Clear questions.
Give HR, finance and technology a shared starting point. Open the evidence, identify what needs confirmation and bring the unresolved questions to your review.
These are SSGI’s public service materials. They do not disclose client information or present fictional examples as customer results.
Public-source review: . These statements describe published scope; they are not an independent audit, completed RFP or security attestation.
Read SSGI’s service overviewPeople and service ownership
Published service description · HR & People
Andrew and Laura Decker lead SSGI Benefits. Review the agency background and agree the people responsible for your account, employee questions and escalations.
- Responsibility to agree
- SSGI and your employer’s service lead
- Still requires evidence
- Account-specific contacts and service commitments are not established by this page.
Confirm together: Named service contacts, included work, escalation route and any service commitments belong in your agreed scope.
Workforce and market fit
Published service description · Leadership
Start with the agency’s published license list and your workforce locations. A license, carrier appointment and available plan are separate questions.
- Responsibility to agree
- SSGI, the employer and relevant carriers
- Still requires evidence
- No workforce-size, carrier-network or geographic fit has been approved for your organization.
Confirm together: Confirm licensed support, markets and provider access for each relevant location before proceeding.
Technology and data access
Published service description · Technology
The public SSGI One examples use fictional data. Private account access requires its own authorization; organization-specific connections are scoped separately.
- Responsibility to agree
- Your authorized account administrator and SSGI
- Still requires evidence
- Public tools do not establish private account access, a live integration or a security certification.
Confirm together: Document systems, permissions, data responsibilities and security requirements. A public demonstration does not establish compatibility or a security certification.
Commercial and transition decisions
Published service description · Finance
Use the planning brief to frame contribution assumptions and implementation responsibilities. Public examples are educational inputs, not quotes or client outcomes.
- Responsibility to agree
- Your finance lead, SSGI and the relevant providers
- Still requires evidence
- Fees, compensation, implementation dates and service levels require an actual agreement.
Confirm together: Confirm services, fees, compensation disclosures, carrier requirements and timing in the actual review.
From public exploration to authorized work
01 / Public website + browser AI
Explore publicly
Find public guidance, try fictional examples and prepare review materials. Public tools do not open private employee records.
Try the public task02 / Your SSGI One workspace
Work with permission
Account access and assigned permissions govern the actual workspace. Confirm who can see, change and approve information for your organization.
Review connection boundaries03 / Your team + SSGI + providers
Agree the responsibility
Name the service owners, required approvals and escalation route. Organization-specific integrations and carrier requirements need their own review.
Review service responsibilities
What your technical review should establish
- Systems and permissions
- Identify each system, data owner, permitted action and who can grant or revoke access.
- AI and human decisions
- Separate public assistance from private account work. Agree where human approval, licensed advice and escalation are required.
- Evidence before commitment
- Request the applicable architecture, data handling and service documentation for the actual proposed scope.
- Integration acceptance
- Confirm compatibility, provider terms, costs and a bounded test before enabling a connection. Public demonstrations are not certifications.
A working packet for the buying team
Supporting material by role.
One review, four perspectives. Use the worksheets below to name responsibilities, compare evidence and prepare the questions still to resolve.
These choices frame your discussion; they do not establish service fit or a capacity commitment. They stay in this tab. No employee records are needed.
One set of criteria. Choose the perspective your team needs.
01HR & People · Service responsibility worksheet
Public answer ·
Andrew and Laura Decker lead SSGI Benefits. Review the agency background and agree the people responsible for your account, employee questions and escalations.
Still to confirm: Account-specific contacts and service commitments are not established by this page.
- Workforce and eligibility
- Employer confirms accurate records and authorized decisions; SSGI coordinates the agreed benefits work. Confirm eligibility and acceptance with the carrier or administrator.
- Employee questions
- Agree which questions go to the employer, SSGI or carrier. Name the service contact and escalation route before launch.
- Changes and reconciliation
- Name who requests, reviews, submits and confirms each change. A portal action does not by itself confirm carrier coverage.
Record a proposed owner, evidence and date, unresolved question and next action for each item.
Implementation guide02Finance · Proposal and RFP response outline
Public answer ·
Use the planning brief to frame contribution assumptions and implementation responsibilities. Public examples are educational inputs, not quotes or client outcomes.
Still to confirm: Fees, compensation, implementation dates and service levels require an actual agreement.
- Scope and commercial terms
- Request included and excluded services, fees, compensation disclosures and a proposed responsibility matrix. Record the document, owner and review date for every answer.
- Comparable assumptions
- Use the same enrollment, premiums, contributions, fees and effective dates across proposals. Separate supplied facts from assumptions and unresolved questions.
- Decision record
- Record each requirement as evidenced, partly evidenced or awaiting confirmation. Public descriptions are starting material, not completed RFP responses or a scored recommendation.
Record a proposed owner, evidence and date, unresolved question and next action for each item.
SSGI service overview03Technology · Systems and data boundaries
Public answer ·
The public SSGI One examples use fictional data. Private account access requires its own authorization; organization-specific connections are scoped separately.
Still to confirm: Public tools do not establish private account access, a live integration or a security certification.
- Public website → local planning
- Public guides and fictional demonstrations require no employee records. Review selections stay in this tab unless you download them or explicitly prepare a separate inquiry.
- Authorized account → SSGI One
- Private account access needs separate authorization. Define account roles, permitted data, responsibility for corrections and the route for service requests.
- SSGI One → external systems
- Confirm any carrier, payroll or HR-system connection individually: supported workflow, permission, transfer method, failure handling and reconciliation owner. The public demo does not prove an integration or security certification.
Record a proposed owner, evidence and date, unresolved question and next action for each item.
SSGI One connection boundaries04Leadership · Illustrative transition plan
Public answer ·
Start with the agency’s published license list and your workforce locations. A license, carrier appointment and available plan are separate questions.
Still to confirm: No workforce-size, carrier-network or geographic fit has been approved for your organization.
- Discover → scope
- Confirm locations, current arrangements, renewal timing and the decision owner. Verify licensed support and available markets.
- Plan → authorize
- Agree the service scope, responsibilities and required carrier or administrator steps. Obtain the relevant employer approvals before changing arrangements.
- Prepare → confirm
- Coordinate enrollment and communications, then reconcile completion with the responsible parties. Dates, service levels and a feasible launch plan require agreement; no fixed transition duration is promised.
Record a proposed owner, evidence and date, unresolved question and next action for each item.
Changing benefits advisorsThe download is a self-contained HTML document with sources and a print layout. It is a working outline, not a completed RFP response or agreed service scope.
Bring the right people into the conversation.
HR brings the service priorities, finance the budget assumptions, and IT any system or access questions. SSGI confirms the proposed participants and timing. The first discussion should identify fit, open questions and who owns the next step.
Prepare selected answers for a review request
Choose what to bring into the Contact form. Leadership notes, source notes and financial snapshots are excluded. Nothing is sent until you submit the form.
Message preview
Select an answer to prepare your message.
You can edit or remove the draft on the form. Refreshing clears this one-use handoff; it is not added to the URL or browser storage.
A multi-state employer example
Follow one decision.
See the handoffs.
A fictional 2,500-person workforce. Three states. One benefits team coordinating the work. Shape a discussion brief and see which responsibilities need agreement.
All scenario details are made up. This is a planning example, not a customer story, service commitment or capacity benchmark.
Explore the SSGI One enrollment sample- 1. Workforce
- 2. Responsibilities
- 3. Review brief
Workforce
Maryland · Pennsylvania · Virginia. Begin with the work your team wants to coordinate; coverage and eligibility still need separate confirmation.
What this example shows
- The starting question
- Who coordinates the next benefits step across three states?
- The working artifact
- Your chosen priority, a proposed discussion owner and a responsibility outline, collected in one review brief.
- The evidence still needed
- Confirm service scope, carrier acceptance and actual implementation evidence with the responsible people. No savings or completed service outcome is asserted.
Moving to SSGI
A change of adviser.
A considered transition.
Explore how the work can fit together. The sequence, timing and services are confirmed for your organization before a change is made.
Step 1 of 4 · Discover
Start with the business decision.
Agree what needs to improve before deciding what should change.
- Your team
- Identify your priorities, workforce locations and renewal dates.
- SSGI
- Review the situation with you and clarify the proposed service scope.
Discussion milestone: A shared list of priorities and questions to resolve.
Clarify your prioritiesBring the team into one conversation
Turn questions
into a review brief.
Use the existing planning workspace to collect your priorities and relevant guides. Your local brief is not sent to SSGI. You choose whether to download it and what to share in a separate conversation.
Prepare your planning briefConfirm these before proceeding.
- Licensed support and available markets for your workforce.
- Included services, fees and compensation disclosures.
- Account access, integration scope and data responsibilities.
- Carrier requirements, timing and the named service contacts.
Public screenshots and walkthroughs use fictional sample data. They demonstrate interfaces, not a client outcome or a capacity guarantee.