Checking procurement proposals
Check whether a supplier’s proposal actually provides evidence for each procurement requirement.
Technical
Bachelor’s · applied project
Final result
A comparison prototype and usability report.
Material to create
3 fictional IT tenders × 4 supplier bids
Each tender has 10 requirements. Vary 0–4 unsupported claims and 0–2 contradictions per bid, including clean bids. Keep a hidden, independently reviewed answer key.
What to do
- Build a procurement comparison table with links to supporting bid paragraphs.
How it is tested
Use fictional bids and the hidden issue key; test link correctness and observe reviewers completing comparison tasks. Plan 4 participant sessions.
Before you start
Example tools · HTML/CSS/JavaScript, JSON, spreadsheet These are suggestions; equivalent tools are fine.
Access or people · Recruit students and an independent answer-key reviewer.
Research method · Build and test · 6 steps
- Read the starting sources and choose one established implementation method.
- Write the requirements, data fields, system diagram and test cases.
- Prepare 3 fictional IT tenders × 4 supplier bids. Make the answer key and pass criteria before testing.
- Build a working version of a comparison prototype and usability report.
- Run function, integration and failure-case tests. Record each result.
- Run the practical evaluation and list the changes the system still needs.
Download the complete bachelor plan
Download bachelor instructionsMaster’s · research project
Final result
Comparison screen, bid set and review results.
Material to create
3 fictional IT tenders × 4 supplier bids
Each tender has 10 requirements. Vary 0–4 unsupported claims and 0–2 contradictions per bid, including clean bids. Keep a hidden, independently reviewed answer key.
What to do
- Represent Requirement, Claim and EvidencePassage nodes in a validated JSON-schema graph with stable paragraph hashes and bidirectional indexes.
- Compare direct paragraph navigation with document/page/paragraph references using identical bid packs and a Latin-square assignment.
- Verify schemas, foreign keys, hashes and link resolution; report fault-type precision/recall/F1, clean-bid false alarms, source openings and confidence calibration.
How it is tested
8 IS students review 6 non-overlapping bids, 3 per condition, with identical claims and accessible source packs. Balance order and bid difficulty; hide fault counts. Report per-person misses, false alarms, time, confidence and evidence-backed reasons.
Before you start
Example tools · HTML/CSS/JavaScript, JSON, spreadsheet These are suggestions; equivalent tools are fine.
Access or people · Recruit 8 students and an independent answer-key reviewer.
Start with these three actions
- Write one tender with 10 requirements and one clean bid.
- Create clean and faulty bids with varied fault counts; independently review the hidden answer key.
- Prepare non-overlapping matched bid sets and pilot a single review task before recruitment.
Files, questions and sources
Pilot question: Do direct source links help reviewers find unsupported supplier claims and contradictions?
Literature search: procurement decision support evidence traceability verification
Empty CSV templates: data-plan.csv · evaluation.csv · literature-matrix.csv
Download starter instructionsResearch method · Design, build and test (DSR) · 7 steps
- Read the newest papers and list the closest existing systems.
- Write down the versions, fields, data split, case assignment, random seeds and correct answers for 3 fictional IT tenders × 4 supplier bids.
- Draw the user workflow, data model and system architecture. List the requirements and pass criteria.
- Build a working version of comparison screen, bid set and review results.
- Test every function, connection and failure case. Save the failed tests as well as the passed tests.
- Compare the system with the named alternative. Then run the user task or decision task in the assignment.
- Report the measured result, the failed cases and the design lessons another team can reuse.
Research question and sources
Research question: Test whether source navigation helps reviewers distinguish documented evidence from persuasive claims. Compare identical bids with direct paragraph links versus equivalent document, page and paragraph references; separate clean bids and fault types.
Research result: Measured effects of source links on missed claims, false alarms, review time and reviewer confidence.
Current project literature
- AI-based decision support system for public procurement (2023) peer-reviewed
Presents an IS artifact integrating tender text, semantic search and decision support. - Enhancing transparency in public procurement: A data-driven analytics approach (2024) peer-reviewed
Evaluates a public-procurement information-system artifact for transparent analysis.
IS theory starting points
- Vasconcelos et al. (2023) — Explanations Can Reduce Overreliance — Compare verification cost with trust as explanations of observed decisions.
- Wang & Strong (1996) — Beyond Accuracy — Distinguish accuracy, completeness, representation and fitness for the task.
Search Scopus or Web of Science and ACM Digital Library using the topic query, then follow citations to the thesis start date. Record searches and compare methods, data, findings and limitations in literature-matrix.csv. Use that review to confirm or revise the gap and choose a current comparator. The linked papers are starting points.
Search terms: procurement decision support evidence traceability verification
Non-technical
Bachelor’s · applied project
Final result
An evidence checklist and proposed comparison template.
Material to create
8 fictional bids
Two IT tenders, 4 bids each, 10 requirements/tender. Vary 0–4 unsupported claims and 0–2 contradictions, including clean bids; hide counts from reviewers.
What to do
- Document which evidence reviewers need to compare procurement bids.
How it is tested
Use fictional bid packs in scenario interviews; trace each concern to a missing or unclear document item. Plan 4 participant sessions.
Before you start
Example tools · LibreOffice Writer/Calc, audio recorder with consent; no programming required. These are suggestions; equivalent tools are fine.
Access or people · Recruit procurement staff; no confidential tenders.
Research method · Study and improve · 6 steps
- Read the starting sources and write the exact information problem.
- Prepare 8 fictional bids and a separate answer sheet or coding sheet.
- Run one pilot and fix unclear questions.
- Collect the named evidence with consent.
- Group the findings with the stated categories and check the answer sheet.
- Produce an evidence checklist and proposed comparison template. List the three most useful changes.
Download the complete bachelor plan
Download bachelor instructionsMaster’s · research project
Final result
Evidence checklist and findings on missed supplier claims.
Material to create
8 fictional bids + 6 procurement reviewers
Two IT tenders, 4 bids each, 10 requirements/tender. Vary 0–4 unsupported claims and 0–2 contradictions, including clean bids; hide counts from reviewers.
What to do
- Prepare the same bids as documents and a manual comparison spreadsheet.
- Observe reviewers checking evidence and resolving contradictory claims.
How it is tested
Think-aloud document review; count detected faults against the answer key and code verification strategies.
Before you start
Example tools · LibreOffice Writer/Calc, audio recorder with consent; no programming required. These are suggestions; equivalent tools are fine.
Access or people · Recruit procurement staff; no confidential tenders.
Start with these three actions
- Prepare a pilot with 2 examples from: 8 fictional bids + 6 procurement reviewers. Write the task questions and a reference answer sheet.
- Write a recruitment message, information sheet and consent form for the participants named above. Agree privacy handling with the supervisor before contact.
- Pilot one session after approval; revise unclear questions, finalise the task sets and coding categories, then recruit the planned sample.
Files, questions and sources
Pilot question: Which verification strategies help procurement reviewers identify unsupported claims?
Literature search: procurement decision support evidence traceability verification qualitative scenario study
Interview prompts
- Which requirement is not supported by evidence?
- Which passage supports or contradicts the supplier claim?
- Would you accept this evidence, and what would you clarify?
Empty CSV templates: study-plan.csv · coding-sheet.csv · literature-matrix.csv
Download starter instructionsResearch method · Study, compare and explain · 7 steps
- Read the newest papers and write one exact research question.
- State which people, cases or documents you will study and what you will compare.
- Write the selection rules, questions and analysis steps for 8 fictional bids + 6 procurement reviewers.
- Run one pilot. Fix unclear questions or categories, then keep the guide unchanged.
- Collect the named interviews, cases or documents with consent.
- Analyse them with the stated comparison or coding method. Keep disagreements and missing data.
- Report the answer, the evidence and the practical output named in the assignment.
Research question and sources
Research question: Explain why reviewers accept different evidence for the same procurement criterion. Contrast verification cost with professional role expectations; examine disputed and clean bids without assuming consensus is truth.
Research result: A theory-based account of evidence sufficiency and review responsibility.
Current project literature
- AI-based decision support system for public procurement (2023) peer-reviewed
Presents an IS artifact integrating tender text, semantic search and decision support. - Enhancing transparency in public procurement: A data-driven analytics approach (2024) peer-reviewed
Evaluates a public-procurement information-system artifact for transparent analysis.
IS theory starting points
- Orlikowski & Gash (1994) — Technological Frames — Compare how roles interpret the purpose, operation and use of the same system.
- Vasconcelos et al. (2023) — Explanations Can Reduce Overreliance — Compare verification cost with trust as explanations of observed decisions.
Search Scopus or Web of Science and ACM Digital Library using the topic query, then follow citations to the thesis start date. Record searches and compare methods, data, findings and limitations in literature-matrix.csv. Use that review to confirm or revise the gap and choose a current comparator. The linked papers are starting points.
Search terms: procurement decision support evidence traceability verification qualitative scenario study
Your degree, track and shortlist are saved in this browser.