NFNick FergusonProperty claims candidate

Selected Work

Documentation, field visibility, and practical follow-through.

These examples are sanitized and centered on transferable claims skills. They do not imply carrier claim ownership, coverage authority, or production carrier-platform use.

Operational work

The strongest evidence comes from organized field and business operations.

The emphasis is on accurate records, unresolved-item visibility, stakeholder communication, and practical tools that support the process.

Project-based field support

Field Operations Documentation and Closeout

Supported an active field-service environment by organizing completed work, unresolved items, access constraints, materials, and follow-up needs for clearer stakeholder visibility.

  • Recorded site observations and open items without exposing customer names or sensitive site details.
  • Helped field teams maintain practical project records and clearer closeout communication.
  • Used a practical internal tool as one part of the documentation and follow-up workflow.
IT Pro Direct

Workflow and Information Organization

Built and supported practical documentation, workflow, and technology solutions in small-business and field-service environments.

  • Improved visibility and follow-up through structured documentation and internal tools.
  • Supported secure information handling, technical troubleshooting, and stakeholder communication.
  • Kept the focus on practical operations rather than technology for its own sake.
Communication project

Customer-Facing Website and Communication

Created a focused customer-facing website with clear service information, mobile-readable content, and a direct contact path.

  • Organized information around the questions a prospective customer would need answered.
  • Applied plain-language communication and a straightforward mobile experience.
  • Demonstrated the ability to translate operational detail into clear public-facing information.

Additional technical work

Technical literacy as a supporting capability.

These items are secondary learning and internal-work examples. They are not commercial claims services or production carrier systems.

Prototype / learning work

Claims Document Organization Prototype

Explored ways to organize representative claims documents, notes, and follow-up questions into a clearer human-reviewed workflow.

  • A learning prototype, not a production carrier platform or commercial claims service.
  • Did not make coverage decisions, value claims, or replace licensed professional judgment.
  • Used sanitized or representative material rather than confidential claim-file data.
Additional technical work

Analytics and Internal Tool Experiments

Built small tools and workflow experiments to improve information organization, issue visibility, and practical follow-up.

  • Technical work is presented as supporting evidence of organization and problem-solving.
  • No carrier adoption, production deployment, or business outcome is implied.

Connect

Hiring for a carrier-side property claims role or training program?

Nick welcomes conversations about structured claims development, desk or field adjusting roles, and professional insurance-industry connections.