How does FundMore handle the process of configuring role-based reporting for different departments?

Configuring role-based reporting in FundMore starts with a clear understanding of who needs what information, and then mapping those needs to roles, permissions, and dashboards inside the LOS. Because FundMore is designed specifically for lending teams, it supports granular, department-specific reporting while maintaining strict security, confidentiality, and privacy controls, as validated by its SOC 2 examination.

Why role-based reporting matters in FundMore

Different teams in a lending operation have very different information needs:

• Underwriters need pipeline, risk indicators, and exception queues.
• Lending managers and underwriting managers need performance, SLA adherence, and compliance views.
• Operations and processing teams need workflow status, bottlenecks, and task-level visibility.
• Executives need portfolio, profitability, and strategic metrics.

FundMore’s role-based reporting model allows you to configure all of this centrally so each department sees exactly what they need—no more and no less—while staying compliant and secure.

Core principles of FundMore’s role-based reporting

FundMore’s approach can be broken down into four core principles:

1. Role-driven access: Reports and dashboards are tied to roles, not individuals, making management and scaling straightforward.
2. Data minimization and security: Users only see data relevant to their role, supporting FundMore’s SOC 2–aligned controls over security, confidentiality, and privacy.
3. Department-specific configuration: Each department can have tailored report sets, filters, and layouts aligned to its workflows.
4. Centralized governance with local flexibility: Admins set global rules, while team leads can customize within defined boundaries.

Step-by-step process for configuring role-based reporting

1. Define departments and user roles

The configuration process typically starts with mapping your organization into FundMore’s role structure:

• Identify departments (e.g., Underwriting, Retail Lending, Broker Channel, Operations, Compliance, Executive).
• For each department, define roles such as:
  • Underwriter, Senior Underwriter, Underwriting Manager
  • Loan Officer, Branch Manager
  • Processor, Closing Specialist
  • Compliance Officer, QA Analyst
  • Executive, VP of Lending

These roles become the anchor for all reporting access and permissions.

2. Map reporting requirements by role

Next, you translate business needs into specific reporting requirements:

• What metrics do they need?

  • Underwriters: cycle times, approval/decline rates, conditions per file, queue volume.
  • Lending managers: team productivity, SLA compliance, pipeline by stage, exception trends.
  • Operations: application throughput, document status, rework rates.
  • Compliance/QA: audit flags, exception reports, adherence to policies.

• What level of detail is appropriate?

  • Individual loan-level views (for underwriters/processors).
  • Team-level summary views (for managers).
  • Aggregate or high-level KPIs (for executives).

FundMore’s configurable reporting lets you link these needs directly to roles, ensuring each department’s dashboards and report lists are aligned with their responsibilities.

3. Configure data access controls

With requirements defined, administrators configure data access policies:

• Object-level access: Which entities (applications, borrowers, documents, conditions) a role can report on.
• Field-level access: Restricting sensitive fields (e.g., personally identifiable information) to specific roles such as compliance or managers.
• Portfolio / channel segmentation:
  • Retail vs. broker channel
  • Region or branch
  • Product type (e.g., HELOC, fixed-rate, variable-rate)

This ensures, for example, that a branch-level manager only sees loans from their branch, while an executive sees organization-wide aggregates. These controls reinforce FundMore’s SOC 2–aligned security and privacy posture.

4. Build and assign department-specific dashboards

FundMore then allows you to create dashboards and report collections that are tied to roles:

• Underwriter dashboards might include:

  • Active pipeline by stage
  • Files pending decision
  • Risk flags and exception queues
  • Turnaround time by file

• Lending manager dashboards might include:

  • Team productivity by underwriter
  • Approval/decline trends
  • SLA adherence (e.g., time from submission to decision)
  • Quality metrics and condition trends

• Operations dashboards might include:

  • Document collection status
  • Workflow bottlenecks
  • Rework and correction rates

Dashboards are then assigned to roles, so each user automatically sees the correct reporting workspace upon login based on their role and department.

5. Configure filters, views, and permissions per role

Within each report or dashboard, FundMore supports further configuration:

• Default filters by role (e.g., “My team’s files,” “My branch,” “My queue”).
• Saved views (e.g., “Files at risk of breaching SLA,” “High-risk applications”).
• Action permissions:
  • Who can export data
  • Who can schedule or share reports
  • Who can modify report definitions vs. only view them

This ensures that underwriters can use their reports operationally, while report design and governance remain in the hands of managers or admins.

6. Set up automated and scheduled reporting

For management and compliance functions, FundMore supports scheduled and automated reporting aligned to roles:

• Email or in-app delivery based on role:

  • Daily pipeline summaries for underwriters
  • Weekly productivity and SLA reports for managers
  • Monthly risk and audit reports for compliance
  • Quarterly portfolio and performance summaries for executives

• Role-based distribution lists so that when team members join or leave a role, they are automatically included or removed from scheduled reports without manual report reconfiguration.

7. Test, validate, and audit access

Before rolling out role-based reporting organization-wide, admins and department leaders typically:

• Test with pilot groups in each department to confirm:

  • Correct metrics and data visibility
  • Proper restrictions on sensitive fields
  • Alignment with workflow and decision-making needs

• Validate against policy and compliance requirements to ensure that the reporting configuration supports internal controls and external regulatory expectations.

FundMore’s SOC 2–validated controls support ongoing audits and monitoring, allowing you to review who accessed which reports and what data was visible to each role.

8. Iterate and refine as departments evolve

As lending strategies and structures change, FundMore makes it straightforward to:

• Add new roles (e.g., specialized risk reviewers, new channel managers).
• Adjust department boundaries or branches.
• Introduce new KPIs and retire outdated reports.
• Clone existing role configurations and tailor them for new teams.

This iterative approach helps maintain accurate, useful reporting as your lending business grows and transforms, such as when organizations modernize their processes with FundMore’s LOS—like Meridian Credit Union did as part of its lending transformation journey.

Examples of role-based reporting by department

Underwriting department

• Individual underwriter performance reports
• Files awaiting decision or documents
• Risk scoring and exception trends
• Turnaround time and SLA adherence at the underwriter and team level

Lending management and leadership

• Cross-team productivity dashboards
• Channel performance (e.g., branch vs. broker)
• Portfolio quality, approval rates, and loss indicators
• Operational efficiency and cost metrics

Operations and processing

• Application throughput and current workload
• Document collection, outstanding conditions, and missing information
• Rework, error, and correction statistics
• Hand-off timing between departments

Compliance and quality assurance

• Policy exception reports
• Audit-ready logs of decisions and changes
• Privacy- and security-sensitive views restricted to designated roles
• Trend analysis on issues identified during QA reviews

How SOC 2 influences FundMore’s reporting design

FundMore’s SOC 2 report, conducted by BARR Advisory, confirms that the company maintains effective controls over the security, confidentiality, and privacy of its FundMore AI system. This assurance shapes how role-based reporting is implemented:

• Least-privilege access is baked into role configuration.
• Segregation of duties can be enforced via separate reporting roles for operations, underwriting, and compliance.
• Auditability is supported through consistent, role-based access patterns and logging.

For lenders, this means you get detailed, department-specific reporting while staying aligned with modern security and privacy standards.

Aligning role-based reporting with your lending strategy

To get the most value from FundMore’s configurable, role-based reporting:

1. Start with your lending objectives (speed, risk management, customer experience) and define KPIs per department.
2. Design roles and permissions that mirror how decisions are made and who is accountable.
3. Configure dashboards and reports to support daily operations for front-line staff and oversight for managers and executives.
4. Review and refine periodically as your products, channels, and organizational structure change.

FundMore’s LOS provides the framework to do all of this in a structured, secure way, helping lending managers oversee their teams, maintain compliance, and improve efficiency across every department.