Documentation

Recording isn't a habit yet. You write down what happened in meetings and work, and what got decided, before the day ends. Every record carries an author and a date, so anyone can later tell who wrote it and when. Readers and format don't matter at this stage. The bar is simple: months later you reread your own note and the situation comes back.

• Can record decisions and owners on the same day a meeting ends
• Can attach an author and a date to every record you leave
• Can log the day's work, capturing what you did and how far you got
• Can record while work is in progress rather than after it ends, at least 3 times a week
• Can pick one place to keep records and gather scattered notes there
• Can reread a record you wrote 3 months ago and reconstruct the situation and the reasoning

Notes only you could decode turn into records other people can use. You split a procedure into preconditions, the order of steps, and how to confirm the result, so someone else lands on the same outcome. When you revise a record, you don't erase the old version. You leave what changed, when, and why, which shows the record wasn't quietly rewritten after the fact.

• Can record a procedure split into preconditions, order of steps, and how to confirm the result
• Can collect 3 or more cases where someone followed your written procedure and reached the same result
• Can revise a record without erasing the previous version, noting when and why it changed
• Can separate settled items, open items, and the next check-in date in meeting notes
• Can cite the source of every number and date you write down so it can be traced later
• Can log the time, symptoms, and actions taken in order when an incident or outage occurs

You decide for yourself what to record and in what form. A walkthrough for a first-timer, a fix for someone who already knows the system, a reference someone scans for a value, and an explanation of how things got this way serve different purposes, so they take different shapes. You keep the alternatives you weighed and the reasoning behind a decision, then run the record through review and approval so everyone knows which version holds.

• Can choose whether a topic belongs in a walkthrough, a how-to, a reference, or an explanation, and justify the choice
• Can capture the option chosen, the alternatives considered, and the reasoning in a decision record
• Can name a reviewer and an approver before release, get sign-off, and announce the final version
• Can tag each record with an ID, a scope, and a revision number so the valid version is clear
• Can document your own work well enough that a successor runs it without a face-to-face handover
• Can check for overlap with existing records and decide whether to write a new one or revise the old
• Can produce 3 or more cases where a written record settled a decision without holding a meeting

This is the stretch where more records mean less trust. You set a standard for how much detail each kind of work deserves, and you control distribution, access, and disposal. When two records state the same fact differently, you trace them back to the original and rule on which one stands. Records written as the work happened get marked apart from records reconstructed later.

• Can set and document a standard for how much detail each type of work gets recorded in
• Can trace two records that state the same fact differently back to the original and rule which is right
• Can set access rights and distribution scope separately for a record and note the reasoning
• Can mark records written at the time of the work apart from those written afterward
• Can audit ongoing work for recording gaps and produce a list of what is missing
• Can mark records that have expired so nobody cites them by mistake
• Can select records for external submission to fit the request and document the selection criteria
• Can sample records a tool generated automatically and verify them against what actually happened

Responsibility shifts from writing well yourself to making sure the team writes at all. You design the rules and templates that say what gets recorded and by when, then track whether it actually happens. Reviewing a colleague's records forces you to put your own judgment into words. Records that stopped earning their keep get cut, so the cost of recording stays bearable.

• Can define the team's recording timing rules (what gets written by when) and get agreement on them
• Can design 3 or more record templates and get the team actually using them
• Can review 2 or more members' records and explain your criteria until they write independently
• Can define missing-record rate or writing delay as a metric and measure it every quarter
• Can point to a handover or reorganization where records alone kept the work running
• Can weigh the cost of recording against the benefit, decide what to retire, and actually cut it
• Can produce 3 or more cases where past records let you reconstruct a cause in a retrospective or incident review

You answer for whether the organization's records hold up as evidence outside its walls. You set company-wide recording policy and submit records in audits or disputes, and they pass. When recording keeps failing in the same places, you find the structural cause and change the system rather than the people. The policy also names the areas where not recording is the better call. You publish the method where the industry can see it.

• Can enact a company-wide recording policy stating what gets recorded, when, and by whom
• Can point to records submitted to an external review or audit that passed verification
• Can classify repeated recording failures by cause and carry out a systemic fix
• Can merge the differing recording practices of 3 or more departments into one minimum standard
• Can define where not recording is the better choice and write that boundary into policy
• Can publish the organization's recording method at an industry event or in trade media

You've moved from someone who records well to someone who decides what people record and how. The method you proposed gets adopted outside your own organization and shows up in standards or training programs. This sits above the point where SFIA INCA stops defining at organizational policy, so the achievement shows in the practice that outlives you, not in a grade.

• Can show that 3 or more outside organizations adopted your recording timing and attribution rules as written
• Can present cases where a recording method you proposed entered a standard, guideline, or curriculum
• Can verify 10 or more citations of your recording methodology in publications or lectures
• Can show that a recording system you designed has stayed in operation for 5 years or more
• Can confirm that people you taught now design recording systems for their own organizations
• Can publish where your own method falls short, with alternatives, so others have a place to surpass it