Skip to content

Reducing Billing-Counter Queue Time in a Neighbourhood Supermarket: An OJT Time-and-Motion and Layout Study

  • 12 slides
  • 15 viva questions
  • 5 modules
  • No code needed

@supermarket-billing-queue-time-studyUpdated Oct 2026

Stopwatch time study, basic queueing, a Pareto of delay causes and low-cost fixes with a before/after measurement plan

B.Voc, Retail Management · Sem 6 · Beginner · 6 weeks · Team of 2

More info
Level
Beginner · 6 weeks · Team of 2
Relevant for
All India
Common at
UGC
Syllabus
UGC UGC B.Voc (NSQF) · Final-year project / OJT report · Semester 6
Tech stack
  • Microsoft Excel (pivot tables, charts, Pareto)
  • Stopwatch / time-study sheet
  • POS billing reports
  • Customer feedback form (paper or Google Forms)
  • Store layout sketch
  • SOP document (Word)
For educational purposes only

Unlock this project

Full PPT + speaker notes, the step-by-step method, READMEFIRST, instructions and all 15 viva answers.

One-time. No subscription, no auto-renew, no drama.

Project packs

Credits never expire and work on any project. Use one here, save the rest for your friend who “will pay you back”.

  1. Pinned

    1 min

    Overview

    This is a final-year OJT project report for a UGC B.Voc in Retail Management. Our two-member team trained at GreenCart Family Supermarket (a fictional name), a neighbourhood store of about 5,000 sq ft with four billing counters, a fruits-and-vegetables section and a steady evening rush.

    During the first weeks of OJT we worked at the front end — bagging, helping cashiers and answering customers — and noticed that long queues, not stock-outs, were the most common complaint. Customers with two items waited behind full trolleys, loose vegetables had to be carried back to the weighing scale, UPI payments sometimes failed and had to be retried, and a few price tags did not match the POS price, forcing the cashier to call a supervisor.

    We therefore designed a small time-and-motion study. Using a stopwatch and a simple data-collection sheet we recorded arrival times, waiting times, service times, item counts, payment mode and the cause of any delay for customers at each counter during peak hours. We analysed the data and the store's POS reports in Excel, applied basic queueing ideas (arrival rate, service rate, utilisation, Little's law) and drew a Pareto chart of delay causes.

    The report recommends low-cost interventions — an express counter for five items or fewer, a pre-weighing station in the produce section, UPI QR standees at every counter and a daily price-tag check — together with a before/after measurement plan and a standard operating procedure (SOP) for the billing area.

    Syllabus alignment

    UGC · UGC B.Voc (NSQF)

    Final-year project / OJT report · Semester 6

    Subjects this project applies
    • Retail store operations and front-end (checkout) management
    • POS and inventory software (Retail trade tools)
    • Business statistics with Excel
    • Visual merchandising and store layout
    • Customer service and workplace communication
    How it is evaluated

    See your department's project guidelines.

    1 min read · 15 viva questions

  2. 2 min

    Synopsis

    Abstract

    Billing-counter queues are a major source of dissatisfaction in neighbourhood supermarkets, especially during evening peaks. This OJT study measures queue behaviour at a four-counter supermarket using a stopwatch time study and POS reports, identifies the main causes of delay with a Pareto analysis, uses basic queueing concepts to explain why queues grow sharply when counters are nearly fully utilised, and proposes low-cost changes with a before/after measurement plan and an SOP.

    Introduction

    In organised grocery retail the checkout is the last impression a customer takes home. A store can have good prices and full shelves but still lose regular customers to a nearby kirana or a quick-commerce app if the billing line is slow. Retail management courses teach front-end operations, but students rarely get to measure a real checkout. OJT provides exactly that opportunity.

    Existing situation (observed during OJT)

    • Four general counters; any customer can join any queue regardless of basket size.
    • Loose fruits and vegetables are weighed at the counter only if the section scale is busy, and sometimes items arrive unweighed.
    • One UPI QR code is taped near the cashier; customers lean over to scan it, and payment failures are retried at the counter.
    • Price labels on shelves are updated manually; mismatches with the POS price need a supervisor.
    • Staff open or close counters based on judgement, not on any measured threshold.

    Proposed study and improvements

    • Measure arrival rate, waiting time and service time per counter at peak hours.
    • Classify every delay by cause and rank causes with a Pareto chart.
    • Estimate counter utilisation and explain queue growth with M/M/c intuition and Little's law.
    • Recommend an express counter, a pre-weighing station, QR standees and a morning price-tag audit.
    • Define a before/after measurement plan and an SOP for the billing area.

    Feasibility

    • Technical: a stopwatch or phone timer, printed sheets and Excel are enough.
    • Economic: suggested changes cost little — printed standees, one extra weighing scale placement and staff scheduling.
    • Operational: the store manager agreed to a trial week, and data collection does not disturb customers because observers stand beside the counters.
  3. 1 min

    Problem statement

    At GreenCart Family Supermarket, customers regularly wait a long time at the billing counters during evening and weekend peaks. Shoppers with only a few items queue behind large baskets, loose produce that has not been weighed interrupts billing, UPI payment failures cause retries, and price-tag mismatches force the cashier to stop and call a supervisor. The store manager hears complaints but has no numbers: how many customers arrive per hour, how long they actually wait, how long each transaction takes, and which causes contribute most to delay.

    Without measurement, decisions such as opening an extra counter or moving the weighing scale are made by guesswork. The problem addressed in this OJT project is to measure queue time and service time at the billing counters during peak hours, identify and rank the causes of delay, and propose and plan the evaluation of low-cost interventions that can reduce average waiting time without hiring additional staff.

  4. 1 min

    Objectives & scope

    1. 01Profile the organisation and document the existing billing-area layout and process during OJT.
    2. 02Design a time-study data-collection sheet and record arrival, waiting and service times at each counter during peak hours.
    3. 03Analyse POS reports in Excel for bills per hour, items per bill and payment-mode mix.
    4. 04Estimate arrival rates, service rates and counter utilisation, and interpret them using basic queueing concepts and Little's law.
    5. 05Classify delay causes and rank them using a Pareto chart.
    6. 06Recommend low-cost interventions and prepare a before/after measurement plan.
    7. 07Draft an SOP for the billing area and a short customer feedback form.

    Scope

    In scope

    • One store with four billing counters; observation during agreed peak windows (weekday evenings and weekend late mornings) across the OJT period.
    • Stopwatch measurements of queue-joining time, service start, service end, item count, payment mode and delay cause for sampled customers.
    • Excel analysis of POS summary reports provided by the store manager (no customer-level personal data).
    • Queueing concepts at an introductory level: arrival rate, service rate, utilisation, Little's law and M/M/c intuition.
    • Recommendations, a trial plan, before/after table and SOP.

    Out of scope

    • Installing self-checkout kiosks or new POS software.
    • Detailed staff scheduling optimisation or simulation software.
    • Collecting names, phone numbers or any ID details of customers — the study is fully anonymous.
  5. 2 min

    Methodology

    Research design: descriptive, observational field study (time-and-motion study) with a planned before/after comparison.

    Sampling: peak windows identified from the POS "bills per hour" report (for example 6–9 pm on weekdays). In each observation session each team member watches two counters and records every customer who joins the queue during the session, giving a census of that window rather than a hand-picked sample.

    Data-collection sheet (one row per customer)

    CounterCustomer no.Time joined queueService startService endItemsPayment (cash/UPI/card)Delay codeRemarks

    Delay codes: PT price-tag mismatch, UP UPI failure/retry, LW loose item not weighed, BC barcode not scanning, CH change not available, VR void or return, OT other.

    Derived measures

    • Waiting time = service start − time joined; service time = service end − service start.
    • Arrival rate λ = customers joining per hour; service rate μ = 60 / mean service time (minutes) per counter.
    • Utilisation ρ = λ / (c·μ) for c open counters. As ρ approaches 1, queues grow sharply; this is the key M/M/c insight.
    • Little's law: average number in queue = λ × average waiting time, used as a consistency check between our counts and times.

    Illustrative example (not our data): if 90 customers arrive per hour and the average service takes 2.5 minutes (μ = 24 per hour per counter), four counters give ρ = 90 / 96 ≈ 0.94 — close to saturation, so a small increase in service time causes a large increase in waiting. Your own λ and μ replace these numbers.

    Timeline (6 weeks, team of two)

    WeekActivityOwner
    1Orientation, front-end duties, layout sketch, manager interviewboth
    2Design and pilot the time-study sheet; collect POS reportsMember A: sheet · Member B: POS
    3Baseline observation sessions (at least 6 peak sessions)both
    4Excel analysis, Pareto, utilisation; recommendations to managerMember A: time data · Member B: POS and Pareto
    5Trial of agreed interventions; after-observation sessionsboth
    6Before/after comparison, SOP, feedback summary, report and vivaboth
  6. 2 min

    Architecture & tech stack

    • Microsoft Excel (pivot tables, charts, Pareto)
    • Stopwatch / time-study sheet
    • POS billing reports
    • Customer feedback form (paper or Google Forms)
    • Store layout sketch
    • SOP document (Word)

    The study design runs from observation to recommendation and back to measurement, so that any improvement is demonstrated with data rather than claimed.

    flowchart TD
      A["OJT orientation and front-end duties"] --> B["Layout sketch and process map of billing area"]
      B --> C["Identify peak hours from POS bills-per-hour report"]
      C --> D["Pilot the time-study sheet on one counter"]
      D --> E["Baseline sessions: arrival, wait, service, delay code"]
      E --> F["Excel: waiting and service time statistics"]
      E --> G["Pareto chart of delay causes"]
      F --> H["Utilisation and Little's law check"]
      G --> I["Low-cost interventions agreed with manager"]
      H --> I
      I --> J["Trial week: express counter, pre-weighing, QR standees, tag audit"]
      J --> K["After sessions with the same sheet"]
      K --> L["Before/after comparison, SOP and report"]

    Billing-area layout (before and proposed)

    • Before: four identical counters in a row near the exit; one produce scale inside the fruits-and-vegetables section; a single taped QR code per counter.
    • Proposed: Counter 1 becomes an express counter (≤ 5 items) during peaks, marked with an overhead sign; a pre-weighing station with a staff member at the exit of the produce section; a UPI QR standee facing the customer at every counter plus a backup printed QR; a price-check point near the counters.

    Excel analysis workbook

    SheetContents
    Raw_Before / Raw_Aftertyped time-study rows
    Calcwaiting and service time formulas, flags for delay codes
    Summarypivot: mean, median, 90th percentile waiting time by counter and hour
    Paretocount of delays by code, sorted, cumulative %, combo chart
    POSbills per hour, items per bill, payment-mode share
    Comparebefore/after table below

    Before/after table (to be filled with your data)

    MeasureBeforeAfterChange
    Mean waiting time (min)………
    90th percentile waiting time (min)………
    Mean service time (min)………
    Delays per 100 customers………
    Share of UPI retries………
    Customers rating checkout "good" or better………
  7. 5 modules

    Modules

    • Organisation Profile and Process Mapping (both members)

      Both members document the store's format, size, staffing, working hours and departments, sketch the billing-area layout and map the checkout process from queue joining to bag handover, based on front-end duties during the first OJT week.

    • Time Study and Queue Measurement (Member A)

      Member A designs and pilots the data-collection sheet, trains on consistent start and stop points, leads the baseline and after sessions, and computes waiting time, service time, arrival rate, service rate and utilisation in Excel.

    • POS Report and Delay-Cause Analysis (Member B)

      Member B analyses POS summary reports for bills per hour, items per bill and payment-mode mix, codes every observed delay, builds the Pareto chart and identifies the few causes that account for most delay.

    • Interventions, SOP and Feedback (Member B lead, Member A support)

      Member B drafts the recommendations and the billing-area SOP (express counter rule, pre-weighing, QR standees, price-tag audit, counter opening threshold) while Member A designs the short anonymous feedback form and summarises responses.

    • Before/After Evaluation and Report (both members)

      Both members repeat measurements after the trial week using the same sheet and windows, fill the comparison table, discuss limitations such as day-to-day variation, and compile the final OJT report and presentation.

  8. Locked

    Presentation

    12 slides with speaker notes. The outline below is free; the bullets, notes and the generated .pptx unlock with the project.

    1. Reducing Billing-Counter Queue Time
    2. Organisation profile
    3. Our OJT role
    4. Problem and objectives
    5. Methodology
    6. Queueing basics
    7. Baseline results
    8. Pareto of delay causes
    9. Interventions
    10. Before/after comparison
    11. SOP and learning outcomes
    12. Conclusion and future scope

    Bullets, speaker notes and the .pptx download unlock with the project.

    Presentation is locked: 12 slides, Speaker notes, .pptx download.

  9. 1 min

    Future scope

    • Simple simulation of the checkout in Excel to test how many counters are needed at each hour before changing staff rosters.
    • Staff scheduling based on POS bills-per-hour forecasts, with a rule for opening an extra counter when the queue exceeds a set length.
    • Scan-and-go or self-checkout pilot for small baskets.
    • Electronic shelf labels or a daily price-sync report to remove price-tag mismatches.
    • Extending the study to the home-delivery packing area or returns desk.
  10. 7 sources

    References

    1. University Grants Commission — official website (B.Voc guidelines)
    2. Michael Levy, Barton A. Weitz & Dhruv Grewal, Retailing Management, McGraw-Hill
    3. Swapna Pradhan, Retailing Management: Text and Cases, McGraw-Hill Education (India)
    4. Hamdy A. Taha, Operations Research: An Introduction, Pearson (queueing theory chapters)
    5. Ralph M. Barnes, Motion and Time Study: Design and Measurement of Work, Wiley
    6. Microsoft Support — Create a PivotTable to analyze worksheet data
    7. Retailers Association's Skill Council of India (RASCI) — retail sector skill standards

    Cite this bundle

    OnlyProjects. (2026). Reducing Billing-Counter Queue Time in a Neighbourhood Supermarket: An OJT Time-and-Motion and Layout Study: B.Voc Retail Management project bundle [Educational resource]. https://onlyprojects.online/projects/bvoc-retail-supermarket-billing-queue-time-study

Slides, diagrams & files

12 slides. Titles are free; bullets, speaker notes and the .pptx unlock with the project.

  1. SLIDE 1

    Reducing Billing-Counter Queue Time

  2. SLIDE 2

    Organisation profile

  3. SLIDE 3

    Our OJT role

  4. SLIDE 4

    Problem and objectives

  5. SLIDE 5

    Methodology

  6. SLIDE 6

    Queueing basics

  7. SLIDE 7

    Baseline results

  8. SLIDE 8

    Pareto of delay causes

  9. SLIDE 9

    Interventions

  10. SLIDE 10

    Before/after comparison

  11. SLIDE 11

    SOP and learning outcomes

  12. SLIDE 12

    Conclusion and future scope

Architecture diagram

1
flowchart TD
  A["OJT orientation and front-end duties"] --> B["Layout sketch and process map of billing area"]
  B --> C["Identify peak hours from POS bills-per-hour report"]
  C --> D["Pilot the time-study sheet on one counter"]
  D --> E["Baseline sessions: arrival, wait, service, delay code"]
  E --> F["Excel: waiting and service time statistics"]
  E --> G["Pareto chart of delay causes"]
  F --> H["Utilisation and Little's law check"]
  G --> I["Low-cost interventions agreed with manager"]
  H --> I
  I --> J["Trial week: express counter, pre-weighing, QR standees, tag audit"]
  J --> K["After sessions with the same sheet"]
  K --> L["Before/after comparison, SOP and report"]

Files

Viva questions & answers

3 of 15 questions free. Explain each answer in your own words before you move on.

  1. Concept

    What is a time-and-motion study?

    It is a method of measuring how long each step of a task takes and observing how the work is done, so that delays and unnecessary movements can be identified. In our supermarket we timed each customer from joining the queue to receiving the bill and noted what interrupted the billing.

  2. Concept

    What is utilisation and why does it matter for queues?

    Utilisation is the fraction of time counters are busy, ρ = λ divided by c times μ. When utilisation approaches one, even small variations in arrivals or service times make queues grow very quickly, which is why the checkout feels fine at 7 pm and chaotic at 7:30 pm.

  3. Concept

    State Little's law and how you used it.

    Little's law says the average number of customers waiting equals the arrival rate multiplied by the average waiting time. We used it as a consistency check: queue lengths we counted at intervals should roughly match λ times our measured mean waiting time for the same session.

+12 more questions

They and the answers unlock with the project. Try answering the ones above yourself first. Your examiner will.

For educational purposes only. Use this bundle to understand how the project works, then build and write your own. Submitting it verbatim is between you, your conscience and your external examiner.