MODERNISATION ASSESSMENT — DECISION RECORD
Horizon Dynamics | 5 October 2026
Companion: https://www.horizon-dynamics.tech/services/technology-modernization#assessment-output

FICTIONAL SAMPLE — NOT A COMPLETED CLIENT ASSESSMENT
Business issue: order spreadsheets do not reliably show the warehouse's latest position.
Proposed boundary: one team, customer-linked orders, exception ownership and an agreed stock view.
Retain: financial posting in accounting; reservation and shipment authority in the warehouse.
Defer: forecasting, extra sites and replacement of statutory accounting functions.

SYSTEM MAP
Existing customer records -> proposed order workspace -> existing warehouse application.
Warehouse stock/shipment updates -> proposed order workspace -> authorised sales users.
Agreed financial handoff -> existing accounting. Finance approves its fields and reconciliation.
All arrows are proposed exchanges; their access, direction and cadence require verification.

DECISION LOG
Component: accounting
Decision: KEEP
Basis: financial ownership stays in the existing system for this proposed release.
Evidence required: finance-approved fields and a reconciled sample; actual interface constraints.
Owner: client finance lead.
Could change if: supported exchange cannot meet the agreed operating requirement.

Component: warehouse application
Decision: EXTEND
Basis: preserve stock authority and expose relevant availability and shipments to the order view.
Evidence required: supported interface/export, identifiers, update timing, permissions and recovery.
Owner: assigned technical lead with the warehouse system owner.
Current sample state: UNVERIFIED. Do not promise live stock.
Fallback to assess: scheduled export with visible last-update time and warehouse confirmation.
Could change if: export delay is unacceptable or the vendor permits no suitable supported access.

Component: order spreadsheets
Decision: REPLACE IN STAGES
Basis: a customer-linked order record and exception queue for one operating team.
Evidence required: mapping, permissions, duplicate handling, open-order reconciliation and user review.
Owner: client operations lead, supported by the delivery lead.
Current sample state: PROPOSED. Existing records remain authoritative before an approved switch.

FIRST-RELEASE ACCEPTANCE — NOT YET RUN
- One source customer and its open orders remain correctly linked after repeated transfer.
- A restricted user cannot read those orders or export their details.
- A failed warehouse exchange is visible, owned and recoverable without duplicate stock effects.
- Open-order IDs, quantities and agreed totals reconcile at the same cutoff.
- Users complete the agreed order and exception scenarios.
Record actual result, evidence URL/file, owner and date for each check.

CUTOVER / RECOVERY
Delivery lead prepares rehearsal evidence. Operations accepts the business workflow.
Finance accepts relevant figures. Technical owners confirm access, deployment and recovery readiness.
Decision state: HOLD — required checks and warehouse access remain unverified in this sample.
Before switching: name who can stop cutover, define transaction capture during the transition,
reconcile new transactions before restoring an old route, and agree when its write authority ends.
Restoring an old database alone does not account for new transactions after the switch.

PROPOSAL CONTENTS
Discovery/unknowns, implementation, integrations, data preparation, rehearsals, testing,
user preparation and release. Scope hosting, licences, monitoring and paid support separately.
Record exclusions and change-approval rules before comparing supplier totals.

YOUR ASSESSMENT
Business outcome / decision owner:
Systems, versions, data owners and dependencies:
Evidence inspected (records, interfaces, tests, interviews; dates):
Keep / extend / replace / defer decision per component:
Reason and what evidence could change it:
Unknown / investigation owner / next check / deadline:
First release and exclusions:
Acceptance checks and evidence:
Cutover authority, recovery owner and handling of new transactions:
Build and operating cost assumptions:
Next decision, responsible person and date: