Create a well-structured digital document from supplied records

Create a well-structured digital document from supplied records

Draft audience: Grade 10 intended, subject to teacher review of prerequisites and exact current subject, strand and term placement. This is original learning support, not an official curriculum allocation or marking scheme.

A structured digital document should let readers navigate, identify what a table means and trace a claim to its evidence. Larger bold text can look like a heading while providing no heading structure at all. This activity supplies an actual original report, its editable HTML source and a deliberately poor before-version. You will audit the changes and repair a new small document.

The completed reading-room report (prepared local file; hosting pending) is a standalone native HTML document. Its editable semantic body source (prepared local file; hosting pending) and stylesheet (prepared local file; hosting pending) are also supplied. The report file can be read offline in a browser; its source can be edited as text. These are prepared local files, not existing public downloads. No Word, PDF or account-based copy is needed for the learning job.

Inspect the report before auditing it

Report RR01 describes three fictional shelves. Reference has 12 boxes and 10 readable labels; Stories has 18 and 14; Activities has 8 and 6. Therefore there are 38 boxes, 30 readable labels and 8 labels needing attention. Two supplied sheets contain six blank labels each, so the available count is 12. Under the stated one-label-per-box assumption, using eight leaves four.

The document retains the complete fictional shelf log as source S1 and the complete supplies note as S2. In-text citations link to those records inside the same document. A reader can check the counts without an account or a missing attachment. The recommendation is bounded: check the affected boxes before ordering more materials. The log does not establish missing books, borrowing demand or the effectiveness of a completed repair.

Complete document example

Reading room shelf check

RR01 version 1.0 · 6 October 2026 · Original fictional classroom document

This report recommends checking the eight boxes without readable labels before ordering any additional label sheets. In the supplied reading-room records, 30 of 38 boxes have readable labels. The record does not establish that any books or boxes are missing.

Purpose and scope

The fictional reading room needs labels that let visitors identify a shelf’s contents without opening every box. This check covers the three named shelves at one recorded review. No learner names, borrowing histories, contact details or other personal information are collected. The figures come from source S1, the supplied shelf log.

Recorded box counts

Boxes and readable labels at the fictional shelf check
Shelf Boxes counted Readable labels Labels needing attention
Reference 12 10 2
Stories 18 14 4
Activities 8 6 2
Total 38 30 8

The totals are 12 + 18 + 8 = 38 boxes and 10 + 14 + 6 = 30 readable labels. Eight boxes therefore need label attention. Stories accounts for four of those eight. These figures measure label status, not the number of missing books or the popularity of a shelf.

Recommended next step

Use the supplied spare sheets only after checking which boxes need a new label. Source S2, the fictional supplies note, records two sheets containing six labels each, giving 12 spare labels. If each affected box needs one label and no labels are damaged during preparation, eight labels are sufficient and four remain. The assumptions should be checked before using this as an actual materials plan.

  1. Recheck the eight affected boxes against the shelf log.
  2. Prepare clear descriptions using the existing shelf names.
  3. Review the revised labels for readability and record the new count.

Limits and review

The report contains one fictional snapshot. It does not show how long labels have been unclear, how often visitors use the shelves or whether a different layout would work better. A later check can record whether all 38 boxes have readable labels, while retaining this original record and its date.

Supplied sources

S1 Shelf log

Original fictional record, 6 October 2026: “Reference: 12 boxes, 10 readable labels. Stories: 18 boxes, 14 readable labels. Activities: 8 boxes, 6 readable labels. All counts refer to boxes on the named shelves at this check.” No actual organisation or observer is represented.

S2 Supplies note

Original fictional record, 6 October 2026: “Two unused sheets remain. Each sheet contains six separate blank labels.” The note supplies quantities only; it contains no real price or purchase commitment.

Use styles to express relationships

The source uses one h1 for the report title, h2 elements for main sections and h3 elements for the two source records. CSS controls how those roles look, so changing the section-heading style changes all equivalent headings consistently. A paragraph styled in a large font remains a paragraph; visual size alone does not create a heading relationship.

The table has a descriptive caption, column headers and named row headers. Scope values identify whether a header applies to its column or row. Each numeric cell belongs to an explicit shelf and quantity. No merged cells, screenshots of text or colour-only meanings are needed. The rows also have a textual calculation directly below them, which helps readers check the totals.

W3C guidance on headings supports expressing document hierarchy with meaningful heading elements. W3C guidance on table headers explains associating data cells with headers. Those practices improve structure; this package does not claim an accessibility certification or a completed test with every assistive technology.

Compare the actual before and after

Open the deliberately poor before-version (prepared local file; hosting pending). It uses bold paragraphs as headings, a spacing-based list as a table, an incorrect total and unsupported claims. It is retained as a labelled learning stimulus rather than silently overwritten.

Before-and-after audit of RR01
Issue in before-version Repair in completed report What to verify
Large bold paragraphs imitate headings Semantic h1, h2 and h3 roles with consistent styles. Heading order describes title, main sections and source subsections.
Numbers separated by spaces have no column meanings Native table with caption, column headers and shelf row headers. 12 belongs to Reference boxes; 10 belongs to its readable labels.
The total says 40 Correct count is 12 + 18 + 8 = 38. Body, table and recommendation use the same records.
“All books are missing labels” Eight boxes need label attention. Do not change the counted object from boxes to books.
“Source: the log” has no supplied record Named S1 and S2 citations lead to full fictional source texts. Both citation targets exist and contain the relevant fact.
“It is all fixed” invents completion A recommended check and later review remain conditional. No completed action is claimed without a new record.

Keep a clear file workflow

  1. Keep the labelled before-version as the comparison stimulus. Work on a separate source copy identified as RR01 version 1.0.
  2. Edit the semantic body and stylesheet. Preserve source identifiers S1 and S2 so citations remain meaningful.
  3. Generate or save the standalone report using that body and style. Open the exact resulting file; a filename alone does not establish valid HTML or correct content.
  4. Check headings, every table value, citation targets, narrow-screen wrapping and print layout. A change in the source must be carried into the standalone copy before distribution.
  5. After a substantive revision, change the version and record what changed. Preserve the older checked version if it is needed to explain an earlier decision.

The supplied source and standalone report contain the same body content. They are one teaching document in two useful roles, not two independent reports. No saving, uploading or changing permissions on an actual account occurs here. A file called “teacher” or “final” supplies no access protection or correctness guarantee.

Independent repair practice

Here is the complete new fictional source: R1, “Display trays: East has 7 cards, of which 5 are legible. West has 9 cards, of which 8 are legible.” R2, “Four blank replacement cards are available.” The draft says: “DISPLAY UPDATE. East 7 5. West 9 8. Total 18. Everything is readable. Buy six more. Source: someone.”

Create a short semantic document with a title, a purpose paragraph, a captioned table, a supported next step and both source records. Use headers that distinguish total cards from legible cards. Cite the record supporting each conclusion. Keep the original draft separate and write a three-point audit of your repairs.

Explained answer and review criteria

Total cards = 7 + 9 = 16; legible = 5 + 8 = 13; needing attention = 3. East needs two and West one. Four spare cards can cover three replacements with one left, assuming one replacement per affected card and no waste. There is no supported need to buy six or claim the problem already fixed.

A suitable next step is: “Recheck the three unclear cards, then prepare replacements from the four spares if the check confirms the record.” Award 2 points for correct totals and shelf differences, 2 for real heading hierarchy, 2 for a captioned table with correct header roles, 2 for traceable R1/R2 citations and 2 for a bounded recommendation and retained revision history. Maximum: 10 learning points. Judge the actual document source and rendered reading order, not a promise that styles were used.