Question

Naming convention for projects?

Forum|Forum|9 years ago
July 5, 2016
20 replies
4464 views

What naming convention are you using for projects? I'd love to hear what some others are using. We are currently using: program_projectdescription_date program: should match the ‚Äö√Ñ√∫program‚Äö√Ñ√π selected from the drop-down menu on the Standard Intake Form projectdescription: should match the ‚Äö√Ñ√∫request type‚Äö√Ñ√π selected from the drop-down menu on the Standard Intake Form , include week or quarter for weekly or quarterly communications date: should match the ‚Äö√Ñ√∫go live/distribution‚Äö√Ñ√π date selected on the Standard Intake Form , use a two-digit month followed by a four-digit year Examples: openenrollment_letter_112016 allemployeemeetings_q3presentation_082016

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

Show previous replies

A

Anonymous

We haven't been using naming conventions for projects, just simply a descriptive title that the person seeing the project will have an idea about what the project is about. Then we use many custom data fields to put the descriptive information about the project so that we can filter in reports or display in reports. Curious, though, when using the naming conventions, what is your ultimate goal? Is it for record keeping? Filtering? And then curious why not use custom data instead of naming conventions? Not saying one way is better than the other, just curious so that we can determine at my organization if we are doing it the best way for our needs. Thanks!

T

tadams-1146613

Level 2

At my company, we need to align the project name to be usable and compatible with other programs so we have the naming convention of: Fiscal Year Brand Market Location Season/Product/Program Name Media Type/Format Cheers! -- Scott Adams Workfront - Data Inspires Creativity Business System Analyst Lead

angiet39887144

We do something similar to this too. We do Year.Month ProjectName. So things like "2016.07 PresidentsClub" This is helpful cause it organizes things chronologically, but also makes us remember when we worked on certain things. We are slowly but surely moving to WebDAM so hopefully the timing of projects will have less of an impact moving foward.

K

KarenRu

Level 6

Hi Angie, My comment is less about naming conventions- but curious about your move to Webdam. Did you purchase the WF integration? or is the product seperate? We're in the middle of implementing Web DAM as part of WF- and would love to talk to you offline regarding what you're doing- maybe we can share experiences. tks Karen

P

PeggySe1

Level 2

We use PortfolioAbrv-ProjectName (such as MKTG-New Website)

P

PhilipSt

Level 4

I'm enjoying reading these, as we are going through a discussion on how to name our projects consistently right now. I would love to see examples of some of the custom forms mentioned, to get a better idea of how to use them. Thanks, Phil

S

SkyeHa

Level 10

Phil, good idea, a picture's worth a thousand words. I can't see a point in showing our custom form just because there are so many display logic bits, however here's a screenshot of my project view.

From top to bottom and left to right:

- we're grouping by Division -- a custom field

- our workers track and refer to pieces by Form number and Rev date -- these are custom fields

- the name of the piece is the title of the project, and this is a workfront field, along with our due date, % complete and status. Our upper management refer to pieces by their names rather than form number.

- Custom fields for Piece format, piece type and type of work all combine to indicate complexity. New pieces are more complex than revised pieces, brochures are more complicated than fliers, print is more complicated than PDF.

- PM and Priority are Workfront fields.

Many of our reports are set up in the same way. If we are reporting on projects, the fields we automatically include are Form number and Rev date, right next to the name of the project. For us this also keeps that project name field shorter, since it takes up so much room at the top of a project's page.

C

CommunityUs

Level 4

Vittorio - When you reference using the sequential number in your naming convention is this a manual process or have you found a way to automatically generate that sequential number into the project name field? We are really trying to solve for the ability to have a sequential number in our naming convention without having to manually track and add this.

P

PollyCo

Level 9

Hi Mary, if you haven't voted yet - you might be interested in upvoting this idea in the exchange. Thanks. "https://support.workfront.com/hc/en-us/community/posts/115001218447-autonumber-field-docket-numbers" https://support.workfront.com/hc/en-us/community/posts/115001218447-autonumber-field-docket-numbers

B

BrookeVa

Level 4

We work with multiple clients so the way we set our projects up is like this: Billing Flag - Client Name - Client Project Description - ### NB - Rockfish - Rockfish Website Redesign - 1234 NB stands for nonbillable so that our accounting teams knows we do not have signature on a legal doc yet. Rockfish is the client. Rockfish Website Redesign is the name of the client's project we are working on and the 4 digit number is what we refer to as a "job #" and each project will have it's own unique number. Other billing flags that we use: R - retainer IWO - internal work order E - email approval INV - investment Giving each project a unique job number helps when it comes to logging time. PMs can easily say "bill your time to job # 1234" and the user can easily locate that on a timesheet or the search bar. The way we name projects is also helpful to our accounting team because it gives them the billing flag (letting them know if it's okay to bill), provides the client's name, and the project name. Hope this helps!

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded