Skip to content
All workflows

Sales & purchasing04

A messy enquiry should not mean rebuilding every supplier request.

Turn schedules, drawings and emails into one requirement list, then prepare supplier packs for the relevant product groups.

Illustrative workflow · Fictional sample records, not a delivered client project or measured result.

Follow the change

From incoming information
to something usable.

Requests arrive with mixed layouts, repeated codes, pictures and vague descriptions. Staff interpret the source, retype the specification and rebuild the enquiry for each supplier. Save the interpretation once, together with its evidence.

Switch between the source and the checked result. The sample shows what the software would organise, calculate or flag.

Enquiry 032Fictional example
Compare the incoming information with the checked output
Customer wordingEnquiry 032

A description is not a full specification.

Customer wording: A description is not a full specification.
RequirementCustomer says
ProductPlanter spike light
Quantity24 pcs
Light colourWarm white

Use the customer's image and retain its source reference.

Requirement for reviewEnquiry 032

Known, proposed and missing stay distinct.

Requirement for review: Known, proposed and missing stay distinct.
FieldValueBasis
Quantity24 pcsConfirmed
Colour temp.3000 K optionProposed
IP ratingNot specifiedConfirm

Review options before sending the supplier pack.

Source retainedChecks appliedPerson reviews

Less repeated work

Extract once, then reuse checked requirements across supplier packs.

Earlier checks

Missing quantities, invented specifications and images on the wrong item.

01 / The starting point

What comes in.

  • Customer schedules, drawings and messages
  • Source product images and references
  • Known products and approved specification options

02 / The useful result

What comes out.

Editable grouped enquiry sheets with source images, quantities, units and a short clarification list. Suggested specifications stay separate from confirmed requirements.

The work behind the result

What runs, and who checks.

  1. Sales and technical teamBuild the requirement from evidence
    Software handles
    Extract item lines and source images, retain page references and distinguish repeated codes belonging to different buildings.
    People check
    Confirm project boundaries and resolve contradictory information.
  2. Technical reviewerPropose, then check missing details
    Software handles
    Suggest catalogue options while separating confirmed values, assumptions and unanswered questions.
    People check
    Approve suitable defaults or ask the customer a focused clarification question.
  3. SourcingPrepare the relevant supplier packs
    Software handles
    Group checked requirements, reuse their images and generate PDF or spreadsheet attachments.
    People check
    Select suitable suppliers and approve the message and attachments before sending.

When the straightforward path breaks

The same code refers to two different products.

Two documents may both use LT1 without describing the same fitting. Combining those lines can lose the quantity or specification for a building.

Preserve document and building identities. Ask a focused question only if the sources cannot resolve the conflict.

The review point

A person makes the call.

Confirm grouping and proposed specifications. Warm white suggests a range; the label does not prove an exact colour temperature.

How to know it helped

Measure the actual work.

Measure time to an approved supplier-ready pack, corrections after review and questions answered from evidence already supplied.

Start with a real example

Bring the work you keep doing twice.

A recent job and its documents are enough to start. We trace the repeated steps, check where mistakes enter and define a useful first build around your existing tools.

Discuss this workflow