Best Practice for Managing Internal Request Form(Tracking Only, No In-App Communication

English Forum Asana In Practice Asana for Marketing
,
1

Our Marketing team supports multiple departments and stakeholders through Asana request forms (design, social media, events, web updates, etc.).

We use Asana primarily as an internal tracking and workflow tool. We do not communicate with requesters inside Asana. All confirmations, updates, and completions are handled via email.

We’re currently evaluating whether it’s more effective to:

• Create separate request projects in the sidebar for each category/type of request
or
• Use one centralized request project with custom fields, sections, and rules to organize submissions

Our goal is to keep requests organized and easy to prioritize for our team, without requiring requesters to log into Asana or engage in the platform.

What we’re trying to do:
Create a clean, scalable system to intake and manage requests internally while handling all communication externally.

What we’ve tried so far:
We currently use request forms with manual categorization and email follow-ups, but as volume increases, it’s becoming harder to manage across multiple departments.

What’s confusing:
We’re unsure which structure works best long-term—multiple specialized projects vs. one unified intake project—when Asana is used only for internal visibility and task management.

We’d love to hear how other teams use Asana strictly for internal request tracking while managing communication outside the platform.

Any best practices or examples would be greatly appreciated!

2

Hi @Alice_Cabrera , that’s an interesting question!

Here are some ideas/recommendations for you to consider:

  1. Start with one centralised intake project. Use multiple forms that all submit to the same project. Each form can include a “Request type” field to enable automatic routing.

  2. Use rules to handle the busywork: auto-assign the owner, set the priority/SLA, add a template for subtasks, and multi-home the task to a team’s working project.

  3. Keep a simple kanban for triage: New, Needs info, In progress, Blocked, Done. Save filtered views per team or request type so each group sees only their work.

  4. Add a few key custom fields: Request type, Priority, Department, SLA target, External contact email, and Comms status. Keep it lean, so updates are quick.

  5. Standardise with bundles or task templates so every request spins up the same checklist and fields.

How to handle email-only comms while tracking in Asana

  1. Log the latest external status in the “Comms status” field (e.g., Waiting on requester, Emailed update, Approved, or Final sent).

  2. Paste the latest email summary at the top of the task description or attach the email thread. That gives you internal visibility without moving the conversation to Asana.

  3. If you use Gmail/Outlook add-ons, you can create or update the task from your inbox, but still reply by email only.

When to split into multiple projects

  1. Split if teams have very different workflows or owners, strict access needs, or volume is high enough that one board gets noisy.

  2. If you split, keep a single intake project and let rules multi-home tasks to the right team project. Use bundles to keep fields, rules, and templates consistent across projects.

Why centralised intake first

  1. It’s the easiest to maintain, reporting is cleaner, and you avoid duplicate form management. You can always layer on team projects later for execution while keeping one intake.

A couple of helpful resources

  1. Multi-home overview: https://asana.com/guide/help/tasks/fields#gl-multi-home

  2. How to build an Intake process: How to Build a Project Intake Process [2025] • Asana

  3. Project intake use case: https://help.asana.com/s/article/project-intake?language=en_US

  4. Creating Basic Workflows Academy course: Creating basic workflows

I hope this helps!

3

Hi there,

Your setup and concerns make a lot of sense — this is exactly the point where many Marketing teams outgrow native request forms plus manual email follow-ups.

Since you want to keep Asana strictly for internal tracking and handle all requester communication via email, the most scalable long-term approach is usually:

• One centralized intake
• Structured request forms per category
• Automatic routing and prioritization
• Fully email-based requester communication
• No requester login required

This is precisely the gap that Hipporello Service Desk for Asana ( Turn Asana into a Full-Service Desk Solution | Hipporello ) is designed to solve.

Instead of choosing between multiple projects vs. one project and then manually managing emails and categorization, Hipporello adds a service-desk layer on top of Asana that keeps your internal workflow clean while automating requester communication externally.

Here’s how it maps directly to your needs:

Centralized Intake Without Losing Structure

You can create multiple branded request forms (design, social, events, web updates, etc.), each with its own fields and logic — but all requests can still flow into one or more Asana projects based on rules.

Automatic routing can:
• Send different request types to different projects or sections
• Assign to specific team members
• Apply priority and urgency rules
• Tag and categorize automatically

No manual triage required.

Email-Based Communication — Fully Automated

Since you don’t want requesters inside Asana:

• Requesters submit forms or send emails
• They receive automatic confirmation emails
• Your team replies from inside Asana
• Replies are sent back as email automatically
• Status updates and completion notices are automated
• Requesters can reply by email — it syncs back to the task

So your team stays in Asana, requesters stay in email.

Cleaner Scaling as Volume Grows

As request volume increases, Hipporello helps by adding:

• Ticket-style tracking on top of Asana tasks
• Conversation history per request
• Internal vs requester-visible notes
• Requester portal (optional — email-only also works)
• Cross-department intake without project sprawl

This avoids the typical breakdown that happens when teams try to scale with only native forms + manual inbox handling.

Recommended Model for Your Marketing Team

For your use case, the most effective structure would be:

• Multiple request forms by category
• Rule-based routing into Asana (Hipporello automation)
• One or a few internal projects (not many)
• Automated email confirmations & updates
• All requester communication handled outside Asana
• Team works only inside Asana

That gives you a clean, scalable internal system and a simple external experience for stakeholders.

If helpful, I can walk you through a sample Marketing request workflow built with Hipporello for Asana so you can see exactly how this would look in practice. You can also check our website for the details and getting started in 5 minutes. Turn Asana into a Full-Service Desk Solution | Hipporello