Most executive support work begins with a message that describes a feeling rather than a request. A leader writes "can you sort out the board deck" and the assistant has to reconstruct scope, deadline, audience, and approval from context. A short intake form turns that ambiguity into a shared record before work starts. It also gives the desk a defensible reason to send a request back when key fields are missing.
Executive Support
Build an executive support intake form that stops vague requests at the door
A practical intake form design that captures the decision, deadlines, audience, and access an executive support desk needs before work begins.
Table of contents
Why vague requests create rework
A vague request forces the assistant to guess, and each guess is a branch that may need to be undone. The deck may need a new appendix, a different template, or a shorter version for a verbal update. When the guess is wrong, the rework is invisible in the original message thread. The desk absorbs the cost while the requester remembers only that the task was late.
Rework also hides the real bottleneck. A team may believe it lacks capacity when it actually lacks a clear request. Counting returned or reopened items shows how often the intake failed rather than the production step. That number is more useful than a general complaint about busy weeks, and it points to a fix the team can actually make.
Ask for the decision, not the task
A request should name the decision the output supports. "Prepare the board deck" is a task, while "give the board enough evidence to approve the facility lease" is a decision. The decision tells the assistant which sections matter and which can be cut. It also reveals whether the executive needs analysis, a recommendation, or only a status summary.
When the decision is unclear, the form should require a short answer rather than allow a blank. The requester can write "not sure yet" only if they also name the person who will decide. That second field keeps the request moving without pretending the ambiguity is resolved. The assistant can then route the question to the right owner before production begins.
Capture the deadline and the real deadline
Every request needs two dates, the date the output is due and the date the requester must review it. A deck due Thursday at nine usually needs approval Wednesday afternoon. Without the review date, the desk plans production to the final deadline and leaves no room for correction. The form should make both fields visible next to each other.
The real deadline often belongs to someone outside the conversation. A board packet may need to reach the chair's office a full day before the meeting, and a client proposal may need legal review first. Ask who receives the file and work backward from that handoff. The assistant can then flag a request that is already impossible instead of discovering it later.
Require the audience and output format
Audience changes tone, length, and detail. A one-page note for a chief executive is not the same artifact as a twelve-page appendix for a committee. The form should ask who will read the output and what they already know. That single answer prevents the most common revision request, which is to make the work shorter or more executive.
Output format should be explicit as well. A PDF, an editable document, a slide deck, and a spreadsheet each carry different production steps and review risks. Ask whether the file must be print-ready, accessible, or compatible with a specific system. The desk can then choose the right template before anyone starts writing, which removes a whole class of late-stage changes.
Add an attachment and access check
Many delays come from missing source material rather than missing effort. The form should list the files, links, and system access needed to complete the request. If the requester cannot provide them, the assistant records the gap and the owner who will supply it. This turns a blocked task into a visible dependency instead of a silent wait.
Access deserves its own line because it often takes longer than the work. A shared drive permission, a finance system view, or a calendar delegation can take a day to approve. The desk should confirm access before committing to a delivery time. A request that cannot be opened is not ready to be scheduled, no matter how urgent the message sounds.
Set a triage path for incomplete requests
The form only works if incomplete requests have a defined path. The desk should return the request within one business hour with the missing fields named. The requester can then complete it or ask for help, and the clock starts when the record is complete. This rule protects the desk from chasing information for days without a written agreement.
Some requesters will always send urgent, partial messages. The triage path should allow the assistant to create a draft record from the message and send it back for confirmation. That keeps the work moving while preserving the written scope. It also gives the desk evidence when the same gap appears repeatedly, which is the signal to change the form or the training.
Review the form quarterly
A form collects fields long after the reason for them is forgotten. Review the last quarter of requests and mark which fields were actually used in production. Remove fields that nobody reads and add ones that repeatedly appear in follow-up messages. A shorter form that people complete is better than a thorough form they bypass.
Review the return rate as well. If many requests come back for the same missing item, the field is either unclear or poorly placed. Rewrite the label and test it with two requesters before the next quarter. The form should evolve from observed friction rather than from a wish list of controls, and the desk should say so when it changes. For the approval side of the same problem, see our guide to replacing a status meeting with a weekly brief. For hands-on help with this work, review our executive support services. A useful control reference is the GAO Green Book, which treats clear documentation as part of internal control.
Key takeaways
- Require the decision, audience, and output format, not only a description of the task.
- Capture the delivery deadline, the review deadline, and the person who receives the final file.
- List required attachments and system access so a blocked request is visible before production starts.
- Return incomplete requests within one business hour with the missing fields named.
- Review a quarter of requests and remove fields that requesters and producers never use.
Frequently asked questions
What fields belong on an executive support intake form?
How should the desk handle an urgent request that arrives incomplete?
Who should own the intake form?
Keep reading
Related executive support guides.
Set a vendor renewal calendar for the executive office
A vendor renewal calendar that tracks contracts, owners, notice periods, and renewal risks before the auto-renewal date arrives.
Build a confidential paper destruction schedule for the executive suite
A paper destruction schedule that classifies sensitive documents, sets secure collection points, and records every shred or vendor pickup.
Run a weekly principal-preference check-in without adding meetings
A lightweight written check-in that keeps the desk aligned with a principal's changing preferences and catches drift early.