Pretoria Municipal Print

A city office workflow that had outgrown message chains

The brief came from a municipal print team in Pretoria that handled stationery, notices, forms, vehicle decals and other recurring internal print work for several departments. Requests were landing through our contact form, by phone, and sometimes on paper, which made it harder to track who had approved what and which job was waiting on artwork or payment coding.

The team wanted a single ordering path for staff members, with different access levels for requesters, approvers and production staff. They also needed the portal to fit a public-sector environment where purchase references, cost centre allocation and audit trails matter. The site had to be plain enough for everyday users, but strict enough for departmental controls.

The other pressure point was artwork. Some jobs arrived ready, others needed file checks, layout fixes or sign-off before they could move forward. Without a structured process, jobs would sit in a queue while someone tried to trace the latest version. That was the main issue behind the project.

The rules behind the portal, not just the shopping layer

We built the storefront around role-based approvals, so a staff member could raise a request, a manager could approve it, and the print team could only release work once the right steps had been completed. The portal also separated standard items from custom jobs, which helped the team keep routine orders moving without losing control over special requests.

Product builders were set up for the main items the municipality ordered often, with fields for size, quantity, paper stock, finishing and delivery notes. Price matrices handled combinations that changed by size or quantity, while artwork rules flagged low-resolution files, missing bleeds and incorrect page settings before a job could be accepted.

• Role-based access for requesters, approvers and production staff
• Product templates for repeat municipal print items
• Price matrix logic for quantities, sizes and finishing choices
• Artwork upload with preflight checks and proofing steps
• Order status tracking from submission to production handover

The portal also gave the team clearer visibility on where each order sat. That included submitted, pending approval, in proofing, in production and ready for dispatch. Staff no longer had to chase updates through multiple inboxes or ask around the office for the latest status.

Proofing that suits public work, where one wrong version costs time

Public-sector print work often moves in stages, with more than one person checking language, dates and layout before a final go-ahead. We set up proofing workflows so artwork could be reviewed in sequence instead of being passed around in unmanaged message threads. That reduced the chance of outdated files being printed.

Because the team handled notices and forms that often changed at short notice, we added clear file notes and version handling. Users could upload artwork, see whether it passed the basic checks, and then review the proof before approval. If a file needed correction, the request stayed tied to the same order record.

Courier and payment steps were mapped into the process as well. Some jobs were collected, others delivered to municipal sites, and the system needed to support both without adding manual admin for every order. Payment logic was aligned to the organisation's internal process rather than a retail checkout flow.

• Sequential proofing for internal sign-off
• File checks for artwork size, bleed and resolution
• Delivery notes for collection and courier dispatch
• Order records kept linked to the same job throughout

Seven weeks from structure to live ordering

The implementation ran over seven weeks and was split into setup, template building, approval mapping, staff training and launch support. The first stage was mapping the ordering structure for the different departments, then we moved into the product catalogue and pricing rules. Once the core items were in place, we configured the approval paths and proofing steps.

Training was handled with the staff who would use the portal most often, including people responsible for requests, proofs and admin checks. That covered how to place an order, how to review artwork, how to process approvals and how to manage status updates without leaving the system. The team also got guidance on maintaining templates so future items could be added without rebuilding the whole catalogue.

A municipal print environment has its own rhythm, and the portal had to match that. We kept the process tight enough for controls, but not so heavy that everyday users would avoid it. That balance mattered more than trying to make every action look the same.

What changed once the requests had a proper route

After launch, the biggest shift was clearer ownership. Requesters could see where their order sat, approvers had a defined step, and the production side could work from one record rather than a string of scattered messages. That made internal print requests easier to manage across departments and reduced avoidable confusion around versions and permissions.

The system also made repeat work more practical. Common items no longer needed to be rebuilt from scratch each time, and the pricing logic stayed consistent across standard options. For a municipal office handling many routine print items, that consistency is worth more than a flashy interface.

• Internal requests followed one controlled workflow
• Approvals were tied to named roles instead of loose message chains
• Artwork and proof stages stayed attached to each order
• Staff could use the same portal for routine and custom jobs

It also gave management better visibility on workload and bottlenecks. When approvals sat in one place and production status was visible, it became easier to see where delays were coming from and which department needed a nudge. That is often where the real admin saving lives.

What we would carry into a similar municipal rollout

For a similar project, we would keep the same setup: clearly defined roles, a neat product catalogue, proof checks and easy-to-read status tracking. Municipal teams do not need extra noise. They need a process that matches procurement habits, internal approvals and regular reprints without creating more admin than it removes.

We would also keep the template library focused on the jobs that get ordered often, then expand only where a real workflow needs it. That approach keeps the portal useful without turning it into a long, cluttered list of options. In this kind of environment, clarity beats volume every time.

For organisations in Pretoria and other South African cities that handle internal print requests across multiple teams, the pattern is familiar. Orders need a traceable path, files need checking, and the print room needs one reliable place to work from.