01
Application estate
Legacy estate
COBOL programs, copybooks, JCL, CICS screens, DB2 or VSAM data, scheduler metadata
Decision support
Show what the system does and where the critical rules live
Executive brief
Enterprise deployment
private deployment, access control, integration planning, governance, and support for regulated teams
Scope
Bounded estate
Systems, owners, artifacts, and controls in scope
Method
Source plus SME
Code evidence paired with expert context
Evidence
Source backed
Findings tied to code, jobs, data, and reviews
Output
Retention package
Documentation written for handoff and review
Scope
Start with the assets that carry business behavior.
A useful assessment shows where the legacy behavior sits, which teams depend on it, and what proof is needed before change.
02
Operating workflow
Legacy estate
Batch windows, online transactions, files, reports, controls, exception paths, and handoffs
Decision support
Protect service levels, release windows, and audit expectations
03
Retention path
Legacy estate
Known experts, operating routines, testing gaps, owner decisions, and open questions
Decision support
Choose what to document, validate, hand off, and review first
Assessment path
A short sequence from unclear estate to usable evidence.
The work is scoped enough to move quickly, but specific enough for engineering, audit, and business owners.
Assessment path · 01 / 04
Define the estate
Business impact
Agree on systems, repositories, jobs, files, owners, and the decision the assessment must support.
Assessment outputs
A readable list of programs, jobs, copybooks, interfaces, data stores, owners, and unresolved gaps.
Assessment path · 02 / 04
Analyze the source
Business impact
Build dependency, lineage, control-flow, and business-rule views from source artifacts.
Assessment outputs
Source-backed paths that show how data, rules, jobs, transactions, reports, and downstream systems connect.
Assessment path · 03 / 04
Review with experts
Business impact
Validate findings with application, operations, data, and audit stakeholders.
Assessment outputs
Plain-language findings on fragile logic, weak evidence, missing ownership, batch constraints, and audit exposure.
Assessment path · 04 / 04
Publish the package
Business impact
Deliver maps, rule catalogs, runbooks, interview notes, risks, open questions, and a practical next-step plan.
Assessment outputs
A summary of artifacts, reviewers, dependencies, open questions, and the next work plan for controlled rollout.
Assessment outputs
Concrete artifacts, not loose advice.
Each output is written so a buyer can use it in a planning meeting, audit review, or knowledge handoff.
Inventory and ownership map
A readable list of programs, jobs, copybooks, interfaces, data stores, owners, and unresolved gaps.
Dependency and lineage views
Source-backed paths that show how data, rules, jobs, transactions, reports, and downstream systems connect.
Risk and control notes
Plain-language findings on fragile logic, weak evidence, missing ownership, batch constraints, and audit exposure.
Retention package
A summary of artifacts, reviewers, dependencies, open questions, and the next work plan for controlled rollout.
Risk priorities
The issues that usually block safe legacy work.
COBOL knowledge risk is often an evidence problem before it is a code problem.
01
Hidden business rules
Business impact
Critical calculations or exceptions sit inside paragraphs, copybooks, tables, or old run procedures.
Control focus
Create a source-cited rule catalog and review it with system owners.
02
Unclear dependencies
Business impact
One change can affect jobs, reports, files, interfaces, and downstream teams that were not in the original plan.
Control focus
Map blast radius before work is estimated or scheduled.
03
Weak audit trail
Business impact
Teams cannot explain why a rule exists, who reviewed it, or which source artifacts support it.
Control focus
Keep findings tied to evidence, reviewers, timestamps, and open questions.
Diagnostic questions
Questions to answer before the next decision.
04 Diagnostic questions
- Q · 01
Which systems and data feeds are inside the decision scope?
- Q · 02
Which rules must be explained to business, audit, or operations teams?
- Q · 03
Where do batch windows, files, copybooks, and interfaces constrain change?
- Q · 04
What evidence is required before leaders can trust controlled rollout?
Related briefs
Continue the assessment.
- 01
Enterprise security program
access control, private deployment, audit trails, data handling, and evidence review
Open brief - 02
Pricing and buying model
$0.10 per line of code documented. Pilot starts at $15K for ~100K LOC, then scales with documented volume.
Open brief - 03
Enterprise documentation program
controlled documentation, knowledge capture, approvals, and evidence exports for COBOL estates
Open brief
Next step
Start with one controlled knowledge audit.
Send the system scope, current knowledge risk, and review timeline. COBOLpro will shape the first documentation and retention package around that need.