Questions to ask the client when equipping a new government office

Why gather questions in advance and what it achieves

Estimates for equipping a government office are often revised not because of prices but because of gaps in the input data. It may seem like “we need 80 workstations,” but later you find out half the staff need two monitors, some rooms lack power outlets, or the launch date is already fixed by order.

Well-prepared questions for the client catch those details before calculation. It’s important to clarify everything that affects the choice of equipment, the amount and type of peripherals, installation and delivery schedule. The sooner this is clear, the fewer surprises at the end.

Before the first draft of the estimate ask at minimum for:

• floor plans and zoning (reception, service windows, back office, meeting rooms)
• staff roles and work scenarios (documents, video calls, working with government information systems)
• infrastructure constraints (network, power, space for equipment)
• compatibility and security requirements (what can and cannot be connected)
• dates: readiness of premises, launch date, who accepts the works

Agree immediately on the response format and responsibilities. It’s better if the client appoints a single data owner, confirms answers in writing, and marks disputed items as “under clarification.”

The result should be not only an estimate but a clear package: a short specification for workstations, a list of peripherals and office equipment, and a delivery and commissioning plan.

Basic project inputs and constraints

Start with understanding the site, not with PC models. If you collect this information up front, the estimate will be closer to reality: fewer urgent reorders, fewer cable changes and fewer workstation relocations.

Ask for the exact address and a list of zones included in the project: floors, blocks, offices, security desk, archive, meeting rooms, citizen reception areas. If there’s a BTI plan or an up-to-date room layout, that’s enough for an initial placement of workstations and length estimates for cable runs.

Clarify the readiness stage of finishes and engineering. Is furniture approved or still being chosen? Are power outlets available at planned workstation points where MFPs, terminals and TV panels will be placed? If the finish is not complete, record who will provide final dimensions and outlet locations and when.

Also check site accessibility. Can the team come for a survey and measurements, on which days, and are permits or pre-approved equipment lists required? Secure facilities often have strict work windows (for example, only after 19:00 or on weekends). This directly affects delivery, installation and commissioning timelines.

To capture the inputs in a single message or questionnaire, go through a short checklist:

• address, floors and list of rooms
• availability and currency of floor plans (BTI, layout, furniture placement)
• readiness of finishes, electrical work, cooling and low-voltage cabling
• access rules: passes, escorts, working hours, noise and delivery constraints
• who approves equipment placement changes and who signs the final layout

If, for example, security allows equipment entry only through one entrance at certain hours, logistics and installation must be planned accordingly.

Questions about rooms and layout

To calculate equipment correctly, first fix which rooms are part of the office and how people move between them. Mistakes at this stage almost always lead to estimate revisions: cable lengths change, outlet counts change, workstation types change and even equipment classes change.

It’s convenient to collect these questions as a short checklist on the floor plan (even if the plan is still rough):

• which rooms are in scope: offices, front office, meeting rooms, archive, server room, print and storage rooms, waiting areas
• how many workstations are planned in each room now and what growth is expected in the next 6–12 months
• how the front office is organized: will there be a registration desk, how many service windows, are separate consultant stations needed, where are terminals or info kiosks located (if any)
• are there special environmental conditions: noise, dust, high temperature, very dry or humid conditions
• are special workstations required: for people with disabilities, 24/7 operators, security staff, or for handling confidential documents

Ask the client to mark where outlets and existing power lines are on the plan. If the layout is still changing, agree a freeze date; otherwise procurement may go in the wrong direction.

A practical example: if service windows face a glass façade, monitors may glare, and a printer in the hall may create unwanted noise. In the estimate this results in different displays, moving the MFP to a separate room and adding power and network points.

Staff roles and work scenarios

To avoid reworking the estimate, first fix who will do what and how. It’s important to understand real workloads: not just “a PC is needed,” but what tasks it must handle daily.

Start simply: ask the client to list roles and briefly describe a typical workday for each. Government offices commonly have:

• front office (citizen reception, service windows, registration)
• back office (preparing responses, processing applications, archive)
• management (meetings, approvals, reports)
• accounting and procurement (payments, records, digital signatures)
• call center or information desk (headsets, scripted work)

Next, clarify working modes. It’s important to know how many people sit at workstations simultaneously, whether there are shifts, substitutes or seasonal peaks. If some stations are shared, decide whether separate profiles, fast logins and locked phone numbers are needed.

Ask about applications without getting too technical: which services run all day, which are used rarely, where “heavy” files appear. Separately clarify whether there is video conferencing, digital signatures and crypto-tools, bulk scanning and printing, the need to run two systems at once (a common reason for a second monitor), and workstations for visitors or self-service.

Example: if a front office handles 200+ visits per day and an operator scans documents while consulting via video, this affects the choice of monitor, headset, camera and MFP. For “one-stop-shop” zones it’s often better to split roles into “reception” and “processing” so you don’t buy equally powerful kits for everyone.

Requirements for computers and displays

If requirements for PCs and monitors are clarified in advance, there’s less chance of discovering later that “these staff need a different equipment class.” In government offices workstations are usually split into typical and specialized groups.

First agree on the device type per role: desktop PC, all-in-one, laptop or thin client. “Laptops for everyone” rarely makes sense if people work only in the office. Thin clients are valid only if the server side and network are ready.

Before choosing specific models fix:

• how many workstation types and how many units of each
• whether any roles have higher loads (analytics, GIS, large spreadsheets, graphics, video)
• mandatory software (OS, office suite, specialized systems, crypto providers, drivers for digital signatures), and any localization requirements (Russian and Kazakh interfaces)
• displays: number of screens per workstation, diagonal sizes, need for height adjustment, rotation, VESA mounting or brackets
• expected lifetime of the fleet (for example, 4–5 years) and update strategy: full replacements or phased

A small guideline: the front office often does fine with an all-in-one and a single screen, while a specialist reconciling data between two systems will be more comfortable with two 24–27” monitors. If this isn’t clarified up front, it usually comes up after delivery.

If you procure equipment from a local manufacturer, check compatibility and device class requirements in advance. For example, GSE.kz offers L200 desktop PCs and M200 touch all-in-ones, which helps cover different roles in a unified style and avoids a random “zoo” of models.

Peripherals and office equipment: what to clarify before selection

Peripherals may seem small, but they’re often the reason estimates break: “we need A3,” “printing should be by card,” “there aren’t enough headsets.” To make the specification accurate, record not only device types but usage scenarios.

First clarify where the print center will be and where printing must be at the workstation. For MFPs pay attention to format (A4 or A3), color vs mono, expected volumes, duplex printing, sorting, stapling and trays for different forms. Separately ask about accounting: printing by PIN or by card, and who will be the administrator.

When it comes to scanning, consider the typical documents: passports, applications, contracts — do you need sheet-fed production scanners or are flatbed scanners enough? If barcodes are used, clarify the code types and which system they feed into.

A short set of questions that covers most risks:

• printing: device locations, formats, color, volumes, access restrictions
• scanning: document types, need for automatic feeders, quality and speed requirements
• identification: which cards, tokens, digital signatures or smart cards are used and at which stations
• communications: how many headsets and phones, wired or wireless, need for noise-cancelling microphones
• front office: whether an electronic queue, displays, terminals, kiosks or signature tablets are needed

Example: if a reception area has 6 windows and each prints receipts and scans passports, it’s often better to place 1–2 fast MFPs nearby and separate scanners at the counters rather than buying an MFP for each window.

Infrastructure: network, power, server room readiness

If you don’t collect these inputs now, small issues pop up later: not enough outlets, network not run, no space in the server room.

Start with the network and responsibilities. Is structured cabling already installed or only planned, and who is responsible for installation and acceptance (client contractor, building management, internal IT)? Clarify how many network outlets are needed per workstation — often more than one (PC, phone, printer or thin client).

Then check internet and redundancy: is there a backup channel, where are the demarcation points, and are there requirements for prioritizing critical services? If the office must open on a specific date, know when the provider will connect the main and backup channels.

For power ask plainly: are there dedicated circuits for the server room and for working areas, are circuit breakers sufficient, is grounding done? Clarify where UPSs are needed: server room only or also key points (reception, service windows).

Basic server room checks often missed:

• whether racks or cabinets exist and how many U units are free
• cooling arrangement and who monitors temperature
• access regime: keys, passes, visit log
• space and power for expansion in 6–12 months
• what must be ready before delivery (outlets, patch panels, labeling)

If the rack is full and there’s no separate power line, the launch will be delayed even if equipment is ready. Therefore, fix readiness by dates: what’s done, who is responsible and by which date it will be ready.

Security and regulations: questions without jargon

Ask about security straight away and in simple terms. Requirements often come from security, compliance or those responsible for government information systems rather than from IT.

Start with the main point: what data is processed at workstations and how sensitive is it. If personal data or internal correspondence is involved, rules for access, storage and printing usually apply.

Five quick questions to clarify the situation:

• which systems do employees access and is remote access required
• should networks be segmented: staff, guests, service devices (for example, guest Wi‑Fi)
• are there prohibitions: USB drives, installing software, printing to shared printers
• are device-level measures required: disk encryption, boot passwords, screen lock timers, logging
• who ultimately approves security requirements and signs exceptions

Next clarify account management: will there be a single domain, how are roles assigned (operator, manager, admin), who grants rights and how quickly a new employee is provisioned.

If, for example, a front-office zone has one shared printer but printing must be by card, this affects model selection, setup and deployment schedule.

How to run the client survey: a simple sequence

To avoid circular rework, run the survey as a short session with a clear outcome. It’s easier to collect all answers in one document than to spread decisions across email threads.

Ask the client to prepare at minimum before the meeting: floor plan (even a PDF), a list of departments and a building operations contact. This saves time and immediately reveals constraints on space, pathways and security.

Then follow a simple order and record decisions immediately:

• workstation table by role: number of staff, seating, shift patterns and remote work
• typical kits by role (1–2 options): PC or all-in-one, number of monitors, key requirements
• shared areas and peripherals: meeting rooms, waiting areas, printing, scanning, electronic queues
• infrastructure dependencies: outlets, network, Wi‑Fi, UPS, server room placement
• schedule: delivery dates, installation windows (night/weekend), acceptance stages and signatories

A good practice is to run through one real scenario. For example, a front-office operator prints applications and scans documents while a department head frequently holds video meetings. You’ll immediately see where MFPs, cameras and headsets are needed and where a basic kit is sufficient.

Finally, record who approves the specification, who prepares premises and when the equipment list can be frozen so delivery and installation dates aren’t shifted.

Common mistakes that force estimate rework

Rework usually happens not because of a “bad calculation” but because initial data was incomplete. As a result you buy too much or forget important items that appear during installation.

The first mistake is estimating from staffing numbers without checking shifts and simultaneous users. A department of 30 may operate two shifts and actually need 18 workstations, not 30. Or the opposite: peak visitor times require extra seats and printers.

The second trap is mixing personal and shared devices. Without rules you end up with “one printer per person,” but later learn printers should be shared by zone and only certain counters need scanners.

The third category is site limitations: restricted work hours, pass regimes, noise rules, and delivery windows. Because of this even correctly selected equipment can’t be delivered and installed on time.

Another common omission is work that wasn’t included: installation, cable management, commissioning, data migration, basic user training. These must be explicitly agreed in the estimate even if they seem obvious.

To avoid looping back to calculations, confirm in advance:

• how many people work simultaneously in each zone and shift
• which devices are personal and which are shared and under what rules
• how and when the site can be accessed (passes, hours, security requirements)
• which tasks are turnkey for the contractor and which the client provides
• acceptance criteria for when the work is considered complete

If these points are confirmed in writing, the estimate ceases to be a draft and becomes a plan that can deliver the site on time.

Short checklist before freezing the estimate

Before you “freeze” the estimate, collect answers in one document. The survey then becomes clear input data for procurement and installation without rework.

It’s convenient to keep a single summary table on 1–2 pages: room, number of workstations, staff role, schedule (shifts, remote work), special conditions (citizen reception, security). Note shared areas separately: meeting rooms, reception, archive, manager’s office.

Check yourself:

• each role has a typical kit (PC, monitor(s), OS, headset) and exceptions are described nearby
• peripherals are listed with installation location and responsible person: who approves, who stores consumables, who calls service
• dependencies on site readiness: network, outlets, UPS, server room, access and working windows
• schedule agreed by stages: delivery, installation, testing, training, launch
• work boundaries recorded: what the contractor does and what the client provides

If front-office windows need touch all-in-ones and accounting needs two monitors, this affects outlet counts, stands and installation timing. Better to clarify this before ordering than to change the specification afterward.

Example scenario: how questions turn into a clear specification

Imagine a government office: a front office with 20 operators, 5 managers, 2 IT staff and 1 archivist. The task is to ask the right questions so the estimate doesn’t change after unexpected clarifications.

Start with visitor flow and peaks. Ask how many people arrive per hour on a normal day and during busy periods, how many tokens or documents need printing, and where MFPs will be placed to avoid queues. Often it turns out printing is needed not only by operators: managers print approvals, the archive prints registers, IT prints acts and labels.

Then split kits by role, rather than making “everyone the same.” Usually 3–4 types suffice:

• operator: PC, 2 monitors, headset, access to a nearby scanner or MFP
• manager: PC, 1–2 monitors, camera or microphone for calls
• reception desk: compact PC or all-in-one, ticket printer, display
• archive: PC, document scanner, storage space

Common last-minute items: headsets compatible with specific software, scanners for IDs, electronic queue displays, extra cables and monitor mounts, spare keyboards and mice for reception.

For fast approval, present results in a table: kit type, quantity, key options and installation location.

This format is easy for the client to check and leaves almost no grey areas for rework.

Next steps after the client survey

When answers are collected, quickly turn them into a single set of input data. Otherwise some decisions will start to “drift” during the estimate stage.

Record the questionnaire as “version 1.0” and appoint client-side owners: usually one person for premises and layout, one for roles and workstation composition, and one for dates and acceptance. This reduces the risk of conflicting inputs from different departments.

Then prepare the final inventory: list of rooms, number of workstations in each and which typical kits are needed (for example, “front-office operator”, “back-office specialist”, “manager”, “meeting room”). At this stage agree a reasonable spare quantity: a small reserve is almost always cheaper than urgent post-launch purchases.

At the same time check the calendar: production and delivery times, installation and room layout, configuration and tests, commissioning and who will submit requests in the first weeks.

If you need one contractor to deliver, integrate and support the solution, decide that early. System integrators like GSE.kz (gse.kz) typically handle supply, deployment and ongoing support so specifications and schedules don’t diverge between separate vendors.