Daily Tasks vs. Project Tasks | Community
Skip to main content
MeganBa1
MeganBa1
Level 2
June 2, 2026
Question

Daily Tasks vs. Project Tasks

  • June 2, 2026
  • 4 replies
  • 141 views

Hi there!

We may use Workfront a little differently (maybe not as robustly) than others so I’m looking for some insight.

We have individuals that create “projects” with “tasks” for more daily tasks / updating of items / check lists / documentation (think that they visited a location and want to document what was discussed/observed there).   

Then we have true “Projects” that have meetings corresponding to the goals/expectations of a project, tasks, deliverables, etc.

How we currently have WF structured these “daily/weekly” documentation project items fall in the same programs as true Projects.  I’m looking for any help or insight on how to redesign the system so we have a structure that better distinguishes between Projects and those documentation/one off tasks items.

Thank you!

    4 replies

    ScottMo1
    Adobe Champion
    ScottMo1Adobe Champion
    Adobe Champion
    June 2, 2026

    Hi Megan - this is exactly how we use Workfront.   We also have checklists that generate open issues as well as tabulate quality performance.   Workfront runs our entire company from HR to Facilities to Project Management and many other areas.   Happy to chat.   

      Lyndsy-Denk
      Community Advisor
      Lyndsy-DenkCommunity Advisor
      Community Advisor
      June 2, 2026

      ​@MeganBa1 One approach is to require the use of project templates, then design templates in a way that helps you tell the difference. I can see this going a couple different ways:

      1. You can report on the template usage itself (ex. count the number of projects that used A template, B templates, etc.).
      2. Add a custom form to projects that has a field that defines the differences in project type. You can technically do this without templates, but it’s more work. At the template level you can prepopulate that field. So if templates A and B are for true projects, the field then says, “I’m a real project.” Template C, though, would have that field set to, “I’m not a real project.” Then you can report on all the projects that have “I’m a real project.”
        L
        LisaMc1
        Level 2
        August 5, 2026

        Hi Megan,

         

        We put any individuals’ projects into an “Internal Projects” portfolio and exclude this from any reporting.

          MorganHatcher
          MorganHatcher
          Level 4
          August 5, 2026

          I agree with ​@LisaMc1  - it can be as simple as using a different Portfolio/Program to classify these projects. 

          If you do want these projects to stay in the same Portfolio/Program you could also use Groups as a way to separate them out. The Group Association in a Project is more for settings of that Project and not tied to access. 

          The other suggestions of creating a new field that marks them as a different project type will also work.  

          I would look at how you report on your projects today and see what option would require less updating. For me the Portfolio/Program option would be the easiest to implement, but all these options can be used for the filtering or grouping of reports. 

          Terms & ConditionsAccessibility statement

          Loading footer...