1. PURPOSE

The FDU IT Business Relationship Management Office (BRMO) Charter Framework defines how OIRT builds and maintains strong working relationships with the University’s academic and administrative departments. It creates a clear model for communication, planning, accountability, and partnership so that each department has a known IT contact and a consistent experience working with OIRT.

OIRT exists to serve FDU’s students, faculty, staff, and the larger mission they support. Serving that mission well requires more than technical skill. It requires understanding what each part of the University needs, when it needs it, and why it matters. BRMO formalizes the relationship work that strong IT leaders at FDU already do naturally, making it more consistent, visible, and scalable across the department. As FDU grows in ambition and complexity, OIRT must also grow in its ability to serve as a true institutional partner.

Today, the quality of the relationship between OIRT and a given department can depend too much on individual initiative. Some departments feel well served and well informed. Others experience IT as difficult to navigate. They may be unclear about who to contact, what is being worked on, or how to raise a concern or opportunity. This inconsistency is not a reflection of effort. It reflects the absence of a shared model for how OIRT engages with the University. BRMO establishes that model so every department receives the same quality of partnership regardless of who their IT contact happens to be.

2. DEFINITIONS

These definitions apply to the following terms as they are used in this charter.

BRMO	The Business Relationship Management Office (and Officer) is the function within OIRT that owns, manages, and develops the relationship between the IT organization and the University’s academic and administrative departments. It is not a help desk or an escalation queue, though it can support escalation when needed. Its main role is to create a strategic partnership with the associated business unit.
BRMO Practitioner	An IT leader assigned responsibility for managing the relationship with one or more business units. Practitioners are usually existing IT leaders, not a separate team.
Business Partner	A leader or representative from a University department who works with IT to share needs, priorities, and planning considerations.
Stakeholder	Any faculty member, staff member, or student affected by technology decisions made by IT. Each stakeholder group should have a Business Partner who can represent its interests.

3. FRAMEWORK OVERVIEW

How BRMO Fits Within FDU IT Governance

BRMO is the relationship layer of OIRT governance. It operates continuously through regular meetings, conversations, and planning cycles so IT remains connected to the University day to day and month to month. In addition to standard intake channels, BRMO Practitioners identify significant needs through relationship conversations and make sure those needs are shaped and elevated to IT leadership for planning, prioritization, and decision-making.

Business Relationship Management

Business Relationship Management (BRM) is the practice of building and maintaining a strategic partnership between IT and the departments it serves. It includes understanding business needs, communicating IT capabilities and constraints, aligning technology investments with departmental priorities, and making sure the value of IT is understood by the people who rely on it. At FDU, BRMO does not create a new team. It formalizes work already being done by IT leaders and raises it to a consistent institutional standard.

What BRMO Is and Is Not

BRMO Is	BRMO Is Not
A structured model for how OIRT builds and maintains relationships with University departments	A help desk or escalation queue for IT support issues
A way to surface technology needs, challenges, and ideas from the University to IT	A project management office or delivery function
Proactive engagement, not reactive ticket management	A guarantee that every request will be fulfilled
A bridge between departmental needs and IT planning and governance	A replacement for existing IT service channels
A feedback loop that helps OIRT understand whether it is delivering value	A committee that only meets and produces reports

BRMO is an active practice embedded in how IT leads.

4. STAKEHOLDERS AND RELATIONSHIPS

BRMO Practitioners (IT Side)

BRMO Practitioners are IT leaders, typically directors, managers, or senior staff, who are assigned responsibility for managing the relationship with one or more University departments. Each Practitioner serves as the primary OIRT point of contact, advocate, and communication channel for assigned business partners. They are responsible for understanding their partners’ environment, surfacing needs into IT planning, and making sure partners stay informed about relevant OIRT activities, initiatives, and decisions. At FDU, being a BRMO Practitioner is not an extra assignment. It is a core leadership expectation.

Business Partners (University Side)

Business Partners are the leaders or designated representatives of FDU departments who engage with their assigned BRMO Practitioner. They may include deans, department heads, administrative directors, or delegates. Their role is to represent departmental technology needs and priorities, participate in regular engagement sessions, raise ideas and challenges, and provide feedback on OIRT services and initiatives. Business Partners are not expected to be technical. They are expected to be honest about what is working, what is not, and where technology could better support their goals.

Relationship Alignment Model

Each major University department or functional area is assigned a primary BRMO Practitioner. The CIO’s office maintains the master relationship map and reviews assignments annually or when organizational changes occur. Assignments should reflect the Practitioner’s subject matter knowledge, existing relationships, and workload. Where a department has complex or high-volume technology needs, a secondary Practitioner may be assigned. The goal is simple: no department should ever have to wonder who their IT contact is.

5. OPERATING MODEL

Core Responsibilities of a BRMO Practitioner

• Maintain a regular meeting cadence with assigned business partners, at minimum quarterly and ideally monthly for active or complex relationships.
• Set and share a standing agenda that covers ongoing OIRT activities relevant to the department, open items, and space for new topics.
• Surface project ideas and technology needs from the University into OIRT planning and prioritization processes.
• Communicate proactively so partners do not learn about OIRT changes, outages, or initiatives from someone else first.
• Serve as the escalation path when a business partner has a concern that normal service channels have not resolved.
• Represent the business perspective in internal OIRT conversations, planning sessions, and prioritization discussions.
• Track and follow up on open commitments.
• Share an annual OIRT roadmap summary relevant to each department so partners understand what is planned and why.

Meeting Cadence and Engagement Model

• Monthly or bi-monthly one-to-one meetings between the Practitioner and the primary Business Partner, typically 30 to 60 minutes.
• Quarterly business reviews for higher-complexity relationships that include a broader view of IT services, performance, and upcoming changes.
• Annual planning conversations to align IT priorities with departmental goals for the coming year.
• Ad hoc check-ins as needed for urgent issues, major projects, or significant changes.

Practitioners should maintain brief notes from each meeting and track open items. A shared document or email summary is enough. The goal is continuity, not paperwork for its own sake.

How Needs Surface and Get Addressed

When a Business Partner identifies a technology need, challenge, or idea, the BRMO Practitioner receives it, assesses it, and connects it to the right path within IT.

• Operational issues: directed to the appropriate IT service team, with the Practitioner monitoring for resolution.
• Enhancement requests: logged and brought into the appropriate IT planning cycle.
• New capability ideas: assessed for fit and, if viable, brought to IT leadership for prioritization and planning.
• Information needs: answered directly by the Practitioner.

No idea or need should go unacknowledged. If IT cannot address something, the Practitioner is responsible for explaining why and, where possible, offering alternatives.

Escalation Path

If a business partner has a concern that cannot be resolved at the Practitioner level, the escalation path is BRMO Practitioner, then IT Director or Manager, then CIO. Business Partners should always know where their issue stands and who is accountable for it.

6. DESIRED OUTCOMES

For Business Partners

• A known, trusted OIRT contact who understands the department’s goals and constraints.
• Confidence that OIRT is aware of departmental needs and actively working to address them.
• Advance visibility into OIRT changes and initiatives that will affect the department.
• A clear path to raise ideas, escalate concerns, and receive substantive answers.
• The experience of OIRT as a solutions-oriented partner in achieving the department’s mission.

For the IT Team

• A structured understanding of each department’s priorities, challenges, and technology maturity.
• Earlier visibility into demand, enabling more effective planning and resource allocation.
• Fewer surprises for both OIRT and the FDU community it serves.
• A more informed basis for prioritizing projects and investments.
• A clearer demonstration of the role technology plays in advancing FDU’s goals.

For FDU

• Technology investments that better reflect the University’s actual needs and priorities.
• Increased transparency and confidence between OIRT and the departments it serves.
• A stronger foundation for strategic OIRT planning and governance.
• An OIRT organization recognized as a partner in advancing FDU’s academic and operational mission.

7. MEASURING SUCCESS

Critical Success Factors

BRMO succeeds when Practitioners engage consistently, business partners participate actively, and both sides experience the relationship as genuinely valuable. The most important early signal is whether business partners feel more informed and better served than before, and whether OIRT has clearer, more actionable insight into University needs. These results take time to develop. The first phase focuses on establishing cadence and building trust. Later phases are where strategic value becomes measurable and visible.

Key Metrics

• Business Partner Satisfaction Score: an annual survey measuring responsiveness, communication, and perceived value. Target: establish a baseline within three months and improve by 10 or more points by the end of Year 1.
• Engagement coverage: the percentage of assigned relationships with an active, documented meeting cadence. Target: 100 percent within six months.
• Demand visibility: the number of project ideas and technology needs surfaced through BRMO into OIRT planning. Establish a baseline within three months and track the trend.
• Open item resolution rate: the percentage of commitments made to business partners that are resolved or formally communicated on within 30 days.
• Escalation frequency: tracked as a health signal. Sustained high escalation volume suggests a relationship or process problem that needs attention.

Maturity Milestones

• 0 to 6 months: all relationships assigned, meeting cadences established, and an initial relationship health baseline captured.
• 6 to 12 months: first satisfaction survey completed, open item tracking in place, and an initial pipeline of University-sourced project ideas visible in OIRT planning.
• 12 to 24 months: BRMO is embedded in IT leadership routines, and business partners consistently report feeling informed, heard, and well served.
• 24 months and beyond: BRMO is recognized as a valued institutional function, and OIRT is consistently perceived as a strategic partner in advancing FDU’s mission.

8. GOVERNANCE AND ACCOUNTABILITY

Ownership

The BRMO function is owned by the CIO. Day-to-day operation is the responsibility of each BRMO Practitioner within assigned relationships. The CIO or a designated BRMO lead is responsible for maintaining the relationship assignment map, facilitating periodic Practitioner sync meetings, reviewing satisfaction data, and ensuring the framework is applied consistently across the OIRT team.

Charter Review Cycle

This charter will be reviewed annually. The CIO’s office will assess whether the framework is operating as intended, whether structural changes are needed, and whether metric targets should be adjusted. Business Partners will be invited to contribute to the review. Material changes to the charter require approval from the CIO and acknowledgment from IT leadership.

---

See also