CDBAMImplementation Projects
Method

A path someone else can retrace

A well-run project is not the one that finishes fast: it is the one that, six months later, can still explain why every figure is where it is.

Principles

Four rules we do not negotiate

They are not slogans: they are written into the code and the technical specification of the tool, and they are what we negotiate scope against.

01

We never alter the client’s data

The tool reads, transforms into the target format and writes files. What sits in the source database is historical record, to be located — never corrected on our own initiative. When something is wrong at source, we flag it and pinpoint it; correcting it is the client’s decision.

02

Nothing is produced without validation material

Every output comes with its matching reconciliation, and the two are kept apart: what goes into production on one side, the proof that it checks out on the other. Validation pushed to the end of the project is validation that never happens.

03

Data used is data discarded

Data handled during the project is discarded as soon as it has served the purpose it was used for, and at no point does it travel through the cloud or the internet. We do not keep client databases as an archive, not even after delivery.

04

Silence is a defect

A routine that fails quietly is worse than one that fails loudly. The tool is built to complain early, with the reason written down — and never to pretend it worked when only half an answer came back.

The cycle

How a project actually moves

Within migration and configuration, the generate-and-check pair repeats as many times as needed. A phase is only closed when its evidence reconciles.

Discovery

Processes as they are actually run, volumes, integrations and the exceptions nobody documented.

Migration

Employee records, history and payroll history, with traceable mapping and reconciliation on every round.

Configuration

Pay elements, structure, benefit policies, approval limits and integrations set up with the company’s actual rules.

Validation

Parallel payroll run, record checks and a test script per module, with the evidence filed.

Go-live

Cutover with a plan, contingency decided beforehand and the internal team trained.

Hypercare

Reinforced support through the first cycles, fixing at the root and transferring knowledge.

Security and privacy

Project data has an expiry date

Payroll is sensitive personal data, and the safest way to protect information is not to keep it alive longer than necessary. That principle organises how we handle data.

  • Never through the cloud or the internet. The data used in the work is not sent to external services at any stage of the project.
  • Discarded after use. Once the purpose is served, the data is deleted. It is not kept “just in case” and never becomes an archive for future projects.
  • Credentials are never stored. Access passwords are valid for the working session and must be entered again afterwards.
  • Named access with defined roles. Only authorised people get in, and administrators are separated from those who merely operate.
  • A record of what was done. The project’s relevant actions are logged — which allows the work to be audited without preserving the data.
DATA LIFECYCLE 1 · Used in the project only for as long as the purpose lasts 2 · Purpose fulfilled delivered and validated 3 · Disposal nothing is kept as an archive At no stage does it travel through the cloud or the internet
Deliverables

What the client keeps at the end

Discovery document

The consolidated picture of the landscape: processes, volumes, integrations and the risk points that shaped the plan.

Configuration documentation

The record of what was configured and why — the decision together with the reason, for whoever maintains it later.

Validation evidence

The test scripts with expected results and the outcome of the reconciliations, including the parallel payroll run.

Data dictionary

The field-by-field trace of the migration: where every piece of information that reached the new system came from.

Rather see it before you commit?

Book a technical conversation. We bring the tool, you bring your scenario.