Map the work before changing tools
Take one recent material purchase and follow it from the job request to receipt. Note where the same detail is re-entered, where someone asks for missing specifications, and where the order or delivery status becomes unclear. Ask engineering, stores and purchasing to describe their handovers.
Separate necessary checks from duplication. Confirming an approved drawing or reviewing an unusual supplier deviation may be essential; repeatedly searching for the same job reference is a candidate for improvement.
Make requests complete and consistent
Agree a minimum set of details for a purchasing requirement: job reference, item identity, specification and revision, quantity and unit, required date, destination and any existing stock or order coverage. Decide who resolves missing information before the buyer contacts suppliers.
Use consistent catalogue records and supplier links where practical. A clear description and correct unit help prevent a buyer quoting the wrong material or comparing different quantities.
Structure quotation review
Ask suppliers to separate material cost, freight and other charges and to distinguish confirmed dates from estimates. Compare offers covering the same scope, quantities and currency. If a price or charge is unknown, flag it rather than assuming the best case.
Give the buyer a way to explain the proposed choice, and give the approver access to the evidence. Review requirements may depend on value, technical deviation or internal policy. Automation can support preparation and records without making the decision on behalf of the team.
Close the loop at receiving
An order is not complete simply because it was drafted. Make the approval and issue status visible, then record what actually arrives against the right order line and destination. For partial deliveries, retain the outstanding balance and use a distinct delivery reference for later receipts.
Periodically review unresolved requisitions, expired quotations and orders with outstanding quantities. The aim is to make exceptions visible and assign an owner, not to create another report nobody uses.
Choose a small first improvement
Start with one recurring material category or one group of jobs. Define the fields, responsibilities and review points, then check whether staff can follow the process without extra clarification. Expand only after the underlying data and handovers are reliable.
Recon connects these steps in its development workflow, from job requirements through sourcing and receipt. Supplier RFQs are preview-only and require a separate communication process.
Define a useful measure of progress
Choose a measure that reflects the problem your team actually identified. If the issue is missing job context, review a sample of requests for complete specifications and destinations. If late changes are the problem, inspect how quickly the responsible buyer learns about an approved revision. Record the starting position before deciding whether a change helped.
Measures should not reward bypassing checks. A quicker approval is not an improvement if a necessary technical review has been skipped. Ask the people doing the work whether the new process makes ownership clearer and whether exceptions are easier to resolve.
Keep the scope manageable. A small team may improve one material family by agreeing descriptions, locations, supplier contacts and an approval route. Once that process works, use the lessons to address another family, rather than imposing an incomplete data model across every job at once.
Design a simple exception routine
Set a regular point for reviewing purchases that cannot progress. A short list might include missing specifications, quotations awaiting technical review, supplier choices awaiting approval and orders with overdue or partial deliveries. Each item should have a responsible person and a clear next step.
Avoid turning every exception into an emergency. Categorise by the job's actual required date and the consequence of delay. If the date is uncertain, ask the job owner to confirm it. If a supplier date is only an estimate, say so; converting an estimate into a promise makes later decisions less reliable.
When the same problem appears repeatedly, examine its source. Frequent requests for missing units may indicate a catalogue issue. Repeated orders for the same material may indicate that job requirements and existing commitments are not being reviewed together. A late change to an approved drawing may require a clearer engineering handover.
Review the routine with engineering, stores and purchasing after a trial period. Keep the checks that prevent material or commercial errors and remove duplicated data entry where the same reliable record can serve both teams. Efficiency is an operational outcome to evaluate, not a percentage saving that can be assumed in advance.
Frequently asked questions
Should procurement automation approve purchases automatically?
Not necessarily. Teams can automate or structure preparation while retaining human review and the approval controls their business needs.
Explore how Recon connects engineering requirements with purchasing in the procurement workflow, or request a demonstration.