Evaluate a gate pass system by separating permission to move an asset from evidence that it actually left, changed custody and returned. Define the approver, the physical handover and the record that closes the movement. Test a complete outward-and-return scenario before accepting an approved status as proof that an asset is back on site.
Begin with a familiar movable asset, such as a laptop sent to a workshop. Identify the asset, its present custodian, its destination and the purpose of the move. Then decide which events need separate records. The useful system boundary is the chain of responsibility, rather than the appearance of a printed pass.
What should authorisation prove, and what remains physical evidence?
A proposed gate pass should make a decision understandable: who requested the movement, what was approved and which conditions apply. Physical release needs its own observation. Return needs another. Combining these events into a single complete status makes it difficult to explain whether someone approved a plan or confirmed an actual handover.
ERPNext’s Asset Movement documentation supplies a useful software example. It records transfers, issues and receipts as separate events. The latest submitted movement updates location or custody while earlier movements remain available as history. This is an asset-record model to evaluate alongside a proposed authorisation process; it is not documentation for a barrier controller or physical access reader. ERPNext Asset Movement.
Keep the approval reference and movement reference related but distinguishable. A guard or storekeeper should be able to find the authority for a movement without treating that authority as the movement itself. Define who may confirm the physical event and what identification they must compare with the approved request.
How should location and custody be represented?
ERPNext distinguishes several movement purposes. Transfer changes location, Issue assigns custody to an employee, Receipt returns an issued asset from an employee, and Transfer and Issue combines movement with employee assignment. Choosing a purpose therefore depends on what actually changes. Asset Movement purposes.
The distinction matters for a gate-pass brief. A laptop moving between company locations may remain with the same custodian. An employee taking a device may change custody. A return from an employee should not be recorded merely by editing an address and losing the handover context.
| Event to distinguish | Question for the evaluator | Evidence proposed for the brief |
|---|---|---|
| Movement request | What asset and destination are proposed? | Asset reference, requester and purpose |
| Authorisation | Who approved which conditions? | Decision, approver and request version |
| Physical release | What actually crossed the handover point? | Asset check, releasing person and event time |
| Custody or location change | Which responsibility changed? | Submitted movement linked to the real handover |
| Return and closure | What came back, and who checked it? | Return observation, receiving person and unresolved exceptions |
This table is an original control design for discussion. A particular product may need configuration or additional records to implement it. Ask the demonstrator to identify that work rather than describing the whole table as a standard built-in feature.
What should a configured approval route preserve?
ERPNext Workflows can define multiple approval levels with transition rules and conditions. The selected document type and intended states must be designed before an approval exercise becomes meaningful. Do not assume that a workflow configured for quotations is automatically the correct route for an asset movement. ERPNext Workflows.
The documentation also warns that a custom workflow overrides the regular Save and Submit route. For a submittable document, its draft, submitted and cancelled behaviour therefore needs deliberate handling. Test the route the actual document will follow; the presence of an Approved label does not explain whether submission occurred. Workflow configuration.
Record the proposed decision states in plain language first. A request awaiting authorisation differs from an authorised request awaiting physical release. An asset awaiting return differs from one received with an unresolved condition issue. Decide how these distinctions map to the chosen application’s records before adding convenient buttons.
Original rehearsal: a laptop leaves and returns with an exception
Use a fictional laptop and workshop in a separate test environment. The exercise begins with the laptop’s recorded location and custodian. The requester proposes a workshop visit, and the responsible approver reviews the asset identity, destination and purpose.
After approval, ask another participant to perform the physical-release role. They compare the asset with the request and record what was actually handed over. The system operator then enters the applicable movement record. In ERPNext, the documented creation sequence includes the company, purpose, transaction date and time, asset details and target location or employee before submission. Creating an Asset Movement.
Pause and inspect the result. The Asset Movement guide instructs users to confirm the resulting location and status on the Asset or Asset list. Retain that inspection with the movement reference. A saved draft should not be accepted as evidence of a submitted change. Verifying Asset Movement.
Now introduce a return exception. The laptop comes back, but an accessory listed on the original request is missing. Ask the business reviewer how the physical receipt and the unresolved accessory should be recorded. Receiving the laptop should not require someone to assert that everything is complete.
The team might propose a separate discrepancy record linked to the return, with a responsible person and a next action. That is a design choice to validate, not an asserted ERPNext default. Rehearse finding both the receipt and the open exception from the original request. Only close the overall request according to the agreed business rule.
Which exceptions should be tested before adoption?
Repeat the rehearsal with an unauthorised user, a request changed after approval and an incorrect asset reference. Record what should happen in each case and compare the observation with that requirement. Also test an authorised movement that never occurs, so that cancellation does not masquerade as a physical return.
ERPNext’s Workflow Actions offers a place to track pending workflow actions. Email notification depends on the workflow’s Send Email Alert setting. Workflow Actions are not created for transitions to optional states. Include those conditions in the demonstration whenever the proposed process relies on an inbox alert or a pending-action queue. Workflow Actions.
The Asset Movement documentation says the feature changes custody and location, not asset value. Keep a condition or repair concern distinct from an accounting decision. If the organisation needs valuation, repairs or other linked processing, add it to the brief with its own owner and evidence. Asset Movement.
Finish with a traceable chain: request, decision, observed release, recorded movement, observed receipt and any unresolved exception. That makes the gate-pass requirement concrete enough to compare systems and configuration proposals. For wider operational planning, see business systems. Bring an outward-and-return example when you get started.
By Spout Team. AI-assisted drafting by Codex using the linked ERPNext documentation; independent editorial review remains pending.