Exploratory interviews feed a descriptive survey in GB532's Unit 4 proposal for a propane distributor, and a limitations page explains why neither stage can prove a plan would retain anyone. Searches like "gb 532 unit 4 assignment example", "gb532 unit 4 sample" and "gb532 unit 4 example" land here.
What a finished GB532 Unit 4 research proposal looks like
Roughly eight pages under proposal headings. A one-paragraph background restates the decision from Unit 2 and the secondary review's finding that heat pumps explain about a quarter of the lost gallons. Objectives are copied verbatim from the memo. The design section describes stage one, twelve semi-structured phone interviews with flagged households whose K-factor jumped, and stage two, a mail survey with a web option sent to two strata of automatic customers. A design table maps each objective to the stage and the data that answer it. The proposal then names the design type, exploratory followed by descriptive, and spends a full page on what that combination cannot establish. A ten-week timeline, a budget of about $14,600 split across printing, postage, incentives and analysis hours, and a deliverables list close the document.
How a GB532 Unit 4 example is structured
The proposal is arranged so each section answers a question a manager would ask in order: why spend money, what exactly will be learned, how, what it will not show, when, and at what cost. Interviews come first in the design because the firm does not yet know which reasons for adding a heat pump matter, and survey items written blind would guess. The survey follows to measure how common those reasons are across the customer base. Design type is named explicitly and defended against the alternative a manager might prefer, a price test of the backup plan in a few towns, which is described as the only route to a causal answer and deferred on timing. The limitations page separates what stated intentions can show from what purchases would. Budget lines are itemized so each can be cut without breaking the design.
Objectives carried over word for word
The three Unit 2 objectives reappear unchanged, so a reader can check that every design element serves one of them. An element serving none would be cut before the budget is drawn up.
Interviews where reasons are unknown
Twelve households with the sharpest K-factor jumps are called for twenty-minute conversations about why and when they added a heat pump, which rooms it heats and when the furnace still runs.
A survey where frequency matters
Two strata of automatic customers receive a mailed questionnaire with a web link. The interviews supply the answer options, and the survey estimates how widely each reason and pattern of use appears.
The claim the design cannot make
Stated interest in a backup plan is not a purchase. The page explains that only a field test, offering the plan in some towns and not others, could show whether it keeps customers, and why that test waits a season.
Ten weeks and $14,600
Printing and postage, a small incentive per completed survey, interview time and analysis hours are costed line by line. The timeline puts results on the manager's desk three weeks before contract renewals go out.
Where marks go in GB532 Unit 4
Proposals in this course usually come apart where the design and the objectives part company, and the typical version is a descriptive survey presented as if it could prove that a new plan would change behavior. Instructors look for the design type named, justified and bounded; the bounding is the part most proposals omit. Credit also depends on alignment, every objective matched to a method and every method matched to an objective. Exploratory stages described without a reason for going first appear decorative. Timelines that ignore the decision date, or budgets given as one lump sum, cost feasibility marks. Proposals that list generic limitations, small sample or self-report bias, earn less than those stating what this design specifically cannot conclude. Missing ethics notes about customer data draw comments in some sections.
Get a GB532 Unit 4 example written to your instructions
Paste in the objectives your Unit 2 memo settled on, the Unit 4 prompt and the rubric for your GB532 section, plus any budget or timeline the case imposes. Returned within 24-48h, the proposal matches a design to each objective and states plainly what that design cannot conclude. The first custom sample is on us.
GB532 Unit 4 questions, answered
Does the proposal need a budget if the case gives no figures?
Often yes, because feasibility is usually graded and cost is part of it. Estimate plainly and label the estimates: postage rates, printing, a modest incentive, analyst hours at a stated rate. Graders are not checking whether your prices match a vendor quote; they are checking whether the design could be carried out with the money and time the case describes.
How do I justify choosing a descriptive design over a causal one?
By connecting the choice to the decision and the timeline. A causal design such as a field experiment answers a stronger question but takes longer and costs more. If the manager needs an estimate of how common something is before a deadline, a descriptive design fits. Say what the causal design would add and when it might follow.
Should the proposal include the questionnaire itself?
Usually not yet. Most GB532 sections build the instrument in a later unit, so the proposal describes what the survey will measure and how it will be administered. A short list of the constructs, linked to objectives, shows the plan is concrete. Check the prompt, since a few sections ask for draft items in an appendix.