A new level starts with a list of checked changes
Before the next session, record what changes for your character under your table’s rules and agreements. Changing a level number does not establish that the entire sheet is updated. Nor must every field change: some values can remain the same.
DnD Dynamic Sheet offers ability modifiers, skills, proficiency, expertise, adjustments, fixed values, hit points, counters, notes and spell selection. This guide proposes reviewing that data; it does not claim an automatic level-up assistant or that the app decides your rules.
Agree on the source before editing numbers
Record the edition, book or document and any house agreement you will use. If the character combines options from different sources, identify what justifies each change. Similar feature names do not establish that two versions work identically.
Prepare an external note or use character notes with four columns: area, source, status and next check. In this fictional example, sources identify the document or agreement you need to locate; they are not citations from a particular edition and assign no game values:
| Area | Source to identify | Status in this example | Next check |
|---|---|---|---|
| Hit points | The table’s agreement on the increase | Method agreed; result pending | Determine and record the result before applying it |
| Proficiency | The agreed edition’s table, still to consult | Not checked | Locate the table and establish whether it changes at this level |
| New feature | Text of the chosen option | Name and rule located | Agree how to represent it as data or a note |
These status labels belong to the proposed note, not automatic app states. A pending check remains open even after you have recorded where to look.
Review related data after a change
If you confirm a proficiency change, review the relevant skills and how expertise is represented. If an ability value changes, check its modifier and the sheet values depending on it. Where adjustments or fixed values are present, establish the displayed result’s origin before adding another correction on top.
For a new resource, retain the text explaining expenditure and recovery beside the counter you choose to use. For spells, consult your agreed rule source: the app catalogue has entries with varying completeness, some containing metadata only and some text in English. Appearing in the list does not replace the applicable rule.
Finish with a record someone else can follow
“Hit-point method agreed, result pending; proficiency still to check; feature located, representation pending” preserves our example’s state and separates completed work from open decisions. Resolve that specific point with the table before playing the feature. A sheet opening successfully does not establish that a level increase was applied correctly.
The app is a Windows x64 desktop beta with local data and a lifetime license for one device. It is not a virtual tabletop or campaign manager. Consult its current capabilities and purchase information.