what teaching strategies gold actually is
teaching strategies gold is an observation-based assessment for children from birth through kindergarten. it is published by teaching strategies, llc, and used by many head start grantees, state pre-k programs, and private centers.
the teacher gathers short pieces of documentation — a note, a photo, a work sample — across the year, then rates each child on the objectives at three or four checkpoint windows.
the 38 objectives
gold is organized into 38 objectives across 10 areas: social-emotional, physical, language, cognitive, literacy, mathematics, science and technology, social studies, the arts, and english language acquisition (for dual language learners).
you do not have to document every objective in every window. most programs identify a small set of priority objectives per checkpoint.
the checkpoint schedule
most programs run three checkpoints — fall (october/november), winter (february), and spring (may). some run four. programs receiving federal funds usually align the schedule to their program year.
the two weeks before a checkpoint window closes are the busiest weeks for many teachers. plan for it.
documentation without losing the day
gold documentation is short. a two-sentence note with a date and objective code is a piece of evidence. a photo with a one-sentence caption is a piece of evidence. long narratives are not required.
the highest-leverage habit is capturing two or three notes a day on the floor, not sitting down after school to reconstruct the week.
the color bands and level ranges
each objective is rated on a numeric scale (usually 0-9 or 1-8, depending on the objective). the levels are grouped into color bands by age: red (birth-1), orange (1-2), yellow (2-3), green (preschool 3), blue (preschool 4), purple (kindergarten).
the widely-held expectation for a child at a given age is not a single number; it is a range shown as a colored band on the report. a child inside their expected band is on track. a child a full band below is a flag for a conversation, not a diagnosis.
what a piece of documentation looks like
anecdotal note: two sentences, date, child, and objective code. "5/3, m. built a tower of six blocks, knocked it down, said 'again' and started over. obj 11a persistence." that is a complete note.
photo: one image with a one-line caption tying it to an objective. a photo of a drawing with "m. drew a person with head, body, two arms, and a smile — obj 7a fine motor / 33 emergent writing" earns two objectives at once.
work sample: a page or a photo of a page, kept flat in a folder or captured in the app. a child's name on their own paper is itself an objective.
surviving checkpoint week
pick a small set of priority objectives at the start of each window, not the end. eight to twelve is plenty for most rooms.
block one hour on the friday before the window closes for rating, not documentation. by then, documentation is either there or it isn't; the rating is the actual task of the window.
if you are missing evidence on one objective for one child, one focused observation on monday morning is usually enough. do not rate from memory.
what tiny signals holds that helps
the observation capture tool saves short notes with the child's name and date. the /assessment page lets you tag observations with a framework and objective code. everything you tag flows to the child's timeline, so you can pull a checkpoint together in one sitting.