PlanMaker 2026 · Cell formatting and layout · Intermediate
Design Reusable Cell Styles and Layouts in PlanMaker 2026
Build a readable task sheet with reusable styles, controlled style inheritance, wrapped notes, and a repeatable reset.
A cell style stores a reusable set of formatting attributes. Use a named style for recurring headers or notes rather than rebuilding each format by hand. Keep content, layout and style membership separate so future edits remain predictable.
Create the task-sheet fixture
Enter A1:D4 exactly as follows. Do not merge any cells.
| Item | Owner | Status | Notes |
|---|---|---|---|
| Budget review | Alex | Open | Confirm the final figures before the monthly meeting |
| Inventory check | Sam | Done | Recount the items with quantity differences |
| Supplier call | Jo | Open | Ask about the delivery date and record the answer |
Save an unchanged task-layout-before.pmdx, then a working task-layout.pmdx. The sheet has three records, two Open statuses and one Done status. Those facts must remain unchanged by formatting.
Define a reusable header style
- Select A1:D1. Open Home → Format → Cell styles → Manage cell styles.
- Select Normal as the starting basis and click New. Name the style
TaskHeader, then confirm. - Use Character to choose bold text and a readable font size, such as 11 points. Use Cell to set a pale blue Shading, a bottom Border and left Alignment.
- In Format includes, include Font, Shading, Borders and Cell alignment. Exclude Number format and Cell protection: this header design should not silently change these unrelated properties when reused.
- Click Apply to apply it to the selected cells, then close the dialog.
The expected result is four equally styled heading cells with unchanged text. Choose dark text on a light fill; the words themselves should explain the columns without relying on color.
Define wrapped notes and size the grid
Select D2:D4. Create a second style, TaskNote, based on Normal. Through Character set normal-weight text; through Cell set left and top alignment and enable wrapping. Include Font and Cell alignment; leave Number format and protection out. Apply it.
The direct control Home → Alignment → Wrap text is useful for a one-off cell, but a named style provides one maintenance point for this repeated notes layout. Change widths through Layout → Cells, or drag column-header boundaries. Make A wide enough for Inventory check, B for the names, C for the statuses and D roughly wide enough for a short sentence fragment. Increase row heights until every word of all three notes is visible. Widths and heights are layout choices; do not assume they were saved inside the cell style.
Expected checkpoint: the entire phrase before the monthly meeting is visible in D2, the end of D3 reads quantity differences, and D4 ends with record the answer. Check at a normal reading zoom, not only at an enlarged editing view.
Change the design once and reuse it
Add the same headings to A7:D7. Select that range and choose TaskHeader from Home → Format → Cell styles. Return to Manage cell styles, select TaskHeader, then change its shading from pale blue to pale green through Cell. Both header blocks should change together, without altering the three record rows.
Add A5 = Delivery review, B5 = Lee, C5 = Open, D5 = Confirm the cartons arrived without damage. Apply TaskNote explicitly to D5 and adjust row 5’s height. Appending data does not prove the intended style was inherited. The workbook now has four records and three Open statuses.
Advanced: inheritance without unwanted changes
Create TaskHeaderSecondary based on TaskHeader for a less prominent heading, then customize its font to italic. A later change to the base style affects inherited attributes, while explicitly customized attributes remain independent. Test this on the second heading block, not on a live report.
Be careful with Normal. It is the default for all cells, and changing it can affect the whole document and styles based on it. For this exercise, edit TaskHeader rather than modifying Normal. The Format includes checkboxes are also important: a numeric-format-only style can be useful when you want to retain existing fills and fonts.
Save and reopen the styled workbook
Keep all four records, both heading blocks, TaskHeader, TaskNote and the secondary style from the advanced exercise. Save task-layout.pmdx, close and reopen it. Inspect Manage cell styles for the custom styles, check both heading blocks and the full D5 text, and confirm all task values remain intact. Styles are stored in the document; this does not automatically install them in every future workbook.
Optional reset on a separate copy
After verifying the styled file, use File → Save as to create task-layout-reset.pmdx. Only in this copy, edit TaskHeader’s shading back to pale blue. To remove a custom style from a practice heading, apply Normal and inspect the result. A style selection is not a promise to remove every manual override or restore row heights. For an exact clean reset, open task-layout-before.pmdx; it contains only the original three records, with no row 5 addition or row 7 headings. Never save that recovery over the verified styled workbook.
Troubleshooting
- Only one heading changed: check which style the other heading actually uses.
- Notes remain clipped: inspect wrapping and row height, not just column width.
- Numbers unexpectedly changed appearance: inspect Number format in Format includes.
- Data disappeared after merging: merging retains only the upper-left cell’s content. Use the saved copy and keep record cells unmerged.
Use conditional formatting thresholds when appearance must respond to a value rather than a manually assigned style.
Version and verification notes
PlanMaker 2026 paid desktop; documentation-qualified workflow for Windows, macOS and Linux. NX builds require matching controls; FreeOffice and mobile editions are not verified. These steps use the English ribbon labels; classic-menu placement is not assumed to match. Documented context-menu or alternate ribbon routes are included where verified.
The instructions in this guide were checked against SoftMaker’s PlanMaker 2026 manual. Expected results are reference checks, not observations from a native application run. No current application screenshot is claimed.