This page holds a finished COM-FPX3700 Assessment 2 negotiation plan with the process sequenced, ground rules set, tradeable interests identified, and refusal contingencies written in advance. Searches like "com fpx 3700 assessment 2 assignment example", "comfpx3700 assessment 2 sample" and "com-fpx3700 assessment 2 example" land here.
What a finished COM-FPX3700 Assessment 2 negotiation plan looks like
It reads as an operational document with theory behind it rather than in front of it. The plan states its objective in one line, names who will be in the room and who will not, and sets the ground rules in the words they would be read out in. Each party's interests appear again in compressed form, sorted into what can be traded, what can be shaped and what neither side will move on. The agenda sequences the easier items first for a stated reason. Alternatives away from the table are assessed honestly for both sides, including the uncomfortable case where one party's alternative is strong. A contingency section covers walkouts, refusals to accept the framing, and the arrival of a new demand mid-process.
How a COM-FPX3700 Assessment 2 example is structured
The plan is ordered the way the meeting will run. It opens with the objective and the standard by which the outcome will be judged, so success is defined before anything is designed. A preparation section covers what each side needs to know beforehand, who invites whom and what the invitation itself must say to avoid setting the wrong tone. The ground rules follow, few in number and enforceable, with a note on who holds them. The agenda then sequences the issues and defends the order, explaining what an early agreement buys later on. A concessions section identifies what can be exchanged and what each trade is worth to the other side. The contingency section closes the plan, handling refusal, deadlock and bad faith, and a short paragraph names how the parties would know the agreement held.
Success defined before the design
The plan states what a good outcome would look like and how anyone would recognize it, so later choices can be judged against something.
Ground rules written to be read aloud
A short enforceable set appears in the exact words a convener would use, along with a note on who intervenes when a rule breaks.
Agenda order defended
The sequence of issues carries a reason, usually that an early agreement on something small makes the difficult item survivable.
Alternatives assessed for both sides
The plan examines what each party gains by walking away, including the case where the other side's alternative is stronger than yours.
Refusal planned for, not assumed away
Contingencies cover a party rejecting the framing, leaving the room or raising a new demand, rather than presuming cooperation throughout.
Where marks go in COM-FPX3700 Assessment 2
The recurring failure is the plan that works because everyone behaves. Designs assuming the difficult party arrives newly reasonable have solved a different conflict, and the criteria reading for feasibility notice immediately. Second is the outcome dressed as a process: a paper that states the settlement it wants without designing the conversation that could produce it. Third is ground rules listed with nobody enforcing them. Marks also drain through agendas with no reasoning behind the order, through alternatives assessed only for the writer's preferred side, and through plans that treat a power imbalance as a detail rather than as a constraint on the whole design. Distinguished plans state what they would concede first and what it costs.
Get a COM-FPX3700 Assessment 2 example written to your instructions
Attach the Assessment 2 instructions and the scoring guide from your COM-FPX3700 section, plus the dispute you carried in from earlier work. We write a custom example built as a runnable process, refusal contingencies included, and return it inside 24 to 48 hours. No charge applies to the first custom sample.
COM-FPX3700 Assessment 2 questions, answered
Should the plan predict what the other party will accept?
It should reason about it, with the reasoning visible, and stop short of certainty. Say what their interests suggest they can trade and what evidence points that way, then plan for being wrong. A design that depends on one prediction holding is fragile, while a design that names two likely responses and prepares for each reads as competent.
How is this different from the case analysis assessment?
The analysis diagnoses a conflict and stops there. This deliverable takes the diagnosis as given and designs the conversation that might resolve it, which means sequence, rules, roles and contingencies rather than interpretation. Restating the interest map at length here eats the space the design needs, and leaves the process criteria with very little to score.
What if the two parties have very unequal power?
Then the imbalance shapes the design and should be named in it. Process choices can partly offset it: neutral convening, information shared before the meeting, a rule that each party speaks uninterrupted, an outside participant where your instructions allow one. What loses credit is a plan written as if both sides arrived with equal leverage.