By Unmesh Sheth, Founder and CEO, Sopact. All fund, company and numerical examples are fictional.
Quarterly collection starts with an obligation: this company is expected to provide these measures for this period. The request should show the definitions already agreed, accept appropriate supporting files and make unknown answers explicit.
Nina prepares Cedar's Q2 cycle. RouteWorks and Harbor Homes receive their approved custom measures. MarketLink receives its legacy survey while the new dictionary is being developed. A fourth company whose reporting obligation ended is not included in the expected-return denominator unless its agreement requires a final report.
Build the expected-return register first
Record the company, relevant agreement, reporting period, deployment date, due date, preferred reporting contact, relationship owner, dictionary version and whether a return is required. Keep a reason and approver for exceptions.
The agreement determines the obligation. An inactive CRM status or maturity date may be relevant, but neither should independently erase a final reporting requirement. Review exceptions explicitly.
Separate collection status from approval status. A return can be received on time and still await review. Useful states include Expected, Sent, Received, Clarification requested, Approved, Waived and Overdue. Store the dates needed to reconstruct the path.
Generate a request the company recognizes
Use the applicability and validation rules established with the dictionary-building guide to decide which questions appear, what values they accept and which missing states they preserve. The collector should not need to interpret a lengthy methodology note to supply an answer.
Show the company name and reporting period clearly. List the metric name, then its definition, in the dictionary's order. Supply numeric and explanatory fields where needed. Show units and whether the question concerns a period total, cumulative value or point-in-time observation.
A dictionary-driven survey is only useful if it reproduces the approved version. Compare the generated form with the dictionary before sending it. If the system cannot generate part of the form, document the manual step and its review.
| Answer | Store it as | Meaning |
|---|---|---|
| 0, confirmed by the company | Numeric zero with submitted status | No qualifying result under this definition |
| “Don't know” | Null value plus Unknown status | The company cannot provide the result |
| Blank required answer | Null value plus Missing status | No usable response supplied |
| Not yet required | Null value plus Not yet due status | The approved collection schedule does not yet require it |
| Not applicable | Null value plus approved reason | The measure does not apply to this company or period |
Do not rely on an AI model to guess which meaning a blank had. Prefer an explicit status choice. If free text is accepted, test its normalization and preserve the original response.
Ask for changes and missing evidence, not the whole CRM again
Before deployment, compare this period's required observations with approved evidence already available. Prepopulate stable company context with its source and last-updated date. Display prior-period results as reference values, clearly labeled. Never carry an old result into a new quarter as if it had been reported again.
If a permitted financial file already contains a required current-period value, prepare a proposed extraction for confirmation instead of asking the company to type the same value. Hide irrelevant questions according to the approved company dictionary and schedule. Ask the company to confirm changed context, provide current results and resolve specific gaps.
Create one consolidated request per company and period, even when several donors need its results. Reuse an observation across authorized report views when its definition and scope match. Keep genuinely different donor requirements visible so consolidation does not erase a needed geographic breakdown or evidence requirement.
The recurring cycle should create expected returns from approved schedules, prepare the right questions, record submissions and create exceptions for missing or inconsistent evidence. Send reminders only for outstanding items to the responsible contact, and stop the reminder when the item is resolved, waived or no longer due. Set reminder timing and escalation with the team; do not assume automation should email everyone immediately.
Accept the evidence companies already maintain
RouteWorks can upload its program report and financial statement rather than retyping every value. Ask for source period and document type. List the file formats actually accepted by the configured upload control. Use an existing report only when it supplies the requested evidence; request the missing definition or period separately.
A company workspace can make its dictionary, model, prior returns and approved insights available together. Test what company users can view and correct, and ensure the workspace does not expose internal review notes or another company's information.
Accessibility is part of collection quality. Check meaningful labels, keyboard use, required-field instructions, readable contrast and screen-reader announcements for errors and successful submission. Test these behaviors rather than inferring accessibility from appearance.
Follow up according to the real status
Set a reminder policy with the relationship owner. Specify the first reminder, repeat interval, escalation, pause conditions and exceptions. One fund may need frequent follow-up; another may agree a different cadence. Do not make a client-specific schedule a universal recommendation.
Pause missing-return reminders when the return arrives, when an approved extension applies or when the obligation is waived. A received return awaiting Nina's review should not trigger another “please submit” email. Keep the outbound request, reply, owner and resolution together.
MarketLink is overdue. Its relationship owner records the known reason and next contact date. RouteWorks has submitted and should receive no missing-return reminder, even though its financial evidence will require clarification in the next lesson.
Build this part of your plan
Create the expected-return register for RouteWorks, Harbor Homes and MarketLink. Give each its own dictionary or legacy-survey version. Write RouteWorks's reach question, including the unknown option, and one consolidated reminder for MarketLink. Name the conditions that stop automated reminders.
Check your reasoning: all three are expected this quarter; two have submitted. Submission coverage is 2 of 3. That does not mean two returns are approved, or that every requested metric is available. An excluded company stays visible with its exemption reason rather than silently disappearing.
Test a tool: submit zero, unknown and blank in three test records. Confirm they remain different in the dataset and report. Submit a return after a reminder is queued and verify the workflow does not continue treating it as absent.