portal.higginbotham.com/front-door
Higginbotham
PG
Welcome back

Your apps and tools, all in one place.

Your apps
EmailOutlook
BenefitsEnrollment
ExpensesConcur
Time offPTO
Power BIReporting
Agency systemApplied Epic
HiggGPTAI assistant
SmartsheetWork tracking

One Front Door

What do you need?

Pick the option that fits best. Your answer routes the request automatically, so you never have to know who owns what.

Higginbotham SOS Request Form

Please fill out this form to help us understand and resolve your technical issues effectively.

A ticket receipt is automatically sent to your email address after the form is submitted and a ticket is generated

Hi, Pat. When you submit this form, the owner will see your name and email address.

* Required

Yes
No
Microsoft 365

This content is created by the owner of the form. The data you submit will be sent to the form owner. Microsoft is not responsible for the privacy or security practices of its customers, including those of this form owner. Never give out your password.

Ticket generated

Your SOS ticket is in

Reference REQ‑4821 · A receipt was emailed to you · Typical turnaround: same day

You Front Door Service Desk

What happens next

1It follows the normal SOS processSame form, same queue the service desk already uses. From here it is handled like every other SOS request.
2A technician picks it up, you get updates by emailNo committee, no waiting on a meeting. Track it under Requests any time, most items close the same day.

One Front Door · Quick request

What can we help with?

Two quick picks and the front door sends it straight to the right owner. Change the answers and watch the routing update.

Routes to the right team
Request logged

Sent to the right team

Reference REQ‑4834 · You will hear back by email, usually within a day or two

You Front Door The right team

What happens next

1The owner sees it directlyReports, data, access, and small tweaks go straight to whoever owns that system, not a committee.
2It joins their queue or next updateSimple asks get handled quickly. Anything bigger than a quick win gets flagged as a project.

One Front Door · New project

This one opens the real intake form

Bigger asks use the PMO's actual Project Intake & Summary form. Scroll through it to see what it captures, then click Complete form at the bottom to auto-fill a sample and continue.

Sample answers filled in for the demo. Scroll to review, then continue.
PMO

Project Intake & Summary

Higginbotham PMO
Intake template

Project intake

Project name
Requestor
Requestor department
Date
Project purpose strategic and operational
Project background

Engagement needed / high-level scope

Analysis Business process (current state) Business process (future state) Solutioning (may include a pilot) Implementation Project management Report requirements gathering Other

Impact and cost

Impacted departments
Cost
No cost Cost unknown (analysis needed) Cost known
Reach
Minimala single process Lowone team Moderateseveral teams Highthe full firm Extensivefirm and clients
Urgency
Low Medium High Critical
Importance
Low Medium High Critical

Risks

Scope creep Stakeholder alignment Resource availability Disruption to business as usual Complexity Legal or compliance

Project summary

Description 2 to 3 sentences
Out of scope

Measures of success

Reduce staff hours required Fewer errors or defects Faster process completion Lower costs or savings achieved Improved data quality Higher customer or user satisfaction Less manual work, more automation High adoption by end users Standardized processes Increased revenue or productivity

Solution deployment and oversight

Pilot Software implementation External vendor search or internal build (RFI) Accountability plan Operational maintenance plan Utilization metrics created

Sponsors and ownership

Project sponsor
Project owner
Project manager
Funding sponsor over $25K annual: BJ Meyer / Wes Snow

This walkthrough shows the intake fields that drive prioritization. The full template also captures key activities and milestones, training, communication, assumptions, project team, and stakeholders.

One Front Door · Steering committee

How the steering committee decides

Built for Higginbotham, drawing on a proven IT governance model. A project is not approved in one shot: it earns two clear decisions, and the numbers get vetted by Finance in between, so nothing large is funded on a hunch.

How a project earns approval

Before the committee
1 · Business case, signed offThe requester writes a short case; their department leader signs off before it takes the committee's time.
2 · Quick-win checkIf it is small and low-effort and will not bump current priorities, it skips the committee and just gets done.
Two committee decisions
3 · First review: fund the estimateThe committee decides only whether it is worth scoping and pricing. Yes means a team is assigned to estimate it.
4 · Estimate and pro formaThe PMO scopes the effort; Finance vets the pro forma. Nothing reaches the second vote without real numbers.
5 · Second review: approve to buildWith true cost and return in hand, the committee approves it into the delivery queue, or parks it with a reason.

Who is in the room

Commercial Lines Employee Benefits Personal Lines Operations Finance IT and PMO (chair)

What the committee reviews

Primary request doc The Project Intake & Summary
  • The PMO's standard form, the one filled a moment ago
  • Business need, purpose, background, and options
  • Reach, urgency, importance, cost, and risks
  • Measures of success, sponsors, and any legal or regulatory driver
Attached for the numbers The pro forma, vetted by Finance
  • A multi-year cashflow, with payback, IRR, and NPV
  • The cost of doing nothing, weighed against the spend
  • A sensitivity range on the assumptions that matter most
  • A post-forma that tracks actuals against the projection

The Project Intake & Summary is the request; the pro forma is attached as the financial detail.

What the committee weighs

CriteriaWhat it asksWeight
Strategic fit
Supports the firm's goals and Build to a Billion
25%
Revenue or expense impact
What it earns, saves, or protects
25%
Reach and experience
How many clients and staff it helps, and how much
15%
Effort and cost
What it takes IT and the business to deliver
15%
Legal or regulatory
Whether a rule or carrier requirement forces it
10%
Risk
Risk of doing it, and of not doing it
10%

Illustrative weighting. The committee sets and publishes the final rubric.

Prioritized and visible

On the shared roadmap

Approved projects enter one prioritized queue. Each department keeps a short prioritized list, a few active and a few on deck, and the committee sets priority across them, with delivery status in the open.

#ProjectDepartmentStageStatus
Active, in delivery (up to 5)
1Producer onboarding refreshOperationsDeploy On track
2Carrier data automationCommercial LinesBuild Watch
3Renewals dashboard v2Employee BenefitsBuild On track
4Agency-bill reconciliationFinancePlan On track
5Client portal single sign-onIT and PMOInitiate On track
On deck, approved and queued (up to 5)
6Unified Client Onboarding Portal Just approvedCommercial LinesQueued Not started
7Personal Lines quoting refreshPersonal LinesQueued Not started
8Commission statement automationFinanceQueued Not started
On track: on budget and on schedule Watch: slipping on cost or timeline Off track: well over, well behind, or scope in dispute

This is the whole point. One front door, one queue, one transparent decision. Leaders stop trading favors in the hallway, and everyone can see what is funded, what is next, and how it is tracking, and why.

Front Door Loading… click the glowing area
Click the glowing blue area to move to the next screen.