Column by column, this GB891 Unit 7 collection log shows what a complete record of Wexford fieldwork contains, with every entry bracketed for the candidate to supply. Searches like "gb 891 unit 7 assignment example", "gb891 unit 7 sample" and "gb891 unit 7 example" land here.
What a finished GB891 Unit 7 collection log looks like
A log template of ten columns and a two-page cover memo. The columns: date, study week, plant, crew code, activity, count achieved against count planned, instrument version, person performing, anomaly flag and a cross-reference to the deviation register. Sample rows show the kinds of entry a complete log carries, all bracketed: [week 3, Bowling Green, crew B2, pulse, 4 of 4, v1.1, assistant, no flag]; [week 5, Seymour, all crews, feedback sheets delivered 11:40 Monday, late, flag, D-02]; [week 8, Clarksville, observation cut to 9 minutes by a fire drill, flag]. Weekly subtotals close each block. The cover memo explains column rules, when an anomaly flag is required, and how entries are made the same day, never reconstructed from memory at week's end.
How a GB891 Unit 7 example is structured
The log is built to be read by someone other than its author. Columns are fixed before collection starts and never added mid-study, since a column appearing in week six implies something went unrecorded before it. Count achieved sits beside count planned in every row, so shortfalls are visible without calculation. Instrument version appears on each line because the pilot produced version 1.1 and later amendments may follow; an analysis that cannot tell which items a given answer responded to cannot be trusted. The anomaly flag is deliberately broad, covering anything that departed from the protocol's standard path, and the cross-reference column connects flagged rows to the deviation register without duplicating its explanations. The cover memo's same-day rule carries the most weight, stating that late entries are marked late with both dates, rather than backfilled to look contemporaneous.
Ten columns, fixed in advance
Date through deviation reference, set before week one and unchanged afterward. A column added midway would imply earlier weeks went unrecorded, so the structure is settled before any entry exists.
Planned beside achieved
Every row shows what the protocol expected and what occurred, such as [3 of 4] pulse answers. Shortfalls appear on the line where they happened rather than surfacing only in a weekly total.
Version on every line
Pulse, survey and observation form versions are recorded per entry. When the analysis later asks which wording an answer responded to, the log answers it without anyone relying on memory.
Flags that point elsewhere
An anomaly flag marks any departure from the standard path and carries a deviation register number. The log records that something happened; the register explains it, so neither document repeats the other.
Late entries marked late
An entry made after the day it describes shows both dates. Backfilled rows written to look contemporaneous would make the whole log unreliable, and the memo names that practice as the one to avoid.
Entries belong to the collector
Every sample row is bracketed. What happened at a given plant on a given Wednesday is known only to the person who was there, and the template leaves those entries entirely to the candidate.
Where marks go in GB891 Unit 7
Reconstruction by a stranger is the standard a GB891 collection log is held to. Logs kept as weekly summaries, collection proceeded as planned, hide the shortfalls and irregularities an analysis needs to know about. Instrument versions belong on every line, since mixed versions without labels can undermine every result drawn from them. Planned counts left out of the log make response problems invisible until the results chapter, where they look like concealment. A log that never flags anything reads as unreliable rather than tidy. Entries that seem to have been written at one sitting, identical in phrasing across weeks, draw questions about when they were made. The logs that hold up cross-reference a separate deviation register, mark late entries honestly and keep columns constant from the first day.
Get a GB891 Unit 7 example written to your instructions
Share your protocol, the activities your fieldwork involves and the Unit 7 instructions with rubric. Built to those, the custom log template comes back within 24-48h with fixed columns, a same-day entry rule and sample rows bracketed for you to replace with your real entries. The first costs nothing.
GB891 Unit 7 questions, answered
Will the sample contain real collection data?
No. The log's entries are yours, because only you know what happened at your site on a given day. The sample shows the columns, rules and kinds of entry a complete log carries, with every row bracketed as a placeholder. Your own entries, made as collection happens, are what the course assesses.
How often should a collection log be updated?
Ideally the same day as each activity. Entries written days later drift toward what should have happened rather than what did. If an entry must be made late, recording both the activity date and the entry date keeps the log honest and shows a reviewer exactly which rows were reconstructed.
What is the difference between a collection log and a deviation register?
The log records every collection event, routine or not, in a fixed format. The register records only departures from the protocol, each with its reason, consequences and any approval needed. Flagged log rows point to register entries, so the log shows that something happened and the register explains it.