Tagging Project Documents

Modified on Thu, 5 Dec at 1:47 PM

To tag documents for Projects added to the Company Assets in Symphony, complete these instructions.

 

1. Prepare the Document(s)

All validation documentation submitted should be highlighted and contain comments (“tags”) indicating the specific reference for validation. 

  • Use any comment function in the PDF (Portable Document Format). 
  • Symphony will guide evaluators in searching for the text in the comments (annotations) (see Figure 1). 


Comment Toolbar in Adobe

Figure 1. Use any Comment method to prepare the documents. 

    

2. Upload the Documents to My Company

Go to My Company > Projects/Past PerformanceUsers can add and remove documents, and edit/update reference tags as needed. 

  1. Create a Project Experience to reference.
  2. Upload supporting documents to the project (see Figure 2)
  • All project documents should be in .pdf format. 
  • The Adobe portfolio feature is not recommended.

 

The Company Name displays on the top left.

Upload project documents in My Company

Figure 2. Upload Project Documents to My Company > Projects/Past Performance

  

3. Reference the Documents

Fine-tune the Project Details by selecting a Reference document(s) for each claim (see Figure 3).


Project Detail tags should match the Symphony Tag Legend Figure 3. Project Details match the Symphony Tag Legend. 


When answering a question, each document reference will be linked to the question it is applied to, and the reference tag will guide the evaluators to the comment in the document(s). NoteTags for a specific claim can be used more than once in the PDF document, and multiple documents with a common tag can be used to support the same claim. 

 

The Tag Legend only applies to the core project details in the Company assets because this data is the most reusable (see Table 1)The recommended tags are:

 

COSTS
 Other Direct or Indirect Costs
CR 
 Cost Reimbursement
FOREIGN Foreign Country/Location(s)
FTE
 Full-Time Equivalents
LOCATIONS 
 Number of locations
NAICS
 North American Industry Classification (NAICS) code
OCONUS 
 Outside of the Continental United States
POP 
 Period of Performance
PSC Product and Service Code (PSC)
TCV 
 Total Contract Value
TEAMING 
 Subcontractor/Teaming

Table 1.

 

Best Practices

  • Project documents can be generalized and do not need solicitation-specific file names. 
  • For consistency, only use one tag per claim in Symphony.
  • Add various tags throughout the document(s).
  • The tags must match in both the PDF(s) and Symphony so that the evaluators can easily find the support for each claim.


4. Polish the Proposal

The most important part of “tagging” is that the PDF comment matches the reference in Symphony for that specific claim. Follow these steps:

  1. Starting on the Dashboard, select the Solicitations tab. 
  2. Start or Continue a proposal Submission
  3. Select the Projects/Past Performance tab to add or edit Project(s).
  4. Use the Project's Performance Factor link to add the solicitation-specific tags to a project experience, and to earn additional points for the solicitation (see Figure 4)
  5. Enter the keyword from the document(s) into the tag (location in file) field.  


The Submission displays the Solicitation Name on the top left and the Live Score on the top right. 

Adding Performance Factors to projects in a proposal

Figure 4. The Performance Factors link appears as a Begin or Modify button. 


During an evaluation, Symphony will guide evaluators in searching for all instances of the tag in one or more documents selected for the file reference field. 

  • The evaluator will see everything entered in the "location in file" field. 
  • The evaluator can locate claims faster by using the comments and they help them to look in the right place.

 

Watch this video for a brief overview.


Need technical help? Contact us  


Users should be aware that the information on this website may not reflect the official positions of the Federal Government. The views and opinions expressed by agents of Apex Logic, Inc. are those of its employees and do not necessarily reflect those of the Federal Government or any of its officials. Guidelines and requirements provided by the Federal Government in the form of solicitations, amendments, modifications, or any other communications supersede any information provided by Apex Logic, Inc. If you have questions about this disclaimer, please contact us.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article