CPORT is a five-part checklist for handing over a task clearly: Context, Purpose, Outcomes, Resources and Time. What does CPORT fix? Most handovers of work fail because something was left unsaid or unexplained, not because the person can't do the work. Who does CPORT help? The CPORT model is particularly helpful for anyone delegating work or tasks. It helps most where working memory, reading unstated expectations or getting started are harder, which is common for neurodivergent staff. However, this can also be true in high-paced or high-pressure environments, where workload is high with a lot of distractions and similar situations.
Context
Context is all about what's already happened, what's already been decided and any surrounding situational information that is relevant to the task - such as market, environmental or broader customer activity. It's there to answer questions such as "What do they need to know that I know?" For example, "The board rejected the last version because it was too long".
Purpose
Purpose explains the "why" the task exists and what it feeds into. It should answer questions such as "What is this for?", for example, "These numbers decide whether we hire in Q1." For many people, having a clear understanding of the purpose will allow them to exercise more effective judgment when they are completing the task. This understanding, along with the Context, enables them to make better decisions about what information to include and how to shape the final product in a way that best meets the actual need.
Missing these two steps will often lead to the work product missing expectations, rework and general frustration on all sides.
Outcomes
Outcomes describes what "done" looks like. It's the "what" of the task. It should address the question "how will we both know it's finished?". For example, "Two pages, for the exec team, draft quality is fine." Be as specific and detailed as possible (within reason) here to ensure that the person picking up the task has a very clear understanding of what the output looks like. Alignment on this point is important as it helps minimise ambiguity and misunderstanding of what done or good looks like.
Resources
Resources can cover a wide range of external supports that might be available. This can include funding, access to people, tools or templates, systems, proformas or past examples of similar work outputs. It could be specific equipment or building access. Resources deals with the question of "What do they need, and who can they ask?". An example might be "Use last year's template. Priya has the raw data."
Time
Time covers both the deadline and milestones or frequency of updates. It should answer "When, and what's the first checkpoint?" For example, "First draft Wednesday, final Friday, because the client sees it Monday."
For short, sharp tasks, checkpoints or preplanned reviews may not be required. However, for longer running tasks, it is good practice to establish a rhythm for updates or check-ins early. For some people, having a defined, more immediate deadline with an expectation attached can be key to aiding their ability to initiate and maintain focus on the task.
Where does CPORT come from?
The CPORT framework can't be pinned down to any single origin. However, Benjamin P. Taylor's work and Ensemble Consulting both cover it in some detail, with an earlier connection to Elliot Jaques.
Jaques's earlier task assignment checklist is the closest known predecessor of CPORT. Jaques's core idea was that a task is defined by its output (quantity and quality), its deadline and the resources allocated to it. CPORT is essentially a simplified version of the model that Jaques defined, which better supports an effective 5-minute handover and is well suited to the pace of modern work.
Whatever its origins, CPORT is certainly not mine. Through my coaching, what I've seen is that missed deadlines and "poor quality" work are most often tied to unclear handovers rather than ability. If you’re already seeing performance concerns, check the handover first. Our guide to managing neurodivergent employees covers the wider conversation.
Why it works
The greatest value that the CPORT framework provides is to bring the often unsaid parts of a task into the open. By removing the guesswork from the handover, it both forces the giver to think about what they are asking for and what their expectations are. For the receiver, it removes the ambiguity that often either slows them down or catches them out when the work doesn't meet the underlying ask.
Additionally, by writing it down, it becomes a shared record that both sides can refer to. This is helpful for those who may need to have a constant reference point to check against to ensure the work they are doing meets the task requirements. It also provides a baseline to measure success against. And this again can go both ways. Was the work done to requirements? Were the requirements given clearly and accurately? What are the opportunities for improvement for both sides of the task equation?
A CPORT template you can copy
To keep things practical and useful, here's a simple template that you can use yourself when assigning a task to someone. Sometimes less is more, but making sure the key relevant details are covered is what's most important. Be specific, clear and where possible avoid jargon and inferences.
Task:
Context: what's happened so far / what's decided
Purpose: what this is for
Outcomes: what done looks like (format, length, audience, polish)
Resources: tools, templates, people, budget
Time: final deadline / first checkpoint / why that date
Usage note: send it in writing, then talk through it. Ask the recipient to say back what done looks like based on the brief.
Three mistakes that undo it
When you first use CPORT, it may feel like extra admin to get work done, and the value may not feel worth it. As I've told so many of my clients, the 10 minutes you spend in preparation, planning or writing up a task using the CPORT framework will more than pay for itself later in avoided rework, frustration and disappointment.
These are three common mistakes that people make when putting the CPORT model into practice.
Saying it aloud only.
Without the written reference, it can be easy to forget what was being asked. It also removes the opportunity for the receiver of the task to digest the requirements and consider any additional questions or concerns they might have. These will end up being discovered along the way, where they could have been addressed or avoided with a little extra preparation up front.
Skipping Purpose ("just do it my way").
Understanding the underlying objective provides space for innovation and creative solutions. I've seen instances of the "do it my way" being implemented only for the manager to realise once the work is done that the output doesn't actually meet the requirements of the task. By limiting the initiative of the receiver to find a best-fit solution, results can at times be suboptimal.
Having said that, there may well be instances where a very directive approach to how the task should be completed is appropriate. By providing the Purpose, you give important context as to why that approach is required or expected and can alleviate internal resistance, anxiety and overthinking by the receiver and help them focus on getting the work done.
"ASAP" as the Time
Clarity and specificity should be the cornerstone of any CPORT-defined task. ASAP is neither. Time is inherently measurable and so should be clearly defined. ASAP as a stated term can also be interpreted differently by different people. It's a relative term, and what the manager means by ASAP could be very different to what the employee thinks it means. This could easily lead to the employee feeling an unnecessary level of stress to complete the work sooner than is actually required, or they will delay completion based on their interpretation of the time requirement.
CPORT works in reverse too
Whilst designed to support a manager allocating a task to an employee, the CPORT model can also be used in the opposite direction.
An employee receiving a task can run the request through the model, using each letter as a question if the brief is unclear: "What's this for? What does done look like?" etc. Seeking clarity using the CPORT framework to provide structure to their review of the brief can ensure they get the answers needed to do the job actually being asked.
Frequently Asked Questions
What does CPORT stand for?
CPORT stands for Context, Purpose, Outcomes, Resources and Time. Together they cover what someone needs to know before they start a task.
Who developed CPORT?
No one person is credited with the acronym. It builds on Elliott Jaques's task assignment work, covered in "Where does CPORT come from?" above.
What is a CPORT briefing?
A CPORT briefing is a short written handover using the five headings, followed by a quick conversation. The person taking on the task then says back what done looks like, so you both know you're on the same page.
Is CPORT only for neurodivergent staff?
No. CPORT helps anyone handing over or receiving work. It makes the biggest difference where expectations usually go unsaid, and where working memory or getting started is harder.
How is CPORT different from SMART goals?
SMART checks whether a goal is well written. CPORT covers the whole handover: the background, the reason and the support, as well as the target. You can use both, with a SMART goal sitting inside Outcomes and Time.
How long does a CPORT brief take?
For most tasks, five to ten minutes to write and a couple of minutes to talk through. Longer projects may need more detail under Resources and Time.
For worked examples and how to use CPORT with neurodivergent team members, read the full guide.
Want your managers using CPORT without thinking about it? Manager Coaching builds habits like this into how your team hands over work. Book a free consultation.