The requirement was not met
The expected content, format or evidence was missing.
Home · Journey map · Self-paced
Stage 01 / 06
Receive & Triage
Nothing exists until it is logged — one door, one owner, one deadline.
01Log it the same working day
02A named owner within one working day
03Pick the track: fast · standard · complex
Completion gate
Before you move on — can you…
Start the stage →
Stage content
2 modules to build discipline at the source
Start with the decision-maker’s perspective, then turn the idea into daily operating discipline.
Module 01
The Decision-Maker’s Lens
See your work from the Council’s side of the table
- 01Name the decision
Start with what the Council must be able to decide.
- 02Understand the gate
See what the Secretariat tests before agenda entry.
- 03Transform information
Turn facts into meaning and one institutional position.
- 04Test readiness
Answer all five decision questions visibly.
- 05Protect confidence
Catch gaps before they become a formal return.
What you will be able to do
01Map the Council and Secretariat roles
02Build decision-support products
03Run the five-question diagnostic
04Quantify the cost of a return
05Think like the first reviewer
The five questions every submission must answer
- 1What exactly is being asked or decided?
- 2Why now?
- 3What is the evidence?
- 4What are the implications?
- 5What do we recommend — precisely?
If any of the five is missing, the submission is not decision-ready. Full stop.
Explore the ideas
Open a card for the key message, the logic behind it, what good looks like and a practical example.
↗Visual briefThe decision sentenceCan the reader name the decision in one sentence?
Key messageCan the reader name the decision in one sentence?
01DECISIONComplete: “Because of this, the Council can decide…”
02SIGNALIf the sentence is hard for you, it is harder for the reviewer.
03SHIFTStart with the decision — not the template.
Why it matters
Senior readers cannot act on a broad topic; they act on a clearly framed decision. The decision sentence exposes whether the submission has a real purpose.
What good looks like
One sentence names the decision, its subject and the intended outcome—without background, process language or vague verbs.
Practical example
“Approve Option B to close the surveillance gap by Q4, within the proposed budget.”
The question that changes everything
What decision did your last submission enable?
Think of the last memorandum, executive brief, presentation or status report your team sent to the Executive Council.
Submission
01Memorandum→
02Executive brief→
03Presentation deck→
04Status report→
The hesitation is the signal
If your team cannot clearly state the decision, it is likely unclear to the reader.
1The submission may not be organised around the decision.2The recommendation may not be explicit.3The reader may not know what action is required.4The submission may be returned rather than decided.
Why submissions come back
There was not enough to decide
The paper described the issue but did not establish a decision-ready case.
It answered a different question
The work may have been strong, but it solved the wrong problem.
Change the lens
Current lens: ADAFSA’s side
- What work have we completed?
- What information do we have?
- What do we want to explain?
- What should we include?
Course lens: the decision-maker’s side
- What am I being asked to decide?
- Why is the decision needed now?
- What evidence do I need?
- What are the options and implications?
- What action is required from me?
The journey framework
01Request taxonomy02Intake and clarification03Evidence and analysis04Executive writing05Options and recommendations06Quality gates
1Visual briefCouncil & SecretariatThe Secretariat is a gate — not a letterbox.
Key messageThe Secretariat is a gate — not a letterbox.
01SCREENIs the submission decision-ready?
02PROTECTKeep weak items away from scarce Council time.
03PASSClear ask, evidence, implications and recommendation.
Why it matters
The Council operates at the highest decision altitude. Its Secretariat screens submissions to protect limited agenda time and ensure every item can support a decision.
What good looks like
The first page makes the ask, evidence, implications and recommendation immediately visible. The reader never has to reconstruct the logic.
Practical example
A progress update is informative; a paper seeking approval for a defined option, cost and timeline is decision-ready.
From ADAFSA’s desk to an Emirate decision
Where the Executive Council sits—and why that matters at your desk
Decisions at this altitude shape the Emirate for years. The Secretariat protects that decision environment before any paper reaches the agenda.
Executive Council
The Emirate’s executive decision-making authority
Emirate strategiesPolicies and regulationsBudgets and major allocationsStrategic programmes and initiativesExpansion, redesign or closure of programmes
General Secretariat of the Executive Council
The machinery around the Council
Coordinate the flow of businessScreen entity submissionsQuality-control agenda materialsPrepare matters for considerationFollow up decisions and directives
Government entities, including ADAFSA
Develop and submit decision-ready material
Own the technical factsBuild the institutional positionSubmit through the formal process
The gate: General Secretariat
Not a letterboxIt applies readiness standards; it does not merely pass documents through.
What happens at the gate?
Requirement check
Does the submission answer what was requested?
Decision-readiness check
Can the Council understand the issue and act?
Evidence and quality check
Are the facts, analysis and implications sufficient?
Agenda-readiness check
Is the submission suitable for senior consideration?
Readiness paths
Ready
- Scheduled or progressed through the formal process
- Presented for senior consideration
- Decision enabled
Not ready
- Returned to the entity
- Clarification or rework requested
- Resubmitted when strengthened
Why submissions come back
01Decision sought is unclear02Request was not fully answered03Evidence is incomplete or unsupported04Options and implications are missing05Recommendation cannot be acted upon06Council time would be consumed without enabling a decision
What the gate protects
Council time
Only matters ready for consideration reach the agenda.
Decision quality
Submissions must support informed judgement.
Agenda discipline
Senior attention is reserved for issues requiring senior action.
Institutional credibility
Poorly prepared submissions weaken confidence in the submitting entity.
Reader hierarchy
The Secretariat
Is this ready to support a decision?
Senior officials and advisers
Are the evidence, options and implications credible?
The Council
What are we being asked to decide?
What this means at your desk
- Is the requested decision explicit?
- Does the submission satisfy the Secretariat’s likely test?
- Can a first reader understand the issue quickly?
- Are options, implications and recommendation clear?
- Would I allow this to consume Council attention?
2Visual briefDecisions, not documentsYou are in the decision business.
Key messageYou are in the decision business.
01INPUTDepartments provide the facts.
02SYNTHESISStrategy creates the meaning.
03OUTPUTLeadership receives a precise recommendation.
Why it matters
Raw departmental facts transfer the work of synthesis to the reader. Strategy adds value by turning those facts into meaning and a defensible recommendation.
What good looks like
Lead with the answer, organise two to four supporting arguments, and use only the evidence needed to prove them.
Practical example
Replace forty pages of programme history with six pages covering the gap, options, implications and recommended decision.
From document to decision-support product
You are not sending documents—you are enabling decisions
A submission is a purpose-built decision-support product for a busy, senior, non-specialist reader to decide quickly and defensibly.
Example request through the Secretariat“Assess ADAFSA’s readiness for a livestock disease outbreak and identify any action required.”
40-page compiled report
- History of veterinary services
- Organisational structure
- Awareness campaigns over three years
- Vaccination activity by region
- Detailed departmental updates
- Are we ready?
- Where is the critical gap?
- What are the consequences?
- What will it cost to close the gap?
- What does leadership need to decide?
01Collect departmental inputs02Compile all information03Transmit to the Secretariat
Six-page decision-support product
- 1Ask · answer · recommendation
State the judgement and the exact approval required.
- 2Current situation
One honest readiness exhibit: where we stand today.
- 3Critical gap
Where current capability falls below the required standard.
- 4Options
Practical alternatives to close the gap.
- 5Implications
Financial, legal and operational implications of each option.
- 6Recommendation and decision sought
Preferred option, owner, timeline and exact approval required.
01Interpret the request02Analyse the facts03Recommend the best way forward04Enable a decision
Mindset shift
What information should we include?→Prioritise what matters
Compile departmental inputs→Lead with the answer
Describe activity→Complete the analysis before submission
From facts to answer
Meaning: what do the facts collectively show?
Judgement: what is the current position?
Relevance: what matters to this request?
Options: what can realistically be done?
Recommendation: what should leadership choose?
Decision ask: what exact approval or direction is required?
Ownership model
Departments own the facts
- Accuracy
- Technical depth
- Operational feasibility
- Evidence quality
Strategy owns the meaning
- Interpretation
- Integration
- Prioritisation
- Executive narrative
- Options and implications
- Recommendation and decision sought
The last point in the chain
01Departments understand the substance02Strategy understands the substance and the ask03Secretariat understands the process and applies the standards04Executive Council owns the decision
Test ownership of the answer
A department sends 15 pages of input. Whose job is it to determine what those pages mean for the decision?
Ours. The department’s responsibility ends with accurate input; Strategy’s begins with interpretation.3Visual briefInside the reviewer’s first passThe first review happens in minutes, not hours.
Key messageThe first review happens in minutes, not hours.
01ASKCan it be found immediately?
02CONSISTENCYDo text, tables and annexes agree?
03IMPLICATIONSAre cost, law and delivery covered?
Why it matters
A Secretariat reviewer may decide within minutes whether a submission deserves deeper review. Hidden asks and inconsistent figures create an easy reason to return it.
What good looks like
A two-minute scan reveals the ask and recommendation; totals reconcile; financial, legal and operational implications are covered.
Practical example
If page two requests funding but the annex shows a different total, the submission loses credibility before the analysis is considered.
The first three minutes under queue pressure
A day in the life of a Secretariat reviewer
Under queue pressure, a reviewer does not reward effort—she tests whether the submission can support a decision as it stands.
Monday morning: the queue
The first-pass scan: two to three minutes
The ask
What exactly is ADAFSA requesting?
The recommendation
Is there a clear, precise course of action?
The numbers
Do the figures reconcile across the document?
The implications
Are funding, budget, legal, operational and cross-entity consequences addressed?
The asymmetry of effort
Submission is complete
Hours- Understand and brief the issue upward
- Coordinate relevant entity views
- Resolve dependencies
- Prepare agenda materials
- Slot the item to a crowded agenda
- Support senior consideration
Submission is incomplete
About 15 minutes- Identify missing elements
- Draft the return note
- Request clarification or revision
- Send it back to the entity
The governing question
“If this goes on the agenda as it stands, can the members decide it?”
What the reviewer may flag
- Ask is not visible or is unclear
- Recommendation is not actionable
- Numbers do not reconcile
- Funding implications are not addressed
- Legal or regulatory implications are missing
- Dependency on another entity is unresolved
- Too much background before the answer
- Annexes are doing the work of the main document
The mirror inside ADAFSA
Departments
Own operational facts, records, technical evidence and expertise.
Strategy
Adds interpretation, judgement, integration, options, implications and recommendation.
Secretariat
Applies the same readiness test one level higher.
Apply it to your last submission
What would the reviewer have flagged in the last submission you worked on?
4Visual briefThe five-question testFive complete answers determine readiness.
Key messageFive complete answers determine readiness.
0101–02What is decided — and why now?
0203–04What proves it — and what follows?
0305What do we recommend, precisely?
Why it matters
The five questions are a readiness diagnostic, not a document template. Together they connect purpose, urgency, evidence, consequences and action.
What good looks like
All five answers are explicit and consistent. None is left for the reviewer to infer from background text or annexes.
Practical example
For enhanced import screening: specify the approval sought, the emerging risk, the supporting data, the cost and legal impact, and the exact recommendation.
Pre-submission diagnostic
The five questions every submission must answer
A submission is decision-ready only when the ask, urgency, evidence, implications and recommendation are unmistakably clear.
The goal at the gate
Assemble a Council agenda where every item can be decided. Council time is fixed; the submission queue is not.
What exactly is being asked or decided?
The decision sought
- Approve funding
- Endorse a policy direction
- Approve a programme or initiative
- Issue a directive
- Note information
- Select between options
Can the requested action be stated in one precise sentence?
Why now?
What triggered the need for attention?
- Council request or prior directive
- Approaching deadline
- Emerging risk or incident
- Federal or regulatory development
- Budget planning
- Deteriorating performance trend
- Strategic opportunity
Why should leadership decide this now rather than next quarter?
What is the evidence?
Does the analysis support the recommendation?
- Relevant data and results
- Benchmarks
- Field findings
- Cost and benefit analysis
- Risk analysis
- Measured outcomes
Does every material claim have decision-relevant support?
What are the implications?
What follows if we act?
- Financial: total cost, funding source, recurring commitments
- Legal: required instrument, existing authority, regulatory amendments
- Operational: staffing, capacity, systems, timeline and dependencies
- Social and market: impact on farmers, businesses, consumers and prices
Who pays, who implements, under what authority and with what consequence?
What do we recommend—precisely?
The actionable recommendation
- Preferred option
- Approval or direction required
- Cost and funding source
- Start date
- Responsible entities
- Delivery timeline
- Key conditions
Could the Council adopt the recommendation as a decision with minimal rewriting?
Five-out-of-five test
Readiness rule: Five out of five: ready for quality review. Four or fewer: fix before submission.Failure patterns and likely reviewer response
Clarify the decision sought.
Why is this required now?
Provide supporting analysis.
Address financial, legal and operational impacts.
Specify the proposed course of action.
The mirror: same logic one level down
01Departments provide facts, data, technical evidence and expertise02Strategy interprets, integrates and builds the answer03Secretariat tests the submission using the same logic
Test your hypothesis
Which of the five questions do your submissions most often under-answer—and why?
Treat the five questions as a diagnostic, not a template. Always confirm current Secretariat formats and procedures through official channels.
5Visual briefCost of a returnA return costs far more than the rework.
Key messageA return costs far more than the rework.
01TIMEThe decision loop can lose weeks.
02TRUSTInstitutional credibility is depleted.
03CAPACITYUrgent rework crowds out the next request.
Why it matters
A return restarts the institutional loop: reassignment, new inputs, synthesis, clearance and re-entry into the agenda queue. The cost extends far beyond editing time.
What good looks like
Quality is built at the source, leadership signs defensible material, and the Authority develops a reputation for reliable submissions.
Practical example
Three days of rework can become several weeks of decision delay once coordination, approval and agenda timing are included.
From visible rework to Emirate-wide impact
The true cost of a return—and why ADAFSA’s voice carries beyond ADAFSA
“We will fix it and resend” is not the real cost. The visible revision is only the beginning of the return loop.
The four major costs
Time
Weeks in the Emirate decision cycle
Credibility
Institutional trust weakens with every avoidable return
Leadership protection
Weak papers expose leaders and the Authority to unnecessary risk
Team capacity
Returns consume time and reduce the quality of everything else
1. Time: the full return loop
- Amend the document
- Request missing inputs
- Correct figures
- Revise the recommendation
- Repeat internal approvals
- Resubmit
01Returned by Secretariat02Logged and assigned03Departments re-tasked04Inputs re-prioritised05Submission re-synthesised06Internal clearance repeated07Resubmitted08Re-enters the agenda queue
What is delayed?Infrastructure delivered laterAnimal-health measures laterProgramme funding delayedRegulatory action postponedStrategic opportunities missed
2. Credibility: the trust account
- Reliable evidence
- Clear decision sought
- Complete implications
- Consistent figures
- On-time delivery
- Increased scrutiny
- Lower confidence
- Reduced flexibility
- More questions on future papers
- Reputation for unreliable submissions
The Secretariat remembers patterns, not isolated documents. This shapes how future submissions are read.
3. Leadership exposure
What leadership stands behindEvery numberEvery assumptionEvery implicationEvery recommendationEvery omission
Puncture points that trigger return- Unsupported evidence
- Missing legal authority
- Conflicting figures
- Unaddressed delivery risk
- Unfunded recommendation
- Missing implementation capacity
Quality assurance protects the credibility of the Authority’s leadership.
4. The rework loop
1Submission is returned2Return becomes urgent3Team abandons planned work4Next submission gets less time5Quality falls6Return risk rises
5. ADAFSA’s voice carries beyond ADAFSA
Expert domainsFood securityFood safetyBiosecurityAgricultureAnimal and plant healthSupply resilience
What they influenceEconomic resiliencePublic confidenceSovereign readinessEmirate reputation
From our desk to Emirate impact01Analyst’s desk02ADAFSA submission03Secretariat review04Executive Council decision05Emirate policy, funding or capability06Real-world outcomes
Examples of outcomesStronger supply resilienceSafer food systemsFaster disease containmentBetter-supported producersHigher public confidence
Exercise — The Five-Question Audit
Key messageAudit three recent submissions before the reviewer does.
013 CASESChoose recent, real requests.
025 QUESTIONSScore every decision answer.
031 PATTERNName the recurring gap to fix.
Why it matters
The five questions become useful only when they are applied consistently to real submissions rather than remembered as theory.
What good looks like
Compare several recent cases, score them honestly and identify the repeated gap that most often weakens decision-readiness.
Practical example
If “What are the implications?” is repeatedly weak, add a mandatory implications check before internal clearance.
Guided self-practice
The Five-Question Audit
Apply the decision-readiness test to your last three real submissions and identify where quality gaps cluster.
Scoring methodYClearly and visibly answered2PIncomplete, ambiguous or buried1NNot answered0
Case01What was required?02Why now?03What was the evidence?04What were the implications?05What was recommended?Actual outcome
Complete the audit in 15 minutes
- 2 min01Recall
List three recent requests you personally handled, contributed to or reviewed.
- 6 min02Score
Assess the version that actually went out against the five questions.
- 4 min03Compare
Locate where P and N scores cluster and compare accepted versus returned cases.
- 3 min04Reveal
Build your personal heat map and name the first corrective habit.
Scoring discipline: apply the reviewer’s standard
“The funding implications were somewhere in the annex.”
P at best“The recommendation could be inferred from the conclusion.”
P or N“We discussed it verbally during internal review.”
N in the submitted paperYour personal gap map
Likely pattern and interpretation
How outcomes correlate with the five questions
Usually mostly Y scores; all five answers are visible
Usually several P scores; important elements are present but incomplete
Usually one or more N scores; material gaps prevent progression
Learn from strong cases
Your personal baseline
The shift we make today
The Secretariat identifies the gaps after submission; we receive the return.
Strategy identifies and fixes the gaps before submission; we enable progression.
Hypothesis to test
Implications and precise recommendations are often the weakest answers. Confirm the pattern against your own cases.
Action gate
Score only what the reviewer can see—not what the team knew. Buried or inferred is not answered.
Questions to reflect on
Reflect and apply
See the submission through the gate
Use a real case and answer from the reviewer’s perspective.
Diagnose a return
Which of the five questions did the last returned submission fail, and who could have caught it before it left?
Missing answerInternal ownerEarly catch
Mirror the gate
Where do we return weak departmental inputs ourselves, and what does that teach us about the Secretariat’s role?
Same dynamicQuality at source
Choose precision
Why do vague recommendations feel safer, and what would make precise commitments culturally easier?
Decision riskAccountabilityService
Respect the mandate
What evidence standard follows from ADAFSA being a principal expert voice in its mandate?
AuthorityEvidenceCredibility
Locate synthesis
Where does information become an institutional answer today—in Strategy, in departments or nowhere?
FactsMeaningAnswer
Earn confidence
What would give an ADAFSA submission a confident first read, and how quickly can that confidence be lost?
ConsistencyTrack recordTrust
Decision ruleA submission is a decision-support product — not a document.
01The gateThe Secretariat protects Council time.
02The testAnswer all five decision questions.
03The costReturns delay decisions and erode trust.
Embed the practice in daily work
From gatekeeping to trusted first read
ADAFSA earns a confident first read when every submission converts expert evidence into a precise, complete and defensible decision request.
Our goal
Enable the Executive Council to decide with clarity, confidence and speed.
Seven key takeaways
- 1
The Secretariat is the gate: it screens and quality-controls every submission before the agenda.
- 2
The product is a decision: submissions help a senior reader decide, not display everything the Authority knows.
- 3
Every paper must answer the ask, why now, evidence, implications and precise recommendation.
- 4
Gaps create the return path: an incomplete paper gives the reviewer a fast and legitimate reason to send it back.
- 5
Returns have system-wide costs: delayed decisions, weaker credibility, leadership exposure and less team capacity.
- 6
ADAFSA’s voice carries weight on food security, food safety and biosecurity.
- 7
Audit before submission while every gap is still cheap to fix.
Ownership model
Departments
Own the facts and raw inputs.
Strategy sector
Owns synthesis, meaning, options and recommendation.
Leadership
Owns the recommendation and institutional position.
Secretariat
Tests whether the product is ready for a decision.
Executive Council
Can decide with confidence.
Common challenge and reframe
Ambiguity makes disciplined decoding more important, not optional.
Return or strengthen weak inputs internally; do not transmit them upward unchanged.
Formats evolve. The five governing questions remain stable; confirm current specifics officially.
Price “eventually” in elapsed days, delayed decisions and displaced team capacity.
Tone and credibility discipline
- Systemic blame
- Naming individual failures
- Inventing unofficial rules or procedures
- Describe the pattern as craft and process
- Confirm current requirements officially
- Model the evidence discipline expected in the submission
Signals of a trusted first read
1Visible ask2Precise recommendation3Reconciled figures4Complete implications5Proportionate evidence6Consistent track record
Next stage
Next: control the request before weak interpretation enters drafting
- What type of request is this?
- What is the question behind the question?
- Which assumptions need confirmation?
- What exact output is required?
View all takeaways
- The Executive Council is the executive authority of the Emirate; its General Secretariat (الأمانة العامة للمجلس التنفيذي) is a gate, not a letterbox — it screens and quality-controls everything before it reaches the agenda.
- You are not sending documents; you are enabling decisions. Every submission is a decision-support product, and decision-readiness — not completeness of inclusion — is the standard.
- Five questions decide a submission's fate: What exactly is being asked or decided? Why now? What is the evidence? What are the implications? What do we recommend — precisely?
- The reviewer's fastest legitimate path is the return; every unanswered question is an invitation to take it.
- A return costs weeks of Emirate-level delay, erodes institutional credibility, exposes leadership to decision risk, and buries a small team in rework — quality at the source is the only sustainable model.
- On food security, food safety and biosecurity, ADAFSA is one of the Emirate's principal expert voices — on the matters within our mandate, the Authority's contribution is one nobody else can substitute; the weight is real and so is the privilege.
- The Five-Question Audit is now your habit: run it before submission, not after the return.
Module 03
Intake Discipline
One front door, and a plan that starts from the deadline
- 01Log
One front door, one ID and one visible record.
- 02Triage
Match the machinery to complexity and deadline pressure.
- 03Clarify
Batch questions early and show your interpretation.
- 04Confirm
Turn interpretation into an institutional Restated Ask.
- 05Plan backwards
Protect synthesis, quality and sign-off time.
- 06Task precisely
Mobilise departments only after direction is clear.
What you will be able to do
01Log every request at one front door
02Select the right response track
03Clarify once and early
04Confirm the Restated Ask
05Back-plan with a protected buffer
Explore the ideas
Open a card for the key message, the logic behind it, what good looks like and a practical example.
↗Visual briefThe first-hour effectThe first hour sets the cost curve.
Key messageThe first hour sets the cost curve.
01DIRECTIONInterpret before departments mobilise.
02TIMINGReserve time for synthesis and review.
03REWORKA wrong start is discovered when time is gone.
Why it matters
The first hour determines the direction of every department that follows. A weak start remains hidden until inputs return and the timeline is already spent.
What good looks like
Create control before motion: log the request, interpret it, select the track and reserve time for synthesis and review.
Practical example
Forwarding a raw request in ten minutes feels fast; clarifying it for one hour can prevent days of contradictory rework.
Detailed visual guide
The first-hour control sequence
The first hour determines whether the team gains direction or merely creates motion.
01
Log
Create one traceable record before the request lives in private inboxes.
02
Triage
Match ownership and process to complexity and deadline pressure.
03
Clarify
Batch every material question once and early, with a proposed interpretation.
04
Confirm
Make the Restated Ask an endorsed institutional position.
05
Plan backwards
Protect synthesis, quality review, sign-off and a roughly 20% buffer before tasking.
1Visual briefOne front doorIf it is not logged, it does not exist.
Key messageIf it is not logged, it does not exist.
01IDCreate a traceable request record.
02OWNERName one accountable person.
03DEADLINECapture the exact date and time.
Why it matters
Requests held in individual inboxes are invisible to the institution. A single front door creates continuity, accountability and a reliable audit trail.
What good looks like
Every live request has a unique ID, one accountable owner, the exact deadline and a traceable source from the day it arrives.
Practical example
If the owner is on leave, another team member can still see the request, its status and the next required action.
If it is not logged, it does not exist institutionally
The single front door: if it is not logged, it does not exist
Every Council or senior-office request enters once, is logged immediately and is owned through submission.
The scenario we all know
Monday afternoon
Request arrives by email from the General Secretariat.
Tuesday
A section head sees an accompanying field visit to date-palm farms.
Wednesday
The email is opened and forwarded to the director.
Thursday morning
The request finally surfaces in a conversation.
Why the inbox model fails
✉×
- Visible to one person only
- Vulnerable to absence
- Difficult to track
- Easy to overlook
- Hard to hand over
- Disconnected from portfolio priorities
- Missing a reliable audit trail
The single front door: one entry, one record, one owner
Request ID
One identifier for the full lifecycle.
- Emails
- Tasking notes
- Departmental inputs
- Drafts
- Review comments
- Final submission
- Follow-up actions
Named owner
One accountable person from intake to submission.
- Confirm interpretation
- Coordinate inputs
- Maintain the schedule
- Escalate risks
- Drive internal clearance
- Confirm submission
Deadlines
Record the external deadline and derive internal ones.
- Secretariat submission
- Leadership sign-off
- Quality review
- Draft complete
- Departmental inputs
The 30-second accountability test
“Where are we on the Council request about the food-security dashboard?”
Without a log
- Search inboxes
- Call several colleagues
- Reconstruct the history
- Give an uncertain answer
With a log
- Named owner
- Current status
- Next milestone
- Deadline
- Current risk
- Latest document version
The log begins the audit trail
1Request received2Logged with date and time3Owner assigned4Interpretation confirmed5Departments tasked6Draft reviewed7Leadership approved8Submission sent9Decision followed up
Who knew what—and when?The process survives people and circumstances
Annual leaveSick leaveField visitsStaff transfersRestructuringCompeting priorities
The operating rule: non-negotiable
- Capture or forward through the single intake channel
- Log within hours of receipt
- Assign one named owner
- Record the external deadline
- Trigger triage and backward planning
The platform may vary; the discipline cannot.
2Visual briefSelect the response trackUse machinery proportionate to risk and urgency.
Key messageUse machinery proportionate to risk and urgency.
01FASTKnown answer, narrow scope.
02STANDARDSeveral inputs, normal governance.
03COMPLEXCross-entity, high-risk or ambiguous.
Why it matters
Using the same process for every request either overloads simple work or under-governs risky work. Triage keeps effort proportionate.
What good looks like
Classify on two dimensions—complexity and deadline pressure—then select fast, standard or complex handling.
Practical example
A factual answer due tomorrow may be fast-track; a cross-entity policy proposal due in fifteen days may still require the complex track.
Proportionality determines the machinery
Triage: match the machinery to the request
Every request needs discipline, but not every request needs the same ownership, coordination and review.
Opposite failures from one root: no triage
Over-processing
- Too many meetings
- Excessive review layers
- Senior attention wasted
- Simple responses delayed
- Team fatigue
Under-processing
- Complexity discovered late
- Dependencies unmanaged
- Leadership informed too late
- Cross-government input missing
- Submission overwhelms the team
The two triage axes
Axis 1: complexity
Single-department
- One main evidence source
- Limited coordination
- Factual or narrowly defined
Example: Updated figures on abattoir inspections
Cross-department
- Several ADAFSA divisions
- Inputs must be integrated
- Definitions and positions aligned
Example: Progress against food-security indicators
Cross-government or sensitive
- External government entities
- Strategic or political implications
- Major policy, budget or regulatory decision
Example: Animal-disease emergency preparedness
Axis 2: deadline pressure
Comfortable
Enough time for normal tasking, synthesis, review and approval
Tight
Possible, but milestones and escalation must be activated early
Immediate
Hours or a few days; speed must shape the response design from the start
Triage matrix: cross the axes to choose the track
ComfortableTightImmediateSingle-departmentFast-trackFast-trackFast-track with escalationCross-departmentStandardStandard with accelerated checkpointsComplex: urgent mobilisationCross-government or sensitiveComplexComplexComplex: executive response
Quick track-selection test
- 1More than one ADAFSA department?
- 2Another government entity, sensitive issue or major decision?
- 3Deadline tight relative to the work required?
When uncertain, escalate the provisional track and simplify after verification.
What changes by track / What never changes
What changes by track
- Owner seniority
- Who is informed and how often
- Number of stakeholders
- Depth of coordination
- Review and challenge level
- Checkpoints and escalation
- Type and extent of deliverables
What never changes
- Log entry
- Confirmed ask
- Recorded deadline
- Backward plan
- Quality check
- Clear submission record
Fast-track: simple, focused, factual
Best for
- Single-department request
- Factual response
- Limited synthesis
- Narrow scope
- Short or manageable deadline
Ownership
Analyst or senior analyst; section head informed
Proportionate process
1Log2Confirm ask3Obtain targeted input4One quality check5Secure sign-off6Submit
Typical products
- Data table
- Short factual note
- Brief response
- Updated figures
Failure to avoid: Adding five layers of review to a simple two-page response.
Standard: integrated internal work
Best for
- Cross-department request
- Normal or moderately tight timeline
- Strategic update
- Integrated brief
- Several internal perspectives
Ownership
Senior analyst or section head; directors informed at tasking
Proportionate process
1Log and assign2Restated Ask3Tasking notes4Backward plan5Coordinate inputs6Resolve gaps7Quality gate8Leadership sign-off9Submit
Typical products
- Strategic status update
- Cross-functional briefing
- Executive presentation
- Short memorandum
Complex: cross-government, sensitive or decision-heavy
Best for
- Cross-government request
- Political or reputational sensitivity
- Significant Council decision
- New programme
- Regulatory change
- Budget commitment
- High uncertainty
Ownership
Section head or director; executive leadership informed on day one
Proportionate process
1Kick-off2Workstream leads3Stakeholder and dependency map4Early submission skeleton5Interim checkpoints6Early implications analysis7Senior challenge8Escalation plan
Typical products
- Decision memorandum
- Policy proposal
- Funding request
- Cross-government response
- High-stakes brief
3Visual briefClarify once, earlyClarify once, early, and with a point of view.
Key messageClarify once, early, and with a point of view.
01BATCHSend every material question together.
02EARLYDay one or two — never at the end.
03INTERPRETOffer your reading, then ask to confirm.
Why it matters
Early clarification signals careful reading. Late or fragmented questions signal that the request was not understood until the deadline was already at risk.
What good looks like
Send one organised batch in the first day or two. State your interpretation and ask the requester to confirm or choose between specific alternatives.
Practical example
“We understand the request to cover current-period KPI performance and corrective actions. Please confirm whether revised targets are also required.”
Professional clarification begins with analysis
Asking well: the clarification protocol
A well-framed clarification sent early signals diligence. A wrong submission signals weakness.
✉
The ambiguous request arrives
“Provide an update on food-security performance and the way forward.”
The myth
“Going back with a clarification question makes the Authority look weak.”
The reality
- The request was read carefully
- Ambiguity was identified early
- Consequences of different interpretations were understood
- Rework was prevented early
What actually signals weakness?
- Answering the wrong question
- Discovering ambiguity late
- Sending repeated follow-up questions
- Requiring a second submission cycle
When is clarification legitimate?
Is the ambiguity material?
Would two reasonable interpretations produce materially different scope, evidence or approval?
Scope
- Fresh produce imports only or all categories?
- Abu Dhabi Emirate only or UAE-wide?
- Current programme or full historical period?
Decision sought
- Note progress?
- Endorse direction?
- Approve funding?
- Select an option?
Format and depth
- Two-page brief?
- Presentation deck?
- Full memorandum with exhibits?
- Technical annex required?
Deadline meaning
- Entity submission date?
- Secretariat screening date?
- Leadership review date?
- Council session date?
The clarification formula
State our interpretation
“We understand the request to require…”
Confirm or correct
“Kindly confirm whether this interpretation is correct…”
Present the specific fork
“…and advise whether the submission should include X or remain limited to Y.”
What is not legitimate clarification
“What do you mean by paragraph two?”
“Please explain what is required.”
“What information would you like?”
“Can you provide more details?”
“Please clarify the request.”
What it signals
- No interpretation attempted
- Burden transferred to the requester
- Too broad to answer efficiently
- Weak analytical preparation
The three rules
Batched
Ask all material questions together in one analysed and structured note.
Avoid the drip: repeated questions say “we are still confused”.Once
Pressure-test the batch internally with the owner, section head and director where needed.
Use one professional opportunity; do not substitute the requester for internal analysis.Early
Send within the first day or two—never in the final days.
Day 1–2 shows diligence; days 3–6 increase risk; days 7–10 expose delay.Worked example: a batched clarification note
Our understandingWe understand the request to require a current-period assessment of performance against approved food-security indicators, including material gaps, causes and corrective actions.
Scope
Current period indicators only or complete Emirate indicator set?
Decision sought
Is the paper intended to inform, endorse targets or seek approval?
Deliverable
Short executive brief or full memorandum with exhibits?
Deadline
Receipt by Secretariat or completion of internal screening?
When ambiguity appears late
- Do not create avoidable delay with an open-ended question
- Form the most reasonable interpretation
- Record the assumption explicitly
- Assess risk and escalate to leadership
- State the interpretation transparently
- Flag any material limitation or alternative reading
Channel and audit trail
1Request owner prepares clarification2Internal review and approval3Leadership or authorised channel4General Secretariat5Response received6Request file updated
4Visual briefConfirm the Restated AskMake the interpretation institutional.
Key messageMake the interpretation institutional.
01RESTATEWrite the ask in one paragraph.
02CONFIRMRequester or accountable ADAFSA leader.
03RECORDKeep the agreement in the audit trail.
Why it matters
Interpretation creates risk. Confirming the Restated Ask turns one analyst’s reading into an institutional position that can be defended later.
What good looks like
State what is wanted, by when, in what form and on which assumptions; obtain confirmation and retain it in the request record.
Practical example
For a fast-track item, internal confirmation by the accountable ADAFSA leader may be proportionate when external clarification is unnecessary.
From personal judgement to institutional position
The Restated Ask: making the interpretation institutional
An interpretation becomes safe to act on only when it moves from one person’s judgement into an endorsed institutional position.
A request arrives
“Provide an update on the farmer support programme.”
The hidden work
- What exactly is required?
- What is the expected output?
- What decision will this support?
- Who owns the interpretation?
The Restated Ask anatomy
Scope
What is included and excluded?
Deliverable
What product is required?
Deadline
When must it be ready?
Assumptions
What interpretation choices were made?
Decision context
What decision will this enable?
Why confirmation matters
Protects the analyst
- Without confirmation: “An analyst interpreted it incorrectly.”
- With confirmation: “The Authority made an endorsed interpretation based on available information.”
Protects leadership
- What assumption was made?
- Who reviewed it?
- Why was the approach selected?
- What risks were considered?
Improves the interpretation
- Scope errors
- Hidden assumptions
- Missing stakeholders
- Wrong decision framing
- Wrong output expectations
Confirmation pathways
External confirmation: gold standard
Use when- Ambiguity is material
- Interpretations change the work
- Time allows clarification
- Decision stakes are high
1Restated Ask prepared2Batched clarification3Requesting office confirms or corrects4Shared interpretation in writing
Your interpretation becomes their interpretation—in writing.Internal confirmation: proportionate alternative
Use when- Fast-track request
- Tight deadline
- Clarification is unnecessary
- Interpretation is sufficiently clear
1Restated Ask prepared2Accountable leader reviews3Agreement recorded4Institutional position
The Authority owns the interpretation.The risk ownership principle
Personal risk
“I assumed this was what they wanted.”
Institutional ownership
The Authority reviewed and endorsed this interpretation.
The five-minute habit versus weeks of rework
With the habit
- Write Restated Ask
- Confirm ownership
- Record agreement
- Proceed confidently
Without the habit
- Departments mobilised incorrectly
- Evidence collected for the wrong purpose
- Draft rewritten
- Deadlines compressed
- Additional reviews required
Common mistakes
“I wrote the Restated Ask, so it is done.”
Writing is only the first step; confirmation makes it institutional.
“We are experienced; we do not need confirmation.”
Experience reduces risk but does not remove interpretation risk.
“We will clarify if it becomes a problem.”
Late clarification is often discovered after resources are already committed.
The operating sequence
Log it
The request enters the institutional record.
Restate it
Convert the request into a clear interpretation.
Confirm it
Obtain external confirmation or internal endorsement.
Task it
Only now mobilise the departments.
5Visual briefPlan backwardTen working days becomes four.
Key messageTen working days becomes four.
01DAY 4Department inputs due.
02DAY 8Quality gate complete.
03DAY 9Leadership sign-off; hold the buffer.
Why it matters
The submission date is not the working deadline. Synthesis, quality review and leadership sign-off consume more than half of a typical ten-day window.
What good looks like
Plan from the deadline backward, protect roughly 20% as contingency and give departments the true input date—not the final submission date.
Practical example
On a ten-working-day request, inputs are commonly due around day four, quality review on day eight and leadership sign-off on day nine.
The input deadline is the real working deadline
Planning backwards: the true deadline is earlier than instinct suggests
The submission deadline is not the working deadline. Inputs must arrive early enough to protect synthesis, quality review and leadership decision-making.
The backward plan: what must happen before submission?
Department inputs due
The real deadline; ask early because one input will be late.
Input deadline at latest
Friday is a half day and leaves only the minimum synthesis time.
Synthesis and draft
Analyse inputs, identify gaps, build recommendation, draft narrative and exhibits.
Quality gate
Structured challenge of the five questions, evidence, logic, implications and consistency.
Leadership sign-off
Provide a full day for real review and approval.
Submission to Secretariat
Better practice is Thursday; keep Friday morning for rescue.
Two rules that protect the plan
The buffer rule
Keep about 20% of the total timeline in reserve: two days in a ten-day request.
- Returned inputs
- Data discrepancies
- Additional options
- Scope clarifications
- Unexpected dependencies
Never plan final-hour approval
- Final-afternoon approval
- Meetings overrun
- Leaders travel
- New questions emerge
- Review becomes rushed approval
Where did the days go?
Backward-plan template
Request loggedIntake ownerDay 0
Restated Ask confirmedRequest ownerDay 1
Department tasking issuedStrategy ownerDay 1
Department inputs dueContributorsDay 4
Synthesis completeStrategy teamDay 7
Quality gateReviewerDay 8
Leadership sign-offLeadership officeDay 9
Secretariat submissionRequest ownerDay 10 by noon
Why instinct fails
Instinct says
“We have ten days.”
Reality says
“We have ten days minus everything required to produce a decision-ready product.”
The module connection
Decode the request
Control intake and timeline
Task departments using the real input deadline
Quick check
6Visual briefMotion vs progressHalf a day of discipline prevents days of rework.
Key messageHalf a day of discipline prevents days of rework.
01RESISTDo not forward the raw request.
02SEQUENCELog → triage → clarify → plan.
03TASKMobilise departments with precision.
Why it matters
Urgency creates an instinct to forward the request immediately. That motion feels productive but multiplies inconsistent interpretations and later rework.
What good looks like
Complete the intake sequence before tasking: log, triage, clarify, confirm and back-plan. Departments then receive one precise direction.
Practical example
Four departments responding to one interpreted brief produce compatible inputs; four departments interpreting the raw request produce four different answers.
Direction first, distribution second
The emotional trap: motion is not progress
The first impulse is to act. Professional discipline creates direction before creating activity.
The emotional impulse
What was actually sent?
“Please provide your inputs.”
What was missing?
- No Restated Ask
- No scope boundaries
- No expected format
- No decision context
- No evidence requirements
- No true internal deadline
The multiplication effect: one request, four interpretations
Operations
Interprets it as: Data request
Produces- Numbers
- Tables
- Statistics
Policy
Interprets it as: Strategic update
Produces- Narrative
- Progress summary
- Challenges
Technical team
Interprets it as: Technical assessment
Produces- Risk analysis
- Technical detail
Finance
Interprets it as: Resource question
Produces- Cost information
- Historical spending
The cost of the shortcut
Started quickly: raw request forwarded
Inputs return with different assumptions, formats, scopes and missing evidence
Re-explain, re-task, rewrite, lose synthesis time and consume contingency
Fast start becomes slow finish
The professional alternative: first hours belong to intake
Log
Create visibility and ownership
Triage
Understand complexity, urgency and stakeholders
Clarify
Resolve material ambiguity once and early
Confirm
Create a shared Restated Ask
Plan backwards
Protect the real deadline and buffer
Task
Mobilise departments with precision
Reframe the feeling
Anxious instinct
“If I have not forwarded something, I have not started.”
Professional discipline
“If I have not clarified the work, I have not started the right work.”
The driving analogy
Leave immediately
- Speed high from the start
- Wrong direction
- Multiple detours
- Late arrival
Plan for ten minutes
- Route defined
- Correct destination
- Fewer corrections
- Early arrival
Test the difference
?
Think of the last request you forwarded immediately. What ambiguity did you distribute?
Exercise — The Ten-Day Countdown
Key messageBuild the ten-day plan backwards.
01START AT 10Fix submission and sign-off first.
02PROTECT 20%Keep two days for the unexpected.
03LAND ON 4Set the true department-input date.
Why it matters
Backward planning makes the hidden work after departmental inputs visible and converts a vague deadline into an operational commitment.
What good looks like
Every milestone has a date and owner, the buffer is explicit, and the plan respects quality review, sign-off and Friday working hours.
Practical example
A strong ten-day plan places inputs near day four and aims to submit on Thursday, holding Friday morning as contingency.
Self-guided application exercise
The Ten-Day Countdown
A ten-day submission window does not mean ten days of departmental work. Backward planning reveals the real input deadline.
Illustrative scenario
Monday morning: the Secretariat asks for a memorandum on progress in strengthening biosecurity at poultry farms.
- Current control measures
- Gaps identified
- Recommended next steps
- Indicative costs
Your task: build a dated milestone plan backwards from submission
Receive
- Request ID
- Owner
- Deadline
- Required output
Decode
- Restated Ask
- Scope
- Decision context
- Evidence needs
Plan backwards
- Start from submission day
- Assign dates
- Assign owners
- Protect the buffer
Defend your plan
- Where is the buffer?
- Why this input deadline?
- Who owns each milestone?
- Is the sequence realistic?
Ten working days: work backwards
Intake logged and clarification batch sent if needed
Request owner
Restated Ask confirmed
Accountable leader
Department inputs due
Animal Health · Policy/Regulation · Finance
Buffer for late or missing inputs and reconciliation
Request owner
Synthesis, draft and exhibits
Strategy team
Quality gate
Independent reviewer
Leadership sign-off
DG or executive office
Submission to Secretariat
Request owner
Where does the time actually go?
Stress-test your plan
Common planning mistakes
- Giving departments days 7–8
- Placing work on weekends
- Clarifying after tasking
- No named owner
- No reserve or buffer
Your personal milestone plan
Questions to reflect on
Reflect and apply
Test your intake discipline
Use a live request and identify where control is currently lost.
Find the front door
What would happen to the last request in a personal inbox if its owner were absent?
VisibilityCoverAudit trail
Notice the urge
Where do you feel pressure to “just start”, and what rework has that motion caused?
AdrenalineRaw forwardingRework
Name the barrier
What stops early clarification: protocol, hierarchy, fear or habit—and which constraints are real?
ChannelConfidenceTiming
Test proportionality
Where are simple requests over-processed and complex requests under-processed?
FastStandardComplex
Protect the buffer
When a late input consumes the buffer, what must the owner do within 24 hours and who needs visibility?
Escalate riskReset planLeadership visibility
Set authority
Who can set the internal input deadline, and how is pushback against an “early” date resolved?
Accountable ownerBackward planDecision rights
Decision ruleThe first hours belong to intake — not tasking.
01ControlOne ID, one owner, one deadline.
02ClarifyOne early batch, with a point of view.
03PlanOn ten days, inputs are due around day four.
View all takeaways
- Every Council request goes through one front door: logged with a request ID, a named owner and a recorded deadline within hours of arrival. No request lives only in an inbox.
- Triage on two axes — complexity and deadline pressure — and place the request on one of three tracks: fast-track, standard or complex. The track sets who owns it, who is informed, and how much process is proportionate.
- Clarification questions are a sign of competence when they are batched, sent once, and sent early — never a drip, and never in the final days.
- Phrase every question as an interpretation to confirm plus a specific choice to make — do the work first, then ask.
- Confirm the Restated Ask with the requester or with ADAFSA leadership so the interpretation is owned institutionally and sits on the audit trail.
- Plan backwards from the deadline: subtract sign-off, quality gate and synthesis, and what remains — usually less than half the timeline — is the true department-input deadline. And respect the shape of the week: Friday is a half working day, so a Friday deadline means Friday noon — aim to submit on the Thursday.
- Keep roughly 20% of the timeline in reserve, never schedule leadership review for the last hours, and remember: rework is always slower than a disciplined first day.