Ancient Megaprojects: Project Management Before It Had a Name

By Victor Hoang · Updated Oct 23, 2026

Picture the problem from the builder's side. A ruler or a council has set a deadline. A crowd of people who don't farm or fight needs feeding. Materials arrive by boat or cart from somewhere else. And nobody has a spreadsheet.

People ran huge, one-off builds for at least 4,500 years before anyone called the job project management. The oldest surviving work diary of a crew belongs to an Egyptian inspector named Merer. He logged limestone hauls for Khufu's pyramid around 2600 BCE. The "project manager" was described in print as a distinct job in 1959. The profession organized itself in 1969. When a job outgrows one person's head, someone writes down who does what, who feeds them, who checks them and what happens when the bill runs over. For the modern story, start with the history of project management.

The civilizations below solved that in different ways, and the records they left behind are surprisingly specific. This article walks through six of them, compares how they handled the same problems, and ends with what the long view says about megaprojects today.

One rule of the road: these builders planned and managed work, but nobody called it project management. They are precursors, not inventors of the discipline. The name and the method arrived much later, and the last section says when.

Timeline at a Glance

The Merer Logbook (around 2600-2000 BCE)

A crew's days get written down, and the grain gets counted

Start on the Nile. A boat named The Uraeus of Khufu Is Its Prow is loaded with white limestone at the Tura quarries, and an inspector named Merer notes where his team slept that night. A team led by Pierre Tallet found the papyri that preserve these entries at Wadi el-Jarf, a Red Sea harbor, in 2013. The Ancient Egypt Research Associates call the find the oldest papyrus archive found in Egypt. It was produced by a crew of sailors and stone haulers, and it includes accounting texts about goods delivered to workers.

The logbook is a work diary, not a plan. The London Review of Books, reviewing Tallet and Mark Lehner's book The Red Sea Scrolls, says Merer led a team of forty men, that the entries cover at least four months of Khufu's 26th year, and that as few as 160 workers were hauling limestone that year. An earlier 2014 journal article by Tallet and Gregory Marouard, as reported by Live Science, described Merer as in charge of about 200 men and placed the log in Khufu's 27th year, so the crew size depends on which reading you follow. History.com's account adds that the log is a two-column daily timetable and names Khufu's half-brother Ankhhaef as "chief for all the works of the king." Dates are loose. The LRB puts the writing between 2607 and 2605 BCE, while AERA dates the archive to the end of Khufu's reign, about 2551-2528 BCE. Chronologies of Khufu's reign differ by decades, so "around 2600 BCE" is the honest label.

There was a chain of command behind the diary. According to the same LRB review, a scribe named Dedi supervised four teams that supplied limestone, and titles such as "director of six" and "director of ten" appear in the records. Workers were paid in food and in lengths of fabric.

The people on the ground lived somewhere. AERA began excavating a settlement at Giza in December 1988, about 400 meters south of the Sphinx, and its site page says it covered more than seven hectares. The crown built it to support the pyramid complexes of Menkaure, Khafre and probably Khufu. Streets held workshops, bakeries, commissaries, kitchens and warehouses, and a royal administrative building had grain silos where grain was handed out for bread and beer. Egypt's own monuments authority says the settlement had four huge galleries that may have been barracks, and that skeletons show hard labor and healed fractures, which it reads as good medical care. Treat the "barracks" reading as a hypothesis.

How were all those people organized? AERA's 2011 field report notes that labor units called phyle in Greek operated in the 4th Dynasty, and that the gallery workmen were probably doing their rotation of service to the king. The documented core is simple: named teams, titled directors, rationed food and a rotating workforce.

Mesopotamia solved the same problem with clay. A British Museum tablet from Girsu (catalogued as BM 013337) dates to year 6 of the Ur III king Shu-Suen, in a period CDLI dates to about 2100-2000 BCE. It records barley to be ground and barley issued for workmen, with a named overseer and a sealing clause. This wasn't a one-off. Magnus Widell of the University of Liverpool notes that receipts are the main kind of tablet to survive from the Ur III archives, with well over 20,000 available to study.

Both societies fed, counted and recorded their workers. Neither had a schedule in the modern sense. What they had was the first habit of the field: write down who did what, with what rations, under whose authority.

What it means for teams today: a daily log with an owner behind each line is the oldest status report on record. If you can't say who is on a task and what they were given to do it, you don't have a plan yet. A project status report is Merer's diary with a template.

The Commissioner's Handbook (312 BCE-100s CE)

Rome documents its water system, and a Greek rule prices the risk

This era overlaps with the next, because Rome and China ran their great works at the same time. Stand beside a Roman aqueduct channel in the late first century CE and you would meet crews of foremen, tank attendants, inspectors, stonemasons and plasterers, each group on the payroll of the state or the emperor. The man who organized them wrote it all down.

Sextus Julius Frontinus served as Rome's water commissioner under Emperor Nerva. His handbook on the aqueducts, in the Rodgers translation hosted by LacusCurtius, says he wrote the booklet at the start of his term mainly as a guide for his own learning, and that he had diagrams made of the aqueducts so he could study a problem as if standing on the spot. It dates the first aqueduct, the Aqua Appia, to 312 BCE, when the censor Appius Claudius brought it into the city. The text also standardizes pipe sizes around a unit called the quinaria, so that capacity could be compared across pipes.

The second half of the handbook is a workforce document. In the translation's later chapters, Frontinus says the public crew numbered about 240 men and Caesar's crew 460. Each was divided into categories of workers, including foremen, tank attendants, inspectors, masons and plasterers. He complains that men were pulled off for private jobs, and says he fixed it by assigning each crew's task a day ahead and keeping a record of what was done daily. Earlier, contractors maintaining the conduits had to keep a fixed number of workmen and register their names in the public records.

That is a manager auditing a system, not a builder. But the Romans also had a view on how to price a build. The architect Vitruvius, in the preface to his tenth book, describes a rule from Ephesus: the architect's property was held as security until a public work was finished. If the cost matched the estimate, he was honored. If it ran over by up to a quarter, the public paid the excess. Beyond a quarter, he paid it himself. Vitruvius wished Rome had the same law, and he observes that owners will accept a quarter overrun but often abandon a project when costs rise by half or more.

What it means for teams today: manage the crew you have, not the one on paper. Frontinus found that pulling workers onto side jobs quietly drained his budget, and his fix was a daily assignment. Vitruvius's quarter rule is also a cleaner idea of an estimate than most project charters manage. See our guide on project cost estimation.

The Corvée Empires (221 BCE-600s CE)

Chinese states turn labor into a levy that can be scheduled

The Great Wall and the Grand Canal come to mind first, but the stranger and more useful story is the paperwork. Imagine a township official in Qin territory handing a man a strip of bamboo about three chi long. It records his property, the months he's served and the days he's worked.

That is the picture painted by Wei Chen of Wuhan University, who studied the Qin statutes on corvée labor found in the Yuelu Academy bamboo slips. In the English translation of his article, the statute calls for levying workers annually, taking wealthy individuals first in the growing season so that enough labor remains for local farming, and poorer ones in the off season. Township husbanders took part in deployments, and hamlet and field chiefs carried out the levies according to those contracts. A worker called home for a family funeral had his service extended afterward so that he completed it in full.

This is labor scheduling with a calendar, a ledger and a rule for exceptions. It rode on a unified state. The Smithsonian's National Museum of Asian Art says Qin Shihuangdi built a central bureaucracy, divided the state into provinces and prefectures run by appointed officials, standardized weights, measures, coinage and writing, and expanded roads and canals. The first Great Wall, it adds, was not the one that exists today.

The wall itself is a case in how a project grows without a single plan. Archaeologists excavating the Qi wall in Shandong reported in 2025 that some sections date to the Western Zhou, between 1046 and 771 BCE, with others from the Spring and Autumn and Warring States periods. The World History Encyclopedia says Qin used convicts sent north under guard, that the Han continued construction, and that the wall visible now is almost entirely the work of the Ming. So "the Great Wall" is not one project. It's a chain of projects by successive states, each inheriting the last one's unfinished business.

The Grand Canal followed a similar logic on water. The same encyclopedia says the Sui, after reunifying China in 589 CE, built a canal system by conscripted labor to join the Yangtze and Yellow Rivers, that three canals were eventually built, and that they carried troops and the grain tax north. It also notes the hardship the laborers endured. That is the cost side of corvée: a levy that can be scheduled can also be overspent.

What it means for teams today: a rotating, rule-bound workforce is a capacity model. The Qin statute handled the same tension every team faces now, which is that the people you borrow for the project also have a harvest to bring in. Our guide to resource allocation covers the modern version.

The Cathedral Lodge (1300s)

Masons work by the bell, and a second officer checks the pay

Walk into the masons' lodge beside York Minster in the 1350s and you'd hear a bell, not a foreman's shout, start and end the day. The Minster's Chapter had written the rules down.

The record comes from The Fabric Rolls of York Minster, edited by James Raine and published by the Surtees Society in 1859. "Fabric" means the building, and the rolls are its accounts. The volume's appendix of documents prints a Latin ordinance for the masons and other fabric workers, which the editors think was probably issued in June 1352 as the Chapter prepared to restore the choir. The two master masons and the carpenter swore before the Chapter to enforce it. Work started and stopped by the ringing of a bell, with set rest periods. Winter weeks paid a day's wage less than summer weeks, and a mason lost a day's pay when two feasts fell in a week. The masters were to report the absences and lapses of the workmen to the keeper of the fabric and the comptroller, and each man's pay was reduced to match. A man who refused the rules was to be dismissed.

A later English version, which the editors link to a sworn agreement in October 1370, adds more. Every hour was ruled by a bell, and a mason who slipped away from the lodge was to be punished by "abatyng of his payment" at the master mason's discretion. A new mason had to be tried for a week or more before the master and the keepers of the work accepted him by common consent, and then he swore to keep the rules. The editors record that master Robert de Patrington and twelve other masons swore to it on 31 October 1370.

Three ideas in that ordinance would look familiar in any modern plan. There is a probation period before someone joins the crew. There is a separation of duties, with the person who tracks attendance (the master mason) reporting to a second officer who owns the books. And working hours and pay rules were written down before the first dispute, not after.

What it means for teams today: put the rules of engagement in writing before the project starts, and have someone other than the task owner confirm the hours and the pay. York did that with a bell and a comptroller. Teams do it now with time tracking and approvals.

The Canal Builders (1666-1761)

Contractors, scope and sequence replace the royal decree

By the 1660s the question was no longer how to move a crowd but how to deliver a very specific thing for a fixed price. In 1666 Louis XIV authorized a canal across southern France, and a tax collector from Languedoc named Pierre-Paul Riquet took the contract.

The American Society of Civil Engineers describes Riquet, who had spent more than thirty years as a tax collector in the region, as the author of the plan, with help from François Andréossy and Pierre Campmas. The official canal site says the decree was signed on 7 October 1666, construction began on 1 January 1667, and a convoy of 25 boats left Toulouse on 15 May 1681. It also says the first section built was the water supply system in the Black Mountain, a sequencing choice that tells you he understood what the whole canal depended on. The summit sits 189 meters above sea level, and the ASCE adds that a reservoir at St. Ferréol stores the water released for lockages.

The people side was just as careful. The canal site says the workforce reached up to 12,000, that workers were paid a monthly salary, and that Riquet kept paying those who were sick or kept home by weather, which it calls a first for the era. The site also says the project left him heavily in debt and that he died a few months before it was finished.

Britain's version came a century later. The Linda Hall Library recounts how the Duke of Bridgewater hired James Brindley, a millwright's apprentice with no formal schooling, to build a canal from his Worsley coal mines to Manchester. The hard problem, it says, was getting coal into the boats, so the Duke, Brindley and the Duke's advisor John Gilbert decided to run the boats right into the coal seams through narrow tunnels. That fixed the boat size at about 70 feet by 7 feet. The first stage opened in 1761 with the Barton aqueduct carrying the canal over the River Irwell. It's design by requirement: the cargo defined the vessel, and the vessel defined the route.

Military engineers did something parallel with sieges. The Mont-Dauphin heritage site says Vauban (1633-1707) first used his siege method at Maastricht in 1673, took part in 14 sieges in six years, and is credited with capturing 50 towns, fortifying 300 and building 30. A UNESCO film notes that 12 groups of his fortifications are listed as World Heritage. A repeatable method, applied by one expert across many sites, was the early-modern step toward standard practice.

What it means for teams today: build the thing everything else depends on first, and let the cargo shape the vehicle. Riquet started with the water, and Brindley started with the coal. For the modern tool built on that thinking, see the work breakdown structure.

The Name Arrives (1855-present)

Railroads, charts and a title in print, then the data on overruns

Between the canals and the present, the railroads forced the next set of answers. In 1855 D.C. McCallum and G.H. Henshaw drew an organization chart for the New York and Erie Railroad, now at the Library of Congress. Charts to schedule work followed; our articles on Karol Adamiecki's harmonogram and the history of the Gantt chart pick up that thread, and the history of the org chart covers the railroad diagram in depth.

Network scheduling came next. Kelley and Walker's 1959 paper records that by May 1957 Remington Rand and duPont had begun a cooperative effort to implement what became the critical path method. The title arrived in the same years. In Harvard Business Review in 1959, Paul Gaddis wrote that a new type of manager is being bred, and that the title most generally used was project manager. The Project Management Institute was founded in 1969, which is why the history on who invented project management puts the profession's birth there. The dated timeline tracks every milestone since.

The old problem didn't go away. In his 2014 overview, Bent Flyvbjerg writes that global megaproject spending runs at USD 6 to 9 trillion a year, about 8% of world GDP. His summary of the evidence is blunt: nine out of ten such projects have cost overruns, and he calls the pattern an iron law, "Over budget, over time, over and over again." If roughly one in ten megaprojects hits its budget, one in ten its schedule and one in ten its benefits, he adds, about one in a thousand succeeds on all three. Vitruvius's quarter rule looks gentle next to that.

What it means for teams today: the tools improved a great deal, and the failure rate on very large work barely moved. Better charts don't replace a named owner for each crew, honest estimates and someone checking the books.

Key People

How the Same Problem Got Solved

Key Facts

Key Facts: Ancient Megaprojects

• The Wadi el-Jarf papyri, found in 2013, are the oldest papyrus archive found in Egypt and include logbooks of Merer's crew and accounts of goods delivered to workers.
• Frontinus reports that Rome's public aqueduct crew numbered about 240 men and Caesar's 460.
• Under the Ephesian rule Vitruvius describes, an architect paid any overrun beyond a quarter of the estimate from his own property.
• The Canal du Midi's workforce reached up to 12,000 people, paid monthly and during sickness.
• York Minster's masons had their pay docked for absences reported to a comptroller in the ordinance of about 1352.
• Flyvbjerg reports that nine out of ten megaprojects have cost overruns.

The Pattern Behind the History

Across 4,500 years, five habits recur. We call this the Ledger Pattern, an original synthesis rather than a published model: every large build that held together kept a ledger of people, owners and rules, and every one that unravelled lost track of one of them.

1. Count and feed the crew. Egypt's bakeries and silos, Ur III barley receipts and Riquet's wages all start with who is paid and fed.
2. Name an owner for every gang. Merer's team, Dedi's four teams, York's sworn master masons and the Qin township chiefs each had one accountable person.
3. Write the working rules down. Bells at York, daily assignments in Rome and levy calendars in Qin set expectations before disputes.
4. Have a second person check the first. York's comptroller and Rome's registered contractor names are early examples of separate record keepers.
5. Price the risk to someone's property. The Ephesian rule did it explicitly. Most modern projects don't, which may be why the overruns Flyvbjerg measures keep coming.

What It Teaches Teams Today

• Start with the ledger. Before a Gantt chart, write who is on the work, who owns each stream and what each has been given. A work breakdown structure and a Gantt chart assume that foundation.
• Sequence by dependency. Riquet built the water supply first. Find the thing the rest depends on, which today's critical path method formalizes.
• Separate doing from checking. The person who runs the crew shouldn't be the only one who records its hours or its spend.
• Write rules before the first dispute. York's ordinance and Frontinus's daily assignments both predate the problem they solved.
• Give estimates teeth. A number nobody pays for when it's wrong is a hope, not an estimate.

Builders have been solving the same problem since long before the word project existed. Pick the oldest habit that still fits your team, which is a written ledger with an owner on every line, and add the modern tools on top.