What a library week shows you
Each course row opens into its weeks, and each week holds a deliverable in real form rather than a description of one. The point is shape: how long the thing runs, where the headings fall, what a grading table asks for in practice, and how a worksheet or a deck is actually filled in. Reading one before starting your own week is the cheapest hour you will spend on it.
Reading a stacked week properly
The useful pass is never the first read. Open your own grading table beside the sample and find where each scored row is answered, then notice how much space the document spends on the rows carrying the most weight. That one exercise explains more about how Phoenix work gets marked than any general advice about academic writing.
The second pass is structural. Count the sections, see where sources appear and where they deliberately do not, and look hard at the opening. Most students lose marks in the first paragraph by warming up instead of answering.
The one written for free
One request per student, written to your instructions and delivered in 24 to 48 hours. It is a real deliverable for a real week rather than a teaser, no card is taken, and nothing converts into a subscription afterwards. The offer exists to settle an argument testimonials cannot settle: whether the writing is any good.
Ask on chat or through the request form, giving your course code, the week number and the instructions. The same rubric audit and format pass that paid work receives applies to it.
Which week is worth spending it on
Spend it on the week you would otherwise write badly. That is usually the one carrying the heaviest grading table, or the one landing in the same fortnight as something enormous at work, rather than the shortest one that merely annoyed you. Students who spend it on a small reflection tend to wish they had held it for the plan due two weeks later.
If your week is already stacked in the library, spend the request on a different one and read the stacked week for nothing. There is no rule against doing both, and no advantage in doing neither.
What a sample is meant to do
Everything produced here is described in the terms as a model for reference, built from your own materials and handed to you. Where it goes next is your call and your responsibility, as the terms page spells out. The one fixed point is that no file leaves this desk for a classroom: uploading is something only you ever do.
When the stack has no row for your course
The catalog covers a slice of the Phoenix course list rather than all of it, and rows are added as students ask for them. If your code is missing, the free custom request is the answer: it covers any course, including ones with no presence on this site at all. Send the code anyway, since a missing row is exactly how the next one gets built.
Codes that return nothing are logged, and the ones asked for repeatedly are the ones stacked next. Searching for something that is not here is therefore more useful than it feels at the time.
Send it over
Questions students ask first
Is the free one genuinely free, or a trial with a card attached?
Genuinely free. No card is collected at any point to produce it, and there is nothing to cancel afterwards.
Does the free piece reset when I start a new course?
One per student, not one per course, so starting something new does not unlock another. That is precisely why choosing the right week matters.
Is the free one slower than paid work?
No, it sits in the same queue and lands inside the same 24 to 48 hours, occasionally faster in the quiet months.
Can I see something in my subject before requesting anything?
Yes, the stacked weeks in the catalog are open to read immediately, including nursing rows such as NSG/523 and the composition rows.
Will asking for it start a stream of marketing?
No, the newsletter is a separate box you tick yourself. A request produces a reply about your week and nothing else.