ILLUSTRATIVE ENGAGEMENT / NO CLIENT DATA

See what working
together can look like.

A fictional, bounded example of how DNAction can define and deliver a project. It demonstrates the working approach; it is not a client case study or a commercial offer.

  1. Scope the work
  2. Review decisions
  3. Confirm acceptance
  4. Document handoff

EXAMPLE / ITEM DATA READINESS

One source file.
Decisions you can follow.

Download sample packet ↓
Fictional scenario

A distributor is preparing an item export for an ERP partner. In this example, the review covers one CSV file, up to 500 records, and three fields: item number, description, and unit of measure. No production system is changed.

01 / SCOPE

Know what is included.

One supplied file, a source snapshot, field review, rule proposals, a reviewed output file, an exception register, and a handoff summary.

Target-system configuration, live migration, stock valuation, and unreviewed automatic record merges are outside this example.

02 / REVIEW

Make the decisions visible.

Confirm the business meaning of each field, agree naming and unit rules, and review uncertain matches with the customer’s data owner.

Checkpoint: customer approval of proposed rules before output preparation.

03 / ACCEPTANCE

Check against the agreement.

Reconcile all 500 source records to output or the exception register. Every changed value has a source identifier, agreed rule, and approval reference.

Unresolved decisions remain visible. Approval does not mean the ERP partner has accepted the import.

04 / HANDOFF

Leave a usable record.

Deliver the reviewed output, unchanged source snapshot, change log, exception register, and rule definitions.

Document ownership, open items, intended next step, and any separately agreed support.

SAMPLE DECISION LOG

Record the reason.
Keep the evidence.

Fictional review examples
RecordQuestionDecision / statusOwner
ITEM-014“EA” versus “Each”Standardize to EA after the unit rule is approved.Customer data owner
ITEM-027Same description, different item numbersOpen. Keep separate until identity is confirmed.Customer product owner
ITEM-041BOX with no pack sizeOpen. Request a documented conversion.Customer purchasing owner

THE CUSTOMER’S ROLE

Good delivery is
a shared process.

You provide an authorized, suitably redacted source file and identify the people who can answer business questions. You approve rules and decisions; DNAction records and applies the agreed work.

What your own proposal will define

Specific files, volumes, workflows, and exclusions

Deliverables, review points, and acceptance checks

Responsibilities, access, and data-handling arrangements

Price, schedule, change handling, and support terms

This sample has no fixed price or delivery commitment.

Discuss a scope for your business ↗

LET’S MAKE WORK FLOW

One problem.
A better way forward.

Tell us what’s getting in the way ↗