Daniel Jorge

Insights

Practical questions, explanatory guides and decision frameworks. Enough detail to make your next conversation better—not a promise that one article can replace a professional team.

86 pages

Execution

Developer and contractor: different responsibilities

A construction contract describes work to deliver. A development decision asks whether the entire undertaking deserves the next commitment. Confusing those responsibilities can leave a technically buildable project without a credible customer, sufficient funding or an operating plan.

Execution

From construction scope to whole-project decisions

Knowing how to build is useful preparation for development, but construction knowledge answers only part of the investment question. The transition requires a wider decision perimeter: what happens before the contract, outside its scope and after the building opens.

Execution

The professional team behind a development decision

A long consultant list is not the same as an effective team. Professional appointments become useful when each assignment answers a defined uncertainty and its findings reach the person deciding whether the project should proceed.

Execution

Align design decisions with a supportable budget

Design and budget need a shared reference point. If one team prices an earlier scheme while another develops a more demanding specification, the apparent agreement on cost is fictional. Establish the design version and scope before debating affordability.

Execution

Procurement timing belongs in the project schedule

An item can fit the budget and still threaten the opening date. Procurement has its own sequence of decisions, approvals, fabrication and delivery. A schedule that starts with installation hides the work required to make installation possible.

Execution

Scope gaps are a coordination problem before a cost problem

A gap often appears where two valid proposals meet. Each contractor may have clearly described its own work while neither included the connection between them. Comparing bottom-line prices will not reveal that missing responsibility.

Execution

Track proposed changes before they become surprises

A proposed change deserves visibility before anyone agrees on its final price. Waiting for a signed change order can leave ownership reviewing an obsolete forecast while the team already knows the approved plan is unlikely to hold.

Execution

Forecast cost to complete, not just cost paid

Paid invoices describe part of the past. Ownership needs an estimate of everything still required to reach the intended operating condition. A project can show modest spending today and a serious funding shortfall tomorrow because commitments and unresolved work remain invisible.

Execution

A schedule is a map of dependencies

Dates are useful only when the conditions behind them are visible. A schedule should explain why an activity can start and what its completion enables. Otherwise, moving a bar on the chart can disguise an unresolved commitment rather than solve a delay.

Execution

What a useful site report should tell ownership

A collection of photographs can show activity without explaining whether the project is on plan. Ownership reporting should connect observed conditions with commitments, exceptions and decisions. The reader should know what changed and what requires action without reconstructing the entire construction meeting.

Execution

Quality control and handover planning

Handover begins with a definition of acceptable completion. If ownership waits until the final walk to decide what records, testing and training it needs, a finished-looking property can arrive without the information required to operate or maintain it.

Execution

Completion, occupancy and stabilization are different milestones

A building can be physically complete without being ready for lawful occupancy, fully leased or eligible for permanent financing. A development forecast becomes unreliable when it collapses those transitions into a single opening date and assumes cash follows immediately.

Execution

Plan lease-up before the building is finished

Lease-up is an operating process with its own staffing, information and cash requirements. Starting advertisements near completion does not replace a plan for converting inquiries into lawful agreements, move-ins and collected rent. Construction progress and customer readiness must be coordinated.

Execution

Operating readiness starts during development

Opening transfers the project from a construction organization to a service organization. That transfer needs owners, procedures and usable information. A manager appointed on the last day may inherit equipment, customer promises and reporting obligations that nobody prepared it to handle.

Execution

Capital expenditure planning after opening

A new building still needs a plan for future replacement and improvement. Treating all post-opening spending as an operating surprise can make reported cash look stronger than the asset's actual ability to sustain service and meet ownership obligations.

Execution

How to write a project lesson without rewriting history

A lesson learned should preserve what was known when a decision was made. If the account quietly replaces uncertainty with hindsight, it teaches the wrong procedure and makes an avoidable problem appear obvious only after the outcome became clear.

Partnerships & leadership

What makes a developer partnership worth exploring

A partnership is worth exploring when the parties can explain what they contribute and why coordinated work is preferable to a simpler arrangement. Shared enthusiasm for a property is not enough to establish compatible objectives, working habits or tolerance for uncertainty.

Partnerships & leadership

What a broker brief should contain

A useful broker brief helps a licensed professional distinguish a relevant lead from an attractive distraction. It describes the search decision and its limits, not merely a preferred city and an ambitious project size. Clear criteria make feedback more actionable.

Partnerships & leadership

Align landowner expectations before discussing structure

A landowner may value certainty, timing and continuing involvement very differently from a developer. Those preferences should be visible before discussions turn to a sale, contribution or other arrangement. A creative structure cannot repair objectives the parties never honestly compared.

Partnerships & leadership

Roles and decision rights before economics

An ownership percentage does not tell the team who may approve a redesign, sign a financing amendment or stop a purchase. Governance needs an explicit decision map before economic terms can be understood as a workable relationship.

Partnerships & leadership

Questions about additional capital before a commitment

A balanced opening budget does not explain who funds a later shortfall. Additional capital questions belong before commitment, when the parties can still compare obligations calmly. A spreadsheet can calculate a gap; it cannot create an obligation or willingness to contribute.

Partnerships & leadership

Distribution waterfalls: a fictional teaching example

A distribution waterfall describes the order in which available cash is allocated under an agreement. It does not create cash. Understanding the sequence is more useful than remembering a preferred-return percentage without knowing what must happen before or after it.

Partnerships & leadership

Reporting is part of the relationship

Partnership reporting is an agreed information obligation, not a favor provided when results look encouraging. The parties need a common view of performance, uncertainty and upcoming decisions. A polished update is inadequate if it hides exceptions that could change their obligations.

Partnerships & leadership

Identify conflicts before they shape decisions

A conflict can exist even when a proposed service is competent and the price appears reasonable. The issue is whether another interest could influence judgment, information or approval. Disclosure should arrive before the affected decision, not after someone discovers the relationship.

Partnerships & leadership

Cross-border conversations need clear professional boundaries

A shared language can make a development conversation easier without making the legal setting familiar. International participants may attach different meanings to ownership, guarantees, taxes and professional roles. Begin by establishing which jurisdiction and relationship the conversation actually concerns.

Partnerships & leadership

Education and an investment offering are not interchangeable

An educational discussion can explain capital structures without presenting an investment opportunity. The distinction depends on the actual content and circumstances, not simply a label at the bottom of a page. Calling a communication educational does not settle its legal character.

Partnerships & leadership

Expansion should follow operating capacity

Another project adds more than potential revenue. It adds decisions, cash demands, reporting and service obligations that may arrive at the same time as existing commitments. Expansion deserves a capacity test before it becomes a geographic or portfolio target.

Partnerships & leadership

Why an Orlando headquarters can support a broader Florida focus

Daniel Jorge's headquarters remains in Orlando. A headquarters can organize analysis and ownership decisions across a broader area, but its address does not establish local market knowledge or delivery capacity everywhere. Regional work still needs evidence and appropriate professionals on the ground.

Partnerships & leadership

What prospecting in Miami means, and does not mean

Miami prospecting means investigating whether a market and particular opportunities merit further work. It is not a claim of an operating Miami office, an approved project or local delivery commitments. The Miami office is planned; Orlando remains the headquarters.

Partnerships & leadership

A disciplined decision not to proceed

Declining a project can be the result of useful development work. The decision becomes defensible when it identifies the evidence, unresolved exposure and commitment that no longer makes sense. An unexplained rejection teaches little; a clear decision record preserves the reasoning.

Partnerships & leadership

Leadership field notes: questions, decisions and follow-through

Leadership in development is visible in the questions a team can raise and the decisions it can trace. A field note can capture that work without becoming a diary, a motivational speech or an invented story about personal achievement.

Partnerships & leadership

Development decisions and the people they affect

A development decision changes conditions for people beyond the ownership group. Residents, neighbors, workers and service providers experience effects that may not appear in the first financial model. Those effects deserve specific questions rather than a broad claim that every project benefits its community.

Search