Digital material acceptance act: the receipt-inspection-quarantine process

What usually goes wrong during material receipt

The main mistake is assuming the supplier’s inspection replaces on-site incoming control. During transport the load can be partially swapped, damaged, or mixed. Documents often arrive after the goods. If there isn’t a simple rule on site like “accepted only after inspection,” whatever was unloaded first goes into use.

Another problem is that acceptance becomes a formality: a paper is signed, a couple of phone photos are taken, and everyone disperses. When defects or mismatches appear a week later, it’s unclear what exactly arrived, where it was stored, who saw the defect, and which delivery the photos belong to.

Traceability most often breaks on everyday details. For example, the act may lack a link to the batch and waybill, the unloading location might be missing. Photos stay in messaging apps without date, delivery number or a clear author. Quality documents (passport, certificate, protocol) are stored “somewhere in procurement” separate from the acceptance record. Some goods are accepted “by word” because they’re “urgently needed,” and quarantine is skipped. Different people apply statuses differently because there’s no single rule.

A separate risk is substitution and batch mismatch. On paper there might be one brand, size or manufacturer, while something else arrived. If this is discovered after installation or commissioning, losses multiply.

Paper acts and chat photos don’t give a reliable link between “delivery - batch - evidence - decision.” A digital acceptance act is valuable because it records everything in one place: what was delivered, what was inspected, how it was confirmed and who decided.

The correct outcome of the process is always the same: for each batch there must be an unambiguous decision — usable or not. The decision must have a reason and attached evidence. Until a decision is made, the material is considered quarantined and must not enter production.

Roles and responsibilities in the acceptance chain

For a digital material acceptance act to work, each step must have a clear owner. Not “we all checked together,” but who creates the record, who confirms facts, who makes the decision and who is responsible for the evidence.

The initiator of acceptance is the person who first physically meets the delivery and can quickly record its arrival. On site this is usually a warehouse worker or a logistician. Sometimes a foreman initiates acceptance if the material goes straight to the work area and it’s important to stop unloading immediately in case of discrepancies. Procurement usually doesn’t take part in the inspection but must see the status to raise a claim to the supplier in time.

It’s convenient to split inspection into “quantity” and “quality.” Quantity (places, mass, labeling, packaging, completeness) is confirmed by the warehouse. Quality is confirmed by Q/C or the person responsible for quality. If measurements or tests are required, a laboratory is involved. If the material is critical for safety, add an engineer, technical supervision or the client’s representative into the check.

The “approved for use” decision should be made by one person by role, not “whoever was nearby.” Usually this is the quality manager or the site supervisor (depending on material type and authority matrix). It’s important that the approver sees not only the act itself but also inspection results, comments and attached documents.

Allocate responsibilities like this:

• Initiator (warehouse worker/logistician/foreman): creates the act, records arrival and initial photos.
• Warehouse: confirms quantity, batch identification and storage location.
• Q/C/quality (and laboratory if needed): records control results and nonconformities.
• Technical supervision/engineer: provides conclusions for critical items.
• Evidence archive owner: ensures photos, reports and records are complete and immutable.

You need a formal substitution scheme. For example: if the quality responsible is unavailable, an appointed deputy can temporarily make the decision by order; the system requires a reason for substitution; the temporary approval has a limited duration; all decisions are logged so the primary responsible can confirm them later.

Process flow and material statuses

A good incoming control flow is one continuous stream: receipt - inspection - quarantine - approval for use. The rule is simple: material cannot be issued to production until a decision is recorded and quarantine lifted.

Create the digital acceptance act as early as possible so all events link to a single document. In practice this is one of three moments: before unloading (if waybills and expected items are known), during unloading (record arrival and initial inspection), or after counting (when exact quantities matter). A hybrid often works: a draft at arrival, finalized after counting.

Control points should be visible directly in the record: time, who confirmed (name/role/signature), current status and the physical storage location (zone, rack, bin). If the storage place changes, update the record. Otherwise quarantine becomes unmanageable.

Statuses should be the same for a batch and for the logistic unit (pallet, box, piece). Minimal set:

• Received (arrived, counting/inspection not finished)
• Under inspection (incoming control, sample selection, protocol requests ongoing)
• Quarantine (physically isolated and blocked in records; issuance prohibited)
• Approved (usable, with reason and approver)
• Rejected (including options: return to supplier or disposal)

Handle partial deliveries separately. One waybill can have multiple acts or a single act with several batches, but statuses must be set for each batch. If partial defects are found, don’t apply one status to the whole delivery. For example, out of 10 pallets, 2 may go to quarantine and then to “Rejected,” while 8 after inspection get “Approved” and proceed to work.

Unit of record and identification: batch, pallet, unit

A key decision in incoming control is what exactly you accept and what then moves through statuses. Practically there are three levels: batch, pallet (logistic unit) and piece/unit of measure (bag, roll, box, item, meter). If you choose too large an object (only the waybill), you lose control in partial deliveries. If too small (each item), the process becomes heavy.

A practical scheme: legally rely on the waybill, manage quality by batches. Pallets help physically separate and find items quickly, and the unit of measure is needed when a batch is opened and consumed in parts.

To prevent the digital act from becoming “paper for the sake of paper,” define data links in advance: order (or request) - delivery - batch - storage location - work object (site, room, stage). Then you can always answer: which materials with which status went to which work.

Labeling must be clear for people and the system. Usually enough are:

• unique internal batch number,
• QR or barcode on a tag,
• pallet or container number,
• a clear quarantine tag (color, text, date),
• status indication: “received,” “under inspection,” “quarantine,” “approved,” “rejected.”

Keep reference lists short: suppliers, nomenclature, sites (warehouses/zones), control norms (what to check and how to confirm). Also enforce immutability rules: after signing the act key fields cannot be edited (supplier, nomenclature, batch, quantity, unit, dates, results, signatures). If there’s an error, create a corrective document rather than editing retrospectively.

Data set for the digital acceptance act

For the digital acceptance act to be legally and operationally meaningful, it must clearly answer three questions: what was delivered, in what condition, and what decision was made.

Minimum required fields (must-have)

Below are data fields that usually cover accounting, quality control and subsequent investigations.

• Act header: unique number, date and time, site, acceptance zone (gate, warehouse, area), receiving organization.
• Delivery data: supplier, carrier, waybill number, order/contract number, vehicle number and driver name (if needed), supplier contact person.
• Material description: name, internal code/sku, specification (GOST/TU/CTO or specification number), unit of measure, quantity per documents and actual quantity, discrepancy (plus/minus) and reason.
• Batch identification: batch/heat/lot number, production date, shelf life or storage period (if applicable), number of places (pallets, boxes), serial numbers (if any).
• Conditions and external inspection: packaging integrity, seal numbers, signs of wetting/impacts, critical conditions (temperature, humidity) and how they were recorded.

Fields that make the act practical

Without these, the process usually stalls at inspection and quarantine steps.

• Status and route: “under inspection”, “quarantine”, “approved for use”, “rejected”.
• Basis for the decision: reference to protocol/certificate/internal rule, short comment.
• Signatures and roles: who accepted quantity, who checked quality, who approved the decision (name, position, shift).
• Attachments (as links to records): photo IDs, scanned document IDs, test protocol numbers (avoid duplicating files in text).

Example: 20 bags of mix per waybill, actually 19 arrived, two bags have torn corners. The act records the discrepancy and packaging defect, notes the batch number and sets status to “quarantine” until the quality engineer’s conclusion.

Photo rules and storage of protocols

Photos and documents for incoming control must answer a simple question: half a year later, without disputes, can you prove what was accepted, in what condition, and on what basis it was approved (or rejected)?

Photo capture: what to shoot and how

A minimal set of photos should be mandated by the regulation and made mandatory in the digital act. Usually five types are sufficient:

• overall view of the delivery: vehicle/pallet/unloading area to show volume and context;
• labeling and tags: batch number, sku, date, manufacturer, legible without guessing;
• packaging and seals: corners, straps, seals, signs of opening;
• defects and nonconformities: chips, dents, moisture traces, mixed items;
• storage conditions on site: where it was placed, presence of cover, pallets, protection from water and dirt.

Photo quality matters more than quantity. Labels must be readable, without filters or heavy editing. For disputable defects include a scale: ruler, marked sticker, or an object of fixed size. When photographing serial numbers, take two shots: one for context and a close-up.

Naming, metadata and immutability

To avoid losing files, use a unified name and folder template. A practical format: YYYYMMDD_Site_ActNo_Batch_Type (for example, 20260203_Atyrau_000231_B124_Label).

In the act card save metadata: author, time, role (warehouse/QC), comment. Where allowed by security policy, add geotag and device model. Metadata should appear in the log but cannot be edited retrospectively without a trace.

Store test protocols and certificates in their original form (PDF from the supplier) plus a scan/photo if the document arrived on paper. Each file must be linked to the act and batch number so a document from another delivery cannot be substituted.

Storage rules should be explicit:

• originals are never overwritten: only a new version with a reason;
• deletion is forbidden or requires justification and is logged;
• an action log records who uploaded, viewed or changed status;
• access by roles: viewing allowed to participants, editing only to responsible persons;
• retention period is defined by project policy (often at least the warranty and claims period).

Quarantine: physical and record isolation

Quarantine means a simple thing: the material is on site and recorded in stock, but cannot be used until a decision on quality and completeness is made. It protects against accidental use of materials without confirmation.

Physical isolation should be obvious even to someone new to the warehouse. Usually a separate zone or dedicated rack with a clear “QUARANTINE” tag is used. Where appropriate, add a seal on the storage place. At the same time, implement a direct prohibition on issuance: without status “Approved for use” no unit leaves for production or the site.

In records, quarantine is a separate status and preferably a separate virtual stock location. Good practice: the system disallows creating an outbound document if the batch has status “Quarantine.” Issuance is possible only after an authorized decision (Q/C/quality/client).

Allowed operations in quarantine are limited and predefined. For example: movement only within the quarantine zone; sample selection and protocol creation; additional inspection and recount; photographing labeling, damage and packaging; relabeling internal tags (without altering manufacturer data).

Deadlines are as important as statuses. Set target inspection times (e.g., 24–72 hours) and escalation rules: day 1 overdue — notify the responsible; day 2 — notify warehouse and quality managers. After that, stricter measures may follow depending on business needs.

Handle nonconformities with one scenario: record a discrepancy act (what exactly didn’t match), attach photos and protocols, then choose an outcome — supplier claim, return, sorting with partial admission, or disposal. Example: 10 boxes of cable arrived, 2 boxes with damaged insulation. In records the whole batch remains in quarantine, but the decision may approve 8 boxes and send 2 back, with separate statuses and documents for each portion.

Approval for use: criteria and recording the decision

Approval for use is the formal moment when material changes status from “quarantine/under inspection” to “approved” and can be issued to production or site. The decision must be based on clear grounds, not a verbal agreement.

What the decision should be based on

Grounds typically come from three sources: test results (lab protocols, measurements), visual inspection outcomes (damage, labeling, packaging), and document verification (passport, certificates, declarations, waybill). If any block is incomplete, the material stays in quarantine. “Conditionally allowed” is possible only by predefined rules and with restrictions.

Tie acceptance criteria to the specification and tolerances in advance: conformity to brand and size, allowable deviations, completeness, quantity, shelf life, condition on delivery. For sensitive materials add transport and storage conditions: “bags without signs of wetting,” “seals intact,” “temperature regime observed.”

How to approve and what to record

Approval is convenient via an approval route with levels and deadlines. For example, the warehouse confirms quantity and integrity, the quality engineer confirms tests and protocols, the site manager gives final approval within 24 hours of receipt.

Record at minimum in the digital act:

• decision status (approved, rejected, conditionally approved with restrictions);
• decision number and date, approver name and role;
• criteria used (reference to specification items or checklist points);
• comment: exactly what was checked and what was unsatisfactory (if any);
• evidence: photos, protocols, document verification notes.

To preserve traceability, the decision must be linked to the batch/pallet and then follow through issuance to production and to the specific work object. Example: rebar arrived, documents match the grade, but some bars have corrosion. The decision can be “conditionally approved”: allow 80% of the batch, keep 20% in quarantine, specify storage zone and requirement for additional cleaning or supplier replacement.

How to design and implement the process step by step

Start not with the act form but with what you actually control. Different material groups require different logic: for concrete passports and timing matter, for cable labeling and meters do, for fasteners batch and certificates do. If you don’t separate nomenclature by check rules, the digital process quickly becomes “one button for everything.”

Then map the process into a short chain with statuses and roles. Each status must have an owner and a clear next step; otherwise materials will stall in “inspection” for weeks.

Practical sequence:

• Define nomenclature groups and minimal checks for each (documents, visual check, measurements, lab).
• Configure statuses and approval routes by roles: warehouse records delivery, Q/C inspects, engineer/manager decides.
• Determine required fields of the digital acceptance act and templates for typical deliveries (e.g., “serial product,” “bulk,” “cable”).
• Introduce photo rules: where photos are mandatory, how many shots, angles, and what constitutes an unacceptable photo (blurry, no tag, unreadable batch number).
• Organize quarantine physically and in records: separate zone, clear tagging, QR/tags linking to the batch and act.

To get the process working, run a pilot at one site and for a narrow set of materials. Start with items that most often cause disputes: cable, rebar, consumables.

For the pilot set success criteria and feedback channels:

• how many acceptances are completed without “requesting missing documents”;
• share of materials properly placed in quarantine;
• average time from acceptance to decision “approved/rejected”;
• how many acts are returned for correction due to missing photos or mandatory fields.

After 1–2 weeks of the pilot, record changes to rules and templates and only then expand the process to other material groups and sites.

Common mistakes and pitfalls

The most common problem is creating the act retrospectively. At unloading there’s no time, photos remain on phones, and later people try to “match” them to a batch. The dispute then becomes a battle of memory.

Second pitfall — weak identification. When a pallet contains different batches or opened packaging lacks new labels, you cannot prove what was inspected and what was issued.

Third — “quarantine only in the system.” The status is set but the pallet stands next to good material and the warehouse worker hands it over out of habit. Quarantine works only with both record and physical isolation: separate zone, bright tag, and issuance block.

Fourth — decision without grounds. Status “Approved” or “Rejected” must not exist by itself. There must be a reason, reference to a protocol/certificate, a comment and who made the decision.

Fifth — documents scattered across chats, email and folders. Without a single repository and change log versions get lost and it’s unclear who edited what.

Simple rules prevent these errors:

• Create the act immediately at acceptance and attach photos only from the batch card.
• Forbid mixing batches without repackaging and new labeling.
• Make quarantine “double”: a physical zone + issuance block in records.
• Require a reason and attached protocol before changing status.
• Don’t overload the act with fields: keep only what actually affects the decision.

Example: if cable arrives and some reels go to quarantine due to damaged packaging, without clear photo links and batch numbers those reels can easily “disappear” among good ones within a day.

Short checklist before releasing material to work

Before issuing from quarantine do a quick fact-based check, not a visual guess. This checklist ensures the digital acceptance act is complete, materials are identifiable, and the admission decision can be proven later or at an audit.

Check five points:

• Identification: the act and batch have unique numbers that match the tag or QR on the pallet/packaging. If material is broken into parts, labeling is transferred to each unit.
• Quantity and discrepancies: the actual count matches documents. If shortages, mix-ups, damage or surplus exist, they are documented with reasons and responsible persons.
• Photo evidence: at least three types of photos exist — overall view, close-up of label/tag, close-up of defect (if any). Photos of documents are clear with number, date, stamp/signature readable.
• Status and blocks: the record status must not allow issuance to production until “Approved for use.” If the system still permits issuance, that’s a risk: set a block or require mandatory confirmation.
• Documents and decision: certificates, passports, test protocols are attached and open correctly. The admission decision is signed by the responsible party, with date/time and author (name/role).

Practical rule: if any item fails, return the material to quarantine immediately, create a task to correct data and re-check. This prevents releasing a batch without a clear history.

Next steps: pilot, archive and sustaining the process

Start with a pilot on a limited set of items. Choose critical materials: those that affect safety, quality or have high substitution risk (cables, fasteners, chemicals, expensive equipment). For these impose stricter checks and mandatory photos; for common consumables use a simplified scenario.

To prevent quarantine from accumulating, agree on inspection deadlines and responsible persons in advance. A working rule: every status has an owner and a maximum time. After expiry the system requests a comment and reason for the delay.

• “Received” — warehouse records arrival and labels units.
• “Under inspection” — Q/C inspects and checks documents.
• “Quarantine” — warehouse ensures isolation and blocks issuance.
• “Approved/Rejected” — authorized person signs the decision.

Define a single archive for photos and protocols right away: where it’s stored, who grants access, backup policy and retention period. Appoint an administrator and a simple naming rule: object (batch/pallet), date, supplier, status.

On-site equipment typically needed: tablets or rugged smartphones for acceptance, a workstation for document checks, a label printer for tagging, sometimes a barcode scanner. Example: a cable delivery of 12 reels — each is labeled, photos are linked to a specific reel, and the test protocol is attached to the batch.

If ERP/WMS integration and secure infrastructure (access rights, logs, fault tolerance) are needed, plan that as a separate implementation project. In such cases it’s useful to involve a system integrator, for example GSE.kz: you can pre-plan architecture, site workstations and 24/7 support where it’s truly critical.