The in-service is not a favour to the rep. It's your competency record.

Hospitals let reps in to teach because accreditors expect staff to be competent on the equipment they use, and expect the organization to show it. A calendar entry proves the rep came. It does not prove anyone learned anything.

What an in-service is, in the hospital's own words

One health system's vendor code of conduct defines it as a pre-planned, pre-arranged group presentation that takes place in an inpatient area, involving physicians, pharmacists, nursing or other care providers. The same policy adds two conditions that reps often miss. A vendor may only in-service a product the hospital has already accepted: an item on the formulary, a new indication for one, or a study the review board approved. And every in-service must be monitored by the hospital's own personnel.

The device equivalent of the formulary is value analysis. Hospitals say so directly: new items are not to be used until the value analysis team has approved them, or materials management has granted a one-time use. So the in-service comes after the committee, never before it, and it is the hospital's session with the rep as the instructor, not the rep's session in the hospital's building.

Why the hospital wants it: competency, and competency is auditable

For a new device, the guidance from sterile-processing and infection-control practitioners is specific: schedule the training with the manufacturer's representative, hold it on site, and include hands-on training, a return demonstration and competency verification for each staff member. The return demonstration is what makes it count. Watching a slide deck does not.

Behind that sits the accreditor. Healthcare leaders are expected to demonstrate that staff have the education, training and competencies needed to perform their roles safely, on the equipment they actually use. The in-service exists so the hospital can say, for a named nurse on a named device, that this happened.

The educator keeps the record, and the record is the deliverable

Look at any perioperative educator's job description and the same line appears: maintain accurate records of educational programs, attendance, evaluations and staff competencies, and provide reports as required by regulatory bodies. That is the artefact the hospital needs from an in-service, and a calendar produces only the first half of it. Who was there is the beginning of the record. Who demonstrated the skill is the end of it.

The shape of the educator's work matters too. Educators plan by cohort and by quarter: orientation intakes, competency fairs, annual skills days. A competency fair covers many products in one day, which is a different scheduling shape from one rep booking one slot. And night and weekend staff are structurally hard to reach, because educators work days. Hospitals that solve it run the same session again at half past midnight.

The numbers are smaller than the register suggests

A published case study of one specialty hospital gives a rare per-facility figure: 681 registered vendor representatives, and about three vendor visits a day, with up to forty possible. The register of who may come in is large. The daily traffic is not. What the hospital is managing is not volume but proof.

What to ask of any system that holds this

  • Keep "invited" and "attended" as two separate facts. Neither implies the other: people who accepted don't come, and people who declined turn up.
  • Record attendance by name, marked by the person or on their behalf by the organization.
  • Let both organizations read the same record, so the rep's company holds the same list you do.
  • Export it, so it can sit in your education records where the accreditor will look.
  • Do not confuse it with the competency sign-off. That belongs with the return demonstration, and with your learning records, not with a calendar.
In QuickTouch

An in-service on the Calendar carries an invitation list, answered per person, and a separate attendance list the hospital records by name. Both organizations read it, and it exports as a file. The competency sign-off stays with your education records on purpose: QuickTouch is not a learning management system and does not pretend to be one. See in-services and attendance

Sources Main Line Health, Vendor Code of Conduct, for the definition and the two conditions. Nancy Chobin RN, Holding manufacturers accountable for their IFUs, Infection Control Today, August 2018. symplr, case study of a Baton Rouge specialty hospital, July 2021, for the visit and register figures. Perioperative RN educator job postings, 2026, for the record-keeping duty and the cohort planning shape. HealthManagement.org, Engaging the night-shift nurse, for the shift problem.
Previous: What a value analysis committee wants Next: An accepted visit is not a badge