The web team handles requests from across the organization — content updates, landing pages, bug fixes, new pages, and more.
To keep work moving fast and fairly, all requests must go through the Asana form.
Slack messages, DMs, and verbal requests are not tracked and cannot be guaranteed.
If it's not in the form, it doesn't exist in the queue.
How it works
The Request Process at a Glance
1
📝
You Submit the Form
Fill required fields, include desired deadline and all assets.
›
2
🔍
Web Team Triages
We review, assign priority, and confirm or adjust your deadline.
›
3
✅
Assets Confirmed
SLA clock starts only once copy, design files, and specs are all ready.
›
4
⚙️
Work Begins
Task enters active queue. You'll be notified when in progress.
›
5
🚀
Delivered
Completed, marked done in Asana. Review and confirm.
Your responsibility
Web team responsibility
The Form
What to Fill In
Be specific. Not "update website" — something actionable like "Update pricing page hero copy."
e.g. "New LP — Q2 Partner Program launch"
Select: Content Update, New Page, Bug Fix, Image/Assets, Technical, SEO, Design Adjustment, or Other.
e.g. "New Page"
Who owns this request and should receive updates? Tag yourself or the relevant team member.
e.g. "Bruce Chen / Demand Gen"
📅 Desired Due Date
RequiredWhen do you need this live? Be realistic — this helps us plan. We'll confirm or flag a capacity conflict.
e.g. "March 21, 2026"
📝 Description & Context
RequiredExplain what's needed and why. Link to briefs, copy docs, Figma files, or reference pages. More detail = faster delivery.
e.g. Copy doc link, Figma, or reference LP URL
🖼️ Assets & Files
OptionalAttach or link all assets: images, copy doc, design mockup, form specs. The SLA clock only starts once all assets are confirmed ready.
e.g. Figma link, Google Doc, Drive folder
Prioritization
How Priority Is Assigned
⚠️ Priority is set by the web team — not by requesters. You provide your desired due date and business context. We assign the priority level based on the criteria below. This ensures fairness across all teams and prevents every task from becoming "urgent."
| Level |
SLA Target |
What qualifies |
Examples |
| P0 Critical |
Same day |
Site down, broken form, revenue-impacting bug, exec-directed emergency. Reserved for genuine crises only. |
Broken nav, 404 on key page, form not submitting |
| P1 High |
24–48 hrs |
Launch-blocking work, active campaign with hard external deadline, time-sensitive announcement. Business impact is imminent. |
LP for event in 2 days, product launch page, press release |
| P2 Medium |
2–3 days |
Standard planned work: page updates, new LPs, content refreshes, blog publishes. All assets must be ready at submission. |
Webinar LP, copy update, new blog post, image swap |
| P3 Low |
4–5 days* |
Nice-to-have improvements, low-traffic pages, internal requests, no external deadline. *May slip when higher-priority work enters the queue. |
Footer link, minor copy tweak, internal resource page |
Important rules
Three Things to Know
🕐
The clock starts when assets are ready
Missing copy, design files, or specs? Your task enters "Waiting on Requester" status. The SLA begins only once everything is confirmed complete.
📬
No form = no queue
Slack messages, DMs, and hallway requests are not tracked. If it's not in Asana, it doesn't officially exist — even if someone acknowledged it in chat.
⚖️
Not everything can be P1
The team serves 15+ requesters. If every task is "urgent," none of them are. Priority is assigned objectively — not based on how the request was worded.
Submit a request
Ready to Get Started?
Submit a web request
Fill in all required fields, attach your assets, and set a realistic due date.
Not in #mkt-webflow-production? DM Rafael to get access.
Open Web Request Form →