How we’re organized
Blevins Holdings operates with shared services teams (IT, HR, Finance, Legal) that support all business units, alongside dedicated operational teams within each unit. Most employees belong to a primary team and may collaborate cross-functionally on projects. If you’re not sure which team owns something, start with your manager or ask in #ask-anything on Slack.Shared services teams
Human Resources (HR)
Purpose: Recruiting, onboarding, employee relations, benefits administration, performance management, and offboarding.
Own these processes:
- Hiring and onboarding — see Hiring SOP
- Offboarding — see Offboarding SOP
- Performance reviews — see Performance Review SOP
- Benefits enrollment and questions
To submit a request: [HR ticketing system or form — to be added]
Information Technology (IT)
Purpose: Managing company systems, devices, software, network security, and IT support.
Own these processes:
- Device provisioning and management
- Software and access provisioning
- Security monitoring and incident response — see Incident Response SOP
- IT change management — see Change Management SOP
For urgent issues: it@blevinsholdings.com
For security incidents: security@blevinsholdings.com SLA:
Finance & Accounting
Purpose: Bookkeeping, financial reporting, payroll, accounts payable/receivable, and budget management.
Own these processes:
- Payroll processing
- Expense reimbursement — see Expense Policy
- Vendor payment and invoicing
- Budget planning
For expense reimbursement: Submit via [expense system — to be added]
Payroll questions: [email]
Legal & Compliance
Purpose: Contracts, regulatory compliance, corporate governance, intellectual property, and legal risk management.
Own these processes:
- Contract review and execution
- Vendor agreements — see Vendor Management SOP
- Regulatory compliance
- Policy review and updates
For contract review: Submit via [legal intake form — to be added]
Operations
Purpose: Cross-functional process management, project coordination, vendor management, and operational efficiency.
Own these processes:
- Vendor management — see Vendor Management SOP
- Cross-functional project coordination
- Process documentation (these SOPs!)
Business unit teams
[Business Unit 1 Name]
Purpose: [What this team does, who they serve]
Slack channel: #[team-channel]
Standup / team meeting: [Day and time]
[Business Unit 2 Name]
Purpose: [What this team does, who they serve]
Slack channel: #[team-channel]
Standup / team meeting: [Day and time]
Cross-functional norms
Working with another team
- Start with Slack — Most requests can be handled in the team’s help channel
- Use the ticketing system — For IT, HR, Legal, and Finance requests, use the appropriate system so nothing falls through the cracks
- Respect response SLAs — Shared services teams have defined response times; plan ahead for non-urgent requests
- Escalate when needed — If a request is urgent or stuck, escalate to the team lead directly
Meeting norms
- Come prepared — read relevant docs, review the agenda, bring questions
- Meetings should have an owner, an agenda, and a summary/action items afterward
- Default to async for status updates — use Slack threads or project docs instead of meetings
- See the Communication guide for full meeting norms
Full team directory
For a full list of employees with roles, contact info, and team membership, see [the employee directory — link to internal system, e.g., Rippling, BambooHR, Notion].Last updated: [Date] — owned by HR