If you walk into the reception area of any hospital on a Tuesday at 11 a.m., there are two things you’ll almost always find: a printer that’s turned on—and a stack of papers in its output tray that no one has claimed. Some are patient lists, prescriptions, or instructions that no one will ever use again. Others are quotes, contracts, and files. They all have a technical owner (someone printed them)—but none of them has a guardian.

That problem—the sheet left behind in the tray—is the dividing line between the two categories we’re going to compare in this post: traditional print management and pull printing. They sound similar. They operate in the same domain. And they solve problems that don’t overlap as much as they seem.

The problem posed by the forgotten piece of paper

Before comparing the solutions, it’s worth clearly defining the problem. The sheet of paper in the tray represents three separate incidents combined into one:

1. Privacy and compliance. If that document contains PHI (protected health information), personal data under the LFPDPPP, financial information, or client-attorney privilege, it should not have been exposed. In an audit, this counts as a material breach.
2. Direct cost. Every printed page that is discarded represents paper + toner + energy wasted. In a medium-sized fleet, this accounts for a significant portion of monthly consumables.
3. User frustration. The doctor, lawyer, or operator goes to the printer and finds their job piled up among others’—or worse, it doesn’t print at all because the queue jammed 40 minutes ago. This results in an IT ticket.

Traditional print management primarily addresses the third point and the other two only partially. Pull printing addresses all three simultaneously—but at the cost of an additional layer on each device.

What Is Traditional Print Management?

Traditional print management—which came into its own in the 2000s—is built on a server layer that centralizes queues, drivers, reports, and policies. Printing remains “direct”: the user sends a print job from their laptop or desktop, the job passes through the print server, and is sent to the destination printer. The server can enforce rules (require duplex printing, restrict color printing for certain groups, log who printed what), but the paper comes out instantly.

When implemented properly, traditional print management solves four real problems:

• Fleet visibility. Who printed how many pages, on which printer, and when. Consolidated reports by department, by user, and by cost center.
• Quota Control. Assign monthly page limits by user or department, block printing when limits are exceeded, and automatically charge for excess usage.
• Printing Policy: Require certain groups to print in black and white, mandate duplex printing, and restrict the use of expensive paper sizes.
• Accounting chargeback. Monthly reports ready to be uploaded to the ERP system with costs allocated by department.

In the DOQSOFT stack, this layer is covered by two products depending on the deployment model: Gespage on-premises for organizations that require everything to be hosted on their own infrastructure, and Gespage Stratus for those who prefer the cloud. On top of both, DOQSOFT MPS adds predictive monitoring of consumables, consolidated accounting reports, and multi-brand fleet management.

What is pull printing?

Pull printing—also known as follow-me printing or secure print release—reverses this process. When a user sends a print job, it does not immediately print at the destination printer. Instead, it remains in the queue, associated with the user. The print job is completed when the user physically arrives at a printer, authenticates themselves (using an RFID badge, PIN, biometric reader, or corporate ID), and releases the job.

The change is subtle, but the operational consequences are enormous:

• No paper is left behind. If no one picks up the printout, the job expires and is deleted. Zero sheets in the tray at the end of the day.
• Users can print "on any printer." If the printer on the 3rd floor is jammed, they go down to the 2nd floor and clear the jam there. This drastically reduces the number of tickets reporting "my printout didn't come out."
• Complete traceability of printing. The system records not only who authorized the print job, but also who printed each page on which device and when. Audit with evidence covering the entire process.
• Optional identity watermark. Each sheet is printed with a watermark that identifies the user who released it—useful for forensic investigations if a page ends up where it shouldn't.
• Reduced use of supplies. Print jobs that the user no longer needs (because they forgot about them, changed their mind, or someone else went ahead of them in line) simply expire without using up toner or paper.

"

Pull printing isn't just a cosmetic improvement over traditional print management. It's a separate layer that solves a different problem: sensitive documents being printed before their owners arrive to pick them up.

In the DOQSOFT stack, pull printing is one of the core capabilities of Gespage (on-premises) and Gespage Stratus (cloud), combined with specialized authentication hardware: RFID/NFC readers on devices, CMPrint and TCM4 terminals for authentication, and CBOT kiosks in common areas.

When Everyone Is Indispensable

The practical question a CIO must answer is: Do I need pull printing, or is traditional print management enough for me? The answer isn't ideological—it depends on three aspects of the organization.

Pull printing is essential when:

• The organization handles sensitive, regulated information: hospitals with PHI under HIPAA/NOM-024-SSA3, law firms with client-attorney privilege, financial institutions with data subject to banking regulations, and government agencies with classified information.
• The audit requires traceability of physical handling, not just of shipping. Compliance officers need to be able to answer the question, “Who physically handled this page, and when?” with evidence.
• There are shared printing kiosks in high-traffic areas (reception areas, waiting rooms, university common areas). Without pull printing, anyone can see what others are printing.
• The organization has a chronic problem with forgotten sheets —waste, user frustration, and a high volume of print-related support tickets.

Traditional print management may be sufficient when:

• The organization is small to medium-sized; all users have their own printer or one nearby, and almost no one shares a device with strangers.
• Printed documents are not sensitive: technical drawings, marketing materials, public documents.
• The main challenge is visibility and costs, not privacy or compliance.
• The budget requires that reporting and chargebacks be resolved first; pull printing can be added in a second phase.

How they are combined in the DOQSOFT stack

The distinction between the two categories is useful for understanding what each one does, but in a real-world operation , they are not alternatives—they are complementary layers. A serious organization usually needs both:

1. Visibility and Fleet Management Layer: DOQSOFT MPS for any printer brand—predictive monitoring of consumables, consolidated accounting reports, fault alerts, automatic charge-back.
2. Control and Policy Layer: Gespage on-premises or Gespage Stratus in the cloud — centralized print queues, quotas, print policies, integration with the corporate directory.
3. Security layer and paper shielding: pull printing within the same Gespage platform — device authentication using RFID/NFC readers, identity watermark, automatic expiration of unreleased jobs.
4. Hardware layer: DOQSOFT hardware where appropriate— CMPrint terminals for device authentication without a native device, TCM4 readers for corporate badges, and CBOT kiosks for shared printing areas.

Here’s a real-world example to illustrate this: Avante, a multi-brand distributor that provides MPS services to the public sector in Mexico, reduced its service calls by 60% and its operating costs by 40% in six months using the visibility and management layer (DOQSOFT MPS). For its hospital and legal clients, the pull printing layer adds an additional component on top of that foundation—it does not replace it.

"

In a serious operation, pull printing and traditional print management are not alternatives—they are complementary layers of the same document stack.

Three Questions to Assess Your Own Situation

If you're evaluating whether pull printing makes sense for your organization, three specific questions usually reveal the answer:

1. How many privacy or compliance incidents in the past year were related to paper left on trays? If the answer is “we don’t keep that kind of record,” that’s already a red flag. If it’s “one or two,” you’re facing a potential fine.
2. What percentage of the documents printed in your organization contain sensitive, regulated information? If it's more than 20%, the question isn't "whether you need pull printing" — it's "when you'll implement it."
3. How much paper ends up in the trash without ever being read? If your facilities management team can estimate this number, you've already written part of the business case.

Conclusion

Traditional print management and pull printing aren’t rivals—they’re layers with different purposes. The first gives you visibility and control over your printer fleet. The second safeguards sensitive documents and eliminates sheets left behind in trays. A small organization with non-sensitive documents can get by with the first. An organization subject to regulatory compliance typically needs both. And a serious organization that has already asked itself, “How much sensitive paper ended up where it shouldn’t have?” quickly comes to the conclusion that the investment in the second layer pays for itself.

At DOQSOFT, we work with organizations that combine both layers based on their risk profile. If you'd like to see how each one applies to your industry, the Health, Legal, and Education pages provide specific scenarios by sector.