This page serves as a guide to various production support issues. It is organized by category and subcategory, including relevant scenario examples and troubleshooting steps when applicable. The goal is to keep this page regularly updated with new issues to share troubleshooting knowledge across teams. If the agent cannot find a satisfactory answer here, they may contact Rob Donigian, the main engineer for Cord Field. Alternatively, they may reach out to the Staff Software Engineer, Bryan Nelson, or the Software Development Director, Seth McKnight.

1. Admin, Features, and General Questions

1.1 User Accounts

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 Data & Strategy: Kasan Boyd
    • Field Growth and Field Operations: Sky Dsane
    • Finance & Translation Quality: Cari Sury
    • Office of the President and People: Kayla Spann

• ATENTION: Self-registration is currently disabled because of a rise in foreign spam accounts being created in CF.

  • The agent needs to create a person object with the user's TSCO email and ask the user to reset their password by clicking "Forgot Password?"

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:

• Some users require general project access without becoming team members. Depending on the need, roles like "Staff Member" or "Leadership" may be assigned. The agent should exercise judgment to grant the correct permissions.
  • The Leadership role grants read-only access to projects, allowing users to view all project data in Cord but preventing any modifications.
  • Verify with Product Owners for specific 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 specific project with a specific role, we should refer them to the project's Project Manager or Regional Director.

Progress Report: Field Partner and Field Operations Tabs:

• In the future, Field Partners might be given direct access to Cord Field, allowing them to update their project statuses. The "Field Partner" tab will let them enter data into Cord Field, while the "Field Operations" tab will enable Project Managers to review and correct these updates.

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 | Field Zone Pages:

• These pages are designed to assign the Regional Director to their designated Field Region and the Field Operations Director to their respective Field Zone.
  • This feature automatically assigns the correct RD and FOD after a user selects a Field Region on the project page.

Files Card Standard Folders:

• Some users might question why folders are missing from the Files card, such as whether we have a standard folder structure or what happened to the previously available folders.
  • 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, instruct users to verify if they were accidentally relocated to another folder by checking each folder individually. If items have been moved, users can easily drag and drop them within the "Files" card. Additionally, the folder path at the top of the page can be used to move folders and files as needed.
    • If you determine that the folder or file is genuinely missing (possibly deleted by mistake), check with a developer to see if it can be recovered.
  • Users can create extra folders in the Files card by clicking the "Create Folder" icon at the top right corner of the card.
  • FPMs can rename folders as needed to better suit their specific projects.

Project Workflow and Status Changes:

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

1.3 Other Cord Field Environments

Training Site Requests (Cord Field Training):

• Field Services manages the training site. For general requests like role assignments or partner additions, users should contact the Field Operations Program Coordinator, Justin Stanford, or the Field Operations Services Director, Abby Roberts.
• For system issues, the agent can reach out to the primary Cord Software Engineer, Rob Donigian.

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, the agent should verify that the user's roles include the requested permission. Utilizing the "impersonation" feature is an effective method to test this. For permissions at the Project and Engagement levels, the agent can review the Workflow UI in Cord Field.

• Consider the distinction between project-specific and global permissions.
  • For global permissions, request a developer to provide an updated permissions file from the API policies.
  • If uncertainty remains, consult the Software Development Director for further clarification.

2.3 Data Issues

2.4 PnP Issues

OBS or Storytelling PnPs displaying incorrect Cumulative Progress:

• This usually happens when percentages exceed 100%. Cord extracts the total progress but calculates the percentages over 100% and converts them into different values.
• In the past, it was acceptable to have percentages exceeding 100%, but FOLT (Field Operations Leadership Team) has since revised this policy.
• The Project Manager must update the Planning tab to accurately reflect completed stories before re-uploading the Planning PnP and Progress PnP to their designated cards.

2.5 UI Issues

2.6 Other

Posts section:

• The Cord Field UI includes a posts section where team members can share updates related to objects such as projects, languages, or partners. At present, users can select from these categories of posts within 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 encounters an error when trying to update the project status, despite having the correct permissions. This typically happens if the engagement is already at the target status or if the status isn't part of the standard workflow path.
  • The user should verify and update the engagement statuses, usually by reverting a few steps, before changing the project status.
    • If the user remains confused and unsure how to resolve the issue, the agent can either direct them to the Workflow UI or fix the problem for them.
  • For engagements in final states, this should no longer be an issue, as a fix has been implemented. However, if a rare issue occurs, the agent can update the status on behalf of the user to ensure the engagement status that caused the problem is corrected to the proper status.

Global Translation Leaders (GTL) Fundraising Page:

Seed Company's GTL is a program that benefits from generous investors—individuals, families, small groups, churches, businesses, and foundations—who support training and leadership in Bible translation worldwide.

• This page retrieves information for each Global Translation Leader from Cord and the remaining need from Domo. Since the Remaining Need is updated through Domo, it won't reflect changes immediately after a donation but only during Domo's update cycle. Users can view the landing page and individual Global Translation Leaders at seed.bible/global-translation-leaders.

  • In Cord Field, the data for the GTL Fundraising page is collected from various system components:
    • Photo, name, and gender are retrieved from the person profile page. The name is taken from the public name field, specifically the first name. It is advisable to keep the public last name blank or use a pseudonym if needed, in accordance with the Prudence Protocol.
    • GTL ID, Focus, and biography are obtained from the intern's engagement page. The Focus is specifically sourced from the intern's Position chip, but only at the higher level.
    • The Region is sourced from the project's Marketing Location.

3. Process

3.1 Project Team Management

Requests to temporarily add Consultant role to user's profile:

• In the Field teams, it is common for other Seed Company staff to be temporarily assigned to review and endorse projects when the project's consultant is unavailable.
  • The agent may add the requested role but should monitor the change to remove it when no longer necessary.

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.

Percentages under the PnP step headers:

• The percentages may be adjusted based on various processes used by field partners. These percentages are not directly imported into Cord Field; instead, they contribute to the cumulative summary percentages of the PnP.

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

• Ensure that the uploaded file is the correct PnP for the specific project and quarter.
• Verify that the file is indeed a PnP and not another type of spreadsheet.
  • If the file is correct but the issue still persists, instruct the user to download a new PnP from the Field Library, transfer the data to the new PnP, and then re-upload the file to Cord.
    • If this does not resolve the issue, contact an engineer for further investigation.

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 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.

• If the data is available and the correct Reporting Quarter has been selected in the PnP, please contact the development team for debugging. If not, there may be a formula issue. In this case, the user should try downloading a new version of the PnP from the Field Operations Library or reach out to Harold Good, the owner of the PnP, for assistance.

Issue with selecting the correct reporting quarter:

• The PnP MOU dates are restricted to a five-year limit, likely to match business requirements. If a user attempts to set project MOU dates beyond this period, they won't be able to choose the final reporting quarter in the Progress tab, receiving options like "On track" or "Completed" instead. There may also be mismatches between the MOU dates in the Planning tab and Cord Field, which need to be corrected. Once the dates are aligned between the PnP and Cord, the reporting quarter selection issue should be resolved.

Progress details do not update when the progress report is uploaded for the quarter:

• Verify that step headers are correct in the planning and progress sheets.
• Confirm that the PnP project date range in the Excel file aligns with the actual project start and end dates.
• Ensure the selected Reporting Quarter in the PnP progress sheet matches the quarter the user is uploading the file for.
  • The "Percent Finished & Cumulative sections" will only update if the reporting quarter is correct, as CF reads them to get progress updates.
• Make sure all your scripture goals are identifiable and match those listed in the language engagement overview page from your initial upload of the PnP planning sheet.

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

• Review the PnP planning sheet to ensure a valid scripture reference is entered in the "My notes" column.
• If the reference is incorrect or missing, the user should delete that goal, input the correct scripture reference into the PnP planning sheet, and then re-upload the sheet.

Goals, progress, or steps that are empty or not planned for a specific book:

There might have been a problem with the initial PnP Plan upload, so the user should consider these solutions: verify the spreadsheet version shown next to the project name, and ensure they are using the latest version from the Field Operations Library to prevent parsing issues due to 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 shows whether completing this phase of the project will result in a full Old Testament, a full New Testament, or the entire Bible. It should be established at the start of the project as a target for the next three years. Please refer to the following terms for reference:
  • 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" indicates the use of Artificial Intelligence or Machine Learning tools and processes within the project. Please see the following definitions for clarification:
  • "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 for field users: If users know AI-Assisted Drafting is enabled but are unsure if AI-Assisted Consultant Checking is active, they should click "Draft." If they later discover it is, they need to update the setting 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.
  • The correct process appears to be updating the project status to “Discussing CtP” first, before changing the engagement statuses to “Discussing Suspension” or “Termination”. If the engagements are updated first, the project status change will override the engagement statuses.
• 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 directly submit for Finance approval when it aligns with the pre-established guidelines. This eliminates the need to first “Submit for (RD) Approval” and then immediately “Approve (RD) Change to Plan” to reach Finance.
• As a result, Project Managers are now prohibited from approving or rejecting Plan Changes on behalf of an RD. This workaround is no longer necessary thanks to the new transition addition mentioned above.
• Finally, Project Managers can “retract” their approval request, whether from an RD or Finance, to make additional changes. This prevents them from getting “stuck” and needing the agent’s help to retract or 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:

• Verify that the funding partner indicates the project will be funded until the end of the internship, aligning with the project's dates.
• Cord will default to using the project's MOU dates if the dates are not specified on the partnership cards.

Requests to update the Field Budget amounts:

• The Field Project Manager collaborates with the Financial Analyst to create a budget during project development. After approval and once the project is Active, any updates to the budget require a Change Request. To ensure financial oversight, only the Financial Analyst has the authority to update the budget. * It is important to note that the Financial Services team has not updated the Field Budget figures for active projects to prevent errors, as they regard Intacct as the sole source of truth. They have requested an integration of Intacct with Cord, and we currently have an open GitHub issue to handle this request.

Requests to upload more photos to reports:

• Currently, users can upload only one photo in the quarterly report section. Additional photos can be added to a photos folder within 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, the agent must contact the developers 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 managed through a Change to Plan. The FPM should contact the Financial Analyst, who is authorized to update the dates. If the FA is unavailable, a Lead Financial Analyst or Controller can also make the changes.
  • 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 relates to the progress report’s Team News and Story sections. Each variant box (Investor Communication, Field Operations, Translation, Partner) is assigned a role like Project Manager, Marketing, or Partner. If the logged-in user hasn’t completed one of these sections, a notification will appear, prompting them to fill it out before submitting. This alert is just a reminder, not an error. Users can ignore it and submit the report even if some sections are incomplete.

• For Project Managers, notifications are tied to the Field Operations section. If the Story and Team News sections of the Field Operations box are completed, they should not receive any notifications.
• FPMs have the ability to edit other sections, including the Partner section. However, they will only be notified about updates in the Field Operations section if no data has been entered there.
• Translation variant: the translation variant box is used when a partner shares a story in their local language, enabling the FPM to translate it into English.

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

• Previously, reviving DnD projects was not allowed, but Field Services has now changed this policy. It is now possible to move projects from “Did not Develop” back to “In Development.” However, the agent must involve the Field Services team before making this change in Cord Field.
  • When updating the project status, the agent must also manually update each engagement status, as they don’t change automatically with the project status.

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, then click 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 receive 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.
• Abby Roberts and Justin Stanford now handle all language requests and should receive them through ZenDesk tickets.

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.

Legacy Google Sheet Request Responses:

https://docs.google.com/spreadsheets/d/1_hUyu24pdRTfLdKnLQF4Tf0j_0m9brQPUHPdxktMk-k/edit?pli=1&gid=2029259026#gid=2029259026

Language Engagement Data Management (ProgressBible):

• Source of Record:

  • ProgressBible (PB) treats Seed Company–submitted source data as authoritative for establishing and maintaining Language Engagements.
  • Each Language Engagement is tied to an ISO language code, which directly drives Translation Status and All Access visibility.

• ISO Language Code Updates:

  • When Field Ops updates the ISO language code for an existing engagement:
    • The new ISO code fully replaces the previous code in the Language Engagement record.
    • The previous ISO code is no longer retained or referenced for Translation Status or All Access calculations.
  • If the removed ISO code was contributed only by Seed Company (i.e., no other organizations reporting activity):
    • The language may automatically move from Translation in Progress to Translation Not Started, or potentially to Potential Need, based on remaining data.

• ROLV Code Updates:

  • When a ROLV code is updated but the ISO language code remains unchanged:
    • The updated ROLV code will appear in the current reporting month for that Language Engagement.
    • The prior ROLV code will no longer appear in the current month but will remain visible in historical reports for prior months.
  • ROLV changes do not create a new Language Engagement when the ISO code remains the same.

• Monthly Reporting Model:

  • ProgressBible operates on a monthly reporting cycle.
  • Each month is treated as a new snapshot of partner-submitted data.
  • Data from prior months is not rolled forward into future months; historical data remains fixed for reporting and audit purposes.

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 agent may proceed with the communication on his behalf.
    • Ask which stakeholders need to be informed.

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.

Multiplication Languages:

• The general process for Multiplication Language Requests is managed in Monday, and Field Services now handles all Language Requests, including those for Multiplication languages.
  • Field Services must determine the best process for new languages and current language management. Any questions or requests must be directed to them.

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.