Post-course development plan — tasks and evidence of progress
Start a development plan with a specific task you still find difficult. It might involve analysing data, calculating risk or preparing a clear report. Then decide what to practise and how you will know you can perform the task independently. This lesson shows how to turn a general goal into stages of work, select assessment criteria and test skills on new data. The development card and example will help you plan your next steps and assess progress later. The plan can cover market research or preparation for professional work — without having to place trades. We select the next step according to available time, data and the actual need.

Choose a task another person can verify
A development goal becomes more useful when it names an output and a check. In our hypothetical project, the learner must prepare a data handover that another person can reproduce without a private explanation. The task is to classify the chronology of 24 synthetic event records. It involves no live account, client information or order placement.
The input contains 23 records with documented timezones and one record whose timezone is missing. The learner must preserve every record, classify what the evidence supports and keep the unresolved case visible. Guessing the missing timezone would create a more complete-looking table while weakening the evidence.
This is a project designed for the lesson, not an employer’s recruitment test. It demonstrates a bounded data-handling task; it cannot establish trading profitability, employability or competence in every form of market analysis.
Define completeness and classification as separate checks
| Check | Required evidence | Result in this file |
|---|---|---|
| Input coverage | Every source record accounted for | 24 of 24 retained |
| Chronology classification | Documented timezone available | 23 classified |
| Exception handling | Missing timezone remains explicit | 1 unresolved record |
| Reproduction | Another person reruns the same rules | 23 classified plus 1 unresolved |
Classified-record coverage is 23/24, approximately 95.83%. Input coverage is complete because all 24 records remain accounted for. Those statements are compatible. An unresolved source field does not require deleting the row, inventing its value or reporting that the entire file disappeared.
Write the criterion before assessing the output. If the real task requires classification of every event, the missing information remains a blocking dependency. If the task is to identify supported and unsupported chronology, an honestly retained exception can be part of a correct result.
Test a changed input without changing the explanation afterward
For the next hypothetical check, add one new record with a documented timezone. There are now 25 records:24 classifiable and the same one unresolved. Classified coverage is 24/25 =96%. The percentage rose even though the original missing information was not repaired.
Do not present that increase as proof that the learner gained skill. The denominator and the supplied cases changed. Instead, inspect whether the added row was handled according to the existing rule, whether the exception remained visible and whether another reviewer reproduced the result.
Retain the first output and the changed-input output separately, with their source versions. A reviewer should see what changed in the input, what changed in the method and what changed in the result. If the method changes too, record that as a new version rather than quietly rewriting the earlier assessment.
Build a portfolio entry with a narrow, supported claim
The finished handover can include the synthetic input, transformation rule, exception log and report. Its summary might say: “Every supplied record is accounted for; records with missing timezone evidence remain unresolved; the stated result was reproduced.” That is stronger evidence for this task than an unexplained claim of being advanced.
Record the remaining gap and the next task. It may be obtaining better timestamp documentation, testing a different format or explaining the same exception to a nontechnical reader. More study hours do not answer those questions on their own, and the next task need not involve taking market risk.
The research discussed in the detailed lesson concerns recall of texts by students. It does not validate this handover project as a job-readiness measure or show a financial outcome. Continue with the original development card and treasury example to plan a task, obtain feedback and decide whether to extend, correct or stop the project.
Three exercises with worked answers
The exercise data are hypothetical. Choose an answer, then check the calculation.
From a reproducible handover to the full development plan
The original diagrams, development card and treasury project remain below. Use them to choose a useful next task, state its criteria and assess changed inputs without equating course completion with a professional or financial outcome.
1. Start with an identifiable gap
An exam result, spreadsheet error or project comment may identify a specific task. “Understand the market better” is too broad to decide what to do in the next study session. A better starting point is: “I totalled EUR receipts and payments without separating their dates; the report hid a month with an outflow.”
Choose a role or use for your knowledge: your own research, data analysis, risk, treasury, operations or learning without a career goal. These directions need different projects. You do not need to start with a brokerage account to test your ability to reconcile data or explain cash flows.
The starting point could be exam 16.1, the review of conditions for the activity in 16.3 or feedback on previous work. A lack of material can also be addressed: complete a short diagnostic task with synthetic data and record where help was needed. The result describes the task's scope, not the person's aptitude.
2. Work sequence: task, check, decision
- Gap and evidence
Identify a specific error or omission. - Task and result
Produce work that can be inspected. - Quality control
Compare it with a criterion set beforehand. - New case
Test the same skill on different data. - Decision
Close the task, correct it, change the goal or stop.
Some dependencies are essential: check a report's data before interpreting it, and establish units and dates before comparing scenarios. Others depend on the direction. A cash-flow project does not require prior demo trading, and a data-checking project does not require evidence of strategy profitability.
Roediger and Karpicke's study compared students' rereading with recall. Prior memory testing produced better results in delayed memory tests.[1] In this plan, that supports a short attempt to explain the material independently after a break. The study did not test trading, transfer to professional work or the effectiveness of the schedule below; the project using changed data is a separate editorial proposal.
The 30/90/180-day dates can serve as review points. They do not mean moving from demo to live after a specified number of days. Likewise, one, two or five years are not deadlines for gaining an edge or employment.
The diagram organises one skill task. A correct exercise does not establish readiness to trade, obtain employment or profit from a strategy.
3. Development card: from a gap to a quality criterion
Create one card for one priority. Fill in the fields before starting, and record the result only after checking it. If you do not know the quality criterion, the first task is to establish how to check the work, not to complete more exercises.
| Field | What to enter |
|---|---|
| Goal | The role or application, and the skill tested in this block. |
| Gap and evidence | Task number, data row or comment identifying a specific problem. |
| Task | One clearly scoped activity; dependencies on earlier work. |
| Material | The relevant lesson, document or specification; not a list of everything to read. |
| Result | A file, table, report, code or solution with an explanation. |
| Quality criterion | A condition set before the task, calculation tolerance and invalid-data cases. |
| Time and budget | Available hours, work date and cost limit; possibly PLN 0. |
| Feedback | Who or what checks the result; the scope and how comments are recorded. |
| Review date | When you will compare the result with the criterion, even if incomplete. |
| Next decision | Close within the stated scope, correct, change the material, change the goal or finish. |
“The file exists” checks completion, not correctness. “The result is positive” does not check process quality. For a spreadsheet, a criterion may require totals matching the source, explicit units, detection of a missing date and correct operation on a new case.
| Field | Example entry |
|---|---|
| Goal | Prepare a simple report of future EUR receipts and payments by month. An educational project, not a client service. |
| Gap and evidence | The initial test totalled four documents to +EUR 4,000 without dates. It did not show the net outflow in M2. |
| Task | Build a source table, monthly aggregation and three EUR/PLN exchange-rate scenarios. |
| Material | Data and solution in section 5; the chosen role described in 16.4. |
| Result | A spreadsheet with data, formulas and total checks, plus a note explaining the negative M2 cash flow. |
| Quality criterion | All four documents included once; matching EUR totals; separate months; rate labelled PLN/EUR; a missing date produces an error; the new case in section 6 solved correctly. |
| Time and budget | 6 hours: data 1 h, model 2 h, checks 1 h, explanation and retest 2 h. Budget PLN 0 with spreadsheet software already available. |
| Feedback | A second person compares rows with the source and check calculation. Without one: delayed manual checking, explicitly labelled self-assessment. |
| Review date | Two weeks after opening the card; an organisational date, not a standard learning pace. |
| Next decision | Correct reconciliation and new case → close this gap within the exercise's scope. Date or sign error → correction and another test; unresolved problem → a narrower task or feedback. |
The entry is an example plan, not a declaration that the reader has completed the task. Delayed checking is not an independent audit. The reviewer should understand the subject and have access to the criterion and permitted data; being related or unrelated does not determine the quality of their comments.
4. First block: goal and initial test
The first block need not take a month. It ends when the gap and the plan for testing it have been defined. Someone already working with data may only need to review an existing project; a beginner may need a short diagnostic test.
| Work | Result | Condition for moving on |
|---|---|---|
| Choose an application | One sentence about the role or task | It is clear who would use the result and for what. |
| Attempt without consulting the key | A solution with uncertainties marked | A specific error or need for clarification can be identified. |
| Choose one priority | Development card | The criterion tests the gap within the available time. |
| Set aside time | Two or three calendar blocks and a review date | Total hours fit the time actually available; checking is included. |
First remove errors that distort the entire subsequent analysis: a unit, flow sign, missing cost or incomplete data. A lack of time may require a narrower scope or a different goal; do not attribute it to motivation in advance. The plan requires no purchases, account opening or trades.
5. Second block: a worked example without trading
Synthetic data, not documents from an actual company. The project concerns the timing of EUR cash flows. A positive sign means a receivable to collect; a negative sign means a liability to pay. Full payment is assumed in the stated month, without hedges, fees or taxes. We do not value instruments or propose any trade.
| ID | Month | Amount EUR | Meaning |
|---|---|---|---|
| N1 | M1 | +20 000 | Receivable |
| Z1 | M1 | −12 000 | Liability |
| N2 | M2 | +5 000 | Receivable |
| Z2 | M2 | −9 000 | Liability |
The whole horizon totals +EUR 4,000, but M1 has +EUR 8,000 and M2 −EUR 4,000. A report showing only the total may hide the need to obtain currency in the second month. Whether M1 funds cover M2 depends on whether they were retained and not needed for other payments.
| Month | Net EUR | 4.00 PLN/EUR | 4.20 PLN/EUR | 4.40 PLN/EUR |
|---|---|---|---|---|
| M1 | +8 000 | +32 000 | +33 600 | +35 200 |
| M2 | −4 000 | −16 000 | −16 800 | −17 600 |
| Total | +4 000 | +16 000 | +16 800 | +17 600 |
Check calculation: in M1, (20,000 − 12,000) × 4.20 = PLN 33,600. In M2, (5,000 − 9,000) × 4.20 = −PLN 16,800. Moving the rate from 4.20 to 4.40 increases the value of the M1 net receipt by PLN 1,600, but increases the cost of the M2 net outflow by PLN 800. The positive PLN 800 difference across the whole horizon does not remove the separate need to fund M2.
Keep separate source rows and totals in the spreadsheet so omitted or duplicated documents can be detected. An empty date field should not go into a default month, and a missing rate is not zero. Document ID, sign, currency and date are part of the checks, not decoration.
6. Third block: testing on changed data
Correcting the previous spreadsheet may demonstrate only familiarity with the correction. After a break, test the same skill on a case whose solution you have not yet reproduced. The task below can be done by hand; it requires no real capital.
Check task using synthetic data. Receivable N2 = EUR 5,000 moves from M2 to M3. All other data are unchanged, and the scenario rate is 4.20 PLN/EUR. Show each month's cash flow and the total; explain why the total is insufficient to assess liquidity.
Solution and checking criterion
M1: +EUR 8,000 = +PLN 33,600. M2: −EUR 9,000 = −PLN 37,800. M3: +EUR 5,000 = +PLN 21,000. The total remains +EUR 4,000 = +PLN 16,800. The M2 net outflow increases by EUR 5,000, or PLN 21,000 at this rate. A conclusion about additional funding still requires information about retained funds and other obligations.
Quality criterion: three correct monthly values, a matching total and an explanation of the changed date's effect. A correct total alone does not pass, because aggregation without dates was the gap being tested. This is the editorial exercise's criterion, not a professional standard.
Add two technical checks: remove one document's date and check whether the report flags it; add a document with the same ID and check whether it is flagged for investigation. Compare the repeated ID with the source rather than deleting it automatically — it may be an error or a separate item requiring a more complete identifier.
At the review, record the version, detected errors, corrections and new test result. If the new case remains difficult, narrow the task to dates and signs. If correct, the card closes this gap within the exercise's scope; it does not confirm readiness to handle treasury independently or success in recruitment.
View the solution chart
Synthetic example solution: rate 4.20 PLN/EUR. The total is +PLN 16,800, but the M2 net outflow increases by PLN 21,000. These are flows, not balances; funding needs also depend on available cash and other payments.
7. Periodic review: what completed work demonstrates
An annual review can help with a longer project, but changing a goal need not wait a year. Separate completed activities, result quality and practical application. Four completed reviews demonstrate regularity, not automatically competence.
| Question | Evidence | Decision |
|---|---|---|
| Was the original error corrected? | Comparison of versions and check results | Close only within the checked scope. |
| Does the skill work on a new case? | An independent solution using changed data | A further project or repetition of a specific element. |
| Does the result fit the goal? | Comparison with the recipient's need or tasks of the chosen role | Keep the goal or adapt the project. |
| Does the work fit the available resources? | Actual time, spending and other commitments | Narrower scope, a different date, a pause or an end. |
Record time and money separately if there is no basis for valuing an hour. In a hypothetical example, PLN 2,000 of results attributed to 500 hours gives PLN 4 per hour, but that quotient neither values competence nor determines profitability by itself. Costs, capital, risk and a real alternative use of that time are among the missing factors. Educational programmes are compared in 16.6.
8. Documentation and choosing the next project
Documentation should allow others to reproduce what was actually done. It does not require a public profile or publication of personal account results. A professional project can use entirely synthetic data; employer or client material requires a separate check of permission to share it.
- Description: question, recipient, scope and assumptions.
- Data: origin, data type, units, dates and limitations.
- Result: file version and instructions for running it or reproducing formulas.
- Checks: cases checked, errors, corrections and unresolved issues.
- Conclusion: what the work confirms and what it does not establish.
Trading your own account requires distinguishing historical research, demo and live accounts, and keeping complete records. Use verification names and scopes according to the documents; a reporting-service connection is not an independent audit. Detailed performance presentation is covered in 16.5.
A new direction can be chosen at any review. Two years of trading are not required before starting a data-analysis, operations or risk project. Choosing a specific role and checking current requirements belongs in 16.4; here we prepare a task that tests a gap.
9. Equally valid directions for further work
| Direction | Gap | Project and result | Quality control |
|---|---|---|---|
| Your own strategy research | No control of costs or data selection | A report comparing unchanged rules before and after costs; an archive of trials | Reproducible result, no double deduction of costs, explicit periods and selection. |
| Treasury / exposure analysis | Summing currencies without dates | The model in sections 5 and 6; a comment on funding needs | Reconciled documents, months and units; correct response to a payment-date change. |
| Data analysis / risk | No data-quality checks | A script or spreadsheet detecting a missing date, duplicate ID and incorrect currency | A reproducible exception report on prepared errors, without silently deleting data. |
| Operations | No method for reconciling two records | Two synthetic registers and a discrepancy list with proposed explanations | Each difference has an ID and source; matching items are not exceptions. |
| Learning without trading, or ending the project | No justification for further cost | A note on what to retain, what to end and which task makes sense outside trading | The decision fits the current goal; no trade or purchase is required. |
Five years is not a common maturity deadline for these paths. One person may work on financial reports from the start, another may stay with research, and another may leave the subject. We assume neither the proportions of these choices nor a recruitment advantage from taking the course alone.
For those trading their own account, an organised process does not prove an edge. Trade count, elapsed time and a positive result alone do not remove uncertainty. Even a statistical interval excluding zero requires a correct method, suitable data and consideration of dependence and sample selection; it is not a universal gate to real capital. Research methods are developed in 15.4, and auditing in 15.10.
10. Pausing, correcting and changing the goal
Set rules for changing the plan before the task. They should reflect its risk and cost, not punish a lack of progress. In a project without capital, stopping may mean cancelling a purchase or narrowing the scope; actual trading adds separate rules on exposure and available funds.
| Event | Response | Condition for further work |
|---|---|---|
| Unit or sign error, or a missing document | Suspend the report's conclusion; correct the data | Full reconciliation and a new check case. |
| The same error after two attempts | Different material or external correction; a narrower task | An independent explanation of the mechanism and a correct solution. Two attempts is an organisational threshold, not a diagnosis. |
| The task exceeds the card's time or cost limit | Review the scope before further spending | A consciously accepted new budget or a cheaper variant; stopping is possible. |
| No access to data or a reviewer | Limit the conclusion; use synthetic data if they fit the goal | Describe data and review scope honestly; label self-assessment as such. |
| Changed household circumstances, health or commitments | Pause or change the goal without waiting for the stage to end | Resume only if conditions allow; returning is not obligatory. |
| A perceived need for greater risk to catch up with the plan | Separate the learning plan from capital decisions | Learn with data or demo; no automatic increase in exposure. |
Documenting a decision preserves the reason for change, but is not a condition for the right to stop trading. A short entry is enough: date, available evidence, chosen option and any review date. A project can end without setting a return date.
The plan need not include a paid tool. With a zero budget, choose a scope achievable using available materials. That does not mean every gap can be closed free of charge: if a required resource is unavailable, narrow the goal, postpone the task or consciously change the budget.
11. First work block: 90 minutes
You do not need to reserve a whole weekend. The following 90 minutes are a suggested start, not a guarantee of resolving the gap in that time. They can be split into shorter sessions.
| Time | Task | Result |
|---|---|---|
| 0–15 min | Choose a role or application of knowledge | One sentence about the goal. |
| 15–35 min | Review a task result or take a short initial test | A specific error or gap with evidence. |
| 35–65 min | Complete the development card | Task, result and criterion set before the work. |
| 65–80 min | Check resources and dependencies | A realistic limit on hours and cost; identified materials. |
| 80–90 min | Arrange feedback and review | A check date and decision method, including for an incomplete task. |
Start with one file containing the goal, first card and review date. The next block should produce the result specified on the card. Choosing material for that particular gap is covered in 16.10 — choosing resources for a specific problem.
FAQ — frequently asked questions
Should I move from demo to a live account after 30 or 90 days?
Are one hundred trades enough to finish learning?
Does the plan make sense if I do not want to trade?
What if the quality criterion is not met?
How can I follow the plan without a mentor or paid tools?
Must every stage follow the exact sequence?
Sources and scope of evidence
The card, schedules and projects are editorial proposals. The treasury data are synthetic, with check solutions provided. No study of this plan's effectiveness or professional assessment of the reader has been conducted.
- Roediger H.L., Karpicke J.D., Test-enhanced learning: taking memory tests improves long-term retention, Psychological Science 17(3), 249–255, 2006; DOI: 10.1111/j.1467-9280.2006.01693.x. The study record and abstract were checked on 8 September 2026. It concerns students recalling texts; it does not demonstrate effective trading strategies or the employability of course graduates.