What the Wexford study delivered, set against what its protocol planned and stopping short of outcomes, fills GB891's closing implementation chapter draft. Searches like "gb 891 unit 10 assignment example", "gb891 unit 10 sample" and "gb891 unit 10 example" land here.
What a finished GB891 Unit 10 implementation chapter draft looks like
Around twenty pages under six headings: overview of execution, timeline as run, participant flow, intervention delivery and fidelity, deviations, and implications for replication. The timeline sets planned and actual weeks side by side, showing the ice-storm week and the late follow-up survey at one plant. Participant flow appears as a diagram, all bracketed: [24] crews, [19] supervisors consenting to interviews, baseline survey responses of [274] and follow-up of [241], and [1,036] pulse answers against [1,152] planned slots. The fidelity section reproduces the Unit 8 table crew by crew, delivery, receipt and enactment, flagging two crews below threshold. Deviations are summarized with register identifiers rather than retold. A closing section lists four protocol changes a replicating team should make, beginning with a supervisor-turnover rule written before fieldwork.
How a GB891 Unit 10 example is structured
The chapter answers one question a committee will ask before believing any result: was the intervention delivered as described, and to whom. Planned and actual appear together throughout, never in separate sections, so no departure can hide in the distance between them. Past tense marks everything that occurred, and future tense appears only in the closing replication section, keeping what was done distinct from what is recommended. Participant flow comes before fidelity because a delivery rate means little until the reader knows how many crews and people it describes. Fidelity is reported by crew, not averaged, since a plant-level average would conceal the two crews that fell below threshold. Deviations are cross-referenced to the Unit 9 register instead of retold, which keeps the chapter consistent with the report. Outcomes are withheld deliberately, and a transition names what the analysis chapter will test.
Schedule as planned, schedule as run
Every schedule element appears with its planned week and its actual week. The ice-storm gap and the follow-up survey that ran [nine] days late at one plant are visible in the same table as everything that ran on time.
Flow before fidelity
Crews, supervisors, survey responses and pulse answers are counted first. Delivery rates in the next section then refer to a population the reader has already seen, with every figure bracketed.
Fidelity crew by crew
Twelve rows show delivery, receipt and enactment for each intervention crew. Two fall below the Unit 8 threshold, and the chapter names them rather than letting a plant average absorb them.
Deviations by reference
Each departure appears as its register identifier with a one-line summary. Retelling them here would risk a second version that drifts from the report, so the chapter points to the register instead.
Results held back
No outcome figures appear. Climate change, near-miss counts and observed behavior belong to the analysis chapter, and the transition says what it will examine first, beginning with the Clarksville sensitivity check.
Changes a replicator would make
Four protocol revisions close the chapter in future tense, led by a supervisor-turnover rule and a contamination question for comparison managers from week one rather than month one.
Where marks go in GB891 Unit 10
Describing the plan in the past tense, as though everything proceeded as designed, is the most visible way a GB891 implementation chapter fails. Committee members compare the chapter against the protocol, the collection log and the deviation register, and a figure that disagrees across them undermines the whole account. Fidelity reported only as an overall average hides the variation a committee needs to judge outcomes. Participant numbers that shrink between sections without explanation draw immediate questions. Chapters that slip outcome results into the implementation account blur the line between what was delivered and what it achieved. Deviations retold rather than referenced often drift from the report. Planned and actual side by side, fidelity by group, disciplined tense and a close built on specific protocol changes, not general lessons learned: that combination is what committees reward.
Get a GB891 Unit 10 example written to your instructions
Your protocol, collection log, deviation register and fidelity records, with the chapter template and Unit 10 rubric, give the draft its material. Built from the fieldwork as it ran and stopping before outcomes, the custom chapter brackets every figure so each can be checked against your records. It arrives in 24-48h, and a first is free.
GB891 Unit 10 questions, answered
Does an implementation chapter report results?
Usually not. It reports what was delivered, to whom, how faithfully and with what departures, leaving outcomes for the analysis or results chapter. Keeping the two apart lets a reader judge the delivery before seeing whether it worked. Some templates combine them; yours decides, but the distinction should stay visible either way.
What tense should the chapter use?
Past tense for everything that happened during implementation, since the fieldwork is complete. Future tense belongs only to recommendations, such as changes a replicating team should make. Mixing tenses, or describing planned steps as though they occurred, is one of the first things a committee notices in a draft like this.
How much should the chapter repeat the deviation report?
Very little. Referring to each deviation by its identifier, with a one-line summary, keeps the chapter consistent with the report and avoids two accounts that drift apart. Readers who need detail can turn to the register, which is where explanations and consequences already sit. A committee member comparing documents, as most do at this stage, then finds one account rather than two.