CAGS-03: Conference Sponsorship Management and Revenue Tracking System

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 sponsorship information is often maintained across multiple documents and communication channels, including spreadsheets, email threads, signed agreements, invoices, and financial reports. This can make it difficult to maintain an accurate and up-to-date record of sponsor commitments and revenue.

Details such as sponsor contact information, sponsorship packages, negotiated benefits, agreement status, payment arrangements, and outstanding deliverables may not be consistently recorded in one place. As a result, staff may spend considerable time searching for information, following up on unsigned agreements, confirming sponsorship amounts, and checking whether promised benefits have been fulfilled.

There may also be delays in updating total sponsorship revenue when a new sponsor commits, an agreement changes, or a sponsorship package is revised. Without a reliable consolidated view, conference organizers may have difficulty determining how much sponsorship revenue has been secured, how much is contractually agreed upon, how much has been invoiced, and how much has actually been received.

The problem this project addresses is the lack of a centralized sponsorship management system that maintains accurate sponsor records, tracks contractual commitments and signed agreements, monitors sponsorship deliverables, and provides an up-to-date view of sponsorship revenue.

The proposed application will provide a single source of information for sponsorship administration, improve accountability, and enable accurate sponsorship revenue reporting to support conference planning and budgeting.


Main objectives

The primary objective is to develop a centralized sponsorship management application that streamlines sponsor information collection, agreement tracking, revenue monitoring, and fulfillment of sponsorship commitments.

The specific objectives are to:

  1. Centralize sponsor information: Create a single database containing sponsor organization details, primary contacts, contact information, sponsorship history, and relevant communications.
  2. Track sponsorship commitments: Record sponsorship packages, negotiated amounts, customized arrangements, agreed benefits, and any additional contractual obligations.
  3. Manage agreements and documentation: Store signed agreements and related documents, track signature status, and identify agreements that are outstanding, pending review, or awaiting completion.
  4. Provide an up-to-date sponsorship revenue total: Automatically calculate sponsorship totals based on clearly defined statuses, such as proposed, verbally committed, contractually agreed, invoiced, and received.
  5. Monitor payment status: Track amounts invoiced, payments received, outstanding balances, due dates, and follow-up requirements.
  6. Track sponsor benefits and deliverables: Record what each sponsor is entitled to receive, including logo placement, advertising, exhibition space, speaking opportunities, registrations, and other agreed benefits, as applicable.
  7. Improve communication and follow-up: Provide reminders for unsigned agreements, upcoming payment deadlines, outstanding sponsor information, and incomplete deliverables.
  8. Integrate with conference budget reporting: Make approved sponsorship revenue data available to the conference budget application so that sponsorship commitments and receipts can be reflected in financial forecasts and reporting.
  9. Improve data accuracy and accountability: Reduce duplicate records, maintain a history of changes, establish appropriate user permissions, and provide reports for management and finance staff.

Scope of work

The project will include requirements gathering, process analysis, system design, application development or configuration, testing, and implementation planning.

Phase 1: Requirements Gathering and Process Analysis

  • Review existing sponsorship spreadsheets, agreements, invoices, and tracking procedures.
  • Consult sponsorship staff, conference organizers, and finance personnel.
  • Identify required sponsor details, sponsorship categories, package types, and custom arrangements.
  • Define agreement statuses, revenue statuses, payment tracking requirements, and approval procedures.
  • Document the sponsorship benefits and deliverables that need to be monitored.
  • Identify reporting and integration requirements for the conference budget application.

Phase 2: System and Database Design

  • Design the sponsor information entry forms and administrative dashboard.
  • Define the database structure for sponsors, agreements, packages, payments, and deliverables.
  • Design the sponsorship status workflow from initial prospect through commitment and fulfillment.
  • Establish user roles and access permissions.
  • Develop mock-ups for sponsorship revenue summaries, agreement tracking, and outstanding tasks.

Phase 3: Application Development

  • Build the sponsor database and information entry interface.
  • Enable users to create and update sponsor profiles.
  • Add functionality to record sponsorship packages, agreed amounts, customized benefits, and contractual terms.
  • Implement document uploads for signed agreements and supporting files.
  • Develop automated sponsorship totals and status summaries.
  • Add payment tracking, reminders, and reports for outstanding agreements and balances.

Phase 4: Agreement and Benefit Tracking

  • Configure the workflow for draft, sent, signed, amended, and completed agreements.
  • Establish a process for confirming agreement execution and recording changes.
  • Record the benefits and deliverables associated with each sponsorship.
  • Create tracking views for outstanding sponsor assets, logo submissions, registrations, and other agreed benefits.
  • Configure reminders for key dates and overdue requirements.

Phase 5: Budget Integration and Testing

  • Define which sponsorship amounts and statuses will be shared with the conference budget application.
  • Map sponsorship records to the budget system's revenue categories and reporting fields.
  • Test sponsorship totals, payment balances, agreement status tracking, and document access.
  • Verify that revenue changes are reflected accurately in the receiving system.
  • Test user permissions, audit records, and duplicate prevention.
  • Conduct user acceptance testing with sponsorship and finance staff.

Phase 6: Implementation and Evaluation

  • Prepare user guides and administrative procedures.
  • Establish responsibilities for updating sponsor information and confirming agreements.
  • Demonstrate the system to stakeholders.
  • Evaluate the accuracy of sponsorship reporting and the efficiency of administrative processes.
  • Document future enhancements, including electronic signature integration and sponsor self-service features.

Deliverables 

  • Report, Resources, New protocols/processes
  • Requirements and process documentation Sponsor information, agreement workflows, revenue definitions, and fulfillment requirements are documented and validated.
  • Centralized sponsor database Authorized users can create, update, and retrieve sponsor records without unnecessary duplicate entries.
  • Agreement management module Users can identify agreements that are drafted, sent, signed, amended, or otherwise outstanding.
  • Sponsorship revenue dashboard Sponsorship totals are calculated accurately according to defined commitment and payment statuses.
  • Payment tracking module Invoiced amounts, payments received, and outstanding balances can be reviewed.
  • Benefits and deliverables tracker Sponsor obligations can be assigned, monitored, and marked complete.
  • Budget integration Relevant sponsorship revenue information can be exported or synchronized with the conference budget application.
  • Testing and user documentation Core workflows pass agreed test cases, and users receive instructions for operating the system.

Frequency

  • Bi-Weekly

Skills and training required 

The project team will need a combination of project management, business analysis, application development, financial administration, document management, and data integration skills.

  • Project management Project planning, scheduling, risk management, team coordination, and stakeholder communication.
  • Business analysis Requirements gathering, sponsorship workflow mapping, process improvement, and documenting business rules.
  • Sponsorship and relationship management Understanding sponsorship packages, negotiations, agreements, sponsor benefits, and relationship management processes.
  • Database management Data modeling, sponsor records, agreement tracking, data validation, and duplicate prevention.
  • Application development Form creation, application configuration, workflow automation, and dashboard development.
  • Document management Secure file uploads, document categorization, version control, agreement status tracking, and retention procedures.
  • Financial administration Revenue tracking, invoicing, payment reconciliation, outstanding balances, and reporting definitions.
  • Data integration Importing or synchronizing sponsorship revenue with the budget application and handling data validation errors.
  • Reporting and visualization Sponsorship totals, revenue status summaries, outstanding agreement reports, and deliverable tracking dashboards.
  • Privacy and security Role-based permissions, secure document storage, appropriate handling of contact information, and audit trails.
  • Testing and quality assurance Testing revenue calculations, workflows, document access, reminders, and data accuracy.
  • User training and documentation Preparing operating instructions, administrator guides, and training materials.

For a small capstone team, responsibilities can be combined. Consultation with sponsorship staff and finance personnel will be especially important for defining what constitutes a valid commitment and how revenue should be reported.


Resources required 

A. Human resources

  • Project manager/team lead: Coordinates the project timeline, deliverables, risks, and team activities.
  • Business analyst: Documents requirements and maps the sponsorship management process.
  • Sponsorship subject matter expert: DefiDeliverable
  • Proposed success measure
  • Requirements and process documentation
  • Sponsor information, agreement workflows, revenue definitions, and fulfillment requirements are documented and validated.
  • Centralized sponsor database
  • Authorized users can create, update, and retrieve sponsor records without unnecessary duplicate entries.
  • Agreement management module
  • Users can identify agreements that are drafted, sent, signed, amended, or otherwise outstanding.
  • Sponsorship revenue dashboard
  • Sponsorship totals are calculated accurately according to defined commitment and payment statuses.
  • Payment tracking module
  • Invoiced amounts, payments received, and outstanding balances can be reviewed.
  • Benefits and deliverables tracker
  • Sponsor obligations can be assigned, monitored, and marked complete.
  • Budget integration
  • Relevant sponsorship revenue information can be exported or synchronized with the conference budget application.
  • Testing and user documentation
  • Core workflows pass agreed test cases, and users receive instructions for operating the system.nes sponsorship packages, contractual commitments, benefits, and administrative requirements.
  • Application developer or technical specialist: Builds or configures the system.
  • Database specialist: Designs the sponsor, agreement, payment, and deliverable records.
  • Finance representative: Validates revenue calculations, invoice status, payment tracking, and budget integration requirements.
  • Testers/end users: Validate the system's functionality and usability.
  • For a small team, the business analyst may also handle project coordination, while the developer manages the database and integration tasks.


B. Technology and software resources

  • Computers and reliable internet access.
  • An application development platform, such as Microsoft Power Platform or an approved web application framework.
  • A structured database or data repository.
  • Secure document storage for signed agreements and supporting files.
  • Document and spreadsheet software.
  • Dashboard and reporting tools.
  • Collaboration and version control tools, where applicable.
  • Access to the conference budget application's data requirements or integration documentation.
  • A test environment containing sample sponsor records and fictional agreements.


C. Information and documentation
The team will need access to:

  • Existing sponsor lists and contact databases.
  • Sponsorship packages, pricing, and benefit descriptions.
  • Signed agreements and contract templates.
  • Sponsorship proposals and customized agreements.
  • Invoicing and payment procedures.
  • Sponsorship revenue reports.
  • Sponsor logo and promotional asset requirements.
  • Deliverable checklists and fulfillment procedures.
  • Agreement approval and signing procedures.
  • Data privacy, security, and document retention policies.
  • The financial categories and fields used in the conference budget application.
  • These materials will help ensure the new system reflects actual conference operations rather than introducing an entirely separate process.

D. Financial resources

Potential project costs may include:

  • Software licenses and subscriptions.
  • Cloud hosting, database, or document storage services.
  • Electronic signature services, if required.
  • Integration services or API access.
  • Training and technical support.
  • Testing and implementation.
  • Contingency expenses.


The final cost will depend on the platform selected and whether the organization can use existing licensed tools.

E. Time and stakeholder availability

  • Time for requirements gathering and process analysis.
  • Access to sponsorship and finance staff.
  • Time to review sponsorship agreements and document requirements.
  • Access to the budget application team or technical documentation.
  • Time for data migration, testing, and reconciliation.
  • Stakeholder participation in demonstrations and user acceptance testing.
  • A defined implementation timeline.

NDA or a commercialization agreement for this project?

Yes