Qualitative and quantitative measurement: definitions, the differences with examples, and the three ways to combine them on one record.
Qualitative and quantitative measurements are the two ways to measure an outcome: a number that shows how much changed and the open-text evidence that shows what changed and why. Sopact keeps both on the Connected Record, the metric and the evidence behind it on one participant record under a persistent Contact ID, so an outcome carries its proof instead of a bare figure someone has to defend later.
Impact leads say the same thing on almost every call: “outcomes instead of outputs… we don’t have a mechanism for tracking outcomes right now.” They can measure dollars and hours, but a number with no evidence is hard to trust, and the qualitative proof that would back it up sits in a separate document until an eight-to-nine-month analysis cycle finally reaches it.
Key takeaways
A measurement stack that stores only numbers produces figures no one can defend. The rating of a change goes into a survey tool, the participant’s account of the change goes into a document, and the two are never joined, so an outcome number arrives without the sentence that would prove it. Reconstructing the evidence at report time is slow and easy to dispute.
Sopact is record-centric: the qualitative evidence is read on arrival against a codebook and tied to the same persistent ID as the metric, so an outcome measurement carries its proof on the Connected Record. See the numbers side on quantitative data collection methods, or measure over time on longitudinal data collection software.
Outcome measurement usually spans SPSS, Excel, Qualtrics, SurveyMonkey, and Google Forms for the numbers, with NVivo, MAXQDA, or Dedoose for the narrative when a team has the capacity. Each measures its own half well, and each keeps its output in a separate file, so a metric and the evidence behind it are captured apart and rejoined by hand for a board or a funder.
The one test that sorts them: ask the stack to show an outcome number with the exact participant sentence that evidences it, on one record, and the same view for the prior period. A numbers-only tool answers with a figure and no proof. Sopact answers from the Connected Record, because the evidence was read on arrival and tied to the metric.
The move that makes a measurement defensible is reading the participant’s account against a codebook as it lands, so each outcome number arrives with the sentence that evidences it. Sopact extracts the evidence from the responses and documents a program already collects, so a measurement reduces reporting burden rather than adding a survey on top of what participants already wrote.
Kept on the Connected Record, the measurement is longitudinal: an outcome and its evidence across every wave on one persistent ID, each figure traceable to a sentence. Sopact reads on arrival, so a program measures what changed and can show why, in time to act rather than at the end of a cycle.
A numbers-only stack stores the metric and leaves the evidence in a separate system; the Connected Record reads the qualitative evidence on arrival and ties it to the metric. The difference is whether an outcome carries its proof or a bare figure.
| The question | Number only | Connected Record |
|---|---|---|
| Measure how much changed? | Yes: the metric | Yes, on the participant record |
| Evidence what changed? | In a separate doc | Yes: the sentence, on arrival |
| Defend the figure to a funder? | Reconstructed later | Yes: number and evidence tied |
| Measure the same over time? | Re-typed each period | One persistent record per participant |
See the analysis discipline on mixed-methods data analysis, or compare the two families on qualitative vs quantitative.
A dropping score is worth understanding while you can still respond to it, not in a report written after the program ends. The value of the open-text behind a number is highest the moment it lands, when the reason for a low rating can still change what happens next. That is the premise of the Loop, Sopact’s method for continuous intelligence: collect clean at the source, with the number and the open-text explaining it on one participant record; analyze on arrival, reading each open-text answer against a codebook the moment it lands and tying it to the number; improve in time, so the reason behind a dropping score surfaces while you can still act.
The Loop is also what makes a mixed-methods finding defensible: every theme traces back to the exact sentence a respondent wrote and the number that respondent also gave, the standard detailed in Loop traceability, so a conclusion rests on the Connected Record rather than a hand-coded spreadsheet no one can re-check.
One method, three moves that never stop
Then the next wave reads a little sharper. Read the method: the Loop methodology →
The fastest way to see a measurement with evidence is to run it on your own data. Export an outcome metric with the participant open-text on the same IDs, then paste the prompts below into Sopact Sense’s Assistant, or reason through them with your team. The arrow above each links the Academy walkthrough with the expected output and tips.
Academy walkthrough → Analyze open-ended responses
Here is a batch of open-ended survey responses with each respondent's ID and their rating: [ATTACH]. Read each open-text answer against our codebook as it lands, tag the themes, quote the exact sentence behind each theme, and keep every answer tied to the number the same respondent gave, so I can read the reason next to the score on one record instead of in two separate exports.
Academy walkthrough → Connect the number and the reason
Here is our quantitative data and the open-ended responses on the same participant IDs: [ATTACH]. For each rating, pull the open-text the same respondent wrote that explains it, quote the sentence, and show the number and the reason on one record, so a low score carries the reason a respondent gave rather than sitting in a column with no explanation.
Academy walkthrough → Clean open-ended responses
Here is a raw export of open-ended responses on their participant IDs: [ATTACH]. Flag blanks, duplicates, and off-topic answers, normalize the text so it is analyzable, and keep each cleaned answer tied to its ID and the number that respondent gave, so the open-text is ready to read against a codebook on arrival rather than after a month of hand-cleaning.
Academy walkthrough → Find the drivers behind a score
Here are ratings and the open-ended responses on the same IDs: [ATTACH]. Read the sentiment in each answer, identify the drivers behind the rating with the sentence quoted, and tie each driver to the number, so I can see what is pushing a score up or down from the respondent's own words rather than guessing behind the average.
Each walkthrough is short and practical: what to do, the prompt to run, the output to expect, and the tips that keep it reliable.
Watch: reading open-text against a codebook on arrival and keeping every answer tied to the number on one Connected Record.
They are the two ways to measure an outcome: a number for how much changed and the open-text evidence for what changed and why. Sopact keeps both on the Connected Record, so an outcome carries its proof instead of a bare figure someone defends later.
Because a figure with no proof is hard to trust and easy to dispute. Sopact reads the qualitative evidence on arrival against a codebook and ties it to the metric on the Connected Record, so an outcome number arrives with the participant sentence that evidences it.
A survey tool stores the metric and leaves the evidence in a separate document. Sopact is record-centric: it reads the evidence on arrival and keeps the number and its proof on one Connected Record, so a measurement is defensible.
Yes. Sopact reads the participant’s own words against a codebook and separates what was delivered from what changed, tying the outcome to the sentence behind it on the Connected Record, so a program reports outcomes rather than activity counts.
No. Sopact extracts evidence from the responses and documents you already collect, which reduces reporting burden. The evidence stays on the Connected Record, quoted from the participant’s own words.
Yes. Sopact reads each account against the same codebook, so the evidence and the theme are the same on every run and each traces to a sentence. The Connected Record keeps the metric and its proof together, which makes the measurement defensible.
No. Sopact drafts the evidence and the theme from the participant’s words with the sentence quoted; a human confirms or overrides them, human-in-the-loop. The Connected Record records what was read and from which response.
Sopact keeps every metric and its evidence on one persistent ID, so an outcome across periods is read as a trajectory. The Connected Record survives each cycle, which is what makes a longitudinal, defensible measurement possible.
Next: capture both in one instrument on qualitative and quantitative survey, or measure over time on longitudinal data collection software.
