OĞUZ EROLAI·ADS·APPS

Production Work Orders, Revisions and Quality Tracking

14 min read

I can develop a custom web application that connects your manufacturing engineering team’s customer requirements, technical revisions, work orders and quality records. I define the scope around your production methods, existing ERP data and approval responsibilities. This page describes a proposed development service, rather than an available software product or a completed customer implementation.

Producing a part against the correct drawing requires more than storing the latest file in a folder. Your team needs to know which revision governs each order, what happens to work already started, and who approved the change. I design the application to preserve those relationships.

Example: WO-104 is waiting in assembly

In the illustrative screen, work order WO-104 covers 100 units. Cutting is complete at 100/100. Assembly has reached 60/100, with 40 units still awaiting assembly. Quality inspection has not started.

These stage counts must not be added to claim that 160 units have been produced. They describe the progress of the same 100 units through different stations.

The 60 assembled units and 40 waiting units account for the work order’s planned quantity. Nothing is described as having passed quality inspection before that inspection takes place.

Quantity and transition rules

For each station, I define what input, completed and transferred quantities mean. Scrap and rework are recorded separately rather than hidden inside accepted output.

If a unit returns for rework, it must not be counted as a new finished unit a second time. Partial transfers are possible, but their quantities and destination stage must be explicit.

For WO-104, completed assembly units can enter inspection while the remaining 40 still wait for assembly. Each movement remains tied to the appropriate part of the work order.

If two operators submit the same action, the application checks the work-order and operation identifiers to prevent duplicate movements. Transfers beyond the available quantity require review. Authorised corrections preserve their reason rather than silently erasing earlier activity.

The manufacturing engineering manager’s daily problem

Sales forwards a customer email, engineering updates the drawing and planning releases an order. If the workshop still uses an earlier printout, different teams may act on different information for the same order. Quality staff must then explain which acceptance criteria they used for their inspection.

My priority is to make these breaks in information visible. The manager can review orders blocked by changes, missing technical inputs and exceptions awaiting approval. Each decision retains its owner, recording time, reason and supporting document. The software does not make the engineering decision; it records the conditions under which that decision is applied.

Example workflow: a customer change affects an open order

The following is an illustrative scenario. A customer supplies a drawing that changes the location of a mounting hole. Sales attaches the request to the customer record. Engineering determines whether it concerns new work or a change to an open order.

EventRecord createdOwnerCondition for progress
New drawing receivedTechnical request and source fileSalesOrder and part matched
Impact reviewedEffect on open orders, work in progress and inspectionEngineeringAffected records identified
Implementation approvedRevision decision and effective pointAuthorised engineerReason and approval recorded
Work order updatedWork package linked to the new revisionPlanningBlocked operation released
Inspection completedMeasurement and acceptance recordQualityAuthorised assessment

The previous drawing remains as a superseded version. An authorised person decides whether work must stop, be reworked or finish under the previous requirement. A record awaiting a customer response remains open. Changing the filename on an order does not, by itself, demonstrate that a change has been implemented.

What does a technical customer CRM track?

For this team, CRM includes the customer’s technical contact, supplied specifications, unanswered engineering questions, sample reviews and revision agreements. Each item links to the relevant order. Different product families may have different customer approval contacts.

I define what information sales must provide when handing a request to engineering. A request missing a drawing, material definition or operating condition can be investigated, but cannot be released as ready for production. Commercial pricing and payment information can remain restricted to sales and finance. Engineering users receive the information required for their responsibilities.

The structure behind work orders and revisions

Internal part code, customer part code, product revision, process revision and customer drawing number are distinct fields. Combining all of them into a single version field makes later reconciliation difficult. We first establish which system owns each identifier and which users may change it.

A work order can retain a reference to the instruction effective when it was created. Publishing a new revision must not silently change an existing order’s instructions. That transition requires an explicit action. Cancelled orders, partially completed operations and additional work requests have separate states. A completed status can therefore be traced to the actual operations it covers.

Screens that can be developed for the team

ScreenWork it presentsImportant control
Technical request inboxRequirements received from salesMissing documents and owner
Technical customer recordContacts, specifications and agreementsCustomer and product boundaries
Revision comparisonPrevious and proposed documentsHuman confirmation of changes
Impact assessmentOpen orders and work in progressNo unauthorised bulk update
Work order boardOperations and waiting statesEffective instruction reference
Quality entry formMeasurements, methods and evidenceUnits and mandatory fields
Nonconformance queueInvestigation and corrective actionsClosure authority
Approval deskPending engineering decisionsApprover and reason
Import reviewUnmatched spreadsheet rowsDuplicate and total checks
Record and document historyWho changed what and whenPrevious values retained

The first release does not need every screen. It might cover technical requests, revision approval and affected work orders alone. I design an operator’s required inputs separately from a manager’s desk-based form. If scanners, workshop terminals or other devices are involved, their actual operating conditions require separate testing.

Multiple users, approvals and external access

RoleRecords availablePermitted actionRestricted action
Engineering managerAuthorised products and teamsAssignment, impact approval, exceptionsUsing undefined financial authority
Manufacturing engineerAssigned technical workDraft revisions and assessmentsApproving outside their authority
PlanningReleased ordersUpdating operation plansChanging technical requirements
OperatorAssigned order and instructionProgress and issue entryChanging acceptance criteria
QualityRelevant orders and measurementsInspection and nonconformance entrySubstituting engineering approval
Customer or supplierExplicitly shared documents and questionsReplies and document submissionAccessing other customers’ data

Permissions apply to records and file requests, as well as visible menus. Version controls can prevent one user’s edit from silently overwriting another’s. When an employee leaves, their open assignments can be transferred while the original activity history remains intact.

Moving from Excel and checking repeat imports

I begin with a copy of the workbook and a field map. Part codes, work order identifiers and revision formats must survive the transfer, including leading zeros and codes stored as text. Rules hidden in worksheet names can become explicit data fields.

When the file is uploaded again, a defined key distinguishes existing rows from new ones. Changed rows become proposed updates, identical rows are recognised as repeats, and unmatched rows require review. The import report reconciles source row counts, accepted quantity totals and rejected rows. Different units are not added together. The data owner confirms the authoritative source before the transfer is accepted. An import history and reversal file can be included in the agreed delivery.

How AI can assist with technical documents

AI can help locate a requirement within authorised documents, summarise a long request or draft a list of missing information. I would require the response to show its source document and relevant section. When a drawing symbol cannot be read, the system should flag it for review instead of inventing a value.

An engineer confirms proposed revision differences. Defined rules handle tolerance calculations, measurement acceptance and order quantities. AI does not autonomously release work for production, accept a nonconformance or declare materials equivalent. The scope review establishes which provider, if any, may receive confidential technical documents, along with retention and access conditions. Features requiring prohibited data sharing remain disabled.

Which events can trigger WhatsApp and SMS messages?

Checked 30 October 2026: the WhatsApp Business messaging policy requires approved templates outside the 24-hour window following the customer’s last message. Consent and opt-out rules also apply.

TriggerRecipientSending condition
Technical input missingSales ownerRequest owner confirms the missing field
Revision awaiting approvalAuthorised engineerSubmission for approval completed
Instruction changedRelevant team leadRevision published and impact list confirmed
Sample response outstandingApproved customer contactExternal communication approved
Nonconformance review overdueQuality ownerDefined follow-up condition met

A message can contain a link requiring sign-in rather than a sensitive drawing attachment. WhatsApp connections use the official business API, subject to permission and template requirements. SMS requires an authorised provider and the applicable permission, opt-out and Turkish IYS checks. Service notifications and marketing messages are treated separately.

Each event retains a notification key so reprocessing the same revision does not send the same message twice. Failed delivery remains a failure rather than being marked delivered. An opt-out stops the relevant communication type while the technical task remains visible in the application. The official WhatsApp template documentation and IYS guidance inform these controls.

Connecting ERP and existing systems

If your ERP owns the production order, I first identify the fields the application needs to read. A CSV-based scope can move to an API connection once real access is verified. Compatibility depends on the product version, licence, authentication and interface made available by its provider.

Read access and write access are separate permissions. Displaying an ERP order does not authorise closing it in the ERP. Any write operation needs explicit field ownership, retry rules, reconciliation and approval boundaries. Replacing all accounting, MRP or machine control functionality is not an assumed starting point. Automated machine control requires a separate engineering project.

Management reports and visible failures

Reports can separate pending technical decisions, revision-blocked orders, unanswered customer questions and nonconformances awaiting closure. Each count links to its underlying records. Recording time and event time remain separate so retrospective entries can be understood.

Planned completion and actual status use separate fields. Any forecast shows its method and last update. Import failures, unreadable documents and access errors enter a visible exception queue. Missing critical identifiers, revisions or acceptance criteria block the affected release and identify what needs correction. The emphasis is process delays and causes, rather than employee ranking or automatic punishment.

Defining the first scope, training and support

The initial paid scoping work reviews a current order, a revision example and your approval process. It produces written screens, fields, permissions, connections and exclusions. Outstanding technical questions receive owners rather than being treated as resolved functionality.

We review a synthetic-data workflow before planning a controlled transition into limited operational use. Engineering, planning and quality training follows each team’s part in the same example. Delivery defines documentation, issue reporting, backup ownership, a restore test and change request handling. Support responsibilities and new feature development are specified separately. Timing and fees follow the agreed requirements.

Acceptance scenarios we would test together

  1. Reimporting the same Excel file creates no duplicate work order.
  2. An unauthorised user cannot open another customer’s drawing even with its link.
  3. A new revision cannot change an open order without approval.
  4. A quality record without its measurement unit cannot appear accepted.
  5. Reprocessing an event does not produce a second external notification.
  6. An ERP outage shows the failure and the last successful import.
  7. AI produces no definitive technical answer when supporting evidence is unavailable.
  8. Restoring a backup preserves approvals and document relationships.

Acceptance covers the expected outcome and test data for each scenario, not simply whether a screen opens. Failed steps, correction ownership and retest outcomes are recorded. Permission tests include both allowed actions and actions that must be refused.

Standard software or a custom application?

Configuring your existing ERP or quality software may be the better answer if it already supports the workflow. I first look at the features you use and the connection that is actually missing. Custom development becomes relevant when your particular handover between customer requirements and open orders cannot be represented adequately in the existing product.

A short list maintained by one person may remain suitable for a spreadsheet. New screens alone cannot establish a process if nobody owns the data or the team will not enter records. This scope is unsuitable for delegating technical authority to AI or treating unverified machine data as safe. We start by naming the process that needs clearer control.

Frequently Asked Questions

Must every product follow the same route?

No. Routes can differ by product group. Skipping a stage requires an agreed permission and reason rather than an unrestricted operator choice.

Does station progress change inventory automatically?

Only where inventory movements and their approval rules are included. Stage progress and stock receipt do not have to be treated as the same event.

Does this replace MES or ERP software?

That depends on a separately agreed scope. My starting recommendation is to close the technical request, revision and approval gap around existing systems. Full planning or financial record migration requires its own assessment.

Do old orders automatically switch to the new drawing?

They should not. Affected orders are listed and their production status reviewed. An authorised, recorded decision controls the transition.

Can operators see every customer document?

No. They can access the approved instructions needed for their assigned work. Contracts and commercial information can remain under separate permissions.

Can AI extract definitive measurements from drawings?

It may propose extracted information, but I do not promise infallible reading. Ambiguous symbols or units require human review. Technical acceptance remains with authorised staff.

Can we continue using Excel?

Yes. Controlled imports and exports can be defined. Independently editing the same field in Excel and the application requires an explicit data ownership rule.

Can customers receive automated WhatsApp messages?

Defined events can trigger messages when official API, consent and template requirements are satisfied. Document sharing permissions and the customer’s correct technical contact must also be checked.

Request a scope for your engineering workflow

Describe the fields in your work order file, the revision step that causes confusion and the roles that approve it. You do not need to send a real customer drawing in your first message; an anonymised field list is enough to begin. Initial scoping is paid work, followed by a defined development scope and acceptance conditions.

The work order can connect to order preparation and delivery tracking. Completed production does not mean shipment has taken place.

Where inspection controls a transition, quality records can be included as an explicit scope. Lot or serial traceability is offered only after its records and checks have been implemented.

Send your scoping enquiry through the contact page.

Back to top ↑
WHAT YOU CAN ASK FOR

How do I work?
Work-hour packages

Tell me about your business and what you need on WhatsApp or by phone; we agree on a work block of somewhere between 5 and 40 hours and I start doing what is needed. What you get is not a calendar window — it is net working hours spent directly on your business. I can use 40 hours working three days straight, or deliberately spread it out and finish it over a year — whatever the work calls for. I do not spend my time estimating how long something will take, I spend it doing the work; every hour I spend leaves a lasting result in your business. We keep going for as long as you find it useful.

WORK BLOCKS

Why not monthly?
Is 40 hours a week?

On a fixed monthly fee both sides are watching the wrong thing: you watch a fixed cost, the other side watches how many more contracts like this they can line up. Working by the hour puts us both in front of the same thing — the real value of the work that got done. I know not having an upfront answer to "how much will this cost in total?" is the natural cost of this model. But instead of paying a fixed fee for months to a setup that is not producing results, you only pay for the qualified time spent on your work — and you see exactly where that time went, start to finish. That is why my clients keep coming back.

5hours300€ + VAT60€ per hourChoose this block
10hours500€ + VAT50€ per hourChoose this block
20hours800€ + VAT40€ per hourChoose this block
40hours1,400€ + VAT35€ per hourChoose this block