Process review sample

Anonymised sample deliverable

Business process review

Window installation: enquiry, on-site survey, pricing and contract, factory order, delivery, installation and complaints

IndustryWindow installation / Trades with field crewsScopeEnquiry intake, qualification, on-site survey, pricing and contract, factory handover, logistics, installation, closing documents and complaints.MethodBaseline capture of how work runs today, map of the order path from call to sign-off, analysis of handovers between office, surveyor, factory and installation, review of responsibility zones, staged recommendations.Service levelMatches the scope of the “On-site process immersion” service — from three days on site: watching the cycle, interviews, a review of tools and documents. The remote “Process review” delivers the same structure in shorter form: without the operation capture and role analysis, which require being on site.StatusDemonstration sample based on a delivered, anonymised platform. The client name and client data are not used.

Prepared by IT Carrot · Solution architecture and business systems development
Sample dated: August 2026

1. What the review found

Enquiries arrive mostly by phone, but the sale requires a visit: without a survey no price can be quoted. Between the survey and the contract sits a gap that the company pays for in lost deals.

The order of events accepted in this market runs: survey at the customer, measurements returned to the office, pricing by a salesperson, a callback, agreement — and if the customer agrees, a second journey, now theirs, to the office to sign. Between survey and contract lie days and at least two extra contacts, during which the decision goes soft.

The review found this is not a problem of sales speed. It is a structural break: pricing physically cannot happen where the decision is made, because the price lives in the office and the customer is at home. Everything else — transcription errors in the measurements, lost enquiries, arguments about dates — follows from that break.

FindingStatement
Primary constraintThe price is calculated somewhere other than where the decision is made. Between survey and contract stand days and two extra contacts, each of which costs part of the customers.
Recommended first stepMove pricing to the point of survey: a digital survey with required parameters and a pricing engine built on the factory’s production parameters rather than on a price list.
Expected effectSurvey, a binding price and the contract coincide in time and place. Transcription errors in the measurements disappear along with the transcription itself. Quantitative effect is assessed after rollout.

Areas reviewed

Enquiry and sales

  • Call handling
  • Qualification
  • Customer record
  • Sales targets and bonus

Survey and pricing

  • Survey scheduling
  • Product parameters
  • Price calculation
  • Contract and deposit

Production and logistics

  • Factory handover
  • Production stages
  • Delivery
  • Completeness

Installation and closure

  • Installation order
  • Crew
  • Sign-off and photos
  • Complaints

2. Baseline capture of current work

The review starts by capturing how an order travels today. For each operation we record who performs it, how often, which carrier holds the data, and whether the same data is moved again. Everything else in this document rests on this table.

OperationWho performs itFrequencyWhere the data livesRe-keyed
Answering the callSalespersonContinuouslyPhone separate from the database, a note on paperYes — contact and content are entered by hand after the call
Scheduling the surveySalesperson or dispatcherPer enquiryShared calendar or a verbal arrangementYes — territory and surveyor load are estimated from memory
On-site surveySurveyorPer sitePaper survey formYes — measurements and configuration are copied out in the office
Returning measurements to the officeSurveyorAfter every visitA photo of the form, a call, hand deliveryYes — this is the transcription itself
Price calculationSalespersonPer surveyPrice list and a spreadsheet calculatorYes — parameters are entered again
Callback and agreementSalespersonOne or several roundsPhone, correspondenceYes — quote versions are not numbered
Signing the contractSalespersonPer dealThe customer visits the officeYes — the data is entered into the contract again
Handing the order to the factorySalespersonPer contractThe factory’s form, emailYes — the specification is entered in the factory format
Chasing production statusSalespersonRegularlyA call to the factoryYes — the stage is obtained by hand
Installation planningInstallation managerPer orderA separate scheduleYes — address, units and customer are copied into the job order
Closure: sign-off and photosInstallation crewPer installationPaper sign-off, photos on a phoneYes — documents are linked to the order by hand or lost
What follows from thisIn eleven operations out of eleven the data is moved again. The fourth row — returning measurements to the office — is not one of the problems but the root of most of the others: it creates the delay, produces the transcription errors and requires two extra contacts with the customer.

3. State of the operational system

Losses occur in the stretch between survey and contract, and between contract and confirmed readiness for installation.

47/100average process maturityManual reconciliation risk high
11points of re-keyingCandidates for removal
7critical data handoversNeed an owner
2priority pilot flowsDigital survey + pricing

Process maturity

Expert assessment on a 0–100 scale. Higher means a more resilient process.

Lead qualification62
Survey handover40
Quote calculation53
Order control36
Installation planning45
Closing documents48

Structure of operational risk

Distribution of recorded observations by type.

16observations
40% — scattered data32% — losses at handover28% — unclear ownership

The numbers on this demonstration panel are illustrative. In a paid review the assessments are derived from interviews, a sample of deals, accompanying a survey visit and an agreed 0–100 scale.

4. Current process and handover points

The chain describes the typical path of an order from enquiry to closure. It is a process model, not a snapshot of any particular client system.

1

Enquiry

The customer calls or leaves a request.

2

Survey

The surveyor travels to the site.

3

Pricing

The price is derived from the product parameters.

4

Contract

Terms agreed, deposit taken.

5

Production

The order goes to the factory in its own format.

6

Delivery

Readiness confirmed, a date assigned.

7

Installation

The crew carries out the work on site.

8

Closure

Sign-off, photos and complaints attach to the order.

Risks at the handover points

HandoverWhat can be lostConsequencePriority
Call → customer recordContact, source, what was agreedThe enquiry never becomes a record; the second call starts from scratchHigh
Survey → pricingMeasurements, configuration, peculiarities of the openingA transcription error reaches productionCritical
Pricing → customerThe current version of the quoteDifferent versions are discussed and the decision is deferredHigh
Contract → factoryThe specification in production formatRe-keying and divergence from what the customer signedCritical
Specification change → factoryThe fact and content of the changeManufactured to an outdated specificationCritical
Factory → installation planningProduction stage and delivery dateInstallation is planned without confirmed completenessHigh
Installation → closureSign-off, photos, customer remarksThe order is closed without a pack, and a complaint has no basisHigh

Risk heatmap

AreaLikelihoodImpactDetectionResult
Survey parameters transcribed into pricing by handHighCriticalAt installationCritical
Specification change does not reach productionMediumCriticalAt deliveryCritical
Installation planned without confirmed readinessMediumHighOn the installation dayHigh
Photos and sign-off not linked to the orderHighMediumOn a complaintHigh
The customer is lost between survey and contractHighHighIn funnel analysisCritical

5. Why this happens

Lost deals, repeat visits and arguments about dates share the same structural causes.

A. Decision and pricing are separated in space and timeThe customer is ready to decide at the moment of the survey, while the surveyor is standing at the opening. The pricing happens in the office days later. Everything in between works against the sale.
B. Enquiry, site, survey and order have different identifiersThe enquiry, the site record, the survey form and the contract exist as separate entries. They can only be connected through a surname and the salesperson’s memory.
C. The specification is not versionedA configuration change after signing is passed on by message. The factory ends up with the version that arrived last and was noticed.
D. Production and installation use separate plansThe production stage is obtained by phone while the installation schedule is built separately. So the crew travels to the customer without any guarantee that there is anything to fit.
E. Complaints do not feed back into qualityThe cause is captured in conversation and stays with the service desk. No analysis of defects by product type and crew accumulates.
Decision principleThe main effect here comes not from speeding up the existing process but from deleting two of its steps entirely: pricing in the office and the customer’s second visit. Optimising what should disappear is the most expensive form of automation.

6. Who does what — and how much of it is moving data

A deal travels through the office, the site, the factory and installation, and at every transition the data is entered again. Below is where work is duplicated and where a role does not decide anything but moves information from one carrier to the next.

RoleWhat it does todayHow much of that is moving dataReview observation
SalespersonTaking calls, pricing from someone else’s survey, callbacks, contractPricing from another person’s form and re-entry into the contract and the factory formPricing moves to the survey; the role keeps qualification and difficult deals
Survey dispatcherAssigning a surveyor, agreeing a timeSelection from memory about territories and loadAssignment becomes a rule from territory, calendar and workload
SurveyorMeasuring, filling in the form, handing it to the officeThe form is kept on paper and copied out in the officeThe survey is captured in structured form immediately; the role gains pricing and the contract on site
Factory work preparationOrder intake, checking correctnessRe-entry of the specification into the production formatThe order arrives in the factory format with no manual entry
Installation managerCrew schedule, allocation across sitesManual transfer of address, units and customer into the job orderThe job order is generated from the delivery date; the role keeps crew selection by skill
Installation crewFitting, sign-off, collecting the balancePaper sign-off and photos with no link to the orderClosure is completed on site and attached to the order
The organisational conclusion stays with the companyThe review shows which part of the work is moving data and which part is deciding. What happens with the time freed up — redistributing tasks, retraining people or changing the structure — is the owner’s call. There is a particularity here: the surveyor role is not cut but widened — it takes on the sale, and that requires training and a revised incentive.
A price as a commitment, not an estimateThe essential condition for moving pricing to the survey is a calculator built on the factory’s production parameters rather than on a price list. Otherwise the surveyor quotes an estimate that gets corrected in the office, and the company gets the worst of both: the gap remains and trust is lost. The price quoted on site must be the same one that goes into production.

7. States, boundaries and rules

The order passes through explicit states attached to the site rather than to the customer’s surname. Each defines an owner, the required data and the condition for moving on.

StateOwnerRequired informationTransition condition
EnquirySalespersonContact, site address, source, nature of the requestRecord created from the call, survey scheduled
Survey doneSurveyorMeasurements, configuration, peculiarities of the opening, photosRequired parameters filled and validated
Price quotedSurveyor on siteSpecification, price by factory parameters, lead timeThe customer has a binding price, not an estimate
Contract signedSurveyor or salespersonContract, deposit, specification versionDocuments produced, deposit taken
In productionFactorySpecification in production formatThe factory confirmed intake and returned a stage
Ready for installationLogisticsCompleteness, delivery dateReadiness confirmed, job order generated
InstalledCrewSign-off, photos, checklist, customer remarksThe closure pack is attached to the order

Boundaries of automation

The system should determine

  • Which surveyor fits by territory, calendar and workload
  • Whether the survey parameters are complete enough to price
  • What the price is under the current production parameters
  • Whether completeness is confirmed before installation planning
  • Which specification version went to the factory

The system should not decide

  • Whether to grant a discount beyond the approved rules
  • Whether to accept an order with a non-standard opening
  • Whether a complaint counts as a warranty case
  • Whether a return visit is at the company’s cost
  • Which crew is sent to a difficult site

Rules, deadlines and escalation target

A rule without a deadline and an addressee does not work. Below is the minimum set that makes a stalled deal visible while it is still a deal.

RuleDeadlineEscalates to
An order cannot be saved without the required survey parametersAt the moment of entryBlocking rule, no escalation needed
Enquiry received, survey not scheduled1 working dayHead of sales
Survey done, the customer’s decision not recorded2 working daysSalesperson, then head of sales
Contract signed, order not handed to the factory1 working daySalesperson, then management
Specification change after factory handoverAt the moment of changeFactory work preparation and sales, confirmation mandatory
Installation scheduled without confirmed completenessAt the moment of planningBlocking rule, escalation to the installation manager
Installation done, closure pack missing2 working daysInstallation manager, then management
Complaint registered without a cause and typeAt registrationService desk

8. What to do and in what order

The sequence is built so that each stage delivers value on its own and does not require the next one to be finished.

No.RecommendationWhy nowAcceptance criterion
1Digital survey with required parametersRemoves the re-entry of measurements and configuration — the root of most errorsMeasurements are entered once and reach pricing without being rewritten
2Pricing on production parametersMakes it possible to quote a binding price at the survey itselfThe price quoted on site matches the one that goes to the factory
3Contract and deposit on siteDeletes the customer’s second visit and the waiting daysThe deal closes in the same visit and documents are produced on site
4A site and order recordConnects enquiry, survey, contract, production and paymentThe order is traceable under one identifier from call to sign-off
5Two-way exchange with the factoryRemoves re-keying and calls chasing production statusThe order goes across with no manual entry and stages come back into the system
6Installation order from the delivery datePrevents installation being planned without confirmed completenessThe job order is generated automatically and the crew receives the data electronically
LaterComplaint analysis by type and crewUseful once closure is documented in fullComplaint causes accumulate in structured form
Do not start with a CRM in generalA general-purpose CRM laid over the existing process records the gap between survey and contract as a handsome funnel. The place to start is where the gap physically arises — at the tablet in the customer’s home.

Rollout plan

These durations are indicative for a demonstration sample. A real estimate is formed after access to the survey forms, the factory’s pricing and production model, the exchange formats and the integration constraints.

StageDurationOutcomeCheckpoint
Capture and order model2–4 weeksStates, roles, required survey parameters, pricing rulesSales, survey and production approve the model
Digital survey and pricing4–6 weeksMobile parameter entry, a calculator on factory parametersThe surveyor quotes a binding price on site
Contract and deposit on site3–4 weeksDocuments, signature, deposit, printing on siteThe deal closes in one visit
Factory integration3–5 weeksOrder handover and production stage feedbackRe-keying of the specification disappears
Installation and closure2–4 weeksJob order, crew, checklist, sign-off and photos on siteOrders close with a full pack and no paper catch-up

9. Metrics, reporting horizon and next step

This sample claims no numeric effect. In a real review the baseline is recorded first, then the metrics are compared after an agreed period of use.

MetricHow it is calculatedHow to capture the baselineDirection
Share of orders closed during the survey visitContracts signed on site / surveys carried out × 100A sample of deals over a quarter by survey and contract datesUp
Time from survey to signed contractMean in days across closed dealsComparing dates on survey forms and contractsDown
Errors after the survey handoverOrders with a measurement discrepancy / all orders × 100Analysis of complaints and rework over a quarterDown
Number of quote versions before contractMean number of re-pricings per dealA count from correspondence and calls over two weeksDown
Variance in the installation dateActual date − scheduled date, in daysA sample of orders over a quarterDown
Return visitsReturn visits / installations carried out × 100The visit log over a quarterDown
Share of orders with a complete closure packOrders with sign-off, photos and checklist / all orders × 100A sample of closed orders over a monthUp

Horizon: from the call to the annual report

A review does not end at a signed sheet. Deal data has to reach management and annual reporting without being entered again — otherwise the performance of channels, crews and product types remains a matter of opinion.

LevelWhat must arrive without manual assembly
DayScheduled and completed surveys, signed contracts, crew visits
WeekOrders in production by stage, planned installations, open complaints
MonthConversion by channel and surveyor, target attainment, bonus, payments
QuarterProfitability by product type, defects by crew and supplier
YearManagement reporting across sales, production and installation on one data model
If a marketing channel is judged by the number of calls rather than by signed contracts, the cause is usually that the enquiry and the order are not connected by a shared identifier.

Questions to settle before development

  1. Which survey parameters are mandatory in order to price without the office?
  2. Who approves the production pricing model, and how often is it updated?
  3. What discount authority passes to the surveyor, and within what limits?
  4. In what format does the factory accept orders and return production stages?
  5. What counts as confirmed completeness before installation planning?
  6. Which operations must work on site with no connectivity?
Recommended next decisionCapture twenty deals from call to sign-off, recording the date of every step and the number of customer contacts. Separately, ride along with a surveyor to two sites. Output: required survey parameters, pricing rules, a data model and a pilot scope for one survey team.

This document demonstrates the structure and level of detail of the deliverable of the “Process review” service. It is based on the mechanics of a delivered, anonymised platform for a window business, is not legal, tax, construction-engineering or industry advice, and contains no confidential client information. Maturity scores are illustrative. Whether an order can be handed to production without re-keying depends on whether the specific factory offers a suitable exchange format.