This page functions as a guide to various production support issues. It is organized by ticket category and subcategory, including relevant scenario examples and troubleshooting steps when applicable. The goal is to keep this page updated regularly with new issues to share troubleshooting knowledge across teams. If the agent cannot find a satisfactory answer here, they may contact Rob Donigian, one of our Software Developers. Alternatively, they may reach out to the Principal Software Engineer, Carson Full, or the Software Development Director, Seth McKnight.

1. Admin, Features, and General Questions

1.1 New Users

Requests for adding a new user to the system:

• This is the process for adding a new user to Cord Field:
  • First, the agent must ask the user to register for an account at cordfield.com.
  • In the meantime, the agent must confirm with the user's specific HR Business Partner (see list below) that the Prudence Protocol has been acknowledged in ADP and that the user is approved for the role in Cord. It is a good practice to involve the user's supervisor to confirm the role required in Cord.
    • Alternatively, if clarification is needed, the agent can review other similar users and their permissions or, as a last resort, consult with managers, the C-suite, and the Software Development Director for guidance.
    • Once HR and the user's Supervisor confirm, the agent can assign the roles to the user's profile in Cord Field.
  • List of SC Groups along with their respective HR Business Partners:
    • Development, Marketing & Communications, and Technology: Kasan Boyd
    • Field Growth and Field Operations: Sky Dsane
    • Finance & Translation Quality: Cari Sury
    • Office of the President and People: Kayla Spann

Requests to assign a new role to an existing user:

• Initially, the agent must confirm with the user's supervisor whether a change is necessary and understand the new permission requirements.
• After confirming this information, the agent can proceed to update the user's profile with the new role(s).
  • If the suitable new role is unclear, the agent can compare other similar users and their permissions or, as a last resort, seek guidance from managers, the C-suite, and the Software Development Director.
  • Depending on the user's needs, the previous role(s) may be retained or removed.

General permissions:

• Certain users need general access to projects but do not necessarily need to become team members; in those situations, the "Leadership" role might be granted.
  • The Leadership role allows read access to projects but not write access. This means that the user can view all projects in Cord, but cannot modify them.
  • Check with Product Owners for individual cases.

Contractors' access to Cord:

• Contractors are granted access to Cord Field only after they have an active contract with Seed Company, which includes signing a non-disclosure agreement (NDA).
  • Currently, we do not require contractors to sign the Prudence Protocol.

1.2 Project-related questions and requests

Adding users to specific projects:

• If a user requests to be added to a particular project with a specific role, we should refer them to the project's Project Manager or Regional Director.

Questions about the Field Partner and Field Operations tabs on the progress card in Cord Field:

• Field Partners may in the future gain direct access to Cord Field, enabling them to update the status of their projects in the system. The "Field Partner" tab will allow them to input data into Cord Field, while the "Field Operations" tab will give Project Managers the chance to review and correct the updates made by the Partners.

Translation 'Tools' feature:

• This feature on the engagement page enables users to specify or list the tools used in the field for language translation, including AI tools like Scripture Forge and other well-known translation software such as Paratext.
  • This is a list of predefined options, and multiple tools can be added to the engagement page.
  • If a tool is not listed, the Agent may add it once the Field team confirms its use.

Field Region | Zone Pages:

• The feature is designed to assign the Regional Director to their designated Field Region and the Field Operations Director to their specific Field Zone.
  • The feature automates assigning the respective RD and FOD once the user selects a Field Region on the project page.

Questions about missing folders or standard folders in the Files card:

• Some users may wonder about missing folders in the Files card, specifically whether we have standardized folders or what happened to the folders that were previously available.
  • When a project is created, Cord automatically generates the following folders in the Files card:
    • Approval Documents
    • Consultant Reports
    • Field Correspondence
    • Photos
  • If folders (or files) are missing, first check to see if they were accidentally moved to a different folder by looking through each one individually. If you find that they have been moved, you can easily drag and drop the folders or files within the "Files" card. Additionally, you can use the folder path at the top of the page to drag and drop folders and files as needed.
    • If you determine that the folder or file is truly missing, consult with a developer to see if it can be restored.
  • Users can add additional folders to the Files card by clicking the "Create Folder" icon located in the top right corner of the card.
  • Project Managers have the flexibility to rename folders to better meet the needs of their specific projects.

Questions about project workflow and status changes:

• We can direct users to the workflow diagram in Cord Field or the resources in SharePoint (link).

1.3 Questions about other Cord Field environments

Training site requests (Cord Field Training):

• Field is responsible for managing the training site, so for general requests (e.g. role assignments or partner addition), the user must contact the Field Operations Services Director, Abby Roberts.
• For system issues, the agent may contact the Principal Software Engineer, Carson Full.

2. System

2.1 DOMO Issues

2.2 Authorization | Permission Issues

User is unable to access a feature they expect to have access to (see, edit, select, approve, etc.):

• First, confirm that the user's roles have the requested permission. Using the "impersonation" feature can be an effective way to test this. For Permissions at the Project and Engagement levels, the agent can check the Workflow UI in Cord Field.

• Consider the difference between project-specific and global permissions.
  • For global permissions, ask a developer for an updated version of the permissions file from the API policies.
• If there is still uncertainty, contact the Software Development Director for further clarification.

2.3 Data Issues

2.4 PnP Issues

Cord Field does not display/extract Actual Progress exceeding 100% from OBS or Storytelling PnPs.

• Cord is actually extracting the cumulative progress but converting percentages over 100% into different numbers.
• In the past, it was acceptable to have percentages that exceeded 100%, but FOLT (Field Operations Leadership Team) has since revised this policy.
• The Project Manager needs to update the Planning tab to match/reflect completed stories, then re-upload the Planning PnP and the Progress PnP to their respective cards.

2.5 UI Issues

2.6 Other

Posts section:

• The Cord Field UI features a posts section for team members to share project-related updates. Currently, users can choose from the following categories of posts in Cord:
  • Note
  • Prayer
  • Story

• Users must also choose the "shareability" level of the post from the dropdown menu, which includes the following options:
  • Ask to Share Externally
  • External
  • Internal
  • Team Members

Prayer Posts

• Cord Field does not send prayer posts directly to other systems; however, there is a DOMO card that gathers prayer items categorized as "External" and "Ask to Share Externally" from Cord. These prayer requests are collected on a DOMO card, which sends them to [email protected], from which Zapier generates and sends a Slack post to the Prayer channel.
  • For questions regarding these prayer requests, please contact [email protected].

Upload Files button:

• The "Upload Files" button on the main project page allows users to upload files to the Files card. Once a file is in the Files card, users can drag and drop it into any folder within the card.

"Please check engagement statuses" error message:

• The user receives an error message while trying to update the project status, even though they have the correct permissions. This error usually occurs if the engagement is already set to the status the user is attempting to update it to or if one of the engagements in a cluster is already in a final state, such as "Terminated."
  • The user must verify and update the engagement statuses, typically by reverting them one or a few steps back, before updating the project status.
    • If the user is still confused and does not know how to fix the issue, the agent may either guide them to the Workflow UI or rectify the problem on the user's behalf.
  • For engagements in final states, the agent may update the status on behalf of the user, ensuring that the engagement status that triggered the issue is returned to the appropriate level.
    • Once Cord Field is migrated to EdgeDB, this issue may no longer occur, or implementing a fix could be easier. Until then, this workaround remains in effect.

3. Process

3.1 Project Team Management

Requests to temporarily add Consultant roles to people's profiles:

• Within the Field teams, it is not unusual for other Seed Company Staff to be temporarily assigned to review and endorse projects when the project's Consultant is unavailable.
  • The agent can add the requested role, but it is advised to keep track of the change to remove the role when no longer needed.

3.2 PnP Issues

• After the implementation of the PnP extraction validation feature, Cord Field will now indicate any data issues with the PnP, addressing the most common user problems. For a list of validation errors and their respective troubleshooting steps, please visit the PnP Extraction Validation page.

New Columns M, N, and R

• This outlines the preparation for the Admin's renewed focus on velocity and acceleration.

  • Column M will assist administrators in establishing a standard for comparing projects within a specific region. It represents the planned verse equivalents (VE) for a given year, specifically for Stages 1 through 5, excluding Stage 6. This number is expected to fall between 1,000 and 2,000 VE per year.

  • Column N is derived from Column M, calculated by dividing it by 8,000, which serves as a round number representing a complete New Testament (NT). For instance, if Column M is 2,000, then Column N will be 4, indicating that at that rate, it would take the team 4 years to complete one NT.

  • Column R is similar to Column S. However, while Column S reflects the actual number of verses in that row, Column R represents the VE equivalent of Column S. Column R (VE) is the foundation for the entire PnP. In previous versions, this VE in Column R was not displayed, which led to some confusion for FPMs. With the introduction of the new Column R, FPMs can now better understand the distinction between actual verses and verse equivalents (VE).

Requests to use alternate PnP Step Headers:

• This is currently approved with limitations, as some alternate step names have been mapped and integrated into the accepted names in Cord Field. However, the system will still only display the approved names, matching any alternate names to their corresponding approved versions.
  • Using non-approved names can still lead to data extraction failures for both the Planning and Progress PnPs.
  • Some teams find it useful to employ separate PnP files during translation. One version contains the step names discussed with the partner who requested different steps, serving as a reference to document their translation process. The other version, created by the Project Manager, features standard step headers and is uploaded to Cord Field. These two versions are identical except for the differing headers.
    • Although the new accepted step names in Cord are established, it might still be helpful to adopt this practice whenever possible to entirely prevent errors.

Questions about the percentages under the PnP step headers:

• Although the headers should match the step names in Cord Field, the percentages might be revised to reflect different processes used by field partners. The percentages are not directly imported into Cord Field; instead, they are incorporated into the PnP's cumulative summary percentages.

PnP is not being uploaded/figures are not being imported:

• Ensure the uploaded file is the correct PnP for the project and quarter.
• Confirm that the file is not a different type of spreadsheet other than a PnP.

Cumulative progress is not updating correctly:

• Check columns AN/AO/AP for the quarter and year to verify if data has been calculated and entered into the cumulative progress Excel cells:

• If data exists, contact the development team to debug; otherwise, it could be a formula issue, and the user should try a new version of the PnP downloaded from the Field Operations Library or contact Harold Good, the PnP owner.

• If data does not exist, check if the correct Reporting Quarter is selected on the PnP or if there is progress data recorded for the Quarter in the progress tab.

User is unable to select the correct reporting quarter:

• There is a five-year time limit on the MOU dates in the PnP. This limitation may be in place to align with business requirements. If a user sets the project MOU dates beyond this five-year limit, they might be unable to select the last reporting quarter in the Progress tab. Instead, they will only see options such as "On track" or "Completed." Additionally, there may be discrepancies between the MOU dates in the Planning tab and those in Cord Field, and these should be corrected. Once the dates in the PnP and Cord are aligned, the issue with selecting the reporting quarter should be resolved.

Progress detail is not updating when the user uploads the progress report for the quarter:

• Check to ensure step headers are correct in planning and progress sheets.
• Make sure the PnP project date range in the Excel file matches the actual project beginning and end dates.
• Make sure the Reporting Quarter selected in the PnP progress sheet matches the Quarter you are uploading the file for.
  • The "Percent Finished & Cumulative sections" will only update if the reporting quarter is correct, as CF reads them to obtain progress updates.
• Ensure all your scripture goals are identifiable and match those already listed in the language engagement overview page from when you initially uploaded your PnP planning sheet.

Scripture Goal showing up as unspecified (e.g., Isa 34/1292 vs Isa 10:1-34):

• Check the PnP planning sheet to verify that a valid scripture reference was entered in the "My notes" column.
• If not, the user must delete that goal, add the correct scripture reference in the PnP planning sheet, and then re-upload the planning sheet.

Empty Goals and/or Progress or Step(s) not planned for a particular Goal/Book:

• It's possible that there was a problem with the originally uploaded PnP Plan (this could even be from the initial migration); here are some troubleshooting steps:
  • Verify the spreadsheet version listed on the right side of the header with the project name. It is recommended to use the most recent version available in the Field Operations Library to avoid parsing errors caused by row or column mismatches.
  • Check the Step Names in the spreadsheet; they must match the appropriate Methodology Steps found here or the latest approved alternative name, to ensure proper parsing.
  • Download the original PnP Planning spreadsheet and then re-upload it
    • Note that the existing goals may need to be manually deleted before re-uploading the spreadsheet; if there are visible issues with them already, then this will cause no harm.

If users still encounter any PnP issues unrelated to Cord Field, they should contact Harold Good, the owner of the PnP spreadsheet, via the official channel at [email protected].

3.3 Project | Engagement Management

Milestones

• The "Milestone Planned" chip specifically refers to that phase of the project in case the project’s completion results in a full Old Testament, a full New Testament, or a complete Bible. We should set it at the start of a project as something planned for the next three years. Please refer to the following terms:
  • Blank (no value) or a dash indicates that no option has been selected yet for the "Milestone Planned" section.
  • "None" indicates that the project has no milestones planned to be completed for this engagement by the end of this project.
  • "Old Testament" indicates that a complete Old Testament is planned for this language engagement by the end of this project.
  • "New Testament" indicates that a complete New Testament is planned for this language engagement by the end of this project.
  • "Full Bible" indicates that a complete Bible is planned for this language engagement by the end of this project.
• For language engagements with a planned milestone (OT, NT, or Full Bible), a follow-up question must be answered at the end of the project: "Was it [the milestone] completed?" This can be responded to with "Yes", "No", or "Unknown".

AI Assistance

• "AI-Assisted" refers to the use of Artificial Intelligence or Machine Learning tools and processes. Please refer to the following definition of terms.
  • "Draft" (AI-Assisted Drafting) – Though others may be used, this includes three major tools at this time: Scripture Forge, Avodah, and AI BT (used by TWFTW).
  • "Check" (AI-Assisted Consultant Checking) – This primarily refers to AQuA, the only known tool at this time, though others may emerge.
  • "Draft & Check" - Meets both "Draft" and "Check" criteria (see above).
  • "None" – Confirmed that no AI-assisted tools are being used.
  • "Other" – Any AI-assisted tool that does not fall under "Draft" or "Check." This may include using these tools on other steps, for steps that don't clearly match "Draft" or "check" definitions, or any other known use of AI or Machine Learning not already defined.
  • "Unknown" – Usage is unclear or has not been determined.

Note: If you know AI-Assisted Drafting is being used but are unsure if AI-Assisted Consultant Checking is active now, just click "Draft." If you find out later that the AI-Assisted Consultant Checking is being used, update it in Cord Field.

Error when confirming Change to Plan if one or more engagements are in Discussing Suspension or Discussing Termination status:

• In a cluster project, if one or more engagements are in Discussing Suspension or Discussing Termination and the project is undergoing a Change to Plan, the Project Manager must first move the engagements to Suspended (Approve Suspension) or Terminated (Approve Termination). Otherwise, the Financial Approver will receive an error and will not be able to confirm the CtP.
• Alternatively, if the engagement statuses are incorrect, the Project Manager must move them back to Discussing Change to Plan.

New Change to Plan Workflow:

• Project Managers can now submit directly for Finance approval when it is deemed appropriate based on the pre-established guidelines. This skips the double action of having to “Submit for (RD) Approval” and then immediately “Approve (RD) Change to Plan” in order to get to Finance.
• Because of the above, Project Managers are no longer allowed to approve/reject a Change to Plan on behalf of an RD. There is no need for this workaround anymore with the new transition addition above.
• Finally, Project Managers can “retract” their approval request, either from an RD or Finance, in order to make more changes. This prevents them from getting “stuck” and needing the agent's help to retract/revert the approval step.

Requests to verify photos that were included in previous Quarterly Reports:

1. Go to the respective Quarterly Reports card.
2. Click on "All Reports".
3. Select the Quarter you want to review.
4. On the cumulative progress card, click on "View Details".
5. Once you're there, click on the "Media" step in the sidebar on the right.
6. To access the images, click on the drop-down arrow located on the right side of each variant box (Investor Communications, Field Operations, etc.).

Budget Card dates not matching the Memorandum of Understanding (MOU) dates:

• Check if the funding partner shows the project to be funded until the end of the internship, reflecting the project's dates.
• Cord will use the project's MOU dates if the dates are left blank on the partnership cards.

Requests to update the Field Budget amounts:

• The Field Project Manager works alongside the Financial Analyst to develop a budget during project development. Once the project and budget have been approved and the project is Active, the budget must go through a Change Request to be updated. To maintain financial oversite, the Financial Analyst is the only person who can update the budget.

Requests to upload more photos to reports:

• At this time, users can only upload one photo in the quarterly report section. Additional photos can be uploaded to a photos folder in the files card.

Multiplication Projects:

• Multiplication projects at Seed Company are initiatives where partners primarily oversee design, monitoring, and funding. These projects are typically either not funded by Seed Company or receive only minor funding, with the majority being minority funded. Seed Company may offer resources like consulting services without providing direct financial support.
  • Most, if not all, Multiplication projects are managed in Monday.com, with Taylor Martin serving as the main FPM and point of contact.

Requests to change Project sensitivity:

• It is not possible to adjust a project's sensitivity, as it is determined by the highest sensitivity level of all the languages involved.
  • If the Project Manager wants to change the project's sensitivity, they need to request a change in the sensitivity level of the individual languages (refer to 2.4 Language Management).

Project Sensitivity defaulted to "High" upon creation:

• When creating a project in Cord, the sensitivity level is set to "High" by default. However, once an engagement is added, the project's sensitivity level will be updated to match the engagement's level.

Requests to change or update the project's start and end dates:

• For projects In Development: Project managers should be able to update the start and end dates. If they are unable to do so, please contact the development team for debugging. In the meantime, agents can use their admin privileges to update the dates.
• For Active projects: any modifications to active projects must be handled through a Change to Plan. The FPM must contact the Financial Analyst for approval, as the FA is the member authorized to update the dates. If the FA is unavailable, a Lead Financial Analyst or Controller may proceed with the change.
  • The agent can implement the change once they have received approval from the FA, provided neither they nor other financial members are available at that time.

"Submit incomplete report" message:

• The "submit incomplete report" message pertains to the progress report's Team News and Story sections. Each variant box (Investor Communication, Field Operations, Translation, Partner) has an assigned role (such as Project Manager, Marketing, Partner). If the logged-in user hasn't completed one of these sections, a notification will pop up, reminding them to fill it out before submitting. This is purely a reminder, not an error. Users can ignore the message and submit the report even if some sections remain incomplete.

• For Project Managers, notifications are linked to the Field Operations section. If the Story and Team News sections for the Field Operations box are completed, they should not receive any notifications.

• FPMs can edit other sections, including the Partner section. However, they will only receive notifications for the Field Operations section if no data has been entered.

• Translation variant: the translation variant box is used when a partner shares a story in their local language, allowing the FPM to translate it into English.

Requests to move projects from Did Not Develop to In Development (Early Conversations, Pending Concept Approval, etc.):

• If a project naturally reaches a "Did Not Develop" stage, no modifications should be made for historical accuracy. Projects labeled as "Did Not Develop" should stay that way.
  • If a project that was not initially developed with that language (or languages) later develops using it, the project manager should create a new project.
    • Since Cord requires each project name to be unique, the FPM will need to modify the name—many people add labels like "Did Not Develop", "DND", or similar. The FPM may consult their Regional Director for the recommended approach.
• If the status was recently changed to "Did Not Develop" by mistake, the agent can "revive" the project.
  • It's advisable to confirm the mistake by consulting the Project Manager and/or Regional Director, reviewing activity logs, and noting the date of the status update if possible.
  • When changing the status from an end state, the agent needs to individually update the project and engagement statuses, since the engagement status won't automatically update with the project status.
• For final states like "Completed" or "Terminated," the same rules apply regarding history and honest or recent mistakes, although these situations are less common.

Requests to upload a PnP into a previous/already closed Quarter:

• The user should navigate to the Language section, select All Reports under Quarterly Reports, and then click on the specific Quarter (e.g., Q2, Q3). On the Cumulative Progress card, click View Details. If there is no PnP, add it; if it has been revised, select "+ New Version".

3.3.1 Internship | Engagement Management

Interns in the external internship program do not need to sign the prudence protocol, as they will not access Cord Field.

Requests to add Consultant, Mentor, or other roles to Interns:

• This is a standard procedure as interns advance in their training. The request can be approved after confirming with Tonia Berthiaume, the Field Operations Program Manager, or Abby Roberts, the Field Operations Services Director.
  • In case of security concerns, please note that interns in Cord have already undergone vetting and have access to their project data. If they gain access to CORD, they will only be able to access authorized information.

Requests to add an Intern Engagement to Internships that have been moved to "Active":

• A feature has been added to prevent the project from moving forward from "early conversations" without an engagement. Therefore, we should no longer get requests like this from users.
  • For Cohorts, the team might need to include an Intern Engagement in an Active project. The agent can do this by clicking the "plus" icon on the internship's page.
    • Please consult with the Financial team on the project before making the requested addition.

Requests for changes to the intern's information in the engagement section:

• Internships are managed by the FPM or RD, and the Regional Team oversees the project, so these members can proceed with the changes.
  • If the team cannot make the updates, the agent may contact the developers for debugging.

Requests to update or change the intern's surname:

• If the FPM/RD needs to update the intern's surname, they are permitted to do so. It is advisable to record the change with a brief note (1-3 sentences) on a Notes card for future reference or management.

Requests to update project's sensitivity: see Language Management section

3.4 Language Management

Requests for any change to a language (population, name, sensitivity, etc.)

• Language modifications or additions should be submitted using the DOMO CF Language Request Form. Users may also be directed to the Language Profile Dashboard, also available in DOMO, for research before submitting their request.
• Justin Stanford, the current language specialist, may be contacted for complex language questions or issues.

Language Profile Page

• The Language Profile is a dashboard in DOMO, created by Roger Hanggi, and found under the Field Operations page.
• On this page, Cord Field users can utilize a DOMO form to request modifications to existing languages in Cord or the addition of languages that are not yet in the system. The Language Profile page also includes a Video Tutorial for users who need help or more information on how to use the page or submit a request.
  • The process begins by selecting either 'Modify' or 'Add' from the "Requested Action" drop-down menu on the form. Then, the user must search for the existing language, ensuring the language code matches the one to be modified or added. Next, the user should complete all required fields for additions or the optional fields for modifications. It is also advisable to include a brief explanation of the requested change. After submitting, a Zendesk ticket will be generated and added to the Cord Field queue.

Language data flow from Cord Field to Progress Bible to Rev79:

• On a monthly basis, ProgressBible queries Seed Company (SC) APIs and updates ProgressBible data about projects and engagements. In turn, ProgressBible shares the data it has received from SC to update Rev79.
  • Jeff Webster's understanding is that neither Seed Company nor Seed Company staff are able to directly update Rev79 data. This means that we first need to ensure that the correct data, based on Cord Field, is made available to ProgressBible through our APIs.
  • Language engagement data in Rev79 comes from both direct entry in Rev79 and from Progress Bible. Seed Company data goes from Cord Field to Progress Bible and then to Rev79. If something is incorrect regarding an SC engagement in Rev79, that needs to be corrected in Cord. Seed Company does not edit engagement info directly in Rev79 but in Cord Field.

Language Names in Cord:

• The strict Seed Company rule is that any language with a sensitivity level of medium or high must have and use a SC name (pseudonym) that is different from the actual/official language name.

Communication Regarding Name and Sensitivity Changes

• Any changes to the language name or sensitivity levels must be communicated to relevant Seed Company stakeholders, especially when a language is associated with an investor.
  • Initially, the agent must notify Justin Stanford, the Language Specialist, about the change request for review and to verify the connection between the language and an investor. The Language Specialist will then manage all further communication.
  • If the Language Specialist is unable to communicate, the following individuals must be notified of the changes:
    • Jason Cox
    • David Thomas
    • Lauren Kidd
    • Bethan Mingle
    • Jon Stariha

Removing a language from projects:

• If the language is "In Development", the Project Manager should be able to remove the Language Engagements; the Project Manager might not see the delete option (trash can icon) if the engagements are marked as "Did Not Develop";
  • We may remove the language from the project after consulting with the language specialist and notifying the relevant stakeholders.
• If the Project is "Active", "Suspended", etc. (not In Development), we do not Delete/Remote Engagements; the Engagement can be "Terminated" if it is no longer part of the project;
  • We want to keep the history that they were included in the project originally.
• We plan to introduce a "transfer" feature in the future to move a language between projects. This addition could impact this troubleshooting step, requiring a revision once the feature is implemented.

User unable to change/update the status of a Language Engagement from In Development to Active (such as "Active, "Discussing Change to Plan", etc):

• The engagement might have been added after the project began but without updating its status to "Active."
  • The agent can change the Engagement status only after verifying the User's permissions and ensuring a smooth workflow is not possible.

3.5 Partner Management

FPM is unable to remove the Primary Partner or deselect managing partnership option:

• If a project has only one Managing Partner, users must add a new primary partner before removing the existing one or deselecting the managing partnership option.
  • Removing a managing partnership impacts the Financial Reporting Frequency, which is not permitted for FPMs. That's why the FPM must first add an additional managing partner.

Request for a new Partner to be added to Cord Field:

• Must go through the Director of Financial Services, Bety Garcia, or other Controller in Cord.
  • In the event that none of the Controllers are available, the agent may contact a Lead Financial Analyst.

The Financial Reports card does not display monthly or quarterly records | users cannot upload financial reports:

• User must check the managing partnerships under the Partnerships card and ensure that the "Financial Reporting Frequency" prompt has been selected for Monthly or Quarterly.

Requests for changes to reporting type/frequency:

• Needs to go through the Financial Analyst or Lead Financial Analyst on the project.

3.6 Other

Universal Budget Template (UBT) Issues:

• For issues with the UBT not related to Cord Field, users must contact Financial Services, which manages the UBT spreadsheet.
  • Project Managers can obtain the most recent UBT by contacting their Financial Analysts, reaching out to Financial Services, or downloading the UBT directly from the Field Library.

3.7 Domo Issues

Issues unrelated to Cord:

• Users who encounter DOMO issues unrelated to Cord Field should contact the Data Analytics Manager, Lori Gross, or the Data Architect and Analyst, Ken Jones.
• We can also redirect tickets to the DOMO queue.

The project is appearing in the outdated list in Domo/After uploading the Progress Report, DOMO continues to flag the project as "Outdated":

• It's possible that the date difference between the PnP Year & Quarter and Fiscal Year & Quarter of the current date is greater than 45 days.
• When the uploaded PnP Year & Quarter date is 45 days older than the Fiscal Year & quarter of the current date, DOMO should label the project as "Outdated."
• Once the quarterly PnP progress report for the current quarter is uploaded, it should automatically update downstream, and DOMO will remove the 'outdated' status.
  • After uploading the PnP to Cord, it may take 4-8 hours for the changes to be reflected in DOMO.

Domo Alert triggered: Invalid project status and engagement status combination:

• We need to notify the FPM about the alert and ask for a change in the engagement status. If needed, the agent can override the status after consulting with the Project Manager.