CAGS-01: Speaker Information Capture and Transfer

Description of Organization

CAGS is Canada’s only national organization representing the interests of General Surgeons. Our Mission is to empower general surgeons to improve patients’ lives through continued advocacy, education, and research. We advocate on behalf of academic, community, rural and remote General Surgeons on issues related health human resources, transition of practice, pay equity, and the required access to resources to provide care for patients, and for quality of care for surgical patients.

CAGS manages the planning and delivery of the Canadian Surgery Forum – the largest scientific and networking event for General Surgeons in Canada. In addition, through our General Surgery Learning & Resource Centre, we provide educational opportunities to ensure general surgeons can upgrade their skills as part of their Continuing Medical Education and assurance of optimal patient care. To learn more about or join CAGS, explore our website, connect with us on LinkedIn, or donate to the Canadian General Surgery Foundation (CGSF) to help further surgical research in Canada.
CAGS also manages 4 other societies focused on surgery:

  • CSSO
  • CSCRS
  • CHS
  • CHPBA

As well as the Canadian General Surgery Foundation.
We are a very lean team of 6 people and we need help to digitize things!


Problem area

Conference organizers often collect speaker information through multiple methods, such as email, online forms, and spreadsheets. This can create administrative inefficiencies, duplicate data entry, missing information, and delays in preparing the conference program.

In addition, speaker information, presentation details, biographies, travel expenses, reimbursement documentation, and payment information may be managed separately. This makes it difficult to track submission status, ensure all required documentation has been received, and coordinate timely payments.

When speaker information changes after submission, organizers may also need to manually update several documents or versions of the conference program, increasing the risk of errors and inconsistencies.

The problem this project addresses is the lack of a centralized, integrated, and efficient process for collecting, approving, managing, and publishing speaker information while coordinating payment and reimbursement requirements.

The proposed system will provide a single platform where speakers can submit their information, conference administrators can review and approve submissions, approved information can populate the conference program, and the necessary financial documentation can be tracked.


Main objectives

The primary objective is to design and develop a centralized system that automates the collection, approval, and management of conference speaker information, while improving the accuracy and efficiency of conference administration.

The specific objectives are to:

  1. Centralize speaker information: Create a secure online portal where speakers can enter and update their contact details, biographies, photographs, presentation titles, abstracts, and other required information.
  2. Streamline the approval process: Establish a workflow that allows conference administrators to review submissions, request revisions, approve information, and track submission status.
  3. Automate conference program preparation: Enable approved speaker information and presentation details to populate the conference program or a program-ready data source, reducing manual data entry.
  4. Improve payment and reimbursement administration: Collect and track the required payment details, reimbursement claims, receipts, expense information, and supporting documentation.
  5. Improve communication and tracking: Provide notifications and reminders for incomplete submissions, pending approvals, missing documentation, and outstanding reimbursement requirements.
  6. Enhance data accuracy and security: Reduce duplicate records, standardize information, control access to sensitive financial data, and maintain an audit trail of approvals and changes.
  7. Increase operational efficiency: Reduce administrative workload, minimize errors, and provide conference organizers with a clear overview of speaker submissions and outstanding tasks.

Scope of work

The project will cover the planning, design, development, testing, and evaluation of the proposed system.

Phase 1: Requirements Gathering and Analysis

  • Consult conference organizers, finance staff, and other stakeholders.
  • Document the current speaker submission and reimbursement processes.
  • Identify required speaker fields, approval rules, program formats, and financial documentation.
  • Define functional requirements and project success criteria.

Phase 2: System Design

  • Design the speaker submission forms and administrator dashboard.
  • Map the workflow from submission to approval and publication.
  • Design the database and define user roles and access permissions.
  • Develop mock-ups for the conference program and financial tracking views.

Phase 3: System Development

  • Build the speaker portal and secure information storage.
  • Implement submission validation and document uploads.
  • Develop the approval, revision, and notification workflows.
  • Create functionality to export or integrate approved speaker details into the conference program.
  • Build reimbursement and payment tracking features.

Phase 4: Integration and Testing

  • Test the complete workflow from speaker submission to program publication.
  • Verify that approved information transfers accurately to the program.
  • Test financial document tracking, permissions, and notifications.
  • Conduct user acceptance testing with representative users.
  • Correct identified defects and usability issues.

Phase 5: Implementation and Evaluation

  • Prepare user instructions and administrator documentation.
  • Demonstrate the system to stakeholders.
  • Evaluate the system against the project objectives.
  • Document limitations, lessons learned, and recommendations for future enhancements.

Deliverables 

  • Report
  • Resources
  • New protocols/processes
  • Progran to make the transfer

Frequency

  • Bi-Weekly

Skills and training required 

The project team will need a combination of project management, business analysis, technical development, financial process knowledge, and testing skills.

  • Project management Project planning, task allocation, scheduling, risk management, and progress reporting.
  • Business analysis Stakeholder interviews, requirements gathering, workflow mapping, and process improvement.
  • System design User experience (UX), interface design, wireframing, and workflow design.
  • Database management Data modeling, database design, data validation, and management of speaker and financial records.
  • Software development Web forms, application development, workflow automation, and system integration, depending on the selected platform.
  • Data and reporting Spreadsheet management, data imports and exports, reporting, and conference program formatting.
  • Testing and quality assurance Functional testing, integration testing, user acceptance testing, and error handling.
  • Privacy and security Access controls, secure document storage, data protection, and handling of sensitive payment information.
  • Finance and administration Understanding reimbursement policies, receipt requirements, payment approvals, and financial recordkeeping.
  • User training and documentation Preparing user guides, administrator instructions, demonstrations, and support materials.

Not every team member needs expertise in all these areas. Responsibilities can be divided according to team size and existing experience. Training may include short courses, platform tutorials, consultations with finance staff, and hands-on testing.


Resources required 

A. Human resources

  • Project manager/team lead: Coordinates activities, timelines, deliverables, and communication.
  • Business analyst: Documents requirements and maps existing and proposed workflows.
  • Developer or technical specialist: Builds or configures the system and its integrations.
  • Database specialist: Designs data structures and information storage, where needed.
  • Conference organizer or subject matter expert: Explains current procedures and validates requirements.
  • Finance representative: Provides guidance on payment, reimbursement, documentation, and approval processes.
  • Testers/end users: Evaluate the system and provide feedback on usability and accuracy.
  • For a small capstone team, some of these responsibilities can be combined.

B. Technology and software resources

  • Computers and reliable internet access.
  • A development platform, such as Microsoft Power Platform, a web application framework, or another institution-approved tool.
  • A database or structured data repository.
  • Form-building and workflow automation tools.
  • Spreadsheet and document software for program templates and financial reports.
  • Version control and project collaboration tools, where applicable.
  • A test environment with sample speaker records and fictional financial information.

C. Information and documentation

  • Existing speaker submission forms and spreadsheets.
  • Conference program templates and publishing requirements.
  • Speaker communication templates.
  • Reimbursement policies, expense categories, and receipt requirements.
  • Payment approval procedures and financial reporting requirements.
  • Data retention, privacy, and information security policies.
  • Examples of common submission errors and administrative bottlenecks.

D. Financial resources

  • The project may require a budget for:
  • Software subscriptions or application licenses.
  • Cloud hosting, database services, or storage.
  • Integration services, if required.
  • Training materials and technical support.
  • Testing and implementation.
  • Contingency expenses.


Costs will depend on whether the team uses existing institutional software or builds a custom application. A low-cost prototype may be feasible with tools the organization already licenses.
 

E. Time and stakeholder availability

  • Scheduled time for team meetings and development.
  • Access to conference organizers and finance personnel for consultation.
  • Time for requirements review, demonstrations, and user acceptance testing.
  • Access to a representative group of speakers or test users.

A defined project timeline with milestones and deliverables.


NDA or a commercialization agreement for this project?

Yes